In my experience, many problems, from a screen that wouldn't turn on, to a malfunctioning Firewire port, etc were not fixed by zapping the PRAM, even as many as 5 times in a row. However, booting into Open Firmware and issuing the combo of reset-nvram set-defaults reset-all fixed them right up.
PRAM doesn't reset ALL your open firmware settings, where each of these commands does. So a word to all...if zapping PRAM doesn't work...try OF....its proven by me to work.
In my experience, many problems, from a screen that wouldn't turn on, to a malfunctioning Firewire port, etc were not fixed by zapping the PRAM, even as many as 5 times in a row. However, booting into Open Firmware and issuing the combo of reset-nvram set-defaults reset-all fixed them right up.
PRAM doesn't reset ALL your open firmware settings, where each of these commands does. So a word to all...if zapping PRAM doesn't work...try OF....its proven by me to work.</strong><hr></blockquote>
I don't want to refute your experience, I just want to state a few facts. NVRAM is reset by zapping your PRAM. All configuration variables reset by the set-defaults command are also reset by zapping your PRAM. These commands are quite useful on a sun machine, but obsolete on a mac thanks to the keyboard zap shortcut, which is simply issuing these OF commands without the user having to mess around with a command line. The last command issued by the PRAM zap is a reset-all. So why would you sometimes have success with OF commands and not PRAM zaps? It's probably like any electronic device with a reset switch. Sometimes you have to hit it multiple times to get it to work right. I've also found unplugging a machine and letting it sit for 5 minutes and then plugging it back in can fix it. Why? I don't know, but if all else fails, I'll try it and hope.
I don't want to refute your experience, I just want to state a few facts. NVRAM is reset by zapping your PRAM. All configuration variables reset by the set-defaults command are also reset by zapping your PRAM. These commands are quite useful on a sun machine, but obsolete on a mac thanks to the keyboard zap shortcut, which is simply issuing these OF commands without the user having to mess around with a command line. The last command issued by the PRAM zap is a reset-all. So why would you sometimes have success with OF commands and not PRAM zaps? It's probably like any electronic device with a reset switch. Sometimes you have to hit it multiple times to get it to work right. I've also found unplugging a machine and letting it sit for 5 minutes and then plugging it back in can fix it. Why? I don't know, but if all else fails, I'll try it and hope.</strong><hr></blockquote>
Well, sure. Just as long as you, and anyone else reading this thread realizes that sometimes when all seems lost and PRAM won't zap, you should try entering the commands yourself, because whether it SHOULD or not, it works a lot of the time when PRAM doesn't. If only the world were based on "should" instead of "does"...
BTW I'll keep that unplug-for-5-minutes thing in mind
Comments
setenv
devalias
dev / ls
<strong>printdev
setenv
devalias
dev / ls</strong><hr></blockquote>
thx, now can you tell me what they do?
<strong>
thx, now can you tell me what they do? </strong><hr></blockquote>
printdev - shows all OF variables
setenv - used to set OF variables
devalias - shorthand representation of a device path eg devalias "hd" is shorthand for the whole device path of the internal HD
dev / ls - lists all of the machine's devices (I think)
J :cool:
<strong>Anyone know any other besides....
reset-nvram
reset-all
eject cd
mac-boot
shut-down
List um here. Thx</strong><hr></blockquote>
set-defaults
It should go with 2 others...like this:
reset-nvram
set-defaults
reset-all
From what I hear...but good thread idea!
BTW this is my 100th post! PARTY TIME!
<strong>Why don't you create your own commands?? Isn't OF a FORTH based environment??</strong><hr></blockquote>
Yes, it's a FORTH environment. There's plenty of info at Apple's developer site. Just go to developer.apple.com and search for open firmware.
[quote]Originally posted by The All Knowing 1:
<strong>
set-defaults
It should go with 2 others...like this:
reset-nvram
set-defaults
reset-all
From what I hear...but good thread idea!
BTW this is my 100th post! PARTY TIME! </strong><hr></blockquote>
reset-nvram = resets the nvram to it's default values, which can also be reset by zapping the PRAM
set-defaults = sets all configuration variables (including nvram) to their defaults, which can also be done by zapping the PRAM
reset-all = resets the target computer, which can also be reset by zapping the PRAM
Therefore, zap your PRAM instead!
For a complete listing of open firmware commands, try here: <a href="http://www.firmworks.com/QuickRef.html" target="_blank">http://www.firmworks.com/QuickRef.html</a>
<strong>that link didn't work</strong><hr></blockquote>
Worked 4 me.
J :cool:
<strong>
Therefore, zap your PRAM instead!
</strong><hr></blockquote>
Not the same thing, friend.
In my experience, many problems, from a screen that wouldn't turn on, to a malfunctioning Firewire port, etc were not fixed by zapping the PRAM, even as many as 5 times in a row. However, booting into Open Firmware and issuing the combo of reset-nvram set-defaults reset-all fixed them right up.
PRAM doesn't reset ALL your open firmware settings, where each of these commands does. So a word to all...if zapping PRAM doesn't work...try OF....its proven by me to work.
<strong>
Not the same thing, friend.
In my experience, many problems, from a screen that wouldn't turn on, to a malfunctioning Firewire port, etc were not fixed by zapping the PRAM, even as many as 5 times in a row. However, booting into Open Firmware and issuing the combo of reset-nvram set-defaults reset-all fixed them right up.
PRAM doesn't reset ALL your open firmware settings, where each of these commands does. So a word to all...if zapping PRAM doesn't work...try OF....its proven by me to work.</strong><hr></blockquote>
I don't want to refute your experience, I just want to state a few facts. NVRAM is reset by zapping your PRAM. All configuration variables reset by the set-defaults command are also reset by zapping your PRAM. These commands are quite useful on a sun machine, but obsolete on a mac thanks to the keyboard zap shortcut, which is simply issuing these OF commands without the user having to mess around with a command line. The last command issued by the PRAM zap is a reset-all. So why would you sometimes have success with OF commands and not PRAM zaps? It's probably like any electronic device with a reset switch. Sometimes you have to hit it multiple times to get it to work right. I've also found unplugging a machine and letting it sit for 5 minutes and then plugging it back in can fix it. Why? I don't know, but if all else fails, I'll try it and hope.
<strong>
I don't want to refute your experience, I just want to state a few facts. NVRAM is reset by zapping your PRAM. All configuration variables reset by the set-defaults command are also reset by zapping your PRAM. These commands are quite useful on a sun machine, but obsolete on a mac thanks to the keyboard zap shortcut, which is simply issuing these OF commands without the user having to mess around with a command line. The last command issued by the PRAM zap is a reset-all. So why would you sometimes have success with OF commands and not PRAM zaps? It's probably like any electronic device with a reset switch. Sometimes you have to hit it multiple times to get it to work right. I've also found unplugging a machine and letting it sit for 5 minutes and then plugging it back in can fix it. Why? I don't know, but if all else fails, I'll try it and hope.</strong><hr></blockquote>
<img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />
Well, sure. Just as long as you, and anyone else reading this thread realizes that sometimes when all seems lost and PRAM won't zap, you should try entering the commands yourself, because whether it SHOULD or not, it works a lot of the time when PRAM doesn't. If only the world were based on "should" instead of "does"...
BTW I'll keep that unplug-for-5-minutes thing in mind
<a href="ftp://ftp.machack.com/Hacks98/ofpong.sit" target="_blank">ftp://ftp.machack.com/Hacks98/ofpong.sit</a>
If you look at the source, there are a many commands for your enjoyment.