• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Announcing ZuluSCSI - A file-based SCSI device emulator

aperezbios

Well-known member
@Brooklyn It sounds like one or more of your ZuluSCSI boards may be operating in "raw passthrough" mode. If that's the case, the LED on the ZuluSCSI will blink three times upon initialization (to indicate it didn't find a valid image file OR filesystem).

Currently, the only way to change the SCSI ID on a board that's using raw passthrough mode is at compile time. You could, however, create an image of the existing SD card, using something like win32diskimager, or, any other raw disk read utility, and then name that file HDn.xyz, where N is the SCSI ID you desire.
 

Brooklyn

Well-known member
@Brooklyn It sounds like one or more of your ZuluSCSI boards may be operating in "raw passthrough" mode. If that's the case, the LED on the ZuluSCSI will blink three times upon initialization (to indicate it didn't find a valid image file OR filesystem).

Currently, the only way to change the SCSI ID on a board that's using raw passthrough mode is at compile time. You could, however, create an image of the existing SD card, using something like win32diskimager, or, any other raw disk read utility, and then name that file HDn.xyz, where N is the SCSI ID you desire.
Thanks, I was able to get everything to work by formatting the SD cards exFAT with MBR partition table. Then using a blank image file from Blue SCSI. All good now, just thought if I initialized on the Macintosh it would auto create the image files but it doesn’t work that way.
 
Top