Rabbit Hole Computing - User contributions [en]

ZuluIDE Operations Guide

2024-11-11T18:15:34Z

Wikiadmin: Compress list of file name extensions that are ignored, more so it's more readily printable and succinct.

== Setting Up Your ZuluIDE ==

=== Unboxing ===
When you first receive your ZuluIDE, depending on the options you ordered, you should receive the following:

* ZuluIDE RP2040 Compact board
* 3D-printed plastic carrier
* 2x ¼" 4-40 screws
* microSD card
* Hardware interface board (optional)
* Qwiic cable (included with hardware interface board)
* DAC board with mounted Raspberry Pi Pico W (optional)

== Board Overview ==
Take a moment to identify the various parts of the board as shown below.
[[File:ZuluIDE RP2040 Compact (labeled).png|center|frameless|800x800px]]

* '''4-pin Molex floppy power connector:''' Run a standard Molex 4-pin power cable to this port. If your system power supply has only the larger style, get an adapter cable to switch it to the smaller size (the same size as that found on a 3½" floppy disk drive).
* '''40-pin male IDC connector:''' Plug your IDE bus cable into this. The connector is keyed, but some IDE cables lack the key, so make sure that the red stripe on the cable lines up with the little arrow embossed into the connector itself.
* '''Configuration DIP switches:''' These will set how the ZuluIDE responds when the BIOS requests information from the device.
* '''Bootloader button:''' Used during the firmware update process.
* '''I2C Footprint:''' Addon boards can attach through this open footprint either by being soldered directly to it or by attaching standard 0.1" header to this footprint.
* '''Qwiic Port:''' Addon boards can also attach here through the use of a standard Qwiic I2C cable.
* '''MicroUSB Port:''' Used during the firmware update process. Can also be used as a serial monitor to capture debug logs in real time with a second PC.
* '''microSD Card Slot:''' Your SD card with images goes here.
* '''Activity LED:''' Flashes in sync with drive access, also used to indicate status conditions as described later
* '''Eject button:''' Performs a hardware eject for optical drives. Some operating systems will need this after dismounting an image from the system to register that the drive door is closed.
* '''External eject and LED headers:''' If you intend to mount the device internally, but want external access to these, you can use standard 0.1" headers to run an eject button and an LED to a case panel. The red box on the image above indicates the positive pin.

== Molex power connector ==
Make sure that your power connection uses a '''3½" floppy power connector,''' not the larger drive connector used on full-size optical drives, hard drives, and the like.
{| class="wikitable" style="margin: auto;"
![[File:Molex 3.5" power connector.png|frameless|135x135px]]
![[File:Molex 3.5" power connector (top).png|frameless|100x100px]]
![[File:Molex 5.25" power connector.png|frameless|117x117px]]
![[File:Molex 5.25" power connector (top).png|frameless|100x100px]]
|-
| colspan="2" |✅ 3½" connector
| colspan="2" |❌ 5¼" connector
|}
If your host system only has the 5¼" connectors, you'll need to either purchase or make an adapter cable. Making an adapter cable requires the following parts:

* '''4× 5¼ male pins:''' TE Connectivity P/N 60620-1
* '''1× 5¼ male housing:''' TE Connectivity P/N 1-480426-0
* '''4× 3½ female sockets:''' TE Connectivity P/N 170262-1
* '''1× 3½ female housing:''' TE Connectivity P/N 171822-4

When making the cables, use 20-gauge wire. If you're crimping a splitter cable, it's also possible to use 18-gauge wire on the 5¼ side going to the female plug, and then crimp the larger wire going into the male splitter side together with 22 or 24-gauge wire going to the 3½ side. Crimping the cables can be done with standard tools found on Amazon, such as the IWISS SN-025.

== DIP Switch Configuration ==
[[File:DIP switches (ZuluIDE).png|center|frameless]]
Set the three DIP switches according to how the device needs to be configured in the host system.

* '''Switch 1:''' Turn IDE Cable Select on or off. ''Most'' systems will work fine with this off, but there are several systems (especially single-board industrial computers) which will use cable-select to determine primary and secondary drives and thus will need it on. If your system hangs during IDE device detection with the ZuluIDE attached to the bus, try turning this switch ON first.
* '''Switch 2:''' Respond as Primary/Master (OFF) or Secondary/Slave (ON).
* '''Switch 3:''' Debug log disable/enable. If this switch is ON, the device will automatically write out a detailed debug log to <code>zululog.txt</code> on the SD card as long as the device is powered on. Additionally, if you have a USB cable plugged into the MicroUSB port on the device with this switch on, it will also print the debug log over the cable via the RP2040's internal serial connection.

== Qwiic Port and External Hardware Interface ==
The external hardware interface (optional) can be connected to this port. The interface provides a Gotek-like system to navigate disc images stored on the SD card and to cycle through them.
{| class="wikitable" style="margin: auto;"
|+
![[File:Hardware interface (rev 2024a).png|frameless|379x379px]]
![[File:Qwiic cable.png|frameless|338x338px]]
|}
The rotary encoder knob on the hardware interface functions exactly like a Gotek device — spin the knob to change images or menu selections, press the knob to select. The Eject button works exactly like the eject button on the main board, although with the hardware interface attached, it will ask you to confirm the eject by pressing the rotary knob. The User button is currently reserved for future use.

== Activity LED ==
The Activity LED will flash normally during disk access, however, in certain specific failure modes or status changes, you will see it flashing with a pattern.

* '''1 fast blink, at boot time:''' Image file loaded successfully
* '''3 fast blinks:''' No valid images found on SD card
* '''5 fast blinks:''' SD card is present, but is not being detected
* '''Morse code pattern:''' Firmware crash. The particular pattern will indicate where the crash occurred.

If a firmware crash occurs, it will also try to save information to the file <code>zuluerr.txt</code> on the SD card.

== SD Card Preparation and Use ==
Format your SD card with either the FAT32 or exFAT filesystems. If you intend to use images larger than 4 GB in size, you ''must'' format the card using exFAT as the FAT32 filesystem cannot support individual files larger than 4 GB.

Load your images onto the card into the root folder. Images stored in folders, unless they are <code>BIN/CUE</code> images, will be ignored.

For <code>BIN/CUE</code> files, they can be placed into a folder with the same name as the image file; i.e., if you have a <code>BIN/CUE</code> pair named <code>bigdiscofstuff.bin</code> and <code>bigdiscofstuff.cue</code> you should place them in a directory named <code>bigdiscofstuff</code>. This is '''required''' if your <code>BIN/CUE</code> image has a single <code>CUE</code> file and multiple <code>BIN</code> files.

=== Drive Types ===
When configuring the ZuluIDE, you can set it to be multiple different drive types based on the images you intend to use. Out of the box, the ZuluIDE configures itself as an optical drive, but through the [[ZuluIDE INI Configuration|INI file]] or by using '''filename prefixes,''' you can tell the ZuluIDE which device you want it to behave as when you power it on.

==== Using the INI File ====
Under the <code>[IDE]</code> heading, use the <code>Device=</code> value to set the drive type:0

* <code>CDROM</code> (default) will cause the ZuluIDE to respond as an optical drive.
* <code>Zip100</code> will cause the ZuluIDE to respond as an ATAPI-attached 100MB Zip Drive
* <code>Zip250</code> will cause the ZuluIDE to respond as an ATAPI-attached 250MB Zip Drive
* <code>Removable</code> will cause the ZuluIDE to respond as a generic removable media device
* <code>HDD</code> will cause the ZuluIDE to respond as a standard hard disk drive

If this section is absent, or the <code>zuluide.ini</code> file is not present on the SD card, the device will default to behaving as an optical drive.

==== Using a filename prefix ====
Add the following to the beginning of your filename to switch the ZuluIDE's device mode:

* <code>cdrm</code> will cause the ZuluIDE to load the image as an optical drive image.
* <code>zipd</code> will cause the ZuluIDE to load the image as a 100MB or 250MB Zip disk.
* <code>remv</code> will cause the ZuluIDE to load the image as a generic removable media device.
* <code>hddr</code> will cause the ZuluIDE to load the image as a non-removable hard disk image.

The <code>Device=</code> option in the INI file will override this behavior. Additionally, if a filename prefix is specified, all other files that you want to use '''must have the same prefix.'''

==== Filename extensions ====
In optical drive mode, the device will only recognize images that end in <code>.iso</code> or <code>.bin/.cue</code>, while also recognizing folders for purposes of reading multipart <code>.bin/.cue</code> images.

For Zip drives or other removable media,ᚸso long as the filename doesn't contain one of the prefixes above, doesn't have an optical drive image extension (<code>.iso/.bin/.cue</code>), or one of the extensions on the ignored list below, it will load the file as a disk image and attempt to mount it.

If the ZuluIDE starts up as an optical drive, it will use the first image it finds on the SD card as an optical disc.

==== Changing disk images ====
Without the hardware interface or web interface, changing disk images is done by pressing the eject button on the device itself or by performing a hardware eject directly through the operating system. The firmware will cycle to the next available image on the SD card in alphabetical order.

==== Ignore list ====
Files with any of the following extensions will be ignored by the ZuluIDE and will not appear in the list of available images on the hardware or web interfaces, and will not be selected when a hardware eject is performed:

*<code>.cue</code> <code>.txt</code><code>.rtf</code><code>.md</code><code>.nfo</code><code>.pdf</code><code>.doc</code>

Compressed archive file formats:

* <code>.zip .7z .dmg .rar .tar .tgz .gz .bz2 .tbz2 .xz .zst .lzh .lha .lzo .lz4 .arj .hqx .cpt .s7z</code>

Additionally, any file that begins with <code>zulu</code> will be ignored.

==== USB Mass Storage ====
You can use the ZuluIDE as a passthrough to access the SD card directly by putting the option <code>enable_usb_mass_storage=1</code> in the <code>[IDE]</code> section of the [[ZuluIDE INI Configuration|INI file]]. In order to use this mode, the ZuluIDE must not currently be operating as an attached device through the IDE port on a host computer.

==== Hotplugging ====
The ZuluIDE supports removal and re-insertion of the SD card while the device is on and functioning. Until the device detects that a card has been inserted, you'll see the activity LED blink 5 times rapidly, pause, and then repeat until a card is reinserted. Once the card has been detected, the LED will blink once, turn off, and return to normal indication of disk access.

== Updating the Firmware ==
New firmware releases can be obtained by visiting the [https://github.com/ZuluIDE/ZuluIDE-firmware/releases Github page] for the project. The most recent firmware will be listed at the top with a green "Latest" badge. You can update the firmware two different ways.

==== Using the SD card ====
The ZuluIDE can update itself when it's initially powered on. You'll need to have access to the device so you can remove its SD card.

# Power down the system that the ZuluIDE is attached to and remove its SD card.
# Attach the SD card to the computer where you'll download the update.
# From the [https://github.com/ZuluIDE/ZuluIDE-firmware/releases Github page], download the latest firmware file with a '''.BIN''' extension.
# Copy the downloaded '''.BIN''' file to the root folder of the SD card and rename it as <code>ZuluIDE.bin</code>.
# Dismount the SD card from the computer, and reinsert the SD card into the ZuluIDE.
# Power the system back on. The ZuluIDE will automatically begin the firmware update process, which takes about one second. If the system has to boot to the ZuluIDE and its startup is particularly quick, you may need to reset the computer once to allow the firmware update process to complete on the ZuluIDE so it can become ready.
# When the firmware update process finishes, the ZuluIDE will delete the update file and continue on to normal operation.

==== Using the BOOTLDR button ====
[[File:Bootloader button.png|thumb|140x140px|BOOTLDR button]]
If you have physical access to the device and a way to plug the MicroUSB port into a host computer, this is the traditional way to update RP2040-based devices like the ZuluIDE.

# Power down the system the ZuluIDE is attached to, and if necessary, unplug it from its cabling.
# From the [https://github.com/ZuluIDE/ZuluIDE-firmware/releases Github page], download the latest firmware file with a '''.UF2''' extension.
# Attach a MicroUSB cable to the device you'll be uploading the firmware from.
# While holding down the BOOTLDR button on the ZuluIDE, attach the other end of the cable to the MicroUSB port on the ZuluIDE. [[File:Firmware-update.png|thumb|Copy the UF2 file to the device.]]
# A Windows Explorer window may appear with a drive called <code>RPi-RP2</code>. If it doesn't, open a Windows Explorer window and look for a drive with this name.
# Copy the '''.UF2''' file you downloaded to the root folder of the drive that appeared when you plugged in the ZuluIDE.
# The <code>RPi-RP2</code> window should close on its own once the copy completes. When the device disconnects on its own, the firmware update process is complete.
# Disconnect the USB cables and reattach the ZuluIDE to its host, if you removed it in step 1.

== Troubleshooting ==
Some simple things to check before you dive deeper:

* Make sure there are no primary/secondary conflicts on the IDE channel that the ZuluIDE is attached to.
* Make sure that the power connection to the device is secure and attached.
* Try toggling the Cable Select switch. Some BIOSes prefer the device to be one way or the other and there's often little rhyme or reason between even the exact same BIOS on the exact same build across two machines.

For more specific problems, keep reading.

The icon at the left of the problems listed tends to pertain to that particular operating system.

=== [[File:Msdos-icon.png|32x32px]][[File:Win31.png|32x32px]](as optical drive): The ZuluIDE doesn't seem to be recognized under MS-DOS. ===
If you have the ZuluIDE attached as an optical drive in a system that doesn't natively support the ATAPI protocol, you may have to install a third-party driver to allow DOS to see the drive. This was common for all systems based on 386 processors and earlier, most 486 systems, and some Pentium-based systems.

The simplest solution is to obtain a copy of the Microsoft Windows 98 startup disk, and copy the <code>OAKCDROM.SYS</code> and <code>MSCDEX.EXE</code> files from it to the root folder of your boot drive. Then, modify your <code>CONFIG.SYS</code> and <code>AUTOEXEC.BAT</code> files like this:

==== CONFIG.SYS ====
Add this line to the top of the file:

<code>DEVICE=C:\OAKCDROM.SYS /D:MSCD000</code>

==== AUTOEXEC.BAT ====
Add this line to the end of the file:

<code>C:\MSCDEX.EXE /D:MSCD000</code>

Reboot the system, and the drive should populate.

Keep in mind that the only DOS-based CD-ROM driver that has been tested to work with the ZuluIDE at present is the Oak Technology driver (<code>OAKCDROM.SYS</code>). Other generic drivers, such as the LG (GoldStar) or Adaptec drivers may work, but also may not.

=== [[File:Msdos-icon.png|32x32px]][[File:Win31.png|32x32px]](as optical drive): The system recognizes the first disc image loaded, but then acts like the drive isn't ready when I change images. ===
This is currently a known issue. There is a temporary workaround, however.

After changing images, try to access the drive. The system will pause for a long moment, and then you should see a message similar to this:

<code>CDR101: Not ready reading drive E: 
(A)bort, (R)etry, (F)ail?</code>

Press F to fail the check, and then if it drops back to a command prompt, try to access the drive again and it should present the image as normal.

=== [[File:Win9598.png|37x37px]][[File:Winxp.png|36x36px]] (as optical drive): Performing an "eject" command in Windows Explorer doesn't actually cycle to the next image. ===
This is currently a known issue. The workaround for this is to have either the web interface or hardware interface connected and swap images that way. Another workaround is to manually eject the SD card from the ZuluIDE, add a zero to the beginning of the desired disk image's name, and then reinsert the SD card. The ZuluIDE will then look for the first image it can load alphabetically, which should be the newly-renamed image.

Main Page

2024-10-23T01:13:44Z

Wikiadmin:

'''<big>ZuluSCSI Documentation</big>'''

[[Quick Start Guide]]

[[Basic Usage]]

[[Buyer's Guide]]

[[ZuluSCSI v1.2]]

ZuluSCSI v1.2

2024-10-15T02:45:08Z

Wikiadmin: 1 revision imported

[[File:Zuluscsi1.2.jpg|thumb|The ZuluSCSI v1.2 device.]]

== Device Overview ==
The ZuluSCSI v1.2 device is designed as a drop-in replacement for any legacy SCSI {{#tip-text: block device. | A block device is a catch-all term used to describe any device used for storage. This can include hard drives, optical drives, and removable-media drives, such as floppy disk drives.}} By default, the ZuluSCSI v1.2 presents the entire contents of the SD card to the host machine as a single SCSI device, with device type and SCSI ID set using a rotary switch and DIP switch combination.

==== Configuring the ZuluSCSI v1.2 ====
While the ZuluSCSI v1.2's configuration is very similar to the other devices in the family, there are a couple of differences to be aware of with this device.

===== Rotary Switch (device type) =====
The rotary switch on the right side of the device configures the type of device that the ZuluSCSI v1.2 presents itself to the system as. Positions 0 thru 6 are the most common settings. Each setting is:

* '''0:''' Standard hard drive
* '''1:''' CD-ROM or other optical media device (including DVD drives)
* '''2:''' Standard floppy disk devices
* '''3:''' Removable media devices like Zip drives
* '''4:''' Magneto-Optical (MO) drives, such as LS-120 SuperDisk drives, Floptical™ drives, or other similar devices
* '''5:''' ST32430N Seagate Hawk 2GB Hard Drive mode
* '''6:''' Tape Backup mode

===== DIP Switch (SCSI ID) =====
The SCSI ID switch on the right side of the board allows you to set which ID number on the SCSI bus that the device occupies. A device can occupy any of eight positions on a single chain. With all three switches in the OFF position, the device occupies ID 0, and with all three switches ON, the device occupies unit 7.

'''Note:''' Generally, the host device (the device the ZuluSCSI is plugged into) occupies ID 7; unless you've changed it manually in settings elsewhere, avoid using ID 7 for the ZuluSCSI as this will create bus conflicts.

Each switch will add 1, 2, or 4 to the SCSI ID the device occupies, and the legend on the silkscreen shows how this works.

===== Configuration DIP Switch =====
The configuration switch on the left side controls how the device itself operates both on the SCSI bus as well as allowing for some other hardware options. Each switch affects the device as follows:

* '''TERM switch:''' Turns on or off the termination resistor packs on the bus. If this device is either the only device on the bus (other than the host) or is at the end of the bus, turn this on to prevent signal reflections.
* '''DBG switch:''' Switching this on causes the ZuluSCSI to produce a debug log (saved as zuludebug.txt) in the root folder of the SD card. This can be used to provide additional information in the event that you have problems and need to open a support ticket.
* '''DISABLE-DIRECT/RAW switch:''' When off, the device looks for and loads disk image files on the SD card as described in the File Formats section. When on, the device mounts the entire contents of the card as a single block device and presents it to the system.
* '''QUIRKS switch:''' For earlier Macintosh-based systems, you will need to turn this switch on to allow the ZuluSCSI to work with the particular quirks of the early implementations of SCSI found on unpatched '''Apple SC HD Setup''' or '''Drive Setup''' formatting utilities present on classic Macs.

Quick Start Guide

2024-10-15T02:45:07Z

Wikiadmin: 1 revision imported

So: You just got your box from Rabbit Hole Computing, opened it up, and inside were some wrapped-up circuit boards and maybe some parts. Now what?

Well, let's get you up and running!

== SCSI Bus Devices ==

=== Step 1: Prep your SD card. ===
Load either your SD card or microSD card with a disk image. Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus. If you're using a hard drive image, name the image <code>HD0.img</code>, and if it's an optical drive image, name it <code>CD0.iso</code> or <code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in.

Plug the SD card into the slot on the ZuluSCSI board.

=== Step 2: Prep the ZuluSCSI board. ===
Depending on how the system is connected together, you may need to run DB25 cables, IDC-50 pin cables, or use an interposer to switch cable types. Once you've determined whether or not you need to do this, plug the appropriate cable into the ZuluSCSI. Your ZuluSCSI model may only incorporate one type of connection.

The DIP switch block (or jumpers, depending on your device) will need to be set depending on how your host system is configured. Here's the short version for each switch:

* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.
* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.
* '''INITIATOR (RP2040-based devices only):''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system.
* '''DIRECT/RAW (ZuluSCSI 1.2 only):''' Enables direct access mode; allows you to use an SD card itself as a block device.
* '''QUIRKS (ZuluSCSI 1.2 only):''' This switch needs to be enabled on certain early Macintosh systems using a slightly-broken implementation of the SCSI standard to be able to use the unpatched versions of Apple HD SC Setup or Drive Setup.

If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either by populating the 4-pin Molex floppy power connector on your board or attaching a USB cable to the port on the front of the board. Otherwise, you're almost ready to go.

If you are looking to mount your ZuluSCSI board internally, the four mounting holes on any full-size ZuluSCSI board are designed to line up with the bottom holes of any 2.5" hard drive footprint. Any standard 2.5"-to-3.5" mounting adapter can fit the mounting holes on a ZuluSCSI board using M3 screws.

If you want to have an external activity LED, you can populate footprint '''J304''' on the board with a standard 0.1" pin header and run a case LED to this header for that purpose. The cathode (negative) end of the LED is marked by a '''C''' on the board.

=== Step 3: Turn on your device! ===
Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI implementation and the device will mount images as described above, and you should see your device(s) populate in your system.

== IDE Devices ==

=== Step 1: Prep the SD card. ===
Load your microSD card with the disk images you're looking to use in the system. Make sure that their extensions match the device type that you're using. The ZuluIDE defaults to CD-ROM mode without configuration changes, so image names should end in either <code>.ISO</code> or <code>.BIN/.CUE</code> for this mode. All images you're using should be in the root folder of the SD card.

=== Step 2: Prep the ZuluIDE board. ===
Your ZuluIDE board comes set by default to occupy the master position on whichever IDE channel you choose to place it on. If you only have a slave slot available, make sure you move DIP switch 2 to ON to change it to the slave position.

If you're using a modified IDE cable that supports cable select mode or your system requires the use of cable select mode, turn DIP switch 1 on to enable cable select.

If you have the hardware interface, plug the Qwiic connector into either of the Qwiic sockets and set it nearby.

=== Step 3: Turn on your device! ===
Attach your device to the IDE bus, connect the 4-pin Molex floppy power connector with a cable coming off your power supply, make sure that the microSD card is plugged in, and go!

Main Page

2024-10-15T02:45:07Z

Wikiadmin: 1 revision imported

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Buyer's Guide

2024-10-15T02:45:07Z

Wikiadmin: 1 revision imported

You've decided to get one of the Zulu family of devices ― fabulous! We're glad that one of our products can be of use to you. But if you're not quite sure which one best fits your needs, here's some criteria that will hopefully help you pare the list of choices down.

=== Step 1: Determine the bus the device will be on. ===

==== '''The device is a SCSI drive (mechanical hard drive, optical drive, tape drives, some Zip/Jaz/Orb drives and MO drives)''' ====
You'll be using a ZuluSCSI. Go to step 2 below.

==== '''The device is an IDE drive (mechanical hard drive, optical drive, some Zip/Jaz/Orb drives, LS-120 drives)''' ====
You'll be using a '''[https://shop.rabbitholecomputing.com/products/zuluide-rp2040-compact ZuluIDE.]''' Continue to step 2 for mounting options. You can also go to the [[Quick Start Guide]], or if you want more detailed setup and configuration information, visit the [[ZuluIDE Configuration]] page.

=== Step 2: Determine what the installation environment is going to be. ===

====== I have a very old or very finicky device that seems to only like specific drives or media. ======
The best option here is the '''ZuluSCSI 6.4 or ZuluSCSI 1.2.''' The ZuluSCSI 6.4 and ZuluSCSI 1.2 are the most transparent devices out of all of the options and also default to direct read-and-write modes out of the box.

ZuluSCSI 6.4 is the fastest device in the lineup, and is software-configurable down to the device ID and manufacturer strings reported to the host computer, so if there are specific things that need to be set for your particular needs, this device is likely your best bet.

The ZuluSCSI 1.2, while not directly as configurable as the 6.4, is intended out of the box to act as a hard disk. It also features a rotary encoder to force the device to register itself as a particular type, should that be needed, and defaults to using the SD card itself as the media, rather than using disk image files.

If you're talking IDE devices, the next step is to take a look at the [[ZuluIDE INI Configuration]] page and see if there are any options there that can help you.

====== '''The device is going to be permanently mounted inside a host computer and I won't need to access it directly''' ======
Either the '''ZuluSCSI 6.4, ZuluSCSI 1.2, or ZuluSCSI RP2040''' are the best options here. Each of these devices mounts to a standard 2.5"-to-3.5" drive bay adapter, which in turn can be mounted inside a standard 3.5" hard drive bay enclosure.

As for the ZuluIDE, it ships with a mounting bracket that will allow you to mount it in a 2.5"-to-3.5" hard drive enclosure.

====== The device is going to be mounted inside a host computer but I need to access it semi-regularly ======
The '''ZuluSCSI RP2040 or ZuluSCSI RP2040 Compact''' are your best options here. While these devices can be mounted, they can also be left un-mounted (in the case of the Compact) or mounted externally (in the case of the full-size 2040).

For the ZuluIDE, this is the same as above, but you may want to consider adding on the optional hardware control interface and mounting it externally.

====== The device needs to be mounted externally because I'll need regular access to the SD card ======
The '''ZuluSCSI RP2040 Mini or ZuluSCSI Pico Slim''' are your best options here. Each of these devices uses a DB25 connector to access the SCSI bus, so it can easily be mounted externally to a system with an external DB25 SCSI connector. You can also use a ZuluSCSI RP2040, and add a DB25 connector to it and use an external enclosure if you choose.

For the ZuluIDE, the best option here is to physically mount the included bracket to the outside of the case and run the IDE cable and power cable from inside the case; for example, through an open expansion slot.

====== I have a laptop. ======
For laptops with an internal SCSI connection, the '''ZuluSCSI RP2040 Laptop''' is the best option as it can be mounted internally to the case just like a SCSI hard drive.

For IDE devices, this will require an adapter to convert the laptop's 44-pin 2.5" IDE connection to the desktop's 40-pin version. Additionally, the ZuluIDE will have to remain outside the laptop case, however, it can sit in the mounting bracket happily.

====== I need WiFi access to the device, either so multiple machines can access it simultaneously or so I can control it over my network. ======
For SCSI devices, the '''ZuluSCSI Pico Slim''' is the way to go here. This device offers DaynaPORT ethernet emulation, allowing you to attach the device as an Ethernet SCSI device over your wireless network. For instructions on how to set this up, go to the DaynaPORT Emulation page.

For IDE devices, controlling the ZuluIDE is possible wirelessly with an additional Pi Pico W attached to the device's SPI pins or through the Qwiic ports mounted to the device. For details on how to set this up, see the [[ZuluIDE WiFi Control]] page.

=== Step 3: Choose your device. ===
{| class="wikitable"
|+SCSI Devices
![[File:ZuluSCSI 6.4.jpg|frameless|143x143px]]
![[File:Zuluscsi1.2.jpg|frameless|147x147px]]
![[File:ZuluSCSI RP2040 Rev2023a-1.5MB.jpg|frameless|128x128px]]
![[File:ZuluSCSI-Compact-RP2040-Rev2023b-top-cropped.png|frameless|125x125px]]
![[File:ZuluSCSI-RP2040-Mini-in-case.png|frameless|125x125px]]
![[File:ZuluSCSI Pico Slim Assembled.png|frameless|125x125px]]
![[File:ZuluSCSI-RP2040-Laptop version.png|frameless|173x173px]]
|-
|[https://shop.rabbitholecomputing.com/products/zuluscsi-v6-4 ZuluSCSI 6.4]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-v1-2 ZuluSCSI 1.2]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-rp2040 ZuluSCSI RP2040]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-rp2040-compact ZuluSCSI RP2040 Compact]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-rp2040-mini ZuluSCSI RP2040 Mini]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-rp2040-pico-slim ZuluSCSI Pico Slim]
|[https://shop.rabbitholecomputing.com/products/zuluscsi-laptop-rp2040 ZuluSCSI RP2040 Laptop-sized]
|-
|
|
|
|[https://shop.rabbitholecomputing.com/products/zuluscsi-rp2040-compact-homebrew Kit version]
|
|[https://shop.rabbitholecomputing.com/products/zuluscsi-pico-slim-db25-kit Kit version]
|
|}
{| class="wikitable"
|+IDE Devices
![[File:ZuluIDE RP2040 Compact.png|frameless]]
|-
|[https://shop.rabbitholecomputing.com/products/zuluide-rp2040-compact ZuluIDE RP2040 Compact]
|}

Basic Usage

2024-10-15T02:45:07Z

Wikiadmin: 1 revision imported

== SD Card Preparation ==
Both the ZuluSCSI and ZuluIDE devices utilize either SD or microSD cards to load disk images. Your SD card should be formatted either as FAT32 or exFAT '''(not NTFS)''' on at least one partition, if your card has more than one. Cards you use with the device need to fit the following criteria:

* Card must be labeled as either SDXC or SDHC
* MBR or DOS partition type (not GPT)
* No size limitations (see below)

Note that certain older cards (typically manufactured before 2008 and usually 4GB or smaller) will fail to be detected by the device. This is not the fault of the device; it's a speed limitation of the SD card itself. There is no known upper limit to the size of card you can use in the device, and has been tested with 256GB, 400GB, and larger cards that are currently available for sale.

===== File Naming on the ZuluSCSI =====
Create or copy a single valid disk image file into the root directory of your SD card and rename it based on the device you want it to serve as. If the image is a hard drive, name it <code>HDx.img</code> or <code>HDx.hda</code>, and replace the '''x''' in the filename with the desired SCSI ID number, which is a unique number between 0 and 6 (i.e., <code>HD4.img</code> for a hard drive assigned as unit 4 on the SCSI bus). The image will automatically be configured and placed on the SCSI bus.

For optical media images, name image files as <code>CDx.iso</code> or <code>CDx.img</code>, again replacing the '''x''' in the filename with the SCSI ID number. Any image loaded here will be automatically configured by the device as a SCSI-attached optical drive with a standard 2048-byte sector size.

===== File Naming on the ZuluIDE =====
File names on the ZuluIDE are far less restricted, but are still limited to only a few formats. Files ending in <code>.iso</code> or <code>.bin/cue</code> are automatically loaded as optical media images, while images ending in any ''other'' extension not on the [[ZuluIDE File Ignore List|Ignored List]] are treated as other generic removable media, Zip disks, or hard drive images. The type of device the ZuluIDE is configured as defaults to an optical drive, but can be changed with some [[ZuluIDE INI Settings|INI settings]] loaded from the SD card at power-on.

Attach your device to its bus, attach power, turn the system on, and let the device work its magic!

For specifics, see the [[ZuluSCSI Operations Guide]] or the [[ZuluIDE Operations Guide|ZuluIDE Operations Guide.]]

Rabbit Hole Computing:About

2024-10-14T20:55:46Z

Wikiadmin:

[https://www.rabbitholecomputing.com Rabbit Hole Computing] is a small business that's dedicated to providing legacy storage solutions for enthusiasts and industry.

Our products include [https://www.scsi2sd.com SCSI2SD], [https://zuluscsi.com ZuluSCSI], and [https://ZuluIDE.com ZuluIDE], amongst others.

Established in 2018, Rabbit Hole Computing is located in Northern California.

Rabbit Hole Computing:About

2024-10-14T20:55:00Z

Wikiadmin:

[https://www.rabbitholecomputing.com Rabbit Hole Computing] is a small business that's dedicated to providing legacy storage solutions for enthusiasts and industry.
Our products include [https://www.scsi2sd.com SCSI2SD], [https://zuluscsi.com ZuluSCSI], and [https://ZuluIDE.com ZuluIDE], amongst others.

Established in 2018, Rabbit Hole Computing is located in Northern California.

Rabbit Hole Computing:About

2024-10-14T20:51:11Z

Wikiadmin: Created page with "Rabbit Hole Computing is a small business that's dedicated to providing legacy storage solutions for enthusiasts and industry. Established in 2018, Rabbit Hole Computing is located in Santa Rosa, California."

Rabbit Hole Computing is a small business that's dedicated to providing legacy storage solutions for enthusiasts and industry. Established in 2018, Rabbit Hole Computing is located in Santa Rosa, California.

Rabbit Hole Computing:ZuluSCSI v1.2

2024-10-14T20:47:06Z

Wikiadmin: 1 revision imported

Rabbit Hole Computing:Quick Start Guide

2024-10-14T20:47:06Z

Wikiadmin: 1 revision imported

Rabbit Hole Computing:Main Page

2024-10-14T20:47:06Z

Wikiadmin: 1 revision imported

{| class="wikitable"
|+QUICK LINKS
![[Quick Start Guide]]
![[FAQs]]
![[Buyer's Guide|How to Buy]]
![[What Exactly Is SCSI, Anyway?]]
|}
[[File:ZuluSCSI RP2040 Rev2023a-1.5MB.jpg|thumb|The ZuluSCSI RP2040, full-size version.]]

= ZuluSCSI and ZuluIDE =
The ZuluSCSI and ZuluIDE boards are devices designed to emulate legacy mass-storage devices frequently found in vintage computer systems as well as legacy industrial and commercial applications by providing disk images loaded from commonly-available SD cards. The Zulu family of devices provide a simple, easy-to-use interface to load and swap disk images, allowing you to preserve legacy media in a more secure fashion.

The Zulu family of boards operate similarly to the well-known Gotek floppy disk emulation device, loading a disk image from the SD card and presenting it to the system as a variety of different legacy storage devices, from hard drives to optical drives and even Iomega Zip drives. The ZuluSCSI utilizes a standard 50-pin interface, while the ZuluIDE uses the standard 40-pin interface. Both devices are designed to integrate themselves seamlessly into a wide variety of configurations.

=== What can it replace? ===
The ZuluSCSI and ZuluIDE can both replace the following legacy storage devices:

* Hard drives
* Optical drives (including DVD drives)
* Iomega Zip-100 drives
* SyQuest or Iomega Jaz drives
* Floppy disk drives
* LS-120 SuperDisk drives
* Magneto-Optical (MO) drives
* Magnetic tape devices such as LTO drives and StorageTek drives

=== How does it work? ===
The ZuluSCSI uses a microcontroller to configure itself as well as provide functionality to the host system. This device uses the Raspberry Pi Foundation's [https://www.raspberrypi.com/products/rp2040/ RP2040 microcontroller] chip to present itself to the host system as a SCSI device, while allowing the user to work with disk image files on the SD card.

In the ZuluSCSI v6.4's case, the device functions similarly to the older SCSI2SD v6, using a Lattice iCE40 FPGA and an STM32F ARM processor to perform host interaction functions, while configuration and setup is handled using a Windows-based application.

The ZuluIDE provides the same functionality as the ZuluSCSI, but instead lives on the IDE bus in a legacy computer. In addition to its RP2040 microcontroller, the ZuluIDE also brings in a smaller Lattice iCE40 FPGA to handle I/O negotiations on the IDE bus with the host system. With the addition of a separate Raspberry Pi Pico W and a carrier board that can be mounted to the expansion header, you can also access and swap disk images using a web-based interface and even stream Redbook Audio from CD images.

You can use disk images you create yourself, or you can use community-created disk images for your software. We've created several disk images to help you get started; the [[Disk Image Library]] contains a number of blank, pre-formatted images designed for use with various operating systems that can help you with initial setup if you're using your device as a new mass storage option. Naming your disk images is important with each device — see the [[Disk Image File Names]] page for more information on how to name your disk images.

=== Available Devices ===
{| class="wikitable"
! colspan="6" style="text-align:center" |SCSI Devices
|-
! style="text-align:center" |Device Version
! style="text-align:center" |Connector Type
! style="text-align:center" |SD Card Type
! style="text-align:center" |SCSI Termination
! style="text-align:center" |SCSI Initiator Mode
! style="text-align:center" |Other Details
|-
![[ZuluSCSI v6.4]]
|50-pin IDC ribbon
|Full size SD card
|Software-controlled
|Software-controlled
|Designed to work like the SCSI2SD v6, with configuration being performed by a software utility.
The most transparent and fastest SCSI option of all the devices and designed for industrial or commercial applications.
|-
![[ZuluSCSI v1.2]]
|50-pin IDC ribbon
|Full size SD card
|DIP switch controls
|No
|
|-
![[ZuluSCSI RP2040]]
|50-pin IDC ribbon
|Full-size SD
|DIP-switch controlled
|Yes
|Optional DB25 connector footprint
|-
![[ZuluSCSI RP2040|ZuluSCSI RP2040 Mini]]
|DB-25 male
|microSD
|Always on
|No
|ABS plastic enclosure
|-
![[ZuluSCSI Pico Slim|ZuluSCSI Pico Slim (DB25)]]
|DB-25 male
|microSD
|Always on
|No
|DaynaPORT Ethernet (Wi-Fi) emuation, 3D-printed enclosure
|-
![[ZuluSCSI RP2040|ZuluSCSI RP2040 Compact]]
|50-pin IDC ribbon
|microSD
|Jumper-controlled
|Yes
|Also available as a [[ZuluSCSI RP2040 Compact Kit|kit]] with SMD parts pre-soldered; half-size board
|-
!ZuluSCSI Laptop RP2040
|50-pin IDC ribbon
|microSD
|DIP switch controls
|No
|Designed primarily for laptop devices using a 2.5" SCSI interface as their primary boot drive.
|-
! colspan="6" style="text-align:center" |IDE Devices
|-
![[ZuluIDE RP2040|ZuluIDE RP2040 Compact]]
|40-pin IDE connector
|microSD
|N/A
|N/A
|Optional (Gotek-like) hardware interface
Optional Web-based interface and Redbook Audio (in development) available with the addition of a Raspberry Pi Pico W on carrier board
|-
! colspan="6" style="text-align:center" |Retired SCSI Products
|-
!ZuluSCSI v1.1
|50-pin IDC ribbon
|Full size SD card
|DIP switch controls
|No
|The original ZuluSCSI; discontinued
|-
!ZuluSCSI Mini v1.0
|DB-25 male
|microSD
|Always on
|No
|ABS plastic enclosure

|}

== Selecting A Device ==
If you're not sure which device you need, ask yourself these questions:

* Am I replacing a legacy device, such as an aging hard drive or optical drive? Or, am I replacing the media instead, such as old floppy disks, legacy media types like Zip disks, or deteriorating optical disks?
* Do I need to be able to change media on the device (such as swapping floppy disks or changing CDs)?
* Is my device using the SCSI bus or the IDE bus?
* Is the device going to have to migrate from one machine to another, or is it going to live inside a case?
* Do I need Wi-Fi capabilities?

===== If you're replacing drives =====
If you're replacing drives and physical access to the drive itself isn't vital, then the most ideal solutions are either the ZuluSCSI RP2040 or the ZuluIDE RP2040. Both of these can be mounted to drive rails internally and can function on their own without much interaction beyond the initial setup.

===== If you're replacing media =====
If what you're doing instead is replacing a bunch of media, either for preservation or for the sake of convenience, then the ZuluSCSI Pico Slim or ZuluIDE RP2040 with the hardware or Web interface installed is your best bet. The Pico Slim can be easily attached and detached from a system's SCSI bus without having to open a case, and while the ZuluIDE still needs an open case (or exposed IDE cable) for access to the SD card slot, the optional hardware or Web interface can bring media selection controls out so you can easily swap disks when needed.

Rabbit Hole Computing:Buyer's Guide

2024-10-14T20:47:05Z

Wikiadmin: 1 revision imported

Rabbit Hole Computing:Basic Usage

2024-10-14T20:47:05Z

Wikiadmin: 1 revision imported