ZuluSCSI won't boot with Macintosh Plus

[WarriorRocker]

Howdy, hope this is simple!

I have a ZuluSCSI mini and can't seem to get it to do anything.

Trying various image files and zuluscsi.ini changes always results in the question floppy screen.

Booting from a floppy containing 6.0.8 and I don't see any additional drives show on the desktop.

Can someone share their working zuluscsi.ini and perhaps a few known good images?

I get the single LED flash at power up, indicating it has found and loaded an image. Log file below:

[0ms] Platform: ZuluSCSI mini v1.0
[0ms] FW Version: 1.2.0-release Dec 21 2022 18:20:53
[0ms] DIPSW3 is ON: Enabling SCSI termination
[7ms] SD card detected, FAT64 volume size: 122106 MB
[8ms] SD MID: 0x1B, OID: 0x53 0x4D
[8ms] SD Name: GD4QT
[8ms] SD Date: 12/2017
[8ms] SD Serial: 0x59EC5DAB
[12ms] Reading configuration from zuluscsi.ini
[12ms] Active configuration:
[24ms] -- SelectionDelay: 255
[1121ms] Finding HDD images in directory /:
[1123ms] -- Opening /HD6.hda for id:6 lun:0
[1124ms] ---- Image file is contiguous, SD card sectors 4014848 to 4080383
[1125ms] ---- Read prefetch enabled: 8192 bytes
[1185ms] SCSI ID:6 BlockSize:512 Type:0 Quirks:1 ImageSize:32768kB
[1692ms] SCSI PHY operating mode: PIO
[1692ms] Initialization complete!
[8217ms] DBG BUS RESET
[8217ms] DBG BUS RESET
[8462ms] DBG -- BUS_BUSY
[8462ms] DBG ---- SELECTION: 6
[8464ms] DBG ---- COMMAND: Read6
[8464ms] DBG ------ OUT: 0x08 0x00 0x00 0x00 0x01 0x00
[8465ms] DBG ------ Read 1x512 starting at 0
[8466ms] DBG ---- DATA_IN
[8501ms] DBG ---- Total IN: 512 OUT: 0 CHECKSUM: 1860
[8502ms] DBG ---- STATUS: 0 GOOD
[8506ms] DBG ---- MESSAGE_IN
[8506ms] DBG ------ IN: 0x00
[8506ms] DBG -- BUS_FREE
[8507ms] DBG -- BUS_BUSY
[8507ms] DBG -- BUS_FREE
[8508ms] DBG -- BUS_BUSY
[8508ms] DBG -- BUS_FREE
[8509ms] DBG -- BUS_BUSY
[8510ms] DBG -- BUS_FREE
[8511ms] DBG -- BUS_BUSY
[8511ms] DBG -- BUS_FREE
[8512ms] DBG -- BUS_BUSY
[8512ms] DBG -- BUS_FREE
[8690ms] DBG -- BUS_BUSY

[SCSI]
# Settings that apply to all devices
Debug = 1   # 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 1 # 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 = 0 # Enable faster speeds of SCSI2
#EnableSelLatch = 0 # For Philips P2000C and other devices that release SEL signal before BSY
#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 = "QUANTUM"
#Product = "FIREBALL1"
#Version = "1.0"
#Serial = "0123456789ABCDEF"
#Type = 0     # 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

# Settings can be overridden for individual devices.
#[SCSI2]
#Product = "Disk with ID2"

#[SCSI5]
#Product = "CD-ROM Drive"
#Type = 2
# If IMG0..IMG9 are specified, they are cycled after each CD eject command.
#IMG0 = FirstCD.iso
#IMG1 = SecondCD.iso

# Raw sector range from SD card can be passed through
# Format is RAW:first_sector:last_sector where sector numbers can be decimal or hex.
# If end sector is beyond end of SD card, it will be adjusted automatically.
# [SCSI4]
# IMG0 = RAW:0x00000000:0xFFFFFFFF # Whole SD card

 

[Phipli]

How are you powering it?

 

[WarriorRocker]

It's the ZuluSCSI Mini that only has the DB-25 connector. I am plugging it straight into the back of the Mac Plus.

 

[Phipli]

It's the ZuluSCSI Mini that only has the DB-25 connector. I am plugging it straight into the back of the Mac Plus.

The Plus doesn't provide termination power as standard, so unless you've modified your Plus, you'll need to power the board by USB.

 

[WarriorRocker]

Just tried by connecting the micro-usb power and the result is the same. The red LED blinks once at power up, and then blinks every second or so at the question mark screen.

Trying different images and sometimes there are no blinks at the question screen, but always the single blink at power up.

Do you have any links for modifying the Plus to provide proper termination power, or if that is even a generally good idea?

The fact it is generating the log and blinking the LED without being connected to micro-usb means it must be getting power from something?

 

[dochilli]

 

[Phipli]

That's not going to help if you can't use it even with USB power.

I recommend carefully following a tutorial for setting up the ZuluSCSI and using the exact disk image, called the same thing, as the guide says.

 

[avadondragon]

Try the download #8 MacPack_Silverlining image and see if it work for you. The plus is a little picky when it comes to the various SCSI emulators. People have found it to work best with the Silverlining 5.3.1 driver. That's the image I'm using on my PiSCSI. I remember there were some settings in firmware needed on the SCSI2SD to get it working right with a plus so that might effect the ZuluSCSI too.

 

[WarriorRocker]

Tried with the Siliverlining image and still no attempt to boot and booting from floppy there are no additional drives on the desktop.

Using the 6.0.8 Image as HD0.hda and the Silverlining as HD1.hda. No difference if only using HD0.hda or renaming HD0 to HD6.hda etc..

[0ms] Platform: ZuluSCSI mini v1.0
[0ms] FW Version: 1.2.0-release Dec 21 2022 18:20:53
[0ms] DIPSW3 is ON: Enabling SCSI termination
[10ms] SD card detected, FAT64 volume size: 122106 MB
[11ms] SD MID: 0x1B, OID: 0x53 0x4D
[11ms] SD Name: GD4QT
[11ms] SD Date: 12/2017
[11ms] SD Serial: 0x59EC5DAB
[15ms] Reading configuration from zuluscsi.ini
[15ms] Active configuration:
[28ms] -- SelectionDelay: 255
[1178ms] Finding HDD images in directory /:
[1179ms] -- Opening /HD1.hda for id:1 lun:0
[1180ms] ---- Image file is contiguous, SD card sectors 4593408 to 8787465
[1180ms] ---- Read prefetch enabled: 8192 bytes
[1181ms] -- Opening /HD0.hda for id:0 lun:0
[1183ms] ---- Image file is contiguous, SD card sectors 4014848 to 4080383
[1183ms] ---- Read prefetch enabled: 8192 bytes
[1245ms] SCSI ID:0 BlockSize:512 Type:0 Quirks:1 ImageSize:32768kB
[1245ms] SCSI ID:1 BlockSize:512 Type:0 Quirks:1 ImageSize:2097029kB
[1752ms] SCSI PHY operating mode: PIO
[1752ms] Initialization complete!
[8145ms] DBG BUS RESET
[8145ms] DBG BUS RESET
[8390ms] DBG -- BUS_BUSY
[8391ms] DBG -- BUS_FREE
[8392ms] DBG -- BUS_BUSY
[8392ms] DBG -- BUS_FREE
[8393ms] DBG -- BUS_BUSY
[8393ms] DBG -- BUS_FREE
[8394ms] DBG -- BUS_BUSY
[8395ms] DBG -- BUS_FREE
[8395ms] DBG -- BUS_BUSY
[8396ms] DBG -- BUS_FREE
[8397ms] DBG -- BUS_BUSY
[8397ms] DBG ---- SELECTION: 1
[8399ms] DBG ---- COMMAND: Read6
[8399ms] DBG ------ OUT: 0x08 0x00 0x00 0x00 0x01 0x00
[8400ms] DBG ------ Read 1x512 starting at 0
[8401ms] DBG ---- DATA_IN
[8436ms] DBG ---- Total IN: 512 OUT: 0 CHECKSUM: 27859
[8437ms] DBG ---- STATUS: 0 GOOD
[8441ms] DBG ---- MESSAGE_IN
[8441ms] DBG ------ IN: 0x00
[8442ms] DBG -- BUS_FREE
[8442ms] DBG -- BUS_BUSY
[8443ms] DBG ---- SELECTION: 0
[23444ms] WATCHDOG TIMEOUT at PC 0x0801121C LR 0x08011835 attempting bus reset
[23444ms] DBG ---- COMMAND: TestUnitReady
[23445ms] DBG ------ OUT: 0x00 0x00 0x00 0x00 0x01 0x00
[23452ms] DBG -- BUS_FREE
[28760ms] DBG -- BUS_BUSY
[28760ms] DBG -- BUS_FREE
[28786ms] DBG -- BUS_BUSY
[28786ms] DBG -- BUS_FREE
[28811ms] DBG -- BUS_BUSY
[28812ms] DBG -- BUS_FREE
[28837ms] DBG -- BUS_BUSY
[28837ms] DBG -- BUS_FREE
[28863ms] DBG -- BUS_BUSY
[28863ms] DBG -- BUS_FREE
[28888ms] DBG -- BUS_BUSY
[28889ms] DBG ---- SELECTION: 1
[28892ms] DBG ---- COMMAND: RezeroUnit
[28892ms] DBG ------ OUT: 0x01 0x01 0x01 0x01 0x01 0x01
[28893ms] DBG ---- STATUS: 0 GOOD

 

[avadondragon]

Ah! I think I found the magic settings. Hopefully...

Try adding:

[SCSI]
EnableSelLatch=1
SelectionDelay=0

Oh what size SD card are you using? There might be an issue with smaller SD cards on ZuluSCSI. Smaller than 8GB can be hit or miss.
Edit: nevermind I just looked for that info in your log.

 

[jmacz]

+1 to what @avadondragon said. I had strange issues with 2GB and 4GB cards. It's not the size that matters but the age. The older cards didn't implement to spec properly and causes the ZuluSCSI to have issues. Just so happens that the cards from that time period are smaller than 8GB. I don't have a Plus to test but when I was using 2GB/4GB, I ran into lots of boot issues. Moving to a 32GB fixed it for me.

Nevermind... just saw @avadondragon 's nevermind as well looks like your logs show you're using a larger card.

 

[Jockelill]

You need special settings for the plus, the scsi implementation is very quirky, mine struggled as well, but @rabitholecomputing helped me out. If it’s already not solved, I can share you my settings when I’m home tomorrow.

 

[Paralel]

Which ROM one has in their Plus will determine its SCSI behavior, won't it? With each ROM revision there were changes to the SCSI behavior, with only ROM 3 having what would be considered a "standard" SCSI implementation. Plus ROM revisions 1 and 2 are known for having SCSI bugs. ROM 3 was specifically made to solve a particular SCSI bug in ROM 2, if I remember correctly.

 

[mg.man]

ROM 3 was specifically made to solve a particular SCSI bug in ROM 2, if I remember correctly.

Interesting, I wasn't aware of that. I found this - which does highlight a SCSI-related change...
- https://www.tech-insider.org/mac/research/acrobat/8803-f.pdf

 

[mg.man]

I've also just read it properly... of note:

- [2nd Version] This version is the vast majority of beige Macintosh Pluses.

- Bo3bdar Saith Also:
. . .
Not possible to get a specific ROM since they are all the same part number.

Are all 3 versions out there on the Interweb?

 

[WarriorRocker]

Thanks for all the tips, I was able to get this booting but the results seem a bit unstable.

I now have the following settings in my zuluscsi.ini, `EnableSelLatch` seemed to have no real effect.

[SCSI]
Debug = 1   # Same effect as DIPSW2, enables verbose log messages
SelectionDelay = 0   # Millisecond delay after selection, 255 = automatic, 0 = no delay
Quirks = 1 # 0: Standard, 1: Apple, 2: OMTI, 4: Xebec, 8: VMS
EnableSCSI2 = 0 # Enable faster speeds of SCSI2

Out of all of the images I have downloaded only 2 seem to ever work. I also have switched to a smaller 64GB SD card, results seem to be about the same or slightly more stable. Renaming the images between .img or .hda etc seems to have no effect.

None of the Drive images from https://www.savagetaylor.com/downloads/downloads-macintosh/ seem to work at all.

I have had some success with the Silverlining and and 6.0.8 Boot images from https://macintoshgarden.org/apps/rascsi-reloaded

The Siliverlining disk is quite large and restarting the macintosh often results in the question mark screen, not sure what gets corrupted.

The 6.0.8 disk is smaller and seems to be more stable, though I hesitate to start making changes and cause the disk to be unreadable.

Still though, it just seems like there are better settings to be had for the zuluscsi.ini, even the `Quirks` setting seems to have little effect. The `SelectionDelay` seems to have had the greatest effect.

Also I read something about, scsi drivers, being in the first sectors of the disk image. Is this why some images don't work at all? I'm fairly technical but unaccustomed to some of the oddities of these little machines.

 

[Phipli]

Also I read something about, scsi drivers, being in the first sectors of the disk image. Is this why some images don't work at all? I'm fairly technical but unaccustomed to some of the oddities of these little machines.

Some images are just images of a partition, so don't include the full disk with the driver etc. The computer sees them basically as unformatted.

You also can't use more than a 2GB partition on a Plus, so your image must be 2GB or less.

 

[aperezbios]

Howdy, hope this is simple!

I have a ZuluSCSI mini and can't seem to get it to do anything.

Trying various image files and zuluscsi.ini changes always results in the question floppy screen.

[0ms] Platform: ZuluSCSI mini v1.0
[0ms] FW Version: 1.2.0-release Dec 21 2022 18:20:53
[0ms] DIPSW3 is ON: Enabling SCSI termination
[7ms] SD card detected, FAT64 volume size: 122106 MB
[8ms] SD MID: 0x1B, OID: 0x53 0x4D
[8ms] SD Name: GD4QT
[8ms] SD Date: 12/2017
[8ms] SD Serial: 0x59EC5DAB
[12ms] Reading configuration from zuluscsi.ini
[12ms] Active configuration:
[24ms] -- SelectionDelay: 255

Hi @WarriorRocker, did you ever get this sorted? It looks like you don't have SelectionDelay=0 set. I just confirmed on my Mac Plus that it must be set before it will boot. You also need to have EnableSelLatch set to 1:

[SCSI]
EnableSCSI2=0
EnableSelLatch=1
SelectionDelay=0