• 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.

ZuluSCSI & MacIIsi


Dear all in 68kMLA !

I recently bought 2 ZuluSCSI boards to replace my defective Scuzzy WS Drive.

The installation on my MacIIsi (equipped with 64MB RAM and a DayStar Turbo 040)
running system 7.6.1 was successful. I supplied the ZuluSCSI board with extenal
an 5V DC power supply and used passive SCSI termination (SW1 all to OFF).

I used the following ZuluSCSI.ini file

# Settings that apply to all SCSI ids

# Select a system preset to apply default settings
# Known systems: "Mac", "MacPlus"

#Debug = 0 # Same effect as DIPSW2, enables verbose log messages
#SelectionDelay = 255 # Millisecond delay after selection, 255 = automatic, 0 = no delay
#PhyMode = 0 # 0: Best available 1: PIO 2: DMA_TIMER 3: GREENPAK_PIO 4: GREENPAK_DMA
#Dir = "/" # Optionally look for image files in subdirectory
#Dir2 = "/images" # Multiple directories can be specified Dir1...Dir9
#DisableStatusLED 0 # 0: Use status LED, 1: Disable status LED

# Settings that can be needed for compatibility with some hosts
#Quirks = 1 # 0: Standard, 1: Apple, 2: OMTI, 4: Xebec, 8: VMS
#EnableUnitAttention = 0 # Post UNIT_ATTENTION status on power-on or SD card hotplug
#EnableSCSI2 = 1 # Enable faster speeds of SCSI2
#EnableSelLatch = 0 # For Philips P2000C and other devices that release SEL signal before BSY
#EnableParity = 1 # Enable parity checks on platforms that support it (RP2040)
#MapLunsToIDs = 0 # For Philips P2000C simulate multiple LUNs
#MaxSyncSpeed = 10 # Set to 5 or 10 to enable synchronous SCSI mode, 0 to disable

# ROM settings
#DisableROMDrive = 1 # Disable the ROM drive if it has been loaded to flash
#ROMDriveSCSIID = 7 # Override ROM drive's SCSI ID

# Settings that can be specified either per-device or for all devices.
#Vendor = "SyQuest"
#Product = "SQ5110c"
#Version = "1.0"
#Serial = "0123456789ABCDEF"
#Type = 1 # 0: Fixed, 1: Removable, 2: Optical, 3: Floppy, 4: Mag-optical, 5: Tape
#TypeModifier = 0 # Affects only INQUIRY response
#SectorsPerTrack = 63
#HeadsPerCylinder = 255
#RightAlignStrings = 0 # Right-align SCSI vendor / product strings, defaults on if Quirks = 1
#PrefetchBytes = 8192 # Maximum number of bytes to prefetch after a read request, 0 to disable
#ReinsertCDOnInquiry = 1 # Reinsert any ejected CD-ROM image on Inquiry command

Additonally I wrote an empty file HD2.hda on the SD card (Samsung 4GB SDHC).

Refer to the installation reports provided as PDF file.


- SCSIProbe 4.3 detects ZuluSCSI always with SCSI ID1 independent of the file HD2.hda

- After formating and initialisation of the SD card using d2 DriverTM 4.5.4 the
SD card when inserting into a WinPC USB card reader is indicated as "non formated".

- Installation of a SD card as fixed "disk" was successful.
( changes in ZuluSCSI.ini
# Settings that can be specified either per-device or for all devices.
#Vendor = "Rabbit Hole Computing"
#Product = "ZuluSCSI"
#Version = "2022d"
#Serial = "0123456789ABCDEF"
#Type = 0 # 0: Fixed,

The volume named SD-Card3 can be moved to the trash basked.
This seems to be dangerous. The volume "Harddisk" cannot be moved.

- When inserting a SD card containing the files ZuluSCSI.ini and HD2.hda the Mac issues
the message "The format of the volume cannot be read. Want you initialise the volume now?"
Then I choosed to use "DOS 3,6GB" instead "Macintosh 3,6" format.
The Mac issues the error message "Volume cannot be erased because error during initialisation".

Who can help to overcome the problems?

How a SD card can be initialised to be readable by MacOS and DOS/Windows ?


  • Installation ZuluSCSI WinPC.pdf
    143.3 KB · Views: 7
  • Installation ZuluSCSI Mac.pdf
    68.3 KB · Views: 9


Vendor The First
@RV066 Your ZuluSCSI board is entering raw fallback mode. When it does this, the SCSI ID is hard-coded to ID1. If you observe the activity LED on your ZuluSCSI, you'll see it blink three times, which indicates it did not find any valid images on the SD card. In order for the ZuluSCSI firmware to find image files, your SD card must be formatted with FAT32 or exFAT filesystem. Start by re-formatting your SD card with the SD card assocation formatter, which is available for Windows and macOS, from https://www.sdcard.org/downloads/formatter/

Also, there's no need for any ZuluSCSI config file, in most scenarios. Any line that begins with a # is a comment, and will not be processed by the ini ini config file parser in the ZuluSCSI firmware.


The proposed SD card formatter of the SD card assocation can be
run under Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 11
Mac OS X 10.7, Mac OS X 10.8, Mac OS X 10.9, Mac OS X 10.10,
Mac OS X 10.11, macOS 10.12, macOS 10.13, macOS 10.14, macOS 10.15,
macOS 11 and macOS 12 .

WindowsXP and Mac OS 7.6.1 aren't supported.

So I cannot use this proposed formatter SW on my PC running WindowsXP
and on my vintage Macintosh MacIIsi running Mac OS 7.6.1 .

But I tried the test version of TransMac
Using this test version I had been capable to open the HFS Mac Volume
on a SD card and moving some files (PDF, MS-Word and Mac SimpleText)
from this volume to the Windows PC.

Regards RV066


Well-known member
I was able to format an SD card for multiple HFS partitions using a Raspberry PI, HFSUtils and a small tool I wrote in C (ApmTool):