• 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

JT737

Well-known member
Correction: I meant to add that after programing the SCSI2SD with the utility, it then works on pretty much any SCSI-based Mac with little to no issues. Like most folks here, I've found the SCSI2SD drives to be game-changers with classic Macs.
 

aperezbios

Well-known member
The problem here is that ZuluSCSI _is not a SCSI2SD device_, nor is it advertised as such. I strongly recommend you read the manual linked above, and email us with any specific questions you may have, after doing so.
 

Hunter259

Active member
I just got a ZuluSCSI Mini in for my Mac Plus but I can't get it to not crash the machine. Both RaSCSI and BlueSCSI images cause the machine to hard reboot. I've tried several settings to no avail. The machine boots off an old SCSI hard drive and loads the entire 4MB of ram without crashing. Blank images don't crash the machine but don't show in OS which is correct I believe.
 

frankz

Member
I just got a ZuluSCSI Mini in for my Mac Plus but I can't get it to not crash the machine. Both RaSCSI and BlueSCSI images cause the machine to hard reboot. I've tried several settings to no avail. The machine boots off an old SCSI hard drive and loads the entire 4MB of ram without crashing. Blank images don't crash the machine but don't show in OS which is correct I believe.
Can you try with the 6.0.8 image that you can download from https://www.savagetaylor.com/wp-content/uploads/68k_Macintosh/Bootdisks/608_2GB_drive.zip ?
On my Mac Plus, it boots to the Finder, but then the Mac bombs as I try to do almost anything (like just getting “Info about Macintosh” from the Apple menu).
 

Powerbase

Well-known member
Exact same. About info, immediate illegal instruction. Other apps cause infinite loop system errors.
Happens on my 8500 I was using to set it up, when it actually worked with the sd card I used. It didnt like the 32GB sd card I first used and would sad Mac my 475. The 8500 would start but bomb as soon as it started loading up.

You could try different SD cards?
 

dankcomputing

Active member
Bought one and installed it on an Amiga - it was a 2000 with a GVP A2000HC+8 controller. Worked pretty good!

I made a 3.9GB disk image for use on a 4GB card and it was a bit of trial and error to generate a blank image that made sense because I forgot that disk geometry calculators were a thing.

I'll grab another one to try in a Mac.
 
Very strange. I installed the zulu board (default dip swiches untouched) in my Mac se/3 (after copying a correctly named and suffixed .hda file) and it worked perfectly... once! Since then, everytime I start my machine (rominator), it doesn't see zulu (with our without an external scsi2sd plugged in, with or without termination dip switch on or off). There is no conflict with scscsi ID's. zulu is 1, others are 3 and 4. What can I do? Do I have to copy the .init fil on zulu card? I already updated the firmware with ZuluSCSIv1_0_2022-05-17-v1.0.2.bin
Do I have to set the dip switch SW1 on ON or OFF?
 
Very strange. I installed the zulu board (default dip swiches untouched) in my Mac se/3 (after copying a correctly named and suffixed .hda file) and it worked perfectly... once! Since then, everytime I start my machine (rominator), it doesn't see zulu (with our without an external scsi2sd plugged in, with or without termination dip switch on or off). There is no conflict with scscsi ID's. zulu is 1, others are 3 and 4. What can I do? Do I have to copy the .init fil on zulu card? I already updated the firmware with ZuluSCSIv1_0_2022-05-17-v1.0.2.bin
Do I have to set the dip switch SW1 on ON or OFF?
No txt error log in any case. Also, if I switch termination ON on the zulu and have nothing plugged in the SCSI port of the MAC, the zulu blinks in 5 flash sequence as for "SD card not detected" and an SCSI probe (via rominator) indicates "Bus not terminated". I am very puzzled and disappointed. Otherwise BlueSCSI and SCSI2SD work perfectly.
 

rabbitholecomputing

Vendor The First
Please engage with us via e-mail, and _fully_ describe the problem, including which SD card you're using, etc. If you aren't seeing a log, it's because the ZuluSCSI isn't writing one, which almost certainly means it can't find an SD card. Please ensure you're using an SD card that's an SDHC-labeled card. Why are you disappointed, exactly? This thread is not a support forum for every ZuluSCSI customer.
 
Hello, please apologize my 2 previous posts. First of all, english is not my mother tongue. I may have expressed myself the wrong way and have no hard feelings at all. Also, thank you so much for your e-mail. We will discuss this privately and I'm convinced we'll find a good solution. Again, sorry for any inconvenience. Your product worked perfectly the first time I used it. I may have done a mistake when reformatting the card.
 
Many thanks and kudos to the Rabbit Hole Computing people for assisting me. ZuluSCSI now works perfectly and my SE30 is happier than ever! :)
 

dvincent

Member
How do I use dfu-util Linux command manually update ZuluSCSI firmware?
It is NOT updating by putting most recent zuluscsi.bin file in root of SD card.
 

dvincent

Member
I have ZuluSCSI v1.1 and most recent firmware.bin file.
Do I simply use this command:
$
dfu-util -a 0 -s 0x08004000:leave -D /path/to/image.bin

?
 

rabbitholecomputing

Vendor The First
I have ZuluSCSI v1.1 and most recent firmware.bin file.
Do I simply use this command:
$
dfu-util -a 0 -s 0x08004000:leave -D /path/to/image.bin

?
Not sure where you got that (incorrect) memory address from.. The correct syntax/address is:

dfu-util -a 0 --dfuse-address 0x08000000 -D firmware.bin
 

dvincent

Member
Still can't get the ZuluSCSI to flash updates from SD card root.
It was suggested I rename firmware .bin file:
AzulSCSI.bin
but that did nothing.
 
Top