-No Fw800, No USB 2... but I had read long time ago that this is posible.I had never read that. If it is true, it should not matter what model of MDD to buy for OS9.
-Format an HD with Mac Os 9 drivers.
-Use a Mac Os ROM version 10.2
-Force the startup with this HD.
... I never tested this, but may help ...
I had never read that. If it is true, it should not matter what model of MDD to buy for OS9.
Pci usb2 cards work in OS9 as usb1
Pci Fw800 cards work in Os9 as fw400
I asume you mean you cant use onboard usb2.0 ports and fw800.
This is like an old wound that never heals...For a OS9 lover that had bought the wrong MDD, sure it never heals... ;)
We are searching for it :)
So... in conclusion... any Mac gurus that have a MDD FW800 diagnostic CD, please extract everything needed and create a Bootable complete version of OS 9 for us... we look forward to posting a working copy by the end of the week... or month... or year :)
There is "another" ROM that allow the "Spring 2003" iMac G4/800 "Flat Panel" X Only, to boot into Mac Os 9.
I've taken a little time comparing that special ROM (convenient called "Custer") and Mac Os ROM 10.2.1 and I always thought that are almost the same thing. My therory is that the Custer ROM upgrades Mac Os ROM 9.8.1 to 10.2.1, but I may be wrong.
As I haven't any FW800 to test it. I can share This ROM to any one that want to experiment. ...and who knows...
https://discussions.apple.com/message/13022080#13022080 (https://discussions.apple.com/message/13022080#13022080)
So... in conclusion... any Mac gurus that have a MDD FW800 diagnostic CD, please extract everything needed and create a Bootable complete version of OS 9 for us... we look forward to posting a working copy by the end of the week... or month... or year :)
which g4 has usb 2.0 :o
u can have usb 2.0 in win98se ;)
I have uploaded the OS9General FW800 file to the file section but heres the differences betweenIs that "OS9General FW800" the AHT 2.0.1 ? Is the MacOS9 for MDD'03 EDU?
the system files in the system folder for the OS9General Image for the FW400 computers
and the FW800 computers;
Although I also have the install DVD for the PMG4 FW400 that has AHT2.0.2 for those introduced inCan you show us these
2003.
A friend of mine has OS9 running native on his G4 FW800, even though, officially, this is not possible.
To run 9.2.2 on MDD and FW800, you need Mac OS ROM version 9.6.1 and Quicktime 5.02. They are in a file called OS9General.dmg, which decompresses to the last release of the System Folder for OS9. You can get it here:
http://macintoshgarden.org/apps/macintosh-system-922-1021-power-macintosh-g4-mirrored-drive-doors-mdd
That page gives these links:
Mac OS ROM 9.6.1: http://www.megaupload.com/?d=MT4DOQKV
Mac OS 9 MDD DMG: http://www.megaupload.com/?d=XIZRTZXW
I sent my friend a CD containing OS9General.dmg. He loaded it into his FW800 and installed OS9 onto his hard drive. Here's the trick: that hard drive already contained an OS9 driver (installed by another G4).
Neither the OS9 or OSX install disks will put an OS9 driver onto a hard drive in a FW800. THAT's why - the only reason - you "cannot" run OS9 native on a FW800.
When running OS9 native on his FW800, my friend reports that his OSX drive does not mount. Equally, when running OSX, the OS9 drive does not show up. With X the default, my friend uses the Option key at startup, to boot into 9.
I'm wondering if someone with a G5 could try out the same method, to see if OS9 will run native on a G5. Please let us all know.
My friend, Howard Miller, is presently a sheep farmer, but he used to be an Apple dealer in the 1990s. He has a hoard of old Macs and Mac parts, printers, scanners etc that he traded in; if anyone is looking for such, please let him know. His address is mailto:[email protected]
Peter
Apple recently posted a new file to its private Apple Service Provider web page (accessible only by account-holding Apple technicians and resellers) titled "MacTest Pro for Power Mac G4 (March 2003) Version 7.8.1 supports all iMac (Flat Panel) 15 inch systems only."
The file is a CD image which can be downloaded and to a disc, then used as a startup disk. Testing on a "Mac OS X-only" flat panel iMac system revealed that the image properly booted Mac OS 9.
Users can then copy a stripped-down Mac OS 9 system folder to their hard drive, and select it with the "Startup Disk" System Preferences pane, delivering a Mac OS 9 bootable internal disk.
It appears that a new MacOS ROM file (ver. 9.8.1) is what enables booting from the image.
Of course, this solution is only readily accessible by Mac service providers, but it shows that Mac OS 9 boots are not impossible on Apple's new machines. Also, please note that Mac OS 9 startup was not tested on any machines other than the 2003 flat-panel iMac. This method has been independently verified.
: *This model is capable of using Mac OS 9 applications within the Mac OS X "Classic" environment provided with Mac OS X 10.4.11 "Tiger" and lower ("Classic" is not supported starting with Mac OS X 10.5 "Leopard"). It cannot boot into Mac OS 9.
When Apple declared the end of OS 9 bootablity, schools all over the country demanded extra time to finish their conversion to Mac OS X, especially the Server infrastructure. They needed new Macs, but could not yet support them on their older Servers, and could not convert to newer Servers without more time. There was ONE model issued later, only for the Education market, with a single 1.0GHz processor AND a FW800 port that could still boot OS 9.
There is thought to be a special version of the Mac OS ROM file (developed for that Mac) and few more additions that may be able to be coaxed to boot OS 9 directly on a FW800 G4. That Mac OS ROM file was also said to be found in an Apple-only diagnostic package that was never released to the outside world.
That is all the info I have. I have never tried to track down the files or verified their existence.
Chris as I mentioned in your post new Quicksilver I put up photos for a 1ghz fw800 mdd model computer which I paid 0.99c on ebay - however there was no classic system on it - no macos9 ROM.
according to this post in a google group it should be easy:QuoteNeither the OS9 or OSX install disks will put an OS9 driver onto a hard drive in a FW800. THAT's why - the only reason - you "cannot" run OS9 native on a FW800.
When running OS9 native on his FW800, my friend reports that his OSX drive does not mount. Equally, when running OSX, the OS9 drive does not show up. With X the default, my friend uses the Option key at startup, to boot into 9.
I'm wondering if someone with a G5 could try out the same method, to see if OS9 will run native on a G5. Please let us all know.
...put your FW800 into Disk Target Mode, connect it to a Mac Os 9 Mac, and reformat its HD with Mac Os 9 drivers as you'll do whith a normal FW external enclosure.
Then you can drag-install a valid system folder on the FW800 HD (still in DTM mode) and restart your Mac os 9 machine whith the HD of the FW800 (still in DTM mode) to test this HD boot.
Shut down both computers, unplug FW cable, cross your fingers and start the FW800.
Good luck.
I think that Mac Os ROM 10.2.1 will do the trick. But I never tried to boot a FW800 with Mac Os 9...
If you need another ROM version, just ask, I have an almost complete colecction :)
I'll hope to have explained it well...
Well peoples no go - no system folder with the ROMs that I have booted into macos9 on the FW800 - I installed four system macos9 versions with the HD wiped clean each time with Norton utilities Wipe Info.wasnt the whole point to initiaize the drive in os9 on a working g4 everytime
No go guys with 9.5.1, 9.7.1, 10.2.1, install CD of macos9 with version 8.9.1. none worked.
Anymore suggestions?
This supports what I was thinking ages ago that there must be a ROM on the motherboard for OS9 to use to boot into. It is not on the CPU because you can use a FW800 CPU on a FW400 board and boot macos9.
this what I did:
target disk mode from macos9 from a mdd g4 fw400 - wiped HD of FW800 computer using Norton Utilities 6.0.3. Booted into Tiger from mdd g4 fw400 computer and Target Disk Mode reformatted drive with OS9 drivers and installed MDD400 OS9General(then booted) - MDD800 OS9General(then booted) - System folders with different ROMS(then booted).
- The computer only booted up to the question mark on the boot screen - that
I have tried this ages ago and if I can recall same problem happens.
I recall I am revisiting this boot problem - never got it before maybe my
last hope that it may happen this time around...:)
Maybe the cue in the open firmware is the FW800 port on the G4 and G5 models? As soon as that is detected the switch happens - question mark? Who knows?
Tried the MacOs922custer image - error in expansionFile fixed!
"The Mount Image operation did not complete. (130)
The checksum is invalid.
I swear the real problem lies not in the rom but in the openfirmware version
maybe u could hack openfirmware to boot from that device much in the way that they do this usb drive:
https://sites.google.com/site/shawnhcorey/howto-boot-apple-powerpcs-from-a-usb-drive-in-open-firmware
more on openfirmware:
https://www.youtube.com/watch?v=u9OMOHl73IE
https://www.youtube.com/watch?v=K_khaWNGESs
http://lowendmac.com/2007/fooling-the-os-x-10-5-leopard-installer-with-open-firmware/
i attempted to get this up and running today. no chance. i also think we have to hack the open firmware :-)
Production informationwhy dont u compare the BOOT Rom versions of the fw400 vs the fw800?
ROM revision: $77D.44B5
Boot ROM version: 1.1f4
Mac OS ROM file version: 1.3
Serial number: XB00000000XXX-XXX
Software bundle: 694-1137
Sales order number: Not applicable
Firmware Update 4.2.8 includes improvements to starting up Mac OS X from the local hard disk, FireWire target disk mode, network startup, gigabit networking (on systems with gigabit hardware), and system stability. This update also adds support for additional security options that allow the Open Firmware to be password-protected.does this enable target disk mode for powermac g3s? nope it says AGP g4 models only
So if the Fw4oo firmware could be loaded into the Fw800 firmware we would have a
macos9 bootable system with working fw800 and usb2 ports wouldn't we - since these ports are opened up at the level of openfirmware.
So the openformware Boot rom opens the ports to allow input/output - and even when I tried to boot up at this point from o/f boot rom it wouldn't - so it must the boot rom of the computer not the openfirmware boot that is the culprit because both openfirmware boot ROM are the same - refer to photo jpg fw400a and fw800a.
1. Shut down.
2. Start up and hold down cmd-opt-o-f
3. The Boot ROM Revision is displayed at the top of the screen.
4. Type "bye" followed by <return> to continue starting up in Mac OS.
This is like an old wound that never heals...
also apparently any linux install will install yaboot (boot loader) into open firmware as well. maybe we can try to install linux on a fw800 and from yaboot we get the option to boot os9?Yaboot is installed on the hard disk not in firmware and it can't load Mac Os 9 AFAIK :(
also apparently any linux install will install yaboot (boot loader) into open firmware as well. maybe we can try to install linux on a fw800 and from yaboot we get the option to boot os9?Yaboot is installed on the hard disk not in firmware and it can't load Mac Os 9 AFAIK :(
(http://macos9lives.com/smforum/index.php?action=dlattach;topic=762.0;attach=248;image) | (http://macos9lives.com/smforum/index.php?action=dlattach;topic=762.0;attach=250;image) | (http://macos9lives.com/smforum/index.php?action=dlattach;topic=762.0;attach=252;image) | (http://macos9lives.com/smforum/index.php?action=dlattach;topic=762.0;attach=254;image) |
packages: deblocker, disk-label, obp-tftp, telnet, mac-parts, mac-files, hfs-plus-files, fat-files, iso-9660-files, bootinfo-loader, xcoff-loader, pre-loader, elf-loader, usb-his-class, usb-ms-class, usb-audio-class, sbp2-disk, ata-disk, atapi-disk, bootpath-search, terminal-emulatorif u look carefully it seems the rom has a "toolkit" of certain software packages built into itself..
The Macintosh has used a more or less unchanged boot mechanism for over a decade. Even
with initial introduction of OpenFirmware, little changed. The advent of the iMac, and later Mac OS
X, has altered the boot sequence significantly. This paper contains a cursory look at OpenFirmware,
the booting mechanisms used by various operating systems that run on the Power Macintosh (such
as Linux, NetBSD and OpenBSD), as well as the different booting mechanics of several generations
of Macintosh hardware. Particular emphasis will be paid to the boot process of Mac OS X (from the
firmware up to early kernel initialization) and its bootloader, BootX.
The child nodes under /packages are specific support packages necessary for bootstrapping an operating system.
also apparently any linux install will install yaboot (boot loader) into open firmware as well. maybe we can try to install linux on a fw800 and from yaboot we get the option to boot os9?
openfirmware 3.1.1
what does your mac say for dev /rom/boot-rom .properties
name boot-rom
write-characteristic flash
model powermac1,1 version 1.1f4 built on 04/09/99 @ time
BootROM-version
BootROM-build-date
result
info
boot [boot-device [boot-file]] [options]
boot-device primary bootloader location
boot-file kernel location
options flags passed to the kernel (see below)
boot hd:,macos.rom \\:tbxi
with the macos.rom on the hard drive , i guess in the root?boot hd:,\System Folder\Mac OS ROM \\:tbxi
and see if it boots normallyNew World ROM Macs are the first Macs where direct usage of the Open Firmware (OF) subsystem is encouraged. Previous PCI Power Macs used Open Firmware for booting, but the implementation was not complete; in these machines OF was only expected to probe PCI devices, then immediately hand control over to the Mac OS ROM. Because of this, versions 1.0.5 and 2.x had several serious bugs, as well as missing functionality (such as being able to load files from a HFS partition or a TFTP server). Apple also set the default input and output devices to ttya (the modem port on beige Macs), which made it difficult for normal users to get to Open Firmware; to do so it was necessary to either hook up a terminal, or change the Open Firmware settings from inside Mac OS using a tool such as Boot Variables or Apple's System Disk.
The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
One major difference between Old World ROM Macs and New World ROM Macs, at least in classic Mac OS, is that the Gestalt selector for the machine type is no longer usable; all New World ROM Macs use the same mach ID, 406 decimal, and the actual machine ID is encoded in the "model" and "compatible" properties of the root node of the Open Firmware device tree. The New World ROM also sets the "compatible" property of the root node to "MacRISC2" (machines that can boot classic Mac OS using "Mac OS ROM") or "MacRISC3" (machines that can only boot OS X or another Unix-like system).
It is somewhat easier to boot a non-Mac-OS operating system on a New World system, and indeed OpenBSD's bootloader only works on a New World system.
The simplest way to distinguish a New World ROM Mac is that it will have a factory built-in USB port. No Old World ROM Mac had a USB port as factory equipment; instead, they used ADB for keyboard and mouse, and mini-DIN-8 "modem" and "printer" serial ports for other peripherals. Also, New World ROM Macs generally do not have a built-in floppy drive.
BootX
BootX is a Mac OS-based bootloader which is only usable on Old World Power Macs. It requires a bootable Mac OS installation.
The Mac OS X bootloader is also called BootX. These are very different programs written by different people, with an unfortunate namespace collision.
boot cd:,\install\yaboot
and its booting;)"Other Open Firmware settings can be changed using the nvram command while the system software is running." -- http://en.wikipedia.org/wiki/Open_Firmwareif this lets u write to the flash ram to save settings then maybe its possible to open a file on the harddrive and load it as a new version of the rom... first step would be figuring out how to save the current rom as a file tho
The linux way goes to nowhere. Yaboot is chained to BootX.From PPC luddite guide to debian part 5:
BootX instead of load Mac Os ROM it load Yaboot, and Yaboot load Linux or Mac Os X but no Mac Os 9.
The linux way goes to nowhere. Yaboot is chained to BootX.From PPC luddite guide to debian part 5:
BootX instead of load Mac Os ROM it load Yaboot, and Yaboot load Linux or Mac Os X but no Mac Os 9.
"One bug that qualifies as having been around long before is the infamous disappearing partition bug. Every time you run through the Debian installer, it somehow messes up your Mac OS 9 drivers making any OS 9 partition unbootable. It was a nasty surprise for me, but let me take away all the suspense. Simply boot with your Mac OS install CD, launch Drive Setup, highlight your hard drive from the list, and from the Functions menu select Update Driver. Problem solved. You will now be able to boot into OS 9."
"Another thing you should know about OS 9, never use the Startup Disk control panel to choose a startup disk. It'll mess up yaboot and you won't be able to boot into Linux. If this should happen to you, reset the pram (hold down command + option + p + r keys on startup) and yaboot will be restored.
Dual booting between Linux and OS 9 also has an issue with system clocks. While your Debian system is set to UTC time, your Mac system is set to local time, so though your Linux time may be correct, you Mac clock can be several hours off. Solve this with:
sudo nano /etc/default/rcS
and change UTC=yes to UTC=no. Now when you boot into OS 9, the time should display correctly. Also, if you ever need to change timezones in Debian, you can use:
sudo dpkg-reconfigure tzdata"
If you are using the computer in a multi-user environment and the other users prefer Mac OS X you can (easily) configure yaboot to automatically load Mac OS X or OS 9 instead of Ubuntu. -- https://help.ubuntu.com/community/YabootConfigurationForMacintoshPowerPCsDualBoot
http://lowendmac.com/2010/create-a-triple-boot-mac-with-os-9-os-x-and-linux/
It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI.
The tool can be used to flash BIOS/firmware images for example -- be it proprietary BIOS images or coreboot (previously known as LinuxBIOS) images.
you cannot install anything on a live cd!sure u can -- it just wont be there if u reboot ..
Usage: ./flashrom [-h|-R|-L|-p <programmername>[:<parameters>] [-c <chipname>]
[-E|(-r|-w|-v) <file>] [-l <layoutfile> [-i <imagename>]...] [-n] [-f]]
[-V[V[V]]] [-o <logfile>]
-h | --help print this help text
-R | --version print version (release)
-r | --read <file> read flash and save to <file>
-w | --write <file> write <file> to flash
-v | --verify <file> verify flash against <file>
-E | --erase erase flash memory
-V | --verbose more verbose output
-c | --chip <chipname> probe only for specified flash chip
-f | --force force specific operations (see man page)
-n | --noverify don't auto-verify
-l | --layout <layoutfile> read ROM layout from <layoutfile>
-i | --image <name> only flash image <name> from flash layout
-o | --output <logfile> log output to <logfile>
-L | --list-supported print supported devices
-p | --programmer <name>[:<param>] specify the programmer device. One of
internal, dummy, gfxnvidia, drkaiser, satasii, serprog, buspirate_spi,
pony_spi, nicintel, nicintel_spi, ogp_spi, linux_spi.
You can specify one of -h, -R, -L, -E, -r, -w, -v or no operation.
If no operation is specified, flashrom will only probe for flash chips.
ubuntu@ubuntu:~/Desktop/flashrom-0.9.7$
ubuntu@ubuntu:~/Desktop/flashrom-0.9.7$ ./flashrom -p internal
flashrom v0.9.7-r1711 on Linux 2.6.32-21-powerpc (ppc)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK.
Processor detection/init failed.
Aborting.
Error: Programmer initialization failed.
ubuntu@ubuntu:~/Desktop/flashrom-0.9.7$
ubuntu@ubuntu:~/Desktop/flashrom-0.9.7$ ./flashrom -p dummy
flashrom v0.9.7-r1711 on Linux 2.6.32-21-powerpc (ppc)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
but i think there would be another path to go, regarding booting os9. we could try to implement a mac boot rom (for os9) that looks like one for osx. so open firmware thinks it is booting osx when in reality it is booting os9.
sure u can -- it just wont be there if u reboot ..
bless -info /
and see if it says $ bless -info /
finderinfo[0]: 7244 => Blessed System Folder is /System/Library/CoreServices
finderinfo[1]: 0 => No Startup App folder (ignored anyway)
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 31 => OS 9 blessed folder is /System Folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 7244 => OS X blessed folder is /System/Library/CoreServices
64-bit VSDB volume id: 0x174C8C1A011D70E1
This is like an old wound that never heals...
QuoteThis is like an old wound that never heals...
Finally... it heals with confirmed success :)
No more vague stories of a friend who knows a friend that is running 9.2.2 on FW800... real facts !
Wow, tests are just like I expected.. FW800 runs at 400 Speed in OS 9 and 800 in X... The last test is to try to boot to external FW hard drive via the 800 Port by holding "alt" at bootup...
I am guessing the hard drive won't be seen on the 800 port until OS is loaded (Since firmware is from a FW400), but I am curious.
In OS9 the stock Firewire 400 ports does not work anymore! Only the FW800 does! :-(
A quick test under OSX prove it happens on OS9 only, the two FW400 ports works well both under 10.4 and 10.5 so this could be only a driver issue, maybe in OS9 the drivers are rigidly mapped to hardware resources and if the phisical address is changed (like flashing a machine with a different machine firmware) they do not found their way anymore. So this is the first serious problem of this firmware downgrade but if you add a combo PCI card USB/Firewire this issue can be less problematic as it could seem in first place.
After spending a considerable amount of time in testing I cant tell that "unlocked" USB2 mode on integrated MDD port is safe and does not freeze the machine under heavy load under OSX. For OS9 remains true what I wrote in the last post: better to not use these ports for storage devices.
OS 9.2.2
In OS9 the stock Firewire 400 ports does not work anymore! Only the FW800 does! :-(
A quick test under OSX prove it happens on OS9 only, the two FW400 ports works well both under 10.4 and 10.5 so this could be only a driver issue, maybe in OS9 the drivers are rigidly mapped to hardware resources and if the phisical address is changed (like flashing a machine with a different machine firmware) they do not found their way anymore. So this is the first serious problem of this firmware downgrade but if you add a combo PCI card USB/Firewire this issue can be less problematic as it could seem in first place.
At this point I am very satisfied about the downgrade but I really would like to know if the Airport slot and Bluetooth module are working again after this modifications.
Now we're ready for a G5 Macos9 on Steroids...
So from what you said Diehard then at the open firmware level everything is opened up at startup - then it's at the startup of the Mac Operating System that depends whether the ports are used or not?
Apple's Open Firmware is part of their ROM-in-RAM design approach originally used in the first iMac systems. The approach uses a small ROM that contains sufficient code to initialize the hardware and load an operating system. The rest of the system code, that on previous Mac systems (old world) resided on a physical ROM (chip) is now loaded from disk or from network into RAM. Open Firmware is part of this "New World" boot system.
The SMC (System Management Controller) controls a number of the Mac's core functions. The SMC is a chunk of hardware incorporated into the Mac's motherboard. Its purpose is to free the Mac's processor from having to actively take care of rudimentary hardware functions.So basically this "Chunk of Hardware" is obviously a chip or series of chips that are physically located on the MB, and some values that these chips hold can be cleared (By hitting the SMC" reset button and giving a small voltage zap) and thus new "correct" values will be re-read and re-written into the SMC upon power on and the SMC will see everything peachy and BAM... a familiar C Chord Chime will be heard.
Depending on your Mac model, the SMC performs the following functions:And... a whole bunch of other stuff :)
Responds to the press of the power button, including deciding whether the press is for a power off, sleep
Detects and responds to the opening or closing of the lid of a portable Mac.
Manages a portable's battery performance, including charging, calibration, and displaying remaining battery time.
Thermal management of your Mac's interior. This is primarily accomplished by sensing temperature at various places inside your Mac, and then adjusting fan speed to create or reduce airflow.
Step 2: Hardware Self-Test
After the computer is turned on, different "managers" in the computer's read-only memory begin to function. The first is the Start Manager. It makes sure that certain hardware components on the computer's logic board are working, including the microprocessor, read-only memory, drives, ports, expansion slots, and memory (RAM).
The startup sound you hear when you turn on the computer indicates that the Start Manager has successfully completed its tests. You will also see the raster (gray desktop) on the screen, along with the pointer.
If one of the Start Manager tests fails, you may hear a series of tones (sometimes called "error tones" or "death chimes") see a "sad Macintosh" icon on the screen The kind of tones you hear will vary depending on the Macintosh model, and on the kind of component(s) that failed the test.
In OS9 the stock Firewire 400 ports does not work anymore! Only the FW800 does! :-(
fw6093, 10483
-No Fw800, No USB 2... but I had read long time ago that this is posible.:) :)
While I expect to get told to read the entire thread again I'm hoping I could get some quick advice on the futility of my goal. This machine deserves some proper love for sure!
So for Mac Os 9 boot on unsupported iMac G4 please post on :
http://macos9lives.com/smforum/index.php?topic=1173.0
” PowerBook2,2″ encode-string ” MacRISC” encode-string encode+ ” MacRISC2″ encode-string encode+ ” Power Macintosh” encode-string encode+ ” compatible” property
It is based on FORTH, a programming language, where the actual command what to do with a value follows that value. (Like calculating with a HP-28.) So ” PowerBook2,2″ is the string, and encode-string is what to do with it.
MegaWolf is very pleased to announce that it has acquired the MacForth programming environment!! For more details, go to www.macforth.comhttp://www.megawolf.com/
By 2015 it will we 18 pages long and the last page will have a post about success with a Dual 2.7 CPU G5 running Mac OS 9.2.2 !!
But I regret to say it will only have 16 colors available and have no working ports (Firewire or USB), No Audio and No ethernet…
Introduction Date: April 29, 2002 Discontinued Date: November 6, 2002
back to the topic..
http://www.everymac.com/mac-answers/mac-os-9-classic-support-faq/last-macs-to-boot-startup-macos-9.html
lists the fastest as the g4 1ghz ti (radeon 9000)
http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.0.html
As there is some people interested in to Mac os 9 boot on other unsupported Macs I'll open new threads to discuss each specific model issues, and to keep this important thread in to his original sense "MDD Firewire 800" and to solve further questions on this topic.
So for Mac Os 9 boot on unsupported iMac G4 please post on :
http://macos9lives.com/smforum/index.php?topic=1173.0
and for Mac Os 9 boot on unsupported iBook G4 please post on:
http://macos9lives.com/smforum/index.php?topic=1174.0
and for Mac Os 9 boot on other unsupported models, please open new threads...
all g4s that support classic mode but not booting
eMac G4/1.25 (USB 2.0)
Intro. Date: April 13, 2004 Disc. Date: May 3, 2005
Order No: M9425LL/A* Model No: A1002
Subfamily: eMac USB 2.0 Model ID: PowerMac6,4
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 40, 80 GB Std. Optical: 8X "Combo Drive"*
eMac G4/1.42 (2005)
Intro. Date: May 3, 2005 Disc. Date: October 12, 2005*
Order No: M9834LL/A* Model No: A1002
Subfamily: eMac 2005 Model ID: PowerMac6,4
Std. RAM: 256 MB, 512 MB Std. VRAM: 64 MB
Std. HD: 80, 160 GB Std. Optical: 12X "Combo Drive"*
iBook G4/800 12-Inch (Original - Op)
Intro. Date: October 22, 2003 Disc. Date: April 19, 2004
Order No: M9164LL/A Model No: A1054
Subfamily: iBook G4 Model ID: PowerBook6,3
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 30.0 GB Std. Optical: 8X "Combo Drive"
iBook G4/933 14-Inch (Original - Op)
Intro. Date: October 22, 2003 Disc. Date: April 19, 2004
Order No: M9388LL/A Model No: A1055
Subfamily: iBook G4 14-Inch Model ID: PowerBook6,3
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 40.0 GB Std. Optical: 8X "Combo Drive"
iBook G4/1.0 14-Inch (Original - Op)
Intro. Date: October 22, 2003 Disc. Date: April 19, 2004
Order No: M9165LL/A Model No: A1055
Subfamily: iBook G4 14-Inch Model ID: PowerBook6,3
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 60.0 GB Std. Optical: 8X "Combo Drive"
iBook G4/1.0 12-Inch (Early 2004 - Op)
Intro. Date: April 19, 2004 Disc. Date: October 19, 2004
Order No: M9426LL/A Model No: A1054
Subfamily: Early 2004 Model ID: PowerBook6,5
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 30 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
iBook G4/1.0 14-Inch (Early 2004 - Op)
Intro. Date: April 19, 2004 Disc. Date: October 19, 2004
Order No: M9418LL/A Model No: A1055
Subfamily: Early 2004 14-Inch Model ID: PowerBook6,5
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 40 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
iBook G4/1.2 14-Inch (Early 2004 - Op)
Intro. Date: April 19, 2004 Disc. Date: October 19, 2004
Order No: M9419LL/A Model No: A1055
Subfamily: Early 2004 14-Inch Model ID: PowerBook6,5
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
iBook G4/1.2 12-Inch (Late 2004 - Op)
Intro. Date: October 19, 2004 Disc. Date: July 26, 2005
Order No: M9623LL/A Model No: A1054
Subfamily: Late 2004 12-Inch Model ID: PowerBook6,5
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 30 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
iBook G4/1.33 14-Inch (Late 2004 - Op)
Intro. Date: October 19, 2004 Disc. Date: July 26, 2005
Order No: M9627LL/A* Model No: A1055
Subfamily: Late 2004 14-Inch Model ID: PowerBook6,5
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 8X "Combo Drive"*
iBook G4/1.33 12-Inch (Mid-2005 - Op)
Intro. Date: July 26, 2005 Disc. Date: May 16, 2006
Order No: M9846LL/A Model No: A1133
Subfamily: Mid-2005 12-Inch Model ID: PowerBook6,7
Std. RAM: 512 MB Std. VRAM: 32 MB
Std. HD: 40 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
iBook G4/1.42 14-Inch (Mid-2005 - Op)
Intro. Date: July 26, 2005 Disc. Date: May 16, 2006
Order No: M9848LL/A Model No: A1134
Subfamily: Mid-2005 14-Inch Model ID: PowerBook6,7
Std. RAM: 512 MB Std. VRAM: 32 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 4X "SuperDrive"
iMac G4/800 - X Only (Flat Panel)
Intro. Date: February 4, 2003 Disc. Date: September 8, 2003
Order No: M9105LL/A Model No: M6498
Subfamily: iMac Spring 2003 Model ID: PowerMac4,2
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 60 GB (7200 RPM) Std. Optical: 32X "Combo Drive"
iMac G4/1.0 17-Inch (Flat Panel)
Intro. Date: February 4, 2003 Disc. Date: September 8, 2003
Order No: M8935LL/A Model No: M6498
Subfamily: iMac 17" 1 GHz Model ID: PowerMac6,1
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 80 GB (7200 RPM) Std. Optical: 4X "SuperDrive"
iMac G4/1.0 15-Inch "FP" (USB 2.0)
Intro. Date: September 8, 2003 Disc. Date: July 1, 2004
Order No: M9285LL/A Model No: N/A
Subfamily: iMac USB 2.0 Model ID: PowerMac6,1
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 80 GB (7200 RPM) Std. Optical: 32X "Combo Drive"
iMac G4/1.25 17-Inch "FP" (USB 2.0)
Intro. Date: September 8, 2003 Disc. Date: July 1, 2004
Order No: M9168LL/A Model No: N/A
Subfamily: iMac USB 2.0 Model ID: PowerMac6,1
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 80 GB (7200 RPM) Std. Optical: 4X "SuperDrive"
iMac G4/1.25 20-Inch "FP" (USB 2.0)
Intro. Date: November 18, 2003 Disc. Date: July 1, 2004
Order No: M9290LL/A Model No: N/A
Subfamily: iMac USB 2.0 Model ID: PowerMac6,3
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 80 GB (7200 RPM) Std. Optical: 4X "SuperDrive"
Mac mini G4/1.42
Intro. Date: January 11, 2005* Disc. Date: September 27, 2005
Order No: M9687LL/A* Model No: A1103
Subfamily: Mac mini Model ID: PowerMac10,1
Std. RAM: 256 MB, 512 MB Std. VRAM: 32 MB
Std. HD: 80.0 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
Mac mini G4/1.33
Intro. Date: September 27, 2005 Disc. Date: February 28, 2006
Order No: M9686LL/B* Model No: A1103
Subfamily: Late 2005 Model ID: PowerMac10,2
Std. RAM: 512 MB Std. VRAM: 32 MB
Std. HD: 40.0 GB (5400 RPM) Std. Optical: 8X "Combo Drive"
Mac mini G4/1.5
Intro. Date: September 27, 2005 Disc. Date: February 28, 2006
Order No: M9687LL/B* Model No: A1103
Subfamily: Late 2005 Model ID: PowerMac10,2
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80.0 GB (5400 RPM) Std. Optical: 8X "Combo Drive"
PowerBook G4 867 12" (Al)
Intro. Date: January 7, 2003 Disc. Date: September 16, 2003
Order No: M8760LL/A Model No: A1010
Subfamily: 12-Inch Model ID: PowerBook6,1
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 40 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
PowerBook G4 1.0 17" (Al)
Intro. Date: January 7, 2003 Disc. Date: September 16, 2003
Order No: M8793LL/A Model No: A1013
Subfamily: 17-Inch Model ID: PowerBook5,1
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 2X "SuperDrive"
PowerBook G4 1.0 12" (DVI - Al)
Intro. Date: September 16, 2003 Disc. Date: April 19, 2004
Order No: M9007LL/A* Model No: A1010
Subfamily: 12-Inch DVI Model ID: PowerBook6,2
Std. RAM: 256 MB Std. VRAM: 32 MB
Std. HD: 40 GB (4200 RPM) Std. Optical: 8X "Combo Drive"*
PowerBook G4 1.0 15" (FW800 - Al)
Intro. Date: September 16, 2003 Disc. Date: April 19, 2004
Order No: M8980LL/A Model No: A1046
Subfamily: 15-Inch FW800 Model ID: PowerBook5,2
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
PowerBook G4 1.25 15" (FW800 - Al)
Intro. Date: September 16, 2003 Disc. Date: April 19, 2004
Order No: M8981LL/A Model No: A1046
Subfamily: 15-Inch FW800 Model ID: PowerBook5,2
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (4200 RPM) Std. Optical: 2X "SuperDrive"
PowerBook G4 1.33 17" (Al)
Intro. Date: September 16, 2003 Disc. Date: April 19, 2004
Order No: M9110LL/A Model No: A1052
Subfamily: 17-Inch 1.33 GHz Model ID: PowerBook5,3
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (4200 RPM) Std. Optical: 2X "SuperDrive"
PowerBook G4 1.33 12" (Al)
Intro. Date: April 19, 2004 Disc. Date: January 31, 2005
Order No: M9183LL/A* Model No: A1010
Subfamily: 12-Inch 1.33 GHz Model ID: PowerBook6,4
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 8X "Combo Drive"*
PowerBook G4 1.33 15" (Al)
Intro. Date: April 19, 2004 Disc. Date: January 31, 2005
Order No: M9421LL/A Model No: A1095
Subfamily: 15-Inch 1.5/1.33 Model ID: PowerBook5,4
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 60 GB (4200 RPM) Std. Optical: 8X "Combo Drive"
PowerBook G4 1.5 15" (Al)
Intro. Date: April 19, 2004 Disc. Date: January 31, 2005
Order No: M9422LL/A Model No: A1095
Subfamily: 15-Inch 1.5/1.33 Model ID: PowerBook5,4
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (4200 RPM) Std. Optical: 4X "SuperDrive"
PowerBook G4 1.5 17" (Al)
Intro. Date: April 19, 2004 Disc. Date: January 31, 2005
Order No: M9462LL/A Model No: A1085
Subfamily: 17-Inch 1.5 GHz Model ID: PowerBook5,5
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (4200 RPM) Std. Optical: 4X "SuperDrive"
PowerBook G4 1.5 12" (Al)
Intro. Date: January 31, 2005 Disc. Date: May 16, 2006*
Order No: M9690LL/A* Model No: A1104
Subfamily: 12-Inch 1.5 GHz Model ID: PowerBook6,8
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 60, 80 GB (5400 RPM) Std. Optical: 8X "Combo Drive"*
PowerBook G4 1.5 15" (SMS/BT2 - Al)
Intro. Date: January 31, 2005 Disc. Date: October 19, 2005
Order No: M9676LL/A Model No: A1106
Subfamily: 15-Inch 1.67/1.5 Model ID: PowerBook5,6
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (5400 RPM) Std. Optical: 8X "Combo Drive"
PowerBook G4 1.67 15" (Al)
Intro. Date: January 31, 2005 Disc. Date: October 19, 2005
Order No: M9677LL/A Model No: A1106
Subfamily: 15-Inch 1.67/1.5 Model ID: PowerBook5,6
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 80 GB (5400 RPM) Std. Optical: 8X "SuperDrive"
PowerBook G4 1.67 17" (Al)
Intro. Date: January 31, 2005 Disc. Date: October 19, 2005
Order No: M9689LL/A Model No: A1107
Subfamily: 17-Inch 1.67 GHz Model ID: PowerBook5,7
Std. RAM: 512 MB Std. VRAM: 128 MB
Std. HD: 100 GB (5400 RPM) Std. Optical: 8X "SuperDrive"
PowerBook G4 1.67 15" (DLSD/HR - Al)
Intro. Date: October 19, 2005 Disc. Date: January 10, 2006*
Order No: M9969LL/A Model No: A1138
Subfamily: 15-Inch DL SD Model ID: PowerBook5,8
Std. RAM: 512 MB Std. VRAM: 128 MB
Std. HD: 80 GB (5400 RPM) Std. Optical: 2.4X DL "SuperDrive"
PowerBook G4 1.67 17" (DLSD/HR - Al)
Intro. Date: October 19, 2005 Disc. Date: April 24, 2006
Order No: M9970LL/A Model No: A1139
Subfamily: 17-Inch DL SD Model ID: PowerBook5,9
Std. RAM: 512 MB Std. VRAM: 128 MB
Std. HD: 120 GB (5400 RPM) Std. Optical: 2.4X DL "SuperDrive"
Power Macintosh G4 1.0 (FW 800)
Intro. Date: January 28, 2003 Disc. Date: June 23, 2003
Order No: M8839LL/A Model No: M8570
Subfamily: Firewire 800 Model ID: PowerMac3,6
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 60 GB (7200 RPM) Std. Optical: 12X "Combo Drive"
Power Macintosh G4 1.25 DP (FW 800)
Intro. Date: January 28, 2003 Disc. Date: June 23, 2003
Order No: M8840LL/A Model No: M8570
Subfamily: Firewire 800 Model ID: PowerMac3,6
Std. RAM: 256 MB Std. VRAM: 64 MB
Std. HD: 80 GB (7200 RPM) Std. Optical: 12X "Combo Drive"
Power Macintosh G4 1.42 DP (FW 800)
Intro. Date: January 28, 2003 Disc. Date: June 23, 2003
Order No: M8841LL/A Model No: M8570
Subfamily: Firewire 800 Model ID: PowerMac3,6
Std. RAM: 512 MB Std. VRAM: 64 MB
Std. HD: 120 GB (7200 RPM) Std. Optical: 4X "SuperDrive"
Hi Chris
I've got one of those 1,67 ghz Powerbooks and I would love to have a native Mac OS 9 on it ;D
Are then the only two things to consider to install from another Mac OS 9 machine the apple hd driver and then to implant that MacOS ROM 9.8.1 on it?
I want to try soonish
raphael
Reason I tell that story, as it might be related as 9.2.2 was not meant to run on that Mac (with G3 upgrade or not)... But back then there were a few tricks that later became part of a tool to run Mac OS 9.2.x on older Macs. 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:
https://www.thinkclassic.org/viewtopic.php?id=46
Figure it might be a good way to get both forums/threads working together.
I suppose I should introduce myself. I'm a site administrator over at ThinkClassic and the author of that thread. I was also iMac600 over at the 68kMLA forums, but I haven't been active there in quite some time.
Ideally, I'd be able to find where the issues that the OF commands address lie in the Mac OS ROM and System Suitcase and fix them so I could do away with the need for the Open Firmware commands entirely.
dev /
.properties
" PowerBook4,3" encode-string " model" property
" PowerBook4,3" encode-string " MacRISC" encode-string encode+ " MacRiSC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
multi-boot
I'm cross-posting this from ThinkClassic since I think it's something everyone here may find interesting.
It's a bit hit and miss to as what machines it'll work on. I all depends on what driver support Mac OS 9 has for the hardware it's running on. All this ROM does is remove the machine check that prevents Mac OS 9 from attempting to start up. Whether it successfully completes the boot is still up to the OS.
It's a pain that this procedure did not worked with the Mac Mini. The Mother board layout is based on the Intrepid IC, and this IC is supported with Mac Os 9, so in my opinion, may be related with "enabling" the 7447 to Mac Os 9, in the way that some 7448/7447 CPU upgrades
It's a bit hit and miss to as what machines it'll work on. I all depends on what driver support Mac OS 9 has for the hardware it's running on. All this ROM does is remove the machine check that prevents Mac OS 9 from attempting to start up. Whether it successfully completes the boot is still up to the OS.
...
This really is a "try it and see" type project, so if you're up for a challenge, then by all means go ahead and give it a shot.
...We need to get a source to write us some new drivers for some of the basic Video Chip sets that currently elude us.
QuoteIt's a pain that this procedure did not worked with the Mac Mini. The Mother board layout is based on the Intrepid IC, and this IC is supported with Mac Os 9, so in my opinion, may be related with "enabling" the 7447 to Mac Os 9, in the way that some 7448/7447 CPU upgrades
Here is a 7447a that works under OS 9 like you mentioned
http://www.newertech.com/downloads/nwtmang4max.pdf
Hey Mactron, I'm with you, the I/O controller (Intrepid) will most likely not be an obstacle, and the the Mac Mini G4 (1.25,1.33,1.42,1.5) all use a Radeon 9200 so these systems should be promising...(I was really bummed to see the grey screen on the Mac Mini tested, but the 1.5 is the only one with 64MB vram... we need to test a G4 1.25 Original)
Not really sure where to go from here...
Not really sure where to go from here. Keep in mind that mine is a 1.5GHz last-generation model, which could be part of the problem.
Keep in mind that mine is a 1.5GHz last-generation model, which could be part of the problem.
Not really sure where to go from here.
Is possible in openfirmware to limit the amount of the graphics RAM?
Not really sure where to go from here. Keep in mind that mine is a 1.5GHz last-generation model, which could be part of the problem.
I only know of Radeon 9200 PCI working on G3s B&W on OS9. Not sure what drivers you should use for AGP. Maybe 2003' ATI drivers update...
I can suggest you to try to startup the machine from any means you can, ie CDROM, Firewire, USB...
May be you can circumvent the thing that can't let the Mac Os 9 boot.
, checksum error
Loading ELF
DO-QUIESCE finished
I can suggest you to try to startup the machine from any means you can, ie CDROM, Firewire, USB...
May be you can circumvent the thing that can't let the Mac Os 9 boot.
I've tried booting from the internal hard drive and via FireWire. Still boots to a grey screen. There is also a property in Open Firmware under the graphics accelerator called "VRAM,totalsize" with a default value of 04000000 - I reduced this to 02000000 with no effect.
UPDATE
If I attempt to start Mac OS 9 from within Open Firmware (using boot hd:,\\:tbxi), I do manage to get some text output:
The Toolbox ROM (http://en.wikipedia.org/wiki/Macintosh_Toolbox) was embedded inside a CHRP script (http://en.wikipedia.org/wiki/Common_Hardware_Reference_Platform) in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware (http://web.archive.org/web/20140101113916/http://www.openfirmware.org/) could also run a binary boot loader, and version 3.0 added support for ELF objects (http://en.wikipedia.org/wiki/Executable_and_Linkable_Format) as well as the XCOFF (http://en.wikipedia.org/wiki/XCOFF) files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware (http://en.wikipedia.org/wiki/Open_Firmware) command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
One major difference between Old World ROM Macs and New World ROM Macs, at least in classic Mac OS, is that the Gestalt selector for the machine type is no longer usable; all New World ROM Macs use the same mach ID, 406 decimal, and the actual machine ID is encoded in the "model" and "compatible" properties of the root node of the Open Firmware device tree. The New World ROM also sets the "compatible" property of the root node to "MacRISC2" (machines that can boot classic Mac OS using "Mac OS ROM") or "MacRISC3" (machines that can only boot OS X or another Unix-like system).
Boot Process Overviewhttp://web.archive.org/web/20041011114718/http://developer.apple.com/technotes/tn/pdf/tn1167.pdf
The following list is a high level view of the execution path take when a NewWorld-based computer boots Mac OS:
The POST code runs (preliminary diagnostics, boot beep, initialization, and setup). This is similar to code in a Mac OS ToolBox ROM, but it is different in that it does not contain OS-specific code.
Open Firmware initializes and begins execution, including building the Device Tree.
Open Firmware loads the "bootinfo" file, based on defaults and NVRAM settings.
Open Firmware executes the "Forth" script in the "bootinfo" file, which contains information about the rest of the file and instructions to read both the Trampoline code and the ToolBox ROM Image and place them into a temporary place in memory.
The "Forth" script transfers control to the Trampoline code, which functions as the transition between Open Firmware and the beginning of the Mac OS execution.
The Trampoline code gathers information about the system from Open Firmware, creates data structures based on this information, terminates Open Firmware, and rearranges the contents of memory to an interim location in physical memory space.
The Trampoline code transfers control to the ToolBox ROM Image initialization code.
Startup and the Startup Disk Control Panel
The boot sequence, up to loading and execution of the Mac OS ROM image, is controlled by Open Firmware. To provide a user experience like previous Macintoshes, Open Firmware now supports searching for possible boot devices and user overrides of boot devices using keyboard input such as Command-Shift-Option-Delete or "C" to force booting from a CD-ROM.
When the user selects a startup device in the Startup Disk control panel, Startup Disk no longer sets a value in Mac OS PRAM. Instead it generates an Open Firmware path to the device and saves that path in NVRAM as Open Firmware's "boot-device" configuration variable. Open Firmware tries the device specified by "boot-device" first. If this device is unavailable or the user has overridden this with keyboard input, Open Firmware scans other devices looking for bootable drives. Once Open Firmware selects a device, it sets the "bootpath" property in the "chosen" node to the path to that device. The "bootpath" property is what the Mac OS ROM subsequently uses to locate and load Mac OS from disk.
In order for a device to be bootable, Open Firmware needs methods for accessing the drive. For built-in devices, such as SCSI and ATA, these methods are supplied by Open Firmware. For plug-in cards, the PCI configuration ROM on each card must supply these methods for the card as specified in the PCI Open Firmware binding.
Code: [Select], checksum error
Loading ELF
DO-QUIESCE finished
protoolsle5guy;
what makes u think that the key to making anything work is to disable soemthing in openfirmware?
i saw u comment about this before, earlier, perhaps in this very thread, it was in reference to the firewire 800 ports...the presence of the firewire 800 ports is not what stops the mac os boot...
i havent seen many of us really discuss the particulars of what actually happens during a mac os 9 boot ..
...
perhaps it would be helpful to alll minds readin this thread to revisit in another thread the following:
a) the specifics of what actually happens .. chain of events. order of operations... during a mac os boot...
b) why the firmware rollback of the mdd fw800 to fw400 worked + what exactly it changed that enabled it to work
-No Fw800, No USB 2... but I had read long time ago that this is posible.
-Format an HD with Mac Os 9 drivers.
-Use a Mac Os ROM version 10.2
-Force the startup with this HD.
... I never tested this, but may help ...
protoolsle5guy;
what makes u think that the key to making anything work is to disable soemthing in openfirmware?
reading the threads + posts here i feel that alot of u are out of synch with each other in terms of understanding + in depth knowledge + familiarity with the relevant specifics
perhaps it would be helpful to alll minds readin this thread to revisit in another thread the following:
a) the specifics of what actually happens .. chain of events. order of operations... during a mac os boot..
b) why the firmware rollback of the mdd fw800 to fw400 worked + what exactly it changed that enabled it to work
c) why the changes in the mac os rom edited by imic has enabled a boot WITHOUT a firmware downgrade
i think getting everyone on the same page in understanding these facts will provide groundwork for the next ssteps.
which leads me to ask: which install was iMic using with the above test?
and which versions of the ati driver extensions
I only know of Radeon 9200 PCI working on G3s B&W on OS9. Not sure what drivers you should use for AGP. Maybe 2003' ATI drivers update...
i understand your reasoning about the problem of the greyscreen being graphics drivers..Mine, iMic, MacTron or DieHard approach? :P
this makes sense to me much in the same way that my powermac g3 450MHz wont boot if i have the radeon 7000 card installed on a vanilla install of 8.6 or 9.0 but it works fine with 9.1 + 9.2 - i wrote recently saying i had to replace the ati rage 128 to be able to install... suggesting that anyone with a g3 absolutely must keep this rage 128 card for situations like this..
but hoping for someone to develop new graphics drivers is a huuuuuuge longshot ;D but its understandable given the history here this thread started frm a silly post like that about *impossible things* not so long ago right ;D lol lol ptleguy thinks hey.. fuck it . why not try to start a new miracle thread ;D hahahah>:( >:( >:( >:( >:( >:( >:( >:( >:( >:( >:( >:( >:( >:( >:(
a silly post like that about impossible things.I honestly was just asking publicly to DieHard and diehard MacOS9 users if they were aware of HardWare/Software Mods to achieve that.
iMic,
You have already inspired many, where ever you go from here is gravy... thank you for all the hard work... it reminds me of the days we used to use Norton disk edit in MS DOS to Hex out License keys from DBase software Applications (same concept to keep the file the same number of Bytes)... excellent work :)
iMic. Even with most of us been OS9 centric, We, as part of the living PowerPC community have to give thanks to you also for the develop of Leopard Assist. You have broke barriers in both sides of the wall. You have made TigerOnly computers go Leo and OSXonly computers go back to OS9. THANKS for been a truly liberator.
I think you can not "make a brick" of a PowerMac with bad OpenFirmware commands, but it seems that the OpenFirmware level of iMic is way ahead ours... MacTron has said that was dangerous.
This last method seems to work for the iBook from iMic. But not on the MacMini. That lead DieHard that maybe the trouble was not having source of graphics drivers
i dont agree with calling it a dangerous + brute force method at all. the machines are almost identical
it simply undid a change in the combination of machinefirmware / openfirmware settngs code that was placed there on purpose by apple to disable the mac os 9 bootability.
there is no technical reason blocking it from working.. it was deliberate + intentional to disable the os.
as intentional as it was to hold a public funeral.. it doesnt get more deliberate + intentional then that.
the execution of loading of the toolbox image/chrp script was disabled at the openfirmware level..
breaking the chain of events that would lead to a possible boot.
i understand your reasoning about the problem of the greyscreen being graphics drivers..
this makes sense to me much in the same way that my powermac g3 450mhz wont boot if i have the radeon 7000 card installed on a vanilla install of 8.6 or 9.0 but it works fine with 9.1 + 9.2 - i wrote recently saying i had to replace the ati rage 128 to be able to install... suggesting that anyone with a g3 absolutely must keep this rage 128 card for situations like this.. but hoping for someone to develop new graphics drivers is a huuuuuuge longshot ;D but its understandable given the history here this thread started frm a silly post like that about *impossible things* not so long ago right ;D lol lol ptleguy thinks hey.. fuck it . why not try to start a new miracle thread ;D hahahah
but: re graphics cards / drivers being the cause of non-boot
dont forget that japamac claimed to hav booted mac os 9 on many unsupported video cards.. such as the radeon 9800 etc (albeit without 'accelleration')
looking back to the thread of filiphuezen or whatever did he get a grey screen on boot with his radeon 9200?
his card never worked untill he used the freshdraginstall with updated video drivers
which leads me to ask: which install was iMic using with the above test?
and which versions of the ati driver extensions
Yeah, I know this is wishfull thinking, and you even laught about it, but who knows? The partnership between MacOS9Lives! and ThinkClassic is giving unsuspected results. The more who join us, the easiest to know a guy who knows a guy that do @@@
One major difference between Old World ROM Macs and New World ROM Macs, at least in classic Mac OS, is that the Gestalt selector for the machine type is no longer usable; all New World ROM Macs use the same mach ID, 406 decimal, and the actual machine ID is encoded in the "model" and "compatible" properties of the root node of the Open Firmware device tree. The New World ROM also sets the "compatible" property of the root node to "MacRISC2" (machines that can boot classic Mac OS using "Mac OS ROM") or "MacRISC3" (machines that can only boot OS X or another Unix-like system).
Yeah, I know this is wishfull thinking, and you even laught about it, but who knows? The partnership between MacOS9Lives! and ThinkClassic is giving unsuspected results. The more who join us, the easiest to know a guy who knows a guy that do @@@
It's fairly impressive what can be achieved when our communities work together, isn't it? Personally I think it's been fantastic collaborating with Mac OS 9 Lives on this project. Some of the information here has been extremely valuable, especially the documentation and threads on Open Firmware.
The Mac OS 9 Lives Forum will now be dedicated to...
1) Installing, Maintaining, and Extending the functionality of Mac OS 9
2) Installing Digital Audio Software & Music/MIDI Hardware interfaces
3) General questions for Mac OS 9 enthusiasts.
i think ptleguy is drunkDrunk people always say the truth. ;D ;D ;D ;D ;D Cheers!
if it is indeed the "macrisc3" string that enables/disables boot.. this info is contained in *the root node of the open firmware device tree* with property name "compatible"
can't we just overwrite this parameter in openfirmware nv-ram?? rather then having to change the 'mac os rom' ??....
dev /
" PowerBook4,3" encode-string " model" property
" PowerBook4,3" encode-string " MacRISC" encode-string encode+ " MacRiSC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
nvedit
dev /
" PowerBook4,3" encode-string " model" property
" PowerBook4,3" encode-string " MacRISC" encode-string encode+ " MacRiSC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
(Press Ctrl + C)
nvstore
setenv use-nvramrc? true
reset-all
Not in the sense you'll think. IMHO
so to think logically... the 10.2.1 rom file was created for the mdd's as far as we have established
keepin in mind that the single rom file is , in fact an actual script /w an embedded toolbox image..
It's fairly impressive what can be achieved when our communities work together, isn't it? Personally I think it's been fantastic collaborating with Mac OS 9 Lives on this project.
Some of the information here has been extremely valuable, especially the documentation and threads on Open Firmware.
Those post was placed by myself (including some from Think Classic) due to a similar project with a xServe, and to avoid some dangerous reflashing fever around here. But seems that few or nobody have read them... LOL
excellent post ;0 thank you!Code: [Select]dev /
" PowerBook4,3" encode-string " model" property
" PowerBook4,3" encode-string " MacRISC" encode-string encode+ " MacRiSC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
To make it apply automatically with each boot:Quotenvedit
dev /
" PowerBook4,3" encode-string " model" property
" PowerBook4,3" encode-string " MacRISC" encode-string encode+ " MacRiSC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
(Press Ctrl + C)
nvstore
setenv use-nvramrc? true
reset-all
Modified Mac OS ROM with generic MacRISCX entries takes care of Mac OS ROM.. Next thing that comes to mind to kill off another need for the simple open firmware identity spoofing, would be patched last version of DiskUtility that is likely doing it's own check when deciding to display the "Mac OS 9 Driver" option.
/ compatible IOService:/ MacRISC MacRISC2
#!/bin/sh
echo Enabling OS 9 booting...
echo "You may have to enter your password"
# Use nvram command to setup nvramrc with script to make open firmware changes
sudo nvram nvramrc='" /" select-dev
" PowerMac3,6" encode-string " model" property
" PowerMac3,6" encode-string " MacRISC" encode-string encode+ " MacRISC2" encode-string encode+ " MacRISC3" encode-string encode+ " Power Macintosh" encode-string encode+ " compatible" property
unselect
'
# Enable use of nvramrc on boot. Change to "false" if you want to disable again. Or just clear/reset nvram.
sudo nvram "use-nvramrc?"=true
echo done.
So, to Blemk (or anyone else with the energy), I ask, for us to streamline the process by creating...
1) A Bootable Mac OS 9.2.2 CD Image (with Modified iMic 10.2.1 ROM in system folder) that also contains modified Disk Utility (if needed) and an ASR Image that will restore to a fresh volume that also contains Modified iMic 10.2.1 ROM; in other words a New 2015 Mac OS 9.2.2 bootable install CD that we can immediately distribute to get some real world testing going...
AND/OR
2) A Bootable OS X (10.x) CD that contains 2 scripts (or 1 with choices) that...
A) Sets NVRAM for OS 9 Boot so that a normal Mac OS 9 install can be tested AND B) Resets NVRAM back to factory when testing is done
I know this is a lot to ask, but it would expedite the process of testing different machines for OS9 functionality.
AND[/i] B) Resets NVRAM back to factory when testing is done
Use of nvram command in os x was just idea I picked up from a similar open firmware hack/tweak. Not a very complicated script in the first place but put to good use. I just modified what the script is injecting into open firmware.
Time permitting on the rest of my long weekend.. I had plans for OS bootable disk with updated/modified rom.. OS X disk.. Could build it with the script but not sure it is worth it as the script can reside on a USB pen drive easy enough (boot CD/DVD, access script on usb pen drive).
Going to see if I can build the OS disk and put the apparently rare OS 9 ASR tool on it and use it to restore OS 9 image from OS 9 CD image with the modified rom. Would love to find a tool like "nvram" command in OS X that could run from OS 9 so I didn't even have to touch OS X to do this.
In either case, need to get tools to rebuild a OS 9 (or earlier) bootable CD image going. Been ages since I have done so. Wasn't hard with right software tools handy.
BTW, modded Disk Utility is not needed after open firmware changes. As imic noted, it appears to be checking for MacRISC/MacRISC2 as well when deciding to show "OS 9 Driver" option or not. So, only way you would need it (like modified Mac OS ROM) is if you don't do the open firmware change or the change is reset by clearing nvram.
BTW, modded Disk Utility is not needed after open firmware changes. As imic noted, it appears to be checking for MacRISC/MacRISC2 as well when deciding to show "OS 9 Driver" option or not. So, only way you would need it (like modified Mac OS ROM) is if you don't do the open firmware change or the change is reset by clearing nvram.
You don't need a Mac Os 9 or X boot disk to apply a Open Firmware script. There is a special and very small boot image from NewerTech, that can do this ...I can provide it, if it is needed.Can you make a bootable Toast image with the newertech CD that runs the script automatically or at least an idiot proof version and Upload it ASAP ?
QuoteBTW, modded Disk Utility is not needed after open firmware changes. As imic noted, it appears to be checking for MacRISC/MacRISC2 as well when deciding to show "OS 9 Driver" option or not. So, only way you would need it (like modified Mac OS ROM) is if you don't do the open firmware change or the change is reset by clearing nvram.
I understand that, but I am assuming the user will use 1 method or the other (not a combination of both);
So let's talk about the modified ROM method for a moments. If a novice user downloads the Modified 2015 OS9 Install CD with ASR (vaporware right now ), then I am assuming the root level tools that check Risc (like Drive Setup) should also be modified. This would make a useable/bootable CD that a beginner could use to...
1) Boot the unsupported Mac
2) Create a Volume
3) Use ASR to recover Modified ROM version of 9.2.2 (with modified Drive setup) and never have to do the NVRAM at all
Use of nvram command in os x was just idea I picked up from a similar open firmware hack/tweak. Not a very complicated script in the first place but put to good use. I just modified what the script is injecting into open firmware.
Time permitting on the rest of my long weekend.. I had plans for OS bootable disk with updated/modified rom.. OS X disk.. Could build it with the script but not sure it is worth it as the script can reside on a USB pen drive easy enough (boot CD/DVD, access script on usb pen drive).
Going to see if I can build the OS disk and put the apparently rare OS 9 ASR tool on it and use it to restore OS 9 image from OS 9 CD image with the modified rom. Would love to find a tool like "nvram" command in OS X that could run from OS 9 so I didn't even have to touch OS X to do this.
In either case, need to get tools to rebuild a OS 9 (or earlier) bootable CD image going. Been ages since I have done so. Wasn't hard with right software tools handy.
BTW, modded Disk Utility is not needed after open firmware changes. As imic noted, it appears to be checking for MacRISC/MacRISC2 as well when deciding to show "OS 9 Driver" option or not. So, only way you would need it (like modified Mac OS ROM) is if you don't do the open firmware change or the change is reset by clearing nvram.
You don't need a Mac Os 9 or X boot disk to apply a Open Firmware script. There is a special and very small boot image from NewerTech, that can do this ...
I can provide it, if it is needed.
QuoteBTW, modded Disk Utility is not needed after open firmware changes. As imic noted, it appears to be checking for MacRISC/MacRISC2 as well when deciding to show "OS 9 Driver" option or not. So, only way you would need it (like modified Mac OS ROM) is if you don't do the open firmware change or the change is reset by clearing nvram.
I understand that, but I am assuming the user will use 1 method or the other (not a combination of both);
So let's talk about the modified ROM method for a moments. If a novice user downloads the Modified 2015 OS9 Install CD with ASR (vaporware right now ), then I am assuming the root level tools that check Risc (like Drive Setup) should also be modified. This would make a useable/bootable CD that a beginner could use to...
1) Boot the unsupported Mac
2) Create a Volume
3) Use ASR to recover Modified ROM version of 9.2.2 (with modified Drive setup) and never have to do the NVRAM at all
OR with Method 2
1) Boot to a CD that autoruns script
2) Install Mac OS 9.2.2 at usual without Modified ROM
Then we can sit back and have many users test
Mactron...QuoteYou don't need a Mac Os 9 or X boot disk to apply a Open Firmware script. There is a special and very small boot image from NewerTech, that can do this ...I can provide it, if it is needed.Can you make a bootable Toast image with the newertech CD that runs the script automatically or at least an idiot proof version and Upload it ASAP ?
Can you make a bootable Toast image with the newertech CD that runs the script automatically or at least an idiot proof version and Upload it ASAP ?
Was wondering if someone had one of the disks from one of the may cpu upgrade makers that might be easily modified. ;)Here it is:
Can you make a bootable Toast image with the newertech CD that runs the script automatically or at least an idiot proof version and Upload it ASAP ?Was wondering if someone had one of the disks from one of the may cpu upgrade makers that might be easily modified. ;)Here it is:
https://www.adrive.com/public/rNAsCf/NewerTech.toast.sit
This is a Toast copy of the original disk.
This CD boot the computer with a text only interface and apply some Open Firmware commands to enable Mac Os 9 boot to 7448 or 7447 CPUs as if they were 7455 , as iMic have shown,
A nice little switcher app (drop down with options for machine IDs) would be the way to go in the future.
This CD boot the computer with a text only interface and apply some Open Firmware commands to enable Mac Os 9 boot to 7448 or 7447 CPUs as if they were 7455 , as iMic have shown
A nice little switcher app (drop down with options for machine IDs) would be the way to go in the future.
there is an app that does this.. but its old.. from around the 8.6 days or earlier
its called "i wish i were" http://macgui.com/downloads/?file_id=20126
adds to control panels .. similar kind of idea..
QuoteThis CD boot the computer with a text only interface and apply some Open Firmware commands to enable Mac Os 9 boot to 7448 or 7447 CPUs as if they were 7455 , as iMic have shown
Is it possible to Autorun a script (to eliminate errors); can we make a new disk image from this one that types the Open Firmware commands for the user ?
QuoteThis CD boot the computer with a text only interface and apply some Open Firmware commands to enable Mac Os 9 boot to 7448 or 7447 CPUs as if they were 7455 , as iMic have shown
Is it possible to Autorun a script (to eliminate errors); can we make a new disk image from this one that types the Open Firmware commands for the user ?
Not being familiar with OS X as I would care to be, can apple scrip scripts be run from the minimal environment we see during early OS X installers (10.3/10.4/10.5)? if so, I could add this to the "Utilities" menu available during OS X Installer on these versions of OS X install discs.
<CHRP-BOOT>
<COMPATIBLE>
MacRISC
MacRISC2
MacRISC3
</COMPATIBLE>
<DESCRIPTION>
Generic FCode Loader script
</DESCRIPTION>
<BOOT-SCRIPT>
\ **************************************************************************
\ * PowerLogix Generic FCode Loader
\ * Copyright (c) 2003-04 by PowerLogix. All rights reserved.
\ * Written by Terry Greeniaus.
\
...
etc
...
Hi,
I'm newly signed-up so I can share my findings. They point either to me being dim, or the need for a bit more detail in the 'Mac OS 9.2.2 Read Me ' on the disk images.
I have burned a CD from Mac OS 9.2.2 Universal Install.iso. I presume it's fine, because it boots my G4 MDD FW400, and Drive Setup autostarts as designed.
I assume this behaviour is intended to happen identically on the G4 MDD FW800, so that the install does not need a second machine? It doesn't - it won't boot from the CD, but reverts to the OSX drive. Starting with Option held down shows only the OSX drive available as a valid boot drive.
Back on my everyday Mac Mini, I mounted the MacOS9Lives.img image, dug out a FireWire external drive, and Finder copied the System Folder from the mounted MacOS9Lives onto the FW drive. On the G4 MDD FW400, I made sure the System Folder was 'blessed'. Back to the G4 MDD FW800 - starting with Option held down does not list the FireWire drive as a valid bootable volume, even though the startup sequence exercised it for a few seconds. Startup Disk does an even more thorough search on the FireWire drive, but doesn't list OS9, nor does it list the CD.
At this point, having typed the above, I scratched my head, then grabbed MacOSROM_1021_Generic.sit and substituted that ROM for the test one on the FW drive. Option-Startup on the G4 MDD FW800 now reveals the FW drive as a valid boot volume! After using OS9's Startup Disk CP, the machine meekly restarts in OS9 without needing the Option key.
Now impressed!
Cheers,
I am working on another Image That will contain the Modified iMic ROM, his CD can be used on the FW800 and other NON-Supported G4s... However, even if the OS is recognized on unsupported Macs, the booting will vary from not working at all to a full success to anything in between.
Which extensions load for your display card?I've forgotten many of the Mac OS classic tricks. How to tell which extensions are in use?
I've forgotten many of the Mac OS classic tricks. How to tell which extensions are in use?
Cool Video... although you talk too much...lollol, Gf was sleeping a few feet away :)
I woke to find a few questions in my youtube inbox asking how I did this. That was somewhat unexpected its not like I have a lot of subscribers.
PM G4 MDD cannot boot OS9Some people still think we are in 2013. ;D :D
who said that? "PM G4 MDD cannot boot OS9"?A old school user in MacRumors Ppc forum.
A old school user in MacRumors Ppc forum.
I'm tired of most of those "old school" users that now a day think that a PC with Next Step is a Macintosh ... LOL x 2
WOW I never saw an iPhone tower!
WOW I never saw an iPhone tower!
Quoteone should add that this happened in the very very north of andalucia, where people still think that the goat is the biggest animal on earth.
Haha... That's funny IIO!!! ;D
The Power Mac G4 Firmware Update 4.4.8 improves fan control behavior and reduces high speed fan cycling when running in Mac OS 9.
Mac OS Wireless Adapter Compatibility List
(Last updated November 30, 2007)
http://web.archive.org/web/20090323083515/http://www.stateofyo.net/metaphyzx/Wireless.htm
Created an account here just to pop in and say that I have just solved this problem on my own retail MDD G4 FW800. My G4 now dual-boots between OS X Tiger and Mac OS 9.2.2, and both systems are recognized by the Startup Disk control panel.
http://www.blitter.com/
Blitter.Com is a privately run, non-commercial domain promoting Art, Music, Technology and the many intersections thereof.
current machine in studio is 2010 Mac pro and logic 10.2 BUT its midi is funny ! jitter with units is all over the place ! ( I never had those problems under logic 6.4.3 on old mac)everything u need to know to make this 'hack' work is here in this thread, it seems u have not read it carefully enough. you are welcome to do that, or u can download the cd for "unsupported g4's" from the downoads here im not sure if its in the public downloads folder or the members download folder i think it maybe in the public downloads.. but this was an additional solution to the same problem that was created after the fact of thsi thread.. which was a 2nd solution that also worked with a modified "macos.rom" file by our thinkclassic.org user imic.. i suggest u download that cd and burn it and try to boot it.
so .. problem is that G4 don't want to start boot of old system in file that is here fro download.. it say CLASSIC not supported.. Ill go thru forum today .. but Im asking here so maybe i can get it working sooner ;)
...I have 50 synths so I need many midi outputs!...
I have 50 synths so I need many midi outputs!
yes yes so what.. are u guys going to attack this poor guy now too??? give it a restI have 50 synths so I need many midi outputs!
50 synths.... Holy cow!!!😁
mr happy is on the sauce again ???
loading XCOFF
tsize=23000 dsize=2000 bsize=9c000 entry=1c12100
SECTIONS:
.text 01c00000 01c00000 00023000 000000d4
.data 01c23000 01c23000 00002000 000230d4
.bss 01c25000 01c25000 0009c000 00000000
loading .text, done..
loading .data, done..
clearing .bss, done..
_
im not sure how to help as ive never seen this result.. but
using a 10.1 or 10.2 cd to do the formatting + partitioning -- i wouldnt reccommend that you use those..
better to use panther or tiger versions of osx... only because they are more commonplace.
do u have any pci cards installed that could be altering the boot up operation such as a hard drive controller of some sort?
... he thought it was a sawtooth but it was a 4pci slot gigabit ethernet model.. ccmac was talking about reverting the firmware but it turned out this was not neccessary all tht was neccessary to boot 8.6 on the sawtooth was having the original cd which contained the 2.5.1 rom - but the comments he said about saving out a copy of the firmware are whats relevant to this thread and also his comments about this guy, pareis + his openfirmware abilities.. he wrote a script to flash firmware of a mac directly from mac os x called "fwupdater" http://pareis.wordpress.com/2008/02/19/running-firmware-updaters-from-mac-os-x/ AHA! ...
somebody at Apple is wondering who the hell is registering OS 9??? ;D
sorry to revive this thread, but has anyone tried an aluminium powerbook 12 inch 1.5 ghz? would that also work? or other aluminium powerbooks with 1.5 ghz or higher cpu speed...
re: installing the OS9 drivers, mission impossible from the FW 800 itself, not as I read here OS dependent but machine dependent.
video ATI Radeon 9000 Pro - DVI output res is not quite right (1440 x 900 60 Hz is the best option)
video ATI Radeon 9000 Pro - DVI output res is not quite right (1440 x 900 60 Hz is the best option)
Quotevideo ATI Radeon 9000 Pro - DVI output res is not quite right (1440 x 900 60 Hz is the best option)
it should work. did it under OSX?
diskutil partitionDisk /dev/disk1 1 OS9Drivers HFS+ MacHD 0b
diskutil partitionDisk /dev/disk1 2 OS9Drivers HFS+ MacHD 4000M JHFS+ OSXHD R
diskutil partitionDisk /dev/disk1 1 OS9Drivers HFS+ MacHD 0b
diskutil partitionDisk /dev/disk1 2 OS9Drivers HFS+ MacHD 4000M JHFS+ OSXHD R
now we have it, OSX install discs are required to use Terminal, so while you are it, on for example the mac mini solution (which is a real pain to get the drive out and do it elsewhere).
upgrade the existing OS to 10.5, Time machine the contents of the drive to a safe place, and then zap it as above with Terminal to install the OS9 driver
ditto for FW800, and all other none Native OS9 G4 machines.
You can always use Firewire Target Disk Mode if you have another Mac with FW.
You know hold "T" at startup.
you can only boot from firewire if there is a another computer within your reach.Are you implying that we have accepted a member that owns ONLY 1 Mac ?!
you can only boot from firewire if there is a another computer within your reach.Are you implying that we have accepted a member that owns ONLY 1 Mac ?!
This upsets me greatly...hehe
Are you implying that we have accepted a member that owns ONLY 1 Mac ?!
This upsets me greatly...hehe
joke aside, plugging cables can be a real pain depending on the situation. thee more minis you have, the more you will feel the need to build a custom case, and even in my living room there is so much gear on my tables that all my cables are led behind it.Yeah, every room, garage, work, home... there is no escape from the plethora of "stuff" we have accumulated. Old macs never die, they just wait on shelves, to be loved once more.
Are you implying that we have accepted a member that owns ONLY 1 Mac ?!
This upsets me greatly...hehe
no, i was more thinking about the members which have so many macs in their factory hall that afirewire cable might not be long enough.
joke aside, plugging cables can be a real pain depending on the situation. thee more minis you have, the more you will feel the need to build a custom case, and even in my living room there is so much gear on my tables that all my cables are led behind it.
One question , is it possible to Clone a Mac Boot Volume ( normal G4 Not fw 800) with the ASR Software on the CD Rom ?