User Guide


Quick Start
Testing MOL
HFS Volumes
Starting MOL
Newworld ROM

Basic Networking
Advanced Networking
Oldworld Booting
Molrc Summary
External References



[ General | Compatibility Table ]

Starting with the iMac and the B&W G3, Apple introduced "NewWorld booting". In principal, this means that the rom is loaded from a file rather than from a rom chip.

The file 'Mac OS ROM' in the System Folder contains the newworld ROM (also called file-rom). MOL automatically loads the rom at startup. You only need to concern yourself with the newworld rom if you happen to have a version which is incompatible with mol. Visit the ROM compatibility section to find out if your particular rom version is compatible with mol.

Potential poblems

(i) If mol is run on a pre-newworld machine, then the newworld rom might be missing from the System Folder. If this is the case, boot mol from the installation CD and install MacOS from within mol (copying the MacOS ROM file from the CD might work too, but it is not recommended).

(ii) If you an incompatible ROM, then you should either

  • Upgrade MacOS (e.g. to 9.0.4 or 9.2.1)
  • Download the latest version of MOL
  • Obtain a 'Mac OS ROM' file which is MOL-compatible.

For instance, it is possible to download the "Ethernet Update 1.0" from Apple and extract the rom from it using the "Tome Viewer" application. You should make sure you are using a ROM which corresponds to the MacOS version:

  MacOS 8.6 1.6 ROM, extracted from
Mac OS ROM Update 1.0
  MacOS 9.0.4

v3.8-ROM, extracted from
'Ethernet Update 1.0'

Do not use these ROMs with MacOS 9.1 or 9.2. It won't work (and it is not necessary since mol is compatible with recent ROMs).

Normally mol automatically loads the ROM from the System Folder. However, If you want to use a different ROM version, then you should copy the Mac OS ROM file to the linux side and add the resource line

newworld_rom: rom/rom.nw

assuming the rom.nw file is placed in /usr/lib/mol/rom/rom.nw. If the newworld_rom resource is used, then it is important that the '-boot' flag is used to specify the startup volume (otherwise it can happen that some volumes are not properly mounted).

It is important that the rom image is copied as a plain binary file (without any MacBinary encodeing). Here is a two examples how to do this (but remember, you should not normally have to do this):

bash$ mount -thfs /dev/cdrom /mnt
bash$ cp "System Folder/Mac OS ROM"               /usr/lib/mol/rom/rom.nw
bash$ umount /dev/cdrom

The above only works for HFS disks, for HFS+ the hputils pagacke can be used:

bash$ hpmount /dev/hdaXX
bash$ hpcd "System Folder"
bash$ hpcopy -b
"Mac OS ROM"               /usr/lib/mol/rom/rom.nw
bash$ hpumount