BasiliskII and SheepShaver can’t open quadra650.rom


This issue was brought up on Stack Exchange, and I answered it. The question and answer is reproduced below.

Note on deleted Stack Exchange Posts

This is from a deleted question on Stack Exchange. Or rather, this is the “saving for posterity” of an extensive answer that I posted to a question on SuperUser, a question which the original poster, rather inconsiderately, subsequently deleted..! Using a neat edit trick proposed by Mark Booth, see his answer to the question View *my* deleted question and answer with less than 10K on Meta SE, I managed to get hold of my answer, as well as the original question.

To get at your answer to a question that the author deleted, you need the answerPostID from the URL, not the questionPostID, where the URL to the deleted answer is of the form:


and then plug it into Mark’s URL above,


Note that this will not work for the question (if you didn’t write the question – if you did, then I still not sure if it works), and that you need to have edit rights (i.e. you were the authour).

Also of interest

  • You may also wish to see the related link, Linux 68k Macintosh emulator.
  • It is also worth noting that SheepShaver only supports PowerMac (PowerPC) emulation, and NOT 68K.

The Original question

BasiliskII and SheepShaver can’t open quadra650.rom

I was thinking I could run Mac OS 7.5.5 on vMac with color but no it won’t work with color only OS can run. I thought it would work if I use BasiliskII but when I assemble the ROM, SDL.dll and the other stuff, I got an error about the ROM: “Cannot open ROM file.” The same thing happened with SheepShaver.

This is very huge problem and I don’t know how I can fix it. On forums it said quadra650.rom will work but I tried and nothing special, I got the same error. I opened both BasiliskII and SheepShaver and I took a screenshot for you guys to know tell me what’s going on?

"Cannot open ROM file." error

I got the disk image from youtube – Tour of Mac OS 7.5.5 with color + games (with download links). Read the description for .dsk file.

The Answer

Tackling Basilisk II and SheepShaver in turn…

Basilisk II

I’ve managed to reproduce your error, using a Quadra 650 ROM file from a tutorial onRedundantRobot.

The issue is that you need to specify to the emulator where the ROM file is located. Just dropping it in the same directory is not sufficient.

From the BASILISK II readme, the rom preference is defined below:


This item specifies the file name of the Mac ROM file to be used by Basilisk II. If no “rom” line is given, the ROM file has to be named “ROM” and put in the same directory as the Basilisk II executable.

So the easiest option, without requiring you to modify the preferences file, in the Basilisk II directory, rename the ROM file, from quadra650.rom to just ROM.

Rename file to ROM

Or, you could edit the preferences file, by opening the file, BasiliskII_prefs, in notepad (as here is no GUI preferences dialogue) and add

rom C:\<your path>\quadra650.ROM

for example,

rom C:\Users\davinci\Basilisk\BasiliskII_20-02-2015\quadra650.ROM

If your disk is specified corectly then the virtual mac should now boot.

Booted MacOS

Otherwise, you would end up with this (and you may need to use Task Manager to end the Basilisk IIprocess as the window may refuse to close and kill the application):

No disk defined

This is because the same path issue occurs with the disk image, and you may need to specify the path to the disk image in the preferences file. Again from the BASILISK II readme, the diskpreference is defined:


This item describes one MacOS volume to be mounted by Basilisk II.
There can be multiple “disk” lines in the preferences file. Basilisk II can handle hardfiles (byte-per-byte images of HFS volumes in a file on the host system), HFS partitions on hard disks etc., and MacOS-partitioned disks (it can only access the first partition, though). The “volume description” is either the pathname of a hardfile or a platform-dependant description of an HFS partition or drive. If the volume description is prefixed by an asterisk (“*”), the volume is write protected for MacOS.

Basilisk II can also handle some types of Mac “disk image” files directly, as long as they are uncompressed and unencoded.

BeOS: To specify an HFS partition, simply specify its path (e.g. “/dev/disk/scsi/0/1/0/0_3”). If you don’t specify any volumes, Basilisk II will search for and use all available HFS partitions.

Unix: To specify an HFS partition, simply specify its path (e.g. “/dev/sda5”). If you want to access a MacOS-partitioned hard disk or removable volume (Jaz, Zip etc.) and your operating system doesn’t understand MacOS partition tables, you can specify the block device name (e.g. “/dev/sda”) to access the first HFS partition on the device. Under Linux, if you don’t specify any volumes, Basilisk II will search /etc/fstab for unmounted HFS partitions and use these.

AmigaOS: Partitions/drives are specified in the following format: /dev////// “start block” and “size” are given in blocks, “block size” is given in bytes.

Windows: To define a logical volume (Windows NT only), specify its path (e.g. “c:\”). To define a physical volume (NT and 9x), additionally give the “physical” keyword (E.g. “physical c:\”). For safety reasons, volumes are mounted as read-only. This is due to the bugs in PC Exchange. If you don’t specify any volume, the files *.hfv and *.dsk are searched from the current directory. Note that in this case, Basilisk II tries to boot from the first volume file found, which is random and may not be what you want.

So add the line

disk C:\<path>\boot.dsk

for example,

disk C:\Users\davinci\Basilisk\BasiliskII_20-02-2015\boot.dsk

to the preferences file, where path is your path to the Basilisk directory, and rename the System 7.5.5 Boot.dsk file to just boot.dsk

Rename disk image file

The renaming of the file to something simpler is not be strictly necessary but removing the spaces reduces the chance of the file not being recognised or found. The following line does work though, as Basilisk II handles the spaces in filenames without an issue:

disk C:\Users\davinci\Basilisk\BasiliskII_20-02-2015\System 7.5.5 Boot.dsk 


I’ve managed to reproduce your error, using a New World PPC ROM file from a tutorial onRedundantRobot. [Edit: This is because SheepShaver does not support 68K Mac emulation]. If you attempt to use the Quadra 650 ROM file, that you used for Basilisk II, then you will get the following error:

Wrong ROM file - Quadra 650 ROM is incompatible

Copying in the correct New World PPC ROM file is not sufficient, as you will get the following error:

newworld86.rom file needs to be renamed to ROM

If you rename the file to just ROM, again without any file extension, then SheepShaver will run, as desired.

4 thoughts on “BasiliskII and SheepShaver can’t open quadra650.rom”

  1. Just want to point out that it causes Basilisk II to shut down without any message whatsoever. I renamed Quadra to Mac Rom and put in my HFV file as well as the boot image.

    On my *Volumes* I have *System7.hfv I created then I have the boot disk on bottom with the renamed rom file in the path.

    I click start and it shuts off. Yippe! No Mac OS. 😦


  2. BTW: Iv’e gotten Mini Mac emulator to work with no problems whatsoever following the instructions yet Basilisk II just shuts down when I do it.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s