Random lock ups and all. Not sure if it's logic board or card issue, but Bluetooth is fine just not airport. I disable airport and the G4 iBooks are rock solid on Very familiar with the inner workings of LeopardAssist. When I rewrote it and released LeopardAssist 3 earlier this year, I looked into the possibility of tweaking the firmware to have the machine identify as a different model.
Unfortunately I haven't found anything in the iBook's Open Firmware or Device Tree that would allow me to mess around with the model identifiers at this stage.
Mac Error Codes
I haven't worked on this at all in the last few months, mainly focused on my classes and getting this site off the ground. I'm hoping to revisit it at some point in the near future, but it would be nice to have some more knowledgeable people looking into this as well. At the moment I'm probing around in the dark for anything that looks like it could possibly be a hurdle to completing a successful boot.
Reliability is the main reason I'm using an iBook G4 for this attempt. If OS 9 could be made to run on a machine like the iBook G4, it would be a perfect machine for it. Compact, reliable and fast. I'll document that fix for this site soon as well. And yes, Mk. I haven't done much with it, but it's here. I have tentatively promised it to someone else, but if that falls through and you're interested, we'll see how it goes.. Main Macs: So, first post should just introduce myself where appropriate But been following this thread and a few on other forums for some time and finally caved and purchased a MDD FW and a board from a FW I was luck enough to find and put into the FW case so I could run classic.
Basically, purchased the machine strictly to run OS 9. Reason I tell that story, as it might be related as 9. But back then there were a few tricks that later became part of a tool to run Mac OS 9. The search for similar info led me to an interesting thread on another forum in the last few months that many of you may want to take a glance at:.
Yeah, I cheated and made the posts on each almost identical. Great to see that MacOS9Lives is aware of this thread. Unfortunately I'm still stuck at the "error type " I was encountering earlier, and without all that much knowledge of how the OS 9 gusd and gtbl resources work or even where to start with them, I'm not entirely sure how to proceed.
That said, it already boots on an unsupported iMac G4 with this method, and by the sound of it a boot on the MDD FW may be achievable as well. In addition to the existing modifications above, I decided to fake the model identifier for the machine to see if that's where it was getting stuck. Like so:. The following line sets the model property to that of another machine, in this case PowerBook4,3.
After hitting return after mac-boot , the machine started booting up into Mac OS 9, and incredibly, the Error Type error was cleared. Finally, we've reached the "Starting Up There are still some caveats. As soon as it starts loading extensions, the system crashes and drops into MacsBug. The next stage is to see whether it'll boot with extensions disabled.
With extensions disabled, the boot makes it all the way up to where the desktop should be displayed. I'll continue probing around and see what I can find. Using the method I outlined in the above post, I instead decided to try booting the iBook from an OS 9 iMac installation disc. With the disk in the drive, I replaced mac-boot with boot cd: No crashes during startup whatsoever. Machine ID according to OS 9 is However it's still extremely limited. Ethernet is detected, but I haven't determined whether it's functional yet.
FireWire is present and appears to be functional. Battery status appears to be detected and reporting correctly. Video is running with a limited colour palette and it doesn't seem like the sound is there either. Interestingly, the internal hard drive is not detected.
Guide to Classic Mac Error Numbers
Keep in mind that this is currently running from a Mac OS 9 installation disc with almost no extensions, and one made for an iMac G3 at that. If I can install the system and activate additional extensions, the iBook may be a little more usable. If success is encountered there, it'll then be a case of seeing where Mac OS checks for the model identifier likely PowerBook4,3 somewhere in the system and tweaking it so the system can boot without the need for Open Firmware commands.
I've moved some of the extensions back into place and removed MacsBug from the installation OS9General on the internal hard drive. Now, the machine completes a full boot to the desktop. In addition to everything that was working above:. I'll continue installing extensions and see if the situation improves. Updating to version 2. The iBook G4 can now play sound under OS 9! Almost everything is working correctly, or is at least usable.
The machine does however still have one "small" issue. Whenever the machine boots, around the time it starts loading extensions, it switches to x Looking in the Monitors control panel shows that the machine is configured to run at x , but it doesn't seem to be working for some reason. One theory I had and was able to confirm is that the machine seems to think a second display is connected, and this "phantom" display is only capable of a x resolution.
Because it's mirroring the internal display, the internal display also defaults to x Interestingly it didn't seem to occur when booting from the iMac OS 9 installation disc, however that was also incapable of displaying Millions of colours. Adding credence to the phantom display theory, I can temporarily work around the problem with a series of Open Firmware commands from the Screen Spanning Doctor website:.
This forces the phantom display to behave as its own separate screen, without mirroring the internal display. This allows the internal display to run at its native resolution. As you can see, in the Monitors control panel, the second display is still believed to be present in this mode. If I could trace down the source of these problems within the system including the model identifier check , I could eliminate the need for Open Firmware commands entirely and build a pre-imaged version of Mac OS 9 that would work on this machine.
This would without a doubt be the most ideal scenario, since at the moment a loss of power to the NVRAM will clear the commands and render the system unusable until they're re-entered again.
This is awesome Like you said last night Way to go. I've managed to fix the Error Type issue.
The issue was extremely easy to fix, once I found it. It doesn't necessarily mean that OS 9 is easy to install on an unsupported system. The hard disk still needs to be formatted with the OS 9 Disk Drivers, and the System Folder still needs to be blessed.
- Error type 41 upon startup of Imac - Ars Technica OpenForum.
- Guide to Classic Mac Error Numbers?
- G3: time synchronizer error type 41 - Apple Community.
- war commander cheat engine 6.2 for mac.
That'll be my next challenge. Once the ROM is cleaned up, if anyone's willing to do some testing on other machines, perhaps we can make this a group project. I believe this may stand for name table. It contains all the names of the machines associated with the model identifier. These are used around the system, in applications like System Profiler for example. This doesn't actually do anything for the performance or usability of the machine, but it's a nice touch that makes the modification a little more official.
That and it's interesting to see a machine name in OS 9 that we would never have expected before. I am having some considerable difficulty writing additional models into the ROM however. It seems if you edit the table even slightly, even if the syntax is correct, the ROM won't boot the machine afterwards.
Welcome to Low End Mac
I've even had instances where I copied a ROM to the iBook and had it boot, only for the machine to stop booting after a restart. Still no dice. The ROM simply doesn't like being edited. I'll revisit it when I'm not as tired perhaps. I achieved this by removing the individual model identifiers eg. Compare the screenshot below with this image from the post above.
You can see the btbl resource has been cut down considerably. This wasn't as simple as just replacing the strings. Making any changes to the entries resulted in the ROM being unable to boot. I discovered that this is due to the byte that comes immediately before the string. If you take a look at this image:. This number is the number of characters in the string. This creates the possibility of booting Mac OS 9.
I'm still performing some testing at this stage, but I should have more updates here shortly. I thought, with the success of booting OS 9 on the iBook G4, that perhaps I'd try a couple of other machines. The only other machines I have are much newer and have dramatic architecture differences, but I thought I'd have some fun here.
So, how about a Mac Mini Late with a 1.
With the Generic ROM, the system doesn't restrict a startup attempt. However, attempt to boot into Mac OS 9 and So while we're being ridiculous here, how about a Power Mac G5 Quad? So what happens if we attempt to boot Mac OS 9? As soon as the machine even attempts to start loading the ROM, it crashes and produces video corruption all over the screen.
If I restart and boot to Open Firmware, then attempt to boot from the Mac OS 9 drive from there, the output is a little more useful:. This is something I need to restate. However as the iBook G4 proves, the modified ROM does allow OS 9 to start on some unsupported machines - especially those that have similar hardware to supported machines. Your setup has two virtual drives in SheepShaver; one for OS 9, one for your other apps. These are where you do all your OS 9 stuff. If you need the file created by your application on the host machine, that's when you use the OS 9 Finder to copy it to the Unix drive so that it's available in the host's Documents folder.
As for deleting the software: Based on your prefs file, these are the important lines: Any documents you want to transfer to your OS 9 SheepShaver setup from your host will go in the Transfer folder. Then you can grab them from the Transfer folder in your host to do whatever you want with them. Third, it's probably a good idea to append.
Then you always have the option of just opening the disk images in OS X when SheepShaver isn't running, and you have access to all the files in those images. If you want to modify the file, you need to copy it back to an OS 9 virtual disk -- this would be one of the two I previously indicated, however you've named them internally in OS 9.
I think you may be a bit confused about what you're doing when you emulate OS 9. On your physical computer, you run an operating system that ties all the physical parts together and enables you to operate other software. SheepShaver is the equivalent of that physical computer, but written in software so that it runs inside the physical computer's operating system. Instead of a physical hard drive like a computer has, SheepShaver uses files that are stored on the physical hard drive.
We call these "disk images" because they are a snapshot of exactly what we'd see on an equivalent physical drive. So when you start up SheepShaver, it creates its virtual hardware, and one of the things it does is opens those disk image files as if they were physical drives. Once they're open, SheepShaver can read and write data there. Your MacOS9 drive is where the OS 9 operating system for the virtual computer SheepShaver is stored, and the operating system is loaded into SheepShaver's memory from this location, allowing SheepShaver to boot and display data on its virtual screen which is then displayed on your computer's real screen.
When you install software on SheepShaver, you're installing it on one of these virtual disks that is then saved as a file on your actual computer. When you save a file from an application running in SheepShaver, you should be saving it back to this virtual disk. The file that encompasses this disk is on your actual computer, so it is trivial to back up the entire file. OS X has the ability built-in to also mount these virtual disk images as actual disks -- Disk Utility and it's back end software is used to manage these images.
Jump to: Jan 11, Posts: Wed May 23, 4: Mar 27, Posts: Thu May 24, 5: Apr 2, Posts: Thu May 24, 6: Feb 14, Posts: Eric Managing Editor et Subscriptor Tribus: Park Ridge, Illinois Registered: Mar 21, Posts: A hollow voice says "plugh. Apr 19, Posts: NWI, Indiana Registered: Apr 15, Posts: Sat May 26, 3: Longhorn Country Registered: Nov 4, Posts: Sat May 26, 4: Apr 30, Posts: