That's great to hear and fantastic progress. ![=D>]( "Applause")
It's strange that the correct geometry is not being written. I know FServInit is targeted very specifically at the RODIME drives as you've found out. Firstly the copyright pages that everyone knows about (&31 being non-zero will bypass that) in the firmware. However, FServInit also checks the data returned from Inquiry for the vendor/product information. This was to distinguish between the RO652 and RO3000 series, the latter making use of large block transfers.
It should be fine as far as the E01S firmware goes, as I've had the emulator running with non-Rodime disks (hence my confidence that it *should* work)![;-)]( "Wink")
. Critical is the geometry in pages 3 & 4
I do have some logs of the SCSI commands sent by the firmware as it starts up. Frustratingly, I'm not home for another week. I also hacked the FServ dealer disk to work with a disc locally plugged into a Master via a 1MHz adapter if that's any use.
It's strange that the correct geometry is not being written. I know FServInit is targeted very specifically at the RODIME drives as you've found out. Firstly the copyright pages that everyone knows about (&31 being non-zero will bypass that) in the firmware. However, FServInit also checks the data returned from Inquiry for the vendor/product information. This was to distinguish between the RO652 and RO3000 series, the latter making use of large block transfers.It should be fine as far as the E01S firmware goes, as I've had the emulator running with non-Rodime disks (hence my confidence that it *should* work)
. Critical is the geometry in pages 3 & 4 I do have some logs of the SCSI commands sent by the firmware as it starts up. Frustratingly, I'm not home for another week. I also hacked the FServ dealer disk to work with a disc locally plugged into a Master via a 1MHz adapter if that's any use.
Statistics: Posted by markusher — Sat Jan 11, 2025 11:31 pm