Benchmarking Retro Macs : Norton System Info

Benchmarking Retro Macs : Norton System Info

There are a number of classic Mac OS benchmarking tools available. Different ones have various benefits and personal preference is a major factor in choice. I’ve always used Norton’s System Info, which is provided as part of the Norton Utilities suite for Macintosh. I believe that it was first included with version 3 of Norton Utilities, but I need to verify that. As a kid, this was simply the only benchmark we owned, I like that it makes it clear what it is doing to benchmark (tests are named for the low level function that is being tested, often Macintosh Toolbox routines), and it uses a photo of two cats for the graphics tests that is clearly just a photo of a programmer’s pets. Its not even a very good photo, but this little human touch cheers me up every time I see it, and that’s worth a lot.

Lots of Norton Cats
Lots of Norton Cats

System Info requires System 7 to run, and so an alternative benchmarking tool such as Snooper would be needed if you are running System 6. The newest versions of Norton Utilities claim to need Mac OS 8.* but it isn’t actually true.

Over time, there were few obvious changes within the System Info application. Included benchmarks and System used as the baseline (100 in tests) varied through time. I… think it started as the SE, but haven’t seen this version lately… but more common versions were the Quadra 700, and later the Power Macintosh 6100/60. The following shows System Info’s default window on launch. Later versions show a splash screen while launching, earlier versions did not.

Norton System Info Default Window
Norton System Info Default Window

Features include

  • Native 68k and PPC support.
  • An extensive collection of included benchmark results files for both stock and some accelerated Macintosh computers.
  • Top level CPU, 2D (Quickdraw) graphics, disk and FPU scores.
  • Ability to select PPC or emulated 68020 performance on a PowerPC, and physical or software FPU where available.
  • Ability to select which video card and which disk.
  • Advanced mode which shows more detail during tests, and gives more detail in results. Graphical and tabulated results available, with the ability to show tabulated results in relative or absolute terms.
  • Results can be easily shared as saved individual files for each test run.
  • A detailed description of the computer and settings automatically saved with the results file.
  • Warns about some system settings which may impact performance, such as AppleTalk, Virtual Memory, video bit depth and Disk Cache.
  • A tiny application.
  • Ability to export tab separated values (TSV).

Disadvantages

  • New users don’t notice the need to enable advanced features and assume the tool is more simplistic than it is.
  • As is often the case, the performance benefits of a relatively small cache are possibly exaggerated as the tests seem to be repetitive and fit within the cache (difficult because caches give significant real world advantages, but not in all instances).
  • Tests are very much function based and not representative of real world activities.
  • Graphics tests are only QuickDraw 2D, and don’t include any QuickTime, RAVE, QuickDraw 3D, Glide or OpenGL tests.
  • Not scriptable?
  • The CPU speed shown in the main window in MHz isn’t always correct, especially if the accelerator is only enabled during boot, or is able to change speed.

Tips and Tricks

  • Even if the version of Norton you’re using is too new for the computer you are using, if you go into the “Norton Tools” folder and run “System Info” from there, it will launch in most circumstances, as long as you have System 7 or newer.
  • To enable advanced options within the software, select “Show More Choices” from the “Benchmarks” menu. This provides a number of additional drop down menus for fine tuning and seeing results in a greater level of detail throughout the application, as well as some additional menu items.
Show More Choices
Selecting Show More Choices
System Info Default Window More Choices
System Info Default Window More Choices Shown for Volume and FPU, With the Latter Selected
  • Note that generally, the higher the video bit depth you run, the slower graphics performance will be, except where acceleration is only provided at higher bit depths. It was fairly common for video cards to not provide acceleration at bit depths below 8bit, and a small number of cards only provided 24bit acceleration.
  • Screen resolution doesn’t appear to have a significant impact on video scores for many machines, although running at 640×480 is probably best to ensure consistency with built in benchmarks. This said, Computers that use main memory as VRAM like the IIci, IIsi and 6100 can see significant CPU performance changes depending on video settings.
  • When in the “System Ratings” window, selecting a system from the list and clicking the “Get Info” button (see image “All Results Windows” below) will show a description of the system the benchmark was performed on. Details are given of both hardware, software and some system settings.
  • Additional results supplied, but not shown by default, can be added to the various results windows using the “Add Systems To List” menu item from the “Edit” menu.
Add Systems To List
Add Systems To List

Running a Test

Use the “Selected Suites” checkboxes to enable and disable each of the CPU, video, disk and FPU test suites and if in advanced mode, select between the real and emulated CPU, video card, disk (in reality, the list given is mounted partitions) and FPU or software. Not all of these options will be available at all times, depending on the computer under test.

Link to video showing System Info benchmarks (at 3:22)

Once the options are as desired, click the “Run” button. Note that at this point Norton will inform you of any System settings it has detected which will impact the scores and which it thinks you should change. Unless you’re doing specific testing, such as comparing 24bit mode between video cards, it is generally advisable to follow this guidance. A restart may be required for some changes (for example, disk cache, and AppleTalk on some System versions).

After this the tests will start. Depending on the performance of your computer, they may take quite a few minutes to run, especially the disk tests. In the advanced mode, you will be given greater detail of what test is currently being undertaken and what each test scores. This can help with the boredom of waiting for the tests to complete.

Once the benchmarks have completed, System Info automatically opens the System Ratings window, and lists the tests just undertaken as “Current System”. It is probably a good idea to save the results at this point if you plan to keep them for comparison.

Reviewing Results

All Windows
All Result Windows

Note – the screenshot above incorrectly shows zeros for all results. This is an oddity of running the software within some emulators. Something I did for convenience when getting screenshots. On real hardware you will see actual scores for your and other computers.

Viewing Overall Rating / Test Category / Individual Tests

At the top left of the “System Ratings” window, there is a pop-up menu labelled “Show”. This allows you to select each of the four test categories, CPU, Video, Disk or FPU, as well as the default overall summary “System Rating”. The numbers to the right of each system name represent a score, relative to the baseline system (e.g. scaled where a Quadra 700 equals 100, or a 6100/60 equals 100 etc. dependant on the version of System Info you are using. The baseline system is identified in the list by the text “(reference system)” following its name). The bars to the right of these numbers (ordinarily) vary in length and graphically represent the score for each system.

If all tests were not run, the Current System will show as a dash “-” for the tests which were not completed, as well as for the overall “System Rating”.

If advanced mode (i.e. with “show more choices” enabled), an additional drop down menu is available by clicking the downwards pointing triangle to the left of the “System Rating” column heading. This menu allows you to select individual tests for the category currently selected, for example, if you have selected “Disk”, then you will be able to choose to display specifically the random write, or perhaps 1K read test.

It is worth studying the results at this level, especially with respects to video accelerator performance, because it can be interesting to see how different cards perform in different areas. A card that scores well overall might be weak when it comes to rendering text compared to another card that scores lower overall. In this case, if your primary use case is… rendering text – the supposedly “slower” card might be the best card for you as it performs better in your application that mainly renders text.

To assist in comparing results on a test by test basis, clicking the “Show Details” button presents tabulated results. Within this window, a drop down menu enables you to select between “Absolute” and “Relative” results. I find that generally, “Relative” is more usable with the exception of disk scores, as the “Absolute” scores for the disk results are given in KB/s, which is meaningful.

If you manually select a subset of results in the “System Ratings” window before clicking “Show Details” only details for those, plus the baseline system, will be shown.

Tabulated Results
Tabulated Results

Exporting Results

While in the Detailed Ratings view, pressing Command-C will copy a summary of all results to the clipboard. This text can then be pasted into another application, such as for example, in the following screenshot, a text document. To remove unwanted entries either select a subset of results in the “System Ratings” window before clicking the “Detailed Ratings” button, or alternatively quit System Info and move unwanted benchmark files in the “Benchmark results” folder into the “Hidden Results” folder. Any results in the hidden folder wont show in the results lists / export. Moving them back afterwards will make them re-appear next time you relaunch the program.

Results Copied from the Detailed Ratings View, and Pasted into the Text Editor BBEdit

Note that the exported text includes all result types (CPU, Video, Disk and FPU), not just the results that were currently being viewed. The data is Tab Separated Values (TSV) and should be fairly trivial to paste into a Spreadsheet such as Excel or ClarisWorks.

Moving data to a modern computer can be easily achieved with BBEdit. I recommend BBEdit, because it will run on 68k Macs, and is aware of the three common line ending types. By pasting in the data, selecting save, and then clicking the “Options…” button, you will get the following dialogue box, where you can select your preferred line ending type. I’m picking “Unix”, which is best for Linux and modern versions of Mac OS, but if you are on Windows, you will likely want to pick “DOS”.

Saving for Other Platforms

Name the file, including a “.txt” or “.tsv” file extension and save. Once you have moved the file to your modern computer, you should be able to trivially import the data. You may have minor issues if there are unusual characters, due to the classic Mac OS Roman text encoding. The following shows my example exported collection being opened in LibreOffice Calc.

Importing Norton System Info Results into LibreOffice

Note – You should probably uncheck “Comma” and “Semicolon” if you have used these characters in your system descriptions, or if you are using continental European number formats.

The following screenshot shows the text file imported with no further manipulation, other than creating a chart based on the “Current System” and “Overall” columns of the first table of data.

Working with Norton System Info Data in LibreOffice Calc

Description of the Individual Benchmark Tests

The following is an extract from the Norton Utilities 3.2 manual.

Manual Extract for Norton System Info Benchmarks

Variations in test results of up to 1 percent are normal. For disk tests, variations of up to 7 percent are normal due to disk drive operation.

CPU Benchmarks

Some CPU tests actually test more than the CPU itself. For example, some tests access memory (RAM), which tests not only the CPU, but the system bus, memory speed, and caching (if any). These factors can influence test results substantially. For the purposes of benchmarking, these factors are all considered to be part of the CPU.

BlockMove Aligned and BlockMove Misaligned: Measures the rate at which the Macintosh can move memory using the ROM trap BlockMove. On all Macintosh computers, BlockMove is highly optimized and thus is a good measure of memory bandwidth (how much data can be moved per unit time). An aligned and misaligned case are used because on some Macintosh computers performance is much poorer when data is not aligned properly. Newer models, such as the Power Macintosh computers, have excellent performance in both cases.

Memory Read and Write: This is also a memory bandwidth test, but the benchmark accesses memory in the way a program normally would and does not make use of any special machine instructions.

Function Call: Measures the overhead associated with making a series of function calls with arguments. Most application programs make large numbers of function calls.

Bit Shifts: Measures how fast bits can be shifted in a machine word. This type of instruction is used frequently by a wide variety of software.

Multiply and Divide: Measures speed of integer multiplication and division. The tests are slanted more towards multiplication. Application programs frequently use this type of instruction to access arrays.

Branches: Measures how fast code containing conditional branches can run. Branches are on of the most common types of instructions used and can substantially affect performance on some CPUs. Power Macintosh computers have a special processing unit dedicated to processing branch instructions.

Instruction Overlap: Measures the ability of the CPU to execute integer (not floating point) instructions at the same time it accesses memory. The benchmark is written in such a way that memory access should be able to execute at the same time all intervening computations are performed.

Sort: A high-level benchmark that sorts a large array using a quick-sort and insertion-sort hybrid algorithm that makes heavy demands on memory and looping constructs.

Tree: A high-level benchmark that builds a large, sorted binary tree by repeated insertion. Good caching and/or memory bandwidth can speed up this test considerably.

Search: A high-level benchmark that performs a sophisticated string-searching algorithm that makes extremely heavy demands on memory in a partially-sequential way. This test is designed to access memory in a way that most machines cannot cache effectively without a substantial amount of cache memory.

Video Benchmarks

The Video benchmarks test the speed at which common Quickdraw operations can be performed. The benchmarks are designed to measure frequently used operations – not esoteric transfer modes or rarely utilized Quickdraw routines. For example, scrolling operations are emphasized in the overall video rating because they are heavily used by all users. Note that as the video bit depth is reduced, video performance generally increases. If you compare video performance on two different systems, make sure to test at the same video bit depth.

Rectangles, Round Rectangles, and Ovals: These tests cycle through painting, erasing, filling, framing, and inverting the respective shapes with different fill patterns and colors, where appropriate.

Lines: Draws lines of varying slopes and colors. The video circuitry of some Macintosh computers is highly optimized for drawing lines.

Picture: Draws a bitmapped picture at the same bit depth of the screen. It tests the ability of Quickdraw to decode a PICT format picture and place its bits on the screen.

CopyBits: Measures how fast bits can be moved around on the screen using the CopyBits ROM routine, which is heavily used in screen drawing. The small cases are 32 by 32 (the size of a large icon). The small cases are significantly impacted by the overhead of calling Quickdraw and its setup. The large cases minimize this overhead and, thus, more accurately test the actual speed at which bits can be moved. Aligned (to a 32 pixel boundary) and misaligned cases test optimal and non-optimal situations.

DrawText: Measures how fast a sentence can be drawn on the screen. Primary emphasis is placed on drawing plain text, although bold and italic text are tested as well.

Scrolling: Measures how fast bits can be scrolled on the screen. Emphasis is placed on vertical scrolling, but some horizontal scrolling is also performed. Results of this test vary widely depending on the bit depth of the screen.

Disk Benchmarks

By design, the disk tests do not isolate disk speed alone. The benchmarks include factors applications normally experience, such as CPU speed, SCSI bus speed, impact of the disk cache, and fragmentation.

Random Read and Random Write: These benchmarks read or write data into a file in three 1MB bands. The data size read and written varies from 4 bytes to 4 kilobytes. These tests reflect seek time, the effects of the disk cache, and how fast a drive can process numerous small requests to read or write data. They are a good indicator of overall disk performance.

Sequential Read and Sequential Write (1K, 4K, 16K, 64K, and 256K): Measure how fast the drive can read/write data when requested in a specific size chunk. Some drives can transfer data efficiently only in large chunks, others are efficient with many small chunks, but slow down with large chunks. These sequential tests intentionally bypass the built-in disk cache (to eliminate cache overhead) and provide a better indicator of performance of the disk itself. Smart, disk-intensive applications such as Norton DiskDoubler Pro bypass the disk cache, when appropriate, to provide maximum performance. Few current applications employ this technique, however.

FPU Benchmarks

All FPU tests are directly comparable among themselves. For example, you can directly compare the speed of a multiply to an addition, square root, or cosine.

A single-precision floating-point number is 32 bits. Because of differences in the floating point formats supported on various machines, a double-precision number varies in size. For double precision, the fastest format available that is at least 64 bits in size is used.

Multiply, Divide, Add, and Subtract: Measure basic FPU performance in both single and double precision. On some machines, double precision may actually be faster than single precision because single precision numbers must first be converted to double precision before the calculation occurs.

Integer To Single and Single To Integer: Convert an integer number to a single precision floating point number and vice versa. Some machines have hardware instructions for both operations, some have neither, and some have just one. This accounts for dramatically different results that you may encounter, depending on which way the conversion goes.

Sine, Cosine, Tangent, and Arc Tangent: Measure trigonometric performance on double-precision numbers. These results can vary dramatically from computer to computer. Some older models of the Macintosh can actually outperform the new Power Macintoshes on these functions because the Power Macintoshes implement these routines in software.

Absolute Value, Square Root, and Log 10: Measure the absolute value, square root, and logarithm in base 10, respectively, of a double-precision number.

Vector: Measures how fast an array of numbers (vector) can be manipulated. Each element in the array is multiplied by a constant, a constant is added, and the result is stored back into the array (X’ = aX + B).

Getting Norton System Info

Norton System Info was provided as part of the Norton Utilities for Macintosh suite of software. The best way to get a copy of this is by buying a genuine copy on eBay, although I’m quite sure there are copies on Macintosh Garden.

Feedback on this Post

If you have any additional information which you wish to suggest is added to this page, or would like to correct any errors / inaccuracies, please use my contact form to let me know.

Creating a Custom Bootable Classic Mac OS CD from Linux

Creating a Custom Bootable Classic Mac OS CD from Linux

and possibly other operating systems, which I don’t have to hand

The following is a description of the process to easily create a HFS formatted disk image and burn it to a CD, suitable for use in a Macintosh computer running Mac OS 9.2.2 or older, assuming it has an operable CD drive. If your CD drive is struggling to read disks, cleaning its lens can help. I have some short instructions on how to do that here.

The instructions on actually generating an appropriately formatted ISO disk image ready to be burnt to a CD are universal, and apply equally to Linux, modern Mac OS and Windows, but these instructions provide Linux specific detail as it is the only OS I have on hand to test.

What You Will Need

Hardware

  • A computer running Linux (or another OS, but most of my guidance wont be directly applicable)
  • An optical drive capable of burning CDs
  • A blank CD-R
  • A vintage Macintosh running a version of the classic Mac OS, with a functional CD drive.

Software

  • A flavour of Linux, this page assumes a Debian family variant, such as Debian, Ubuntu, Mint or Pop!_OS (other operating systems can be used, but detailed instructions are not provided)
  • Basilisk II – a cross-platform Macintosh Emulator, a bootable disk image with required software (provided below)
  • A ROM image for the emulator, taken from a retro Macintosh you own, or at least equivalent to a machine you own.
  • K3b – CD burning software for Linux (other software may work, but detailed instructions are not provided))

Setting Up the Software

Installation

To install Basilisk II, run the command in a terminal…

sudo apt install basilisk2

To install K3b, run the command in a terminal…

sudo apt install k3b

Download this disk image which will be your main boot disk for the Basilisk II emulator, extract the contents from the ZIP and store it in a convenient location.

Obtain the required Macintosh ROM, from a Macintosh II series or Centris / Quadra ideally, but other ROMs are likely to work. I have been using a IIci ROM. Store it in a convenient location.

First Run of Basilisk II

01 Volumes
01 Volumes

After launching Basilisk II, you will be faced with the window shown above, without the two disks listed. To add these, first, click the “Add…” button, navigate to where you stored the disk image “Bernie.dsk” and select it. This already contains an operating system and the retro Mac software we’ll need to create a bootable CD. “WorkingVolume.dsk” is a second, empty, disk image that we will create now and which will be where we will collate and organise the CD we want to build. Click the “Create…” button and enter the following details for Size and the file name. Navigate to a convenient location to save, and then click “OK”. We now have a 650MB empty disk image in addition to our 1GB, bootable, disk image.

02 Creating Working Volume
02 Creating Working Volume

Within the “Graphics/Sound” tab I set the Width and Height to 640 and 480 respectively. These values suit me, but are not critical – for example you could set 1024 and 768 if you wanted a larger emulated display. Sound settings can be left at your installation’s defaults. In the “Memory/Misc” I set MacOS RAM Size to 32MB, Mac Model ID to Mac IIci, CPU Type to 68030 with FPU and selected a IIci ROM file using the “Browse…” button. With my setup, it was required that I selected “68030 with FPU” and not just “68030”, otherwise the emulated computer would not boot from my particular operating system.

Once you are happy, you can click the “Start” button, and you should be greeted with an emulated Macintosh booting very quickly. Once the startup sequence has completed, the first time only, you will be greeted by a dialogue box asking for you to format the empty “WorkingVolume”, 650MB disk image that you created. Name this disk whatever you want your CD to be called when it mounts on the desktop (after this first time, you will need to do this by renaming the volume on the desktop). Keep the format as the default “Macintosh 650 MB”. Click “Initialize”.

05 Format Working Volume
05 Format Working Volume

The new volume, in my instance called “WorkingVolume” will mount on the emulated desktop, along with “Bernie”, our boot volume and “Unix”. Unix is a link into the host computer’s file system which we will be using later to transfer our complete disk image back to the host for burning to a disk. Your window should look similar to the following.

06 Booted Bernie
06 Booted Bernie

Congratulations! You are now ready to start creating your custom bootable CD!

Creating Your Bootable CD

Use the emulator to fetch the various files you want to put on the CD. If you are on a computer that doesn’t natively support resource forks, such as Linux or a Windows PC, it is best to move any files onto the emulator in a protective container format such as a .bin file, later versions of .sit (SIT5) or some disk image formats. Some disk images can be “added” to the emulator as other emulated hard disks in the same way we added the “Bernie” disk above. Care must be taken as classic Mac OS files contain both a data and a resource fork. The resource fork is not usually recognised by other computer platforms and they are prone to “strip” the resource fork from a file. Doing so severely corrupts most Mac OS files, for example, 68k applications have all of their executable code in the resource fork and removing it… removes the application’s ability to do anything at all, irreparably. Assuming the files you are working with were correctly prepared in the first place (this is sadly more frequently an issue than it should be), extracting the archives / encoded files from within classic Mac OS itself is usually the best, although not only, solution.

Personally, I store files I want to transfer to the emulator in a specific folder on my hard disk, then use the “Unix” volume within the emulator to copy them over to the volume “Bernie”. Here, I extract them (the tools provided within “Utilities” should help in many cases) and then copy the files onto “WorkingVolume”, and arrange them as I want. Note that the window arrangement you leave the windows in will be burned forever into the CD, so it is usually good to move windows up to the top left corner to ensure that they are easily accessible even on a computer with a small screen. In the following example, I have copied a number of items from the “Bernie” disk over to “WorkingVolume”. This includes the System Folder, as this will be the bootable operating system on my CD. This System Folder is a good starting point for bootable disks as it is a universal “minimal install for any computer”, although older computers, such as non-32 bit machines like the SE/30, are not compatible with Mac OS 7.6.1 by default.

07 Setting Up a CD
07 Setting Up a CD

Once you are happy with the contents, icon layout, window positioning and have verified that everything you have placed on the disk works as expected, you are ready to start creating a CD disk image. To do this, open the “Toast Deluxe 4.1.3” folder on the Bernie disk. Then launch the application “Toast Deluxe 4.1.3”. You should see a window similar to the one shown in the second image immediately below. Select “Mac Volume” from the drop down menu, and then drag the “WorkingVolume” disk icon (or whatever you have called your working volume) into the area under the drop down menu. The window should update to similar to the provided image, with the name of your volume following the bold text says “Data: “. Note that Toast will use the CD ROM or CD DVD ROM Extension from the booted Operating System as the CD Driver on the CD it writes, so it needs to be made certain that a version is used which is compatible with the computer you plan to boot. In some cases it might be best to create the custom disk image on the actual machine itself if possible.

Click the button “Data…” and verify that the “Bootable” checkbox is checked if you intend to create a bootable disk. If you do not intend your disk to be bootable, you do not need to do this step. Click “OK” to close this dialogue box again.

10 Select Volume
10 Select Volume

As per the following two images, select “Save as Disc Image…” from the “File” menu, and enter a name for your disk image. Note that you will want to finish the file name with “.iso” – this is important for other operating systems, such as windows, but also serves as a reminder when you are managing your files. You can either save the file on “Bernie” if there is 650MB free, or alternatively save directly to the host by navigating to a suitable location on the mounted “Unix” volume.

Congratulations! You now have a disk image, hopefully formatted correctly to boot a classic Macintosh computer!

Burning the Disk Image

01 K3b Screen
01 K3b Screen

On Linux, launch K3b (which you installed at the beginning of these instructions) and select “Burn Image…” from the “Tools” menu. Near the top of the window under the text “Image to Burn”, to the right of the combo box, is a small button with a folder icon. Click this to use a file open dialogue box to select the CD disk image, in my case “WorkingVolume.iso”, which you intend to burn to a CD. When you select the disk image, you will get an error dialogue box as shown below in the second of the three images – Click “Yes”. This dialogue box is generated because the software doesn’t recognise the format of the disk image, because it is a classic Mac OS disk.

At this point, it is probably a good idea to insert a blank CD-R into your optical drive if you haven’t already. Once the computer has finished probing the disk and the window updates, in the “Burn Image – K3b” window, set “Speed” to the lowest speed offered and click “Start”.

A Real Macintosh IIci Booted from the Example CD

Installing Mac OS 9 on an 800Mhz iBook G4

Installing Mac OS 9 on an 800Mhz iBook G4

When Apple released the first iBook G4, they decided to terminate support for Mac OS 9, requiring users to run 10.3 or 10.4. This is a shame, as personally, I feel a 12″ iBook G4 is an excellent machine for running retro software. This said, there are a number of ways around this difficulty. The following is a record of how I did it.

I’ve seen other instructions which are more complex, noting that there are a number of variants of the G4 iBook. The following instructions are confirmed working specifically on the 12″, 800MHz iBook G4, but may work on other variants of the G4 iBook. Note that the last of the G4 iBooks have a different graphics chipset, which isn’t able to be accelerated within Mac OS 9.

My method made use of another, older, Macintosh, which supported booting Mac OS natively. I used this to format the iBook’s hard disk and include the Mac OS 9 driver, as the option was suppressed when booting the iBook from 10.3 and 10.4. For the remainder of this post, this machine will be referred to as the “other Macintosh”

WARNINGS

This process requires you to format your hard disk. If you have files you want to save, it is recommended that you do a complete backup before starting the process.

These instructions assume you have access to the other Macintosh.

Mac OS 9 is unsupported by Apple on this machine. There are a number of things that wont work. This potentially includes, and may not be limited to… LCD backlight brightness, the AirPort card, USB 2 (ports work as USB 1.1).

It has been noticed that sometimes the computer glitches when it boots and the mouse wont work. This is the same with OS 9 hacked Mac Minis. Usually the machine behaves following a forced restart.

By default, the mac will run at a lower, energy saving, clock speed. Mine defaulted to 450MHz. I left it like this because that is more than enough for almost any classic software I want to run. It is possible to bump this to the full 800MHz by entering the correct commands in Open Firmware, but that isn’t covered here.

Mac OS 9 does not appear in the Startup Disk Control Panel in Mac OS X on these machines.

There are other guides elsewhere on the internet that attempt to fix some of these issues, or allow you to undertake the process without the other Macintosh. The method described here is intended to be fairly basic and easy to follow, with the single complexity of requiring the other Macintosh

Required Hardware

  • An 800MHz 12″ iBook G4
  • A FireWire cable
  • A Macintosh with a FireWire port that is able to natively boot Mac OS 9.x or older

Getting the Needed Files

Download the following, and move them to the other Macintosh. The first link would be best burnt to a CD, otherwise software for mounting an iso disk image, such as Toast or Virtual CD/DVD-ROM Utility, can be used.

Preparing the Hard Disk

I spent quite a while faffing trying to follow instructions on correctly formatting the hard disk that I had found elsewhere. They didn’t work because the author assumed that the iBook was able to format its own disk including the Mac OS 9 Disk Driver, which it isn’t. The solution that worked for me was to connect the FireWire port of the iBook with the FireWire port on another, older Macintosh which supports booting from Mac OS 9 and formatting using that machine and FireWire Target Disk Mode. There are more complex methods detailed elsewhere, designed to trick the iBook into booting from a CD. I’ve not covered those because the following is quicker for me and doesn’t require messing with Open Firmware.

  1. Connect a FireWire cable between ports on the iBook and the other Macintosh.
  2. Power on the iBook G4 you plan to reformat while holding down the ‘t’ key on the keyboard. The iBook should display a FireWire logo on the screen.
  3. Power on the other Macintosh, in either Classic Mac OS or Mac OS X.
  4. The iBook should mount as an external hard disk in Mac OS X. It likely wont appear on the desktop in Mac OS 9.2.2 or older, but that is probably OK.
  5. I recommend creating two partitions (although this isn’t a requirement – you can use a single partition as long as your disk isn’t too large for OS 9), making the first one small (at least 2GB, no more than 180GB (there is an approximately 190GB limit)). In Mac OS X, use Disk Utility to select the iBook hard disk and format the hard disk using the “Partition” tab, making sure you select the “Install Mac OS 9 Disk Drivers” checkbox. Alternatively, in classic Mac OS, use the Utility “Drive Setup” to do the same, the Mac OS9 driver will be installed automatically using Drive Setup.
  6. Don’t power down either machine as the next section continues from this scenario.

Installing Mac OS 9.2.2

  1. Mount the “Mac OS 9.22 Unsupported G4.iso” CD or disk image on the other Macintosh
  1. On this disk, launch the “Apple Software Restore” application and restore the software to the prepared Mac OS 9 iBook partition
  2. Once the restoration has completed, extract the ATYVia_9200M9.sit archive (which you downloaded and transferred independently of the CD image).
  3. Drag all of the contents of the archive onto the iBook Mac OS 9 partition’s Extensions folder – it will ask if you want to replace some existing files, you do want to replace existing files.
  4. If there is a folder called “Multiprocessing” in the Extensions folder, delete it.
  5. Power down the “other” Macintosh and then the iBook and disconnect the FireWire cable.

Booting Mac OS 9.2.2 for the First Time on the iBook G4

Power on the iBook G4 while holding down Cmd+Opt+P+R. This will clear the PRAM and set the computer to default settings. Success will be indicated by a second chime as the iBook restarts itself – you can release the keys after hearing the second chime.

At this point, the computer will probably boot into Mac OS 9.2.2, but if it doesn’t, restart and hold down the option key while starting. This should present you with a boot selection screen. It takes an age to finish loading because it searches for any available local and network operating systems. Once it does finish searching, the cursor will change from a watch to a pointer. Select the Mac OS 9 disk and click the arrow to continue booting.

Congratulations, you have a G4 iBook that boots the Classic Mac OS, and has accelerated 2D and 3D graphics.

Installing Mac OS X

You can install Mac OS X (probably 10.3.x or 10.4.x depending on preference) if you want to. Whatever you do, don’t erase the hard disk or you’ll lose your good work. I’d install Mac OS 10.4 on the second large partition that I prepared when I formatted the iBook’s hard disk.

Note that the Mac OS X “Startup Disk” Control Panel wont show Mac OS 9 as an option. This can be solved by powering on while holding the option key to get the boot selection screen, installing “XPostFacto” and using it as an alternative to Startup Disk, or by doing some terminal hacks that can be found elsewhere on the internet and which make Startup Disk work correctly. I just use the first two options and haven’t investigated the third.

The Mac OS 9 Startup Disk Control Panel works as normal and you can select between Mac OS 9 or Mac OS X there.

Special Thanks

Huge thanks to the folks at MacOS9Lives for all their amazing work getting Mac OS 9 working on various unsupported computers. This post is basically just instructions on how I used their hard work. All credit for this being possible goes to them. Please visit the following thread for more information : http://macos9lives.com/smforum/index.php?topic=2143.0

Author Notes – Things I need to update this page with…

  • You should make a little Open Firmware patcher to automatically set the processor to 450MHz / 800MHz
  • You should modify the installer disk image to include the correct graphics drivers and remove the Multiprocessing folder