Help - Search - Members - Calendar
Full Version: PRAM
Project OS X Forums > Previous Releases > Mac OS X Leopard 10.5 > Leopard Guides & Tutorials > New Users Discussion
Gringo Vermelho
Since the early days, most troubleshooting procedures on real Macs involve "zapping the PRAM".

http://support.apple.com/kb/HT1242

But where is the PRAM on a Hack?

Are the contents written to a file somewhere?

And what about the NVRAM...or is NVRAM and PRAM the same thing?
realityiswhere
QUOTE (Gringo Vermelho @ May 19 2009, 04:06 PM) *
Since the early days, most troubleshooting procedures on real Macs involve "zapping the PRAM".

http://support.apple.com/kb/HT1242

But where is the PRAM on a Hack?

Are the contents written to a file somewhere?

And what about the NVRAM...or is NVRAM and PRAM the same thing?


As far as I'm aware, this is handled by the custom Apple EFI, and is exclusive to the Mac hardware/firmware, not the software.

That is, it's limited to real Macs with real EFI, not regular PC's with BIOS's.
Gringo Vermelho
Thanks, that makes sense.

But then - since we can't have this functionality, what happens with the settings that were supposed to go in PRAM/NVRAM?

Where are these settings stored on a PC running OS X?

EDIT - why can't I reply to this topic?

I wonder if some kind of software redirection to a file would be useful on a Hack. Whatever is stored there must be important.

I'm guessing it would require a lot of skill and knowledge to write a driver that intercepts something that goes on at such a low level.
Kiko
they would go into EFI nvram, which happens to be at a different memory address on macs, so i guess they either never get written (because of lack of EFI interface), or they just get written to normal ram
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.