We get the same correct reply when reading the disc user code from VFS or ADFS, as a final example that this bug is now fixed.
Click here to return to VFS Utils 2.2
