What command do I type into open firmware to make it install from firewire

Hi All I am trying too get Leopard onto my G4 cube using the open firmware to fake the clock speed using the below:
For single CPUs, use the following three lines:
dev /cpus/PowerPC,G4@0
d# 867000000 encode-int " clock-frequency" property
boot cd:,\\:tbxi
However, my installation is going to be via FIREWIRE so what command do I type into open firmware to make it install from firewire and not CD?
Many thanks
Garry

Hello,
I wanted to do exactly the same until I discovered LeopardAssist!! No need to bother with code lines! It works just fine and its free!
http://www.macupdate.com/app/mac/26562/leopardassist/
Hope this helps.

Similar Messages

PowerMac G5 will not boot into Open Firmware, or Boot Manager

I have a PowerMac G5 and it refuses to boot into Open Firmware. I used Command + Option + O + F and held down the Option key. I have tried 3 different Keyboards but no avail.

Hmmm,
Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
/sbin/fsck -fy
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
http://docs.info.apple.com/article.html?artnum=106214
Does it boot from your Install Disc, or show boot choices when holding alt at bootup?

PowerBook G4 17" Boots into Open Firmware; Won't boot from HD or Disk

This PBG417 (1GHz/512MB/60GB) has an complex recent history directly related to this problem. It was thought to have a dead logic board, and was given to me for a very insignificant amount of money. I discovered today (at an Authorized Apple Repair center) it merely had a ribbon cable disconnected from the logic board which kept it from powering on, which, when rge cable was reconnected it did on the spot, fully booting (imagine my satisfaction). However, upon getting home, it booted into Open Firmware instead, and offedrs a choice of typing mac-boot or shut-down. Mac-boot takes it to the grey screen where the question mark/Finder guy blink and nothing happens. I put a grey PowerBook G4 17" system disk in, but not the one that shipped with it, hoping it would do. When I try to boot from disk, it goes to Open Firmware, I enter mac-boot, it goes to happy Finder with no question folder, but stays there with the optical drive occasionally making movememts and sounds. If you enter any command besides shut down or mac-boot, iot says unknown word; the command prompt itself is 0> .
I'm not sure the hard drive is seated correctly. When I got the computer, the drive was removed; I put it in an enclosure and installed Tiger on it and put it back in, but apart from connecting the ribbon cable, it just sat in its bay not fixed down. However, it booted correctly the first time it was successfully started.
Finally, the previous owner removed all 23 bottom case screws when he took out the drive and lost them; the Apple repair tech mustered up about 9 and put them in the crucial locations but it's still not screwed down everywhere, although the one time it booted correctly, it had no screws in it.
It seems the computer doesn't read the hard drive or the disk, but the hard drive mau be installed wrong and the disk, while for a 17" was not the one that shipped with this PowerBook 17". The computer is missing many case screws, bnutg booted properly only when there were none it place. I also tried resetting the PMU but am not sure I did reset it because the Apple article isn't clear about which models have which processes. I tied Target Disk Mode but it woujldn't mount/boot.
How can I get the disk out and how to make it boot to the desktop?

You can try to reset NVRAM here is KBase from apple site:
http://docs.info.apple.com/article.html?artnum=42642
and after that reset PRAM in your unit, here is the kbase:
http://docs.info.apple.com/article.html?artnum=2238
If needed you can also tried to reset PMU, here is the kbase:
http://docs.info.apple.com/article.html?artnum=14449
Make sure you choose the correct step for your unit.
If after all the steps your unit still booting up to open firmware then there is possibility that you have corrupt NVRAM which could not be fixed by doing reset except replacing logic board.
Good luck. Hope this help
Flippo

Long tone on start up and then goes into open firmware

I stumbled upon the older posts here and thought I'd add a solution.
http://discussions.apple.com/thread.jspa?messageID=6115258
It was about an emac starting up with a long tone and the led flashes a few times and then goes into Open firmware, and when doing "mac-boot" in open firmware, it attempts to start, shows the apple symbol, the screen goes dim and crashes.
It could be a bad power switch. To confirm - you can remove the emac case, be careful not to touch the motitor's picture tube. Find the cable to the power switch; with a small wire just touch together the black and red wires on the power switch cable (or it might be red and green). This will start the emac. If it boots up and runs OK then the power switch was bad. Not sure where to buy a new switch. I soldered and glued my switch together.
<Edited by Moderator>

Or, you'll find both the short pigtail-cabled nVidia graphics driven power switch and the version with a longer cable used with the AIT graphics driven models here* for a good deal less.
Note that the later ATI version can actually be used with either product generation.
*I may receive compensation as a result of parts or services being ordered by users specified at the link shown in this message.

Computer Beeps and loads into open firmware

Hello there!
I've been having this beeping problem intermittently for some time now. Randomly before the startup chime I would hear a single beep from my computer before it restarts and loads normally. According to Apple.com/Support it is a memory problem, I didn't give it much thought since my chips are from my brothers QS2002 G4 1) preinstalled 1) purchased from the Apple Retail Store the computer was purchased from.
Well I popped open the case recently and noticed there was a strong collection of dust around one of the banks (lacking an air can + my vacuum couldn't get to it) I just moved the chip to the opposite bank. Problem Solved! Right?
Not! Last night my brother cold booted the computer and I heard from the kitchen the same beep plus this time it booted into open firmware.
So could this be a problem with my logic board? The Apple Speaker sound port is damaged but I believe it should not affect the rest of the board.
PM G4 DP 800Mhz 256Ram ~80GBHD Mac OS X (10.4.9) 2 xtra 512 ram chip, remvd 256 chp. Maxtor 200gb Ext FW H.D.

Just wanted to update this post with the current status.
I ran all the tests I could think of (TechTool, Apple Hardware Test) several times with all of the hardware tests passing (the software ones said that some of the bundles of custom/noncustom icon bits were on/off but I used to receive that message thousands of times with Norton back around the turn of the century.)
While I personally have not heard any tones or seen it boot into open firmware my brother says it still doesn't that randomly and intermittently at times.
I'm not going to bring it to my Apple Store since if I can't find anything wrong then they probably can't either (that plus I don't want them charging me upwards to a $G for a new logic board "just incase that might be the problem" or not.)
I'm going to leave this post open until further notice ("just in case" I find something else that is causing it, "just in case .
QS2001 PM G4 DP 800Mhz 256Ram ~80GBHD Mac OS X (10.4.9) 2 xtra 512 ram chip, remvd 256 chp. Maxtor 200gb Ext FW H.D.

Can't Get into Open Firmware

Hi there,
I've got a G3 All-in-One and I can't seem to get into Open firmware properly. I've got the right combination (Option-Apple-O-F) but the screen just goes black. I've tried this on two different units and they do the same thing. Am I missing something?
Thanks in advance...

every once in a wile mine does the same thing. but it really is at open firmware its just the screen is so dark you can barly see anything even in a room at night with all the lights out. try doing it in a very dark room and look real close to the screen.try resetting pram first to see if that helps and then try to go into open firmware. I have 2 beige G3 AIO's both do this try to hold the key combo as soon as you start to hear the start chime, then if this dont work try to hold them just after the start chime, and try to hold them at diffrent length's of time first start by trying to jusk keeping the key combo held down, then try realeasing then just after start chime, one of these combo holds should work. but make shure you are in a room that will be dark with the light's turned out cause very faintly you should see the open firmware prompt at the very top left of the screen.
good luck

What is the best way to open close and pass instrument handles from labview in teststand parallel model?

I have a number of test systems that use a parallel model with labview. We have a good number of instruments(PXI).
What is the prefered method for open,closing and passing instrument handles in teststand using labview?
Solved!
Go to Solution.

Hi,
No, Below is a bit from the Session Manager Help
Currently, Session Manager supports the following instrument session types:
IVI Sessions—Use an IVI session to obtain the C-based instance handle for an IVI logical or virtual instrument name. NI Session Manager does not support IVI-COM drivers at this time. When IVI-COM drivers are available, you can use an IVI session to obtain an ActiveX interface reference to an IVI-COM driver.
VXIplug&play Sessions—Use a VXIplug&play session to obtain a C-based instance handle for a VXIplug&play logical or virtual instrument name. Configure VXIplug&play names in the <VXIplug&play directory>\<Platform directory>\NISessionMgr.ini file.
VISA Sessions—Use a VISA instrument session to obtain a C-based viSession handle to a VISA resource or logical name. Configure VISA logical names in the <VXIplug&play directory>\<Platform directory>\NISessionMgr.ini file.
Custom Sessions—Use a custom session to create a data container object that shares ActiveX objects you create or other data between software components you write. Use the Attach and Get methods to attach data to and retrieve data from a session. A custom session does not initialize, close, or own an instrument handle. The data you share with a custom session does not have to be instrumentation related. You can create a custom session with any name you request.
Regards
Ray Farmer
Regards
Ray Farmer

Intel iMac, Open Firmware Password Protection and booting from CD

I have an Intel iMac I'm setting up for use in a public library. I want to prevent single user login with the Open Firmware Password Protection utility, but if I do, how do I boot from the OS disc, zap PRAM, etc? The OFPP page has instructions on removing the OF password, but it does not work on Intel Mac's. Also, is there an alternative way to prevent single user login?

No, you were right, I just misunderstood. Technically it's called single-user mode. But, you were right.
Anyway,
Since it seems that there might not be an answer directly related to your topic you could maybe give this a try.
In Simple Finder the user can not restart or shutdown. They can only sleep and log out.
The other problem, however, is if they log out then there are those Sleep, Restart, and Shut Down buttons on the login screen. Luckily, though they can be turned off.
So as of now, if some is logged in in a Simple Finder account they can not restart or shut down the computer in order to get into single-user mode. They can also not get into the Administer account since it is password protected.
The only problem I can see with this is that a person could do a hard shut down, hold the power button down until it turns off, and then boot up and enter single-user mode.
If you want to go ahead and do this, in order to get the computer up and running in the mean time, just post back and I'll be glad to help you set up a Simple Finder account.

What command would you use to open a directory (i work with mostly vista

and xp...basically...I want to get a button to open an explorer file directory

public class Exec {
     public static void main(String[] args) throws Exception {
    String[] commands =
       {"cmd", "/c", "start", "\"title\"", "\"c:/program files\""};
       Runtime.getRuntime().exec(commands);
}You need to pass a dummy title to the start command especially if the target contains spaces.
Bye.
RG.

What do you do when it ask to insert CD2 when installing from the download?

I was unable to activate my CS2 software on the new computer. I have downloaded the new files as suggested on the activation 1-800#. Now it's asking me to insert CD2 and although it was sucessfully downloaded it's not automatically opening it and I don't know what to do. Please help!

move all the extracted files into the folder created by the first cd extraction.

PowerBook G4 boots to Open Firmware without keyboard access

Summary:
Let me provide a little backstory.
According to the [DARPA Visitor Guidelines|http://www.darpa.mil/body/visitor_guidelines.html] wireless network technology is prohibited from DARPA facilities. Laptops with a wireless card are required to be "disabled at the BIOS level".
Before an upcoming visit to DARPA I was told that I would need to make sure my laptop wireless card was disabled. I mentioned that Macs don't have BIOS but I'd look into doing it in Open Firmware. The response from DARPA was that no one has ever successfully brought an Apple laptop into the facility, and that I should procure a PC laptop for my visit. Ah, a challenge!
I booted into Open Firmware (⌘⌥OF), located the wireless card in the device tree, and removed two properties I figured the driver would be searching for: the vendor ID, and the product ID. I exited Open Firmware and continued to boot into Mac OS X v10.5.2.
Sure enough the System Profiler showed that no wireless card was installed. Success! Now I just need to make the device tree modifications persist between reboots.
It seemed the solution was to place the Open Firmware commands I issued to disable the card into nvramrc. So I set nvramrc to contain the same commands, and set use-nvramrc? to be true. I rebooted the machine but the card was still detected.
A bit [more research|http://docs.sun.com/app/docs/doc/805-4436/6j4719c8v?a=view] revealed that the device tree is not created by Open Firmware until after the nvramrc is executed. The solution is to build the device tree in the nvramrc and tell Open Firmware not to rebuild it. The documentation states that this is accomplished with the probe-all, install-console, and banner Forth commands. I added those commands to my nvramrc and rebooted. The contents of nvramrc:
probe-all install-console banner
dev wireless
" device-id" delete-property
" vendor-id" delete-property
The outcome... well technically the laptop has wireless disabled. Almost everything is disabled. The machine now boots directly into Open Firmware with a few ominous bits of output and no response from the keyboard.
no active package
Apple PowerBook5,6 6.4.9.1f1 BootROM built on 01/21/05 at 10:51:16
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.
Welcome to Open Firmware, the system time and date is 05/06/2008 10:00:00
Command security mode
To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.
ok
0 > _
The first sign that something has gone wrong is no active package. The second message just throws another wrench into the works: Command security mode. Yes, the Open Firmware password was enabled. In retrospect this was a bad thing to have set when mucking about in OF. I knew of the RAM change trick (see below) so this was not an issue at the time.
Question:
So the question is: What actions do I need to take to return the laptop to a useable state. That is, booting into Mac OS X.
*Attempted solutions:*
+1. Reset nvram+
The first and most obvious solution is to reset nvram using the snag key combination ⌘⌥PR. Unfortunately do to the firmware password being set, [all snag keys have been disabled|http://support.apple.com/kb/HT1352]. This means no target disk mode (⌘T), boot from CD (⌘C), boot from network (⌘N), etc... In any case an attempt at resetting nvram yields an additional message being appended to the Open Firmware screen:
Release keys to continue!_
+2. Reset nvram after changing amount RAM in system+
Luckily there is a work-around to firmware password protection. Changing the amount of RAM installed in the machine should allow the nvram zap snag to function. I removed one of the two 512MB DIMMS in the laptop and started up while holding down ⌘⌥PR. This results in the same message as above:
Release keys to continue!_
Not so lucky.
+3. Reset the Power Management Unit+
[Resetting the Power Management (PMU)|http://docs.info.apple.com/article.html?artnum=14449] is accomplished by removing the battery and disconnecting the power cord, and then holding down the power button for about 5 seconds. This had no effect besides resetting the system clock to 01/01/1904 00:00:41.
Getting more desperate...
+4. Search logic board for CUDA+
I [opened the machine|http://www.ifixit.com/Guide/Mac/PowerBook-G4-Al-15-Inch-1-5-1-67-BT-2-0 -LR/64] to search for a hidden [CUDA button|http://docs.info.apple.com/article.html?artnum=86760]. As expected, a CUDA button does not exist on this model and the PMU reset is accomplished as noted in attempted solution 3.
+5. Remove internal battery+
Well the laptop is open now, so I tried removing the internal memory backup battery and revisited each of the above solutions. No success.
+6. Remove hard drive+
Again, since the laptop was open, why not remove the hard drive and see what happens. The machine wasn't even making it to the boot-loader hand-off so I didn't expect this to produce any results. No results produced.
Thinking crazy thoughts...
+7. Attempt a firmware update+
Firmware updates have a side effect of resetting the nvram. Also firmware updates are initiated very early in the startup process by holding down the power button until a tone is heard and the power light flashes. My thought was that I would grab a previous firmware update for this laptop and force it to be reapplied. Unfortunately there have been no updates to this model's firmware.
+8. Write my own firmware update script+
While investigating solution #7 I realized that the file BootROMFirmware installed by the firmware updaters for G5s and G4s machines are just Forth programs with a binary payload attached to the end. I learned [Forth|http://en.wikipedia.org/wiki/Forth(programminglanguage)]. The BootROMFirmware files are really cool, since they do everything from drawing the progress bar during the update, uncompressing and check-summing the binary payload, and generally making sure you don't brick your machine. In any case it seem entirely doable to write my own program in Forth and undo the evil I did before. I really only need to flip one bit. I needed the use-nvramrc? variable set to false. So I created this very simple Forth program:
\ debrickifier
setenv use-nvramrc? false
reset-all
The original firmware file had additional attributes set, a creator and file type of fw99. So I set those two attributes on my file as well. I ran strings on the firmware installer program and guessed that it was copying the file to /System/Library/CoreServices. So this is where I placed my Forth file. Reinstalled the drive and rebooted the laptop while holding down the power key to initiate a firmware install. No dice.
Its hard to tell why this is failing. The file may in the wrong place, have the wrong permissions. From what I've reviewed in the original files, the setenv and reset-all words should be available. Maybe the Firmware Update utilities are setting some other magic in nvram before the reboot.
I think I've covered all the different major solutions that I've attempted. Their might be a few more that I've forgotten to mention (like using an external USB keyboard). I still think that getting some Forth to execute via the firmware update mechanism could use some more exploration. My current worst case is that I'll replace the logic board, although I'd hate to do that when I know there are only a few bad bits flipped in a CMOS somewhere.
I'm hoping to snag the attention of the resident hardware/firmware guru that can shed some light upon the firmware update process, but any help or suggestions would be greatly appreciated.
Cheers,
Mark

For your next DARPA visit, another option might be to buy the cheapest possible third-party wireless card — it doesn't even need to work. Insert it into your Powerbook's CardBus slot before visiting DARPA, and turn Airport off in System Prefs. On arrival at DARPA, remove the card from the Powerbook and hand it to the security guard. Retrieve it from the guard as you leave, and turn Airport back on again when you get home or back to your office. Unable to comply with the letter of the dunderheaded regulation because you have no BIOS, you will be complying with the spirit of it instead, and no one will be the wiser.

HELP NEEDED URGENTLY .... please! (open firmware password vs. startup disc)

Hi
1. Macbook Pro 2.33 - I had Bootcamp installed.
2. Decided to delete it... went through Bootcamp procedure
3. Mac restarted - then came up with a flashing folder icon, meaning it couldn't find the startup drive.
4. Forced restart again... and tried pressing ALT key to select Macintosh_HD - it asked for my OPEN FIRMWARE PASSWORD - i only ever use 1 password - I know exactly what this is, as I had turned it on/off before by going to utilities>open firmware.
I don't want to take RAM out... is there another way? I thought if a CD was put in it could trick firmware... by pressing the space bar... though it didn't work
I'm stumped! Anybody willing to help?
Thanks loads in advance!
Pixel.

Boot from Install DVD1 holding down 'C'
Then 'Reset Password' ?
or ...
1. Start up into Open Firmware by pressing and
holding the Command-Option-O-F key combination
during startup.
2. At the Open Firmware prompt, type: reset-nvram
3. Press Return.
4. When prompted for your password, enter it and
press the Return key.
5. It responds OK.
6. At the Open Firmware prompt, type: reset-all
7. Press Return.
This only works with PPC Macs. I have been looking for a way to do something similar with my MBP and have been unsuccessful thus far.
Frank

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

Can't open CDs in Open Firmware

I'm working on a dual boot setup for my laptop, and I have run into an interesting problem: I cannot boot from CDs. If I boot into Open Firmware, and try booting the CD from there, it says that it can't. Entering dir cd:\ in the OF prompt tells me that it can't open cd. Which leads me to believe that there may be a driver problem. I can boot the OS X Leopard DVD fine though. At any rate, it would be nice to know if it's possible to get new drivers, or if there is any way around this. Thanks.

VaultOfThrones wrote:
I'm working on a dual boot setup for my laptop, and I have run into an interesting problem: I cannot boot from CDs. If I boot into Open Firmware, and try booting the CD from there, it says that it can't. Entering dir cd:\ in the OF prompt tells me that it can't open cd.
Why is there a colon in that cd command? Is this some PC thing?
And why "dir" and not "ls"?? And what's with the backwards slash?
If cd is a directory the command would be ls /cd or something like that.
What does the command ls show is in the directory? Is cd even a directory?
Usually cds are usually mounted in /dev under disk. I have never seen a cd mountpoint labeled cd.
cd seems to be a very confusing name since it's also a command.
Message was edited by: nerowolfe

Old iMac & Open Firmware Troubles

Hi,
I have an old iMac (G3 I think?) that did run Mac OS 9.1; until one day I shut off the power via the power button instead of the GUI way, and the next time I turned it off it quit on me. It now (every time it turns on) mockingly shows a blinking folder with the Finder logo and questionmark blinking intermittenly.
So naturely, I brought it to the Apple store, hoping they would help me as they did my old Powerbook 1400c. They did, but not enough to get it functional.
Anyway, I've been able to get it to boot into Open Firmware (via Command+Alt+O+F); but that's it. I tried issuing common commands that people have said worked for them, but to no avail. For example, I used "mac-boot", "boot hd:,\\", "reset-nvram" (or whatever that command is to reset the NVRAM), "reset-all", and even used "boot cd:" (and "boot cd:,\\") while my Mac OS 8 install disk is in there (I don't have 9), but it does not work.
Whenever I issue the "boot hd:,\\" and "boot cd:"; it comes up with the following message:
         load-size=0 adler32=1
         LOAD-SIZE is too small
So my question is this: how/what can possibly be done to get this old computer up and running again? Some people have suggested it could be the logic board, but I am deeply hoping not (I dont' have the skill or money required to get & install one). Any ideas?
        Thanks!
P.S.- Does anyone know the boot command to make it boot from CD? I think the apple guys tried it already (and did not work), but I might as well try again. Also, if it's any help, the Open Firmware version is 3.0.f2 .

Hello,
Would it be correct to assume that the PRAM has been successfully reset?
http://support.apple.com/kb/ht1379
It is possible that the internal 3.6 V battery is bad. This may or may not affect the ability to locate a valid system.
http://manuals.info.apple.com/en_US/iMacG3_originalInstallGuide.PDF
>Mac OS 8 install disk is in there
Is it a Mac OS 8.1 or 8.5 CD that came with the computer, not a plain Mac OS 8 disc?
>Does anyone know the boot command to make it boot from CD?
Normally, one would press the C key. However, if this does not work, you could try holding down the four keys Command(Apple) + Option(Alt) + Shift + Delete(Backspace).
http://manuals.info.apple.com/en_US/iMacG3_originalEmergencyHndbk.PDF
Jan

What command do I type into open firmware to make it install from firewire

Similar Messages

Maybe you are looking for