ZuluIDE Operations Guide - Revision history

Aperez: /* Using the SD card */

2026-02-01T20:18:54Z

Using the SD card

← Older revision		Revision as of 13:18, 1 February 2026
Line 141:		Line 141:
	# Power down the system that the ZuluIDE is attached to and 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.		# 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.		# From the [https://github.com/ZuluIDE/ZuluIDE-firmware/releases Github page], download the latest universal firmware file with a '''.zip''' extension.
	# Copy the downloaded '''.~~BIN~~''' file to the root folder of the SD card and ~~rename it as <code>ZuluIDE.bin</code>~~.		# Copy the downloaded '''.zip''' file to the root folder of the SD card and ''do not re-name the file or extract its contents.''
	# Dismount the SD card from the computer, and reinsert the SD card into the ZuluIDE.		# 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.		# 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.

Mbalmer: /* Troubleshooting */ - add sound card details and CD audio pinout on early SB cards (+215 words)

2025-01-06T16:04:17Z

Troubleshooting: - add sound card details and CD audio pinout on early SB cards (+215 words)

← Older revision		Revision as of 09:04, 6 January 2025
Line 188:		Line 188:
	Reboot the system, and the drive should populate.		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.		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>) and <code>VIDE-CDD.SYS</code>, the driver that is included on the Microsoft CD-ROM Extensions installation floppy disk.

			Other generic drivers, such as the LG (GoldStar) or Adaptec drivers may work, but have not been fully tested.

	=== [[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. ===		=== [[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. ===
Line 203:		Line 205:

	=== [[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. ===		=== [[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.		This issue is related to firmware revisions prior to 2024.12.10. Update your device firmware on the [https://github.com/rabbitholecomputing/ZuluIDE-firmware Github repo].

			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.

			=== [[File:Msdos-icon.png\|frameless\|34x34px]](attached to sound card): The ZuluIDE seems to be working correctly, but it's never detected. ===
			This is a potential hardware configuration issue. Some sound cards, even if they have an actual IDE interface, force themselves to be configured as either the primary or secondary interface in the system and are not configurable. Most sound cards are also capable of recognizing ''only'' optical devices, so if you have the ZuluIDE configured as something other than an optical drive, the card may not recognize the device attached to it. If you want to use the ZuluIDE as something other than an optical drive, attach it to an IDE port attached to the motherboard or I/O card, as opposed to a sound card.

			=== [[File:Msdos-icon.png\|frameless\|34x34px]][[File:Win31.png\|32x32px]][[File:Win9598.png\|37x37px]][[File:Winxp.png\|36x36px]] (with audio DAC board): I have the device attached to my SoundBlaster's CD audio in connector, but I only hear the right channel. ===
			Early SoundBlaster cards (including the Pro and Pro 2) used a different pinout on the CD audio header. Instead of R-G-G-L (right channel, ground, ground, left channel) these cards' pinout was NC-L-G-R (no connect, left, ground, right). You may need to get a different cable.

Mbalmer: Change "not ready" troubleshooting step

2024-11-12T01:55:14Z

Change "not ready" troubleshooting step

← Older revision		Revision as of 18:55, 11 November 2024
Line 191:		Line 191:

	=== [[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. ===		=== [[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~~.		This issue is related to firmware revisions prior to 2024.11.08. Update your device firmware on the [https://github.com/rabbitholecomputing/ZuluIDE-firmware Github repo].

			If you are unable to update the firmware, there is a workaround that you can use until you are able to do so.

	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:		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:

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

2024-11-11T18:15:34Z

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

@@ Line 119: / Line 119: @@
 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>.zip</code>
+*<code>.cue</code> <code>.txt</code><code>.rtf</code><code>.md</code><code>.nfo</code><code>.pdf</code><code>.doc</code>
-* <code>.7z</code>
-* <code>.rar</code>
+Compressed archive file formats:
-* <code>.tar</code>
-* <code>.tgz</code>
+* <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.

Mbalmer: Finish main initial content (+1,207 words, 2 images. OS icons don't count)

2024-11-04T17:39:58Z

Finish main initial content (+1,207 words, 2 images. OS icons don't count)

Show changes

Mbalmer: Initial save (incomplete; 1,381 words, 8 images)

2024-11-03T04:31:39Z

Initial save (incomplete; 1,381 words, 8 images)

@@ Line 23: / Line 23: @@
 * '''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 failure modes as described later
+* '''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.
@@ Line 45: / Line 45: @@
 * '''1× 3½ female housing:''' TE Connectivity P/N 171822-4
-When making the cables, use 20-gauge wire. Crimping the cables can be done with standard tools found on Amazon, such as the IWISS SN-025.
+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 ==
@@ Line 64: / Line 64: @@
 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.
-== SD Card Preparation ==
+== Activity LED ==
-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.
+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.

Mbalmer at 21:38, 2 November 2024

2024-11-02T21:38:24Z

← Older revision		Revision as of 14:38, 2 November 2024
Line 11:		Line 11:
	* Qwiic cable		* Qwiic cable

	=== Board Overview ===		== Board Overview ==
	Take a moment to identify the various parts of the board as shown below.		Take a moment to identify the various parts of the board as shown below.
	[[File:ZuluIDE RP2040 Compact (labeled).png\|center\|frameless\|800x800px]]		[[File:ZuluIDE RP2040 Compact (labeled).png\|center\|frameless\|800x800px]]
Line 27:		Line 27:
	* '''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.		* '''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 ====		== 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.		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;"		{\| class="wikitable" style="margin: auto;"
Line 38:		Line 38:
	\| colspan="2" \|❌ 5¼" 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:

	==== DIP Switch Configuration ====		* '''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. 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]]		[[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.		Set the three DIP switches according to how the device needs to be configured in the host system.
Line 46:		Line 54:
	* '''Switch 2:''' Respond as Primary/Master (OFF) or Secondary/Slave (ON).		* '''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.		* '''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.

			== SD Card Preparation ==
			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.

Mbalmer at 20:10, 2 November 2024

2024-11-02T20:10:59Z

@@ Line 7: / Line 7: @@
 * 3D-printed plastic carrier
 * 2x ¼" 4-40 screws
-* MicroSD card
+* microSD card
 * Hardware interface board
 * Qwiic cable
@@ Line 21: / Line 21: @@
 * '''I<sup>2</sup>C 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 I<sup>2</sup>C cable.

Mbalmer: Created page with "== 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 * Qwiic cable === Board Overview === Take a moment to identify the various parts of the board as shown below. 800x800px * '''4-..."

2024-11-02T19:06:57Z

Created page with "== 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 * Qwiic cable === Board Overview === Take a moment to identify the various parts of the board as shown below. center|frameless|800x800px * '''4-..."

New page

== 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
* Qwiic cable

=== 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.
* '''I<sup>2</sup>C 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 I<sup>2</sup>C cable.