NT4: Medium change not detected after loading a new CD image by eject signal

[elosha]

Hey there, I'm using the BlueSCSI v2 with a DEC Personal Workstation 433au (an Alpha machine). The computer runs Windows NT 4.0 for AXP. I've enabled 512byte sectors for the drive, just like the original CD-ROM drive.

The BlueSCSI works great as always, but when assigning multiple ISO images to one virtual CD drive, and send an eject signal …

• Explorer does not automatically detect a media change
• For example, the disc label stays the old one and AutoRun doesn't trigger
• In fact the medium has changed, and I can access the new contents once I open the emulated drive with Explorer
• Disk Management tool however reflects the media change correctly

How can I fix this? More delay, a missing media change signal? This may actually be a NT problem ;)

[erichelgeson]

Could you provide a debug log doing this action? The next request after medium change should respond back with a check condition medium change then re-insert the next CD - which is the way most OS's do this, but who knows about NT :)

You might also try this setting https://github.com/BlueSCSI/BlueSCSI-v2/wiki/bluescsi.ini#reinsertcdoninquiry

[elosha]

Hi @erichelgeson, I got to access the machine again.

The log looks as follows:

Platform: BlueSCSI
FW Version: 2024.10.26-rel Oct 26 2024 22:02:38
I2C Supported
Flash chip size: 2048 kB
 
=== SD Card Info ===
SD card detected, FAT32 volume size: 30424 MB
SD Name: SD32G, MID: 0x03, OID: 0x53 0x44
 
=== Global Config ===
Reading configuration from bluescsi.ini
Active configuration (using system preset "Generic"):
-- SCSI ID: 6 using Optical image directory 'CD6'
-- Opening 'CD6/AG-Q2CNA-RK.iso' for ID: 6
 
=== Finding images in / ===

=== ROM Drive ===
Platform supports ROM drive up to 1692 kB
---- ROM drive image not detected

=== Configured SCSI Devices ===
* ID: 6, BlockSize: 512, Type: Optical, Quirks: VMS, Size: 188364kB
 
Initialization complete!
INFO: Pico Voltage: 3.207V.
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
SCSI ID 6 negotiated asynchronous mode (period 4x0 ns, offset 0 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
SCSI ID 6 negotiated asynchronous mode (period 4x0 ns, offset 0 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
Switching to next image for ID: 6: CD6/msexcel_8.0.alpha_en-us.iso
SCSI ID 6 negotiated asynchronous mode (period 4x0 ns, offset 0 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
Switching to next image for ID: 6: CD6/msword_8.0.alpha_en-us.iso
---- WARNING: file CD6/msword_8.0.alpha_en-us.iso is fragmented, see https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Image-File-Fragmentation
SCSI ID 6 negotiated asynchronous mode (period 4x0 ns, offset 0 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
Switching to next image for ID: 6: CD6/VCPP-4.00-RISC-Alpha.iso
SCSI ID 6 negotiated asynchronous mode (period 4x0 ns, offset 0 bytes)
SCSI ID 6 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)

The option reinsertcdoninquiry didn't do the trick.

[erichelgeson]

Can you try two things for me?

• Update to the latest firmware
• Get me a debug log when switching

I need to see what the OS is asking about on the SCSI bus to dig in further.