Just implemented missing disk change support(Some eject refusal support as well as a missing mandatory command: MECHANISM STATUS command reporting disk change and insertion status, prevent/allow medium removal command having seperate flags from the normal locking used by the Microsoft feature(using bit 1 instead of bit 0 of the flag)). Mechanism status now reports one slot, containing the insertion status(mounted status of the CD-ROM, which takes the Dosbox handling into account, as well as a second medium changed flag for reporting(set when changing the mounted disk, cleared when reaching Dosbox-X's LOAD_DISK_READIED status)), but the MSCDEX(from MS-DOS 6.22 boot disk) driver(with VIDE-CDD.SYS) still doesn't detect medium change?

After messing a bit with the processing of the Sense Packets(being incorrectly filled and put in the error register(Sense code being invalid, as well as writing the contents to the wrong register)) and related code bugs, I've managed to make it see the disk changes correctly now(using the 10 second spinup and spindown, while insertion takes 4 seconds(fast user to switch that fast indeed! 🤣)).

There's still one odd thing going on: When the disk is reported as not present, for some odd reason the driver(VIDE-CDD.SYS/MSCDEX.EXE) seems to wait for about a minute(about 40-60 seconds) before even displaying the drive not ready error, which after telling it to (R)etry reads the new disk correctly? Anyone knows what the cause of that might be? I don't see it firing any other commands in the meanwhile, so complete radio silence from the software that's running? I don't see it emitting any ATAPI commands in that period until it says the drive isn't ready?