Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There's some dedicated processor on pbook mainboards and some other voodoo that goes on. Here are my suggestions:

    1. Zap the PRAM. Do this by holding cmd-opt-P-R during boot. I think it'll BONG more than once if it zaps. I'm not sure about that.

    2. Enter openfirmware by holding cmd-opt-O-F. At the openfirmware prompt, run "reset-nvram"

    I make no guarantee that these will not cause your Mac to explode, but I do suggest that it's unlikely. I had this problem once, and PRAM-zapping would help for a while
    --
    rjbs
  • Did both PowerBooks have the reasonably recent (January, iirc) Battery Update installed? Does installing it now help?

    If the answers are 'yes' and 'no', then this will have been useless. You never know, though.
  • No more warranty on either powerbook?

      - ask
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();

  • ... the process is different depending on what model you have. See this knowledge base article [apple.com] for more info.

    You might also see what the command line tool battery [mitt-eget.com] thinks is happening.