You can create a ROM Drive by using the Pico’s flash memory to act as a read only device. This can be handy as the ROM drive is stored on the Pico and is independent of any disk images on the SD card. The ROM drive is assigned a SCSI ID and can store an image up to 1692kb
in size. (This space may be slightly less on models using a WiFi Pico board)
You can use a ROM drive as a small boot disk or to store a set of key applications. It is similar to an HD image, but it cannot be written to once it has been flashed to the BlueSCSI’s Pico module.
HD1.rom
, the 1
sets the SCSI ID, you can change this to any ID you wish.log.txt
on the SD card you will see a message indicating success and the original HD1.rom
file will be renamed to HD1.rom_loaded
. You can now delete this file from the SD card. NOTE: MacOS does not honor the lock flag used for the ROM drive, so it will still appear as writable to the system, but will fail if you attempt to write data to it.
To disable the ROM drive set DisableROMDrive=1
in the [SCSI]
section of the bluescsi.ini
file.
[SCSI]
DisableROMDrive=1
You can remove any loaded ROM drives from the BlueSCSI and erase the Pico’s memory using the following steps.
CLEAR_ROM
. log.txt
on the SD card will be updated with the line Cleared ROM drive
. In addition, the ROM Drive section of the log will display ROM drive image not detected
.You can create a ROM Drive using Disk Jockey version 2.5.2 or later (currently this feature only on the Mac version).
HD0.rom
. You can ignore the HD image file if you don’t need one. These steps will instruct you on how to create an empty, unformatted ROM file via the Terminal on MacOS.
Terminal.app
on your Mac (located under Applications > Utilities). cd Documents
and press return to change the working directory to your Documents folder. dd if=/dev/zero of=ROM.hda bs=1k count=1692
and press return to create a ROM.hda
file in your Documents folder. ROM.hda
file is blank! It must be formatted for your target system (like a vintage Macintosh) in order to use it properly. Use your vintage target system (or an emulator) to format the .hda
file and copy any desired files onto the image before you flash the ROM drive image file to the Pico’s memory.NOTE: Some emulators (like the Macintosh emulator Mini vMac or Basilisk II) may not format the
.hda
file in a way that can be used on a real vintage Macintosh. However, you can download a pre-formatted ROM drive image for System 6 or System 7 and use an emulator to write files to it before you flash it to the Pico’s memory.
The following steps were tested with System 7.1 on a Macintosh LC, it assumes you have a bootable Macintosh disk on your BlueSCSI already and the Apple SC HD disk utility.
HD20_512 ROMunformatted.hda
Drive
button until the SCSI ID of your blank ROM file is selected. Click the Initialize
button, you will be asked to confirm you want to erase the disk, choose Init
. It will erase the disk and may prompt you to name the disk.HD20_512 ROMunformatted.hda
to HD1.rom
. (The 1
defines the SCSI ID, you can change this as needed.) As always, your SCSI ID must be unique and not conflict with any other SCSI drive images or devices. Check to ensure the file extension is correct (.rom
) and you don’t have double extensions (such as .hda.rom, etc.).NOTE: Some odd behavior with System 6 and 7 have been observed once a .HDA
file has been made a ROM and flashed onto the Pico. For example, a ROM Drive image formatted using Apple SC HD (v7.1) on System 7.1 will not work or mount with System 6.0.8. In addition, a ROM drive image formatted using System 6.0.8’s built in erase disk function will not work on System 7.1. Opening the drive under System 7.1 will generate -127 errors and eject the disk from the system. We recommend using an already formatted ROM file for your Macintosh system and being aware of these issues.
Generated 2024-12-11