[berg]

Hi again Newstetter ..
Can you reset the pmu?
You're not running MySQL are you?

[Newstetter]

MacCheetah,
Thanks for the Knowledge Base article. It seems that if there was a problem with the PMU that it wouldn't be normal under OS 9 - yes?
I haven't put any PCI cards into the computer since I installed the Pro Tools card when the computer was brand new. Protools runs fine in OS X.
I did add two 128 RAM modules after updating - but I had the problem before adding the memory.

Berg,
Not running MySQL

[MacCheetah3]

Hi
That could seem logical but certainly not an impossible cause. At this point, isn't it worth a try anyway?

[Newstetter]

OK - I held my breath - crossed my fingers - and, weilding a carefully selected toothpick (modified with a blunted end) - I pressed the PMU button....
Went to the kitchen had a few sips of coffee - glanced at the morning paper - - returned to the G4 (affectionately known as 'Fluffy') - - and pressed the power button.
Booted up to 4:00 AM 1969 - reset the clock - took a deep breath - pressed the power button again - selected the 'sleep' command -
and -
and -
NO CHANGE!!!
Still sleeps fine in OS 9 - but Panther is still as restless as ever!
I tried singing lullabyes - playing soothing music - gently stroking the side of the casing - - - Fluffy the panther won't sleep....
---- Soooo -
.... Then I booted from my Firewire drive where I have OS X installed as a backup system for my Powerbook (HAL)...tried the sleep command - and it worked!
I'm thinking that there must be some artifact on my system drive that is somehow getting in the way of the sleep process.
Unless someone can offer any other possibilities (maybe some tweak in the Terminal) ....Perhaps the only way to solve this problem is to zero out the HD and start from scratch.
<arrrrggghhh></arrrrggghhh>

[Newstetter]

UPDATE....
After zeroing the HD and reinstalling OS X and checking the sleep function at every available juncture, I've isolated the cause of the problem!
It seems that Pro Tools is the culprit!
After the OS reinstall I was able to sleep the computer normally until I installed Pro Tools. Somehow PT is disabling sleep - even when it isn't running.
While the Pro Tools manual instructs the user to set the Energy Saver to 'Never Sleep' - it doesn't seem to mention that installing the application actually cripples the sleep command entirely.
Oh well....
Since Pro Tools is the primary use for this computer I suppose I'll have to live with the sleep issue until or unless there's a way to fix it without breaking Pro Tools.
At least now I know where to look for an answer, having ruled out any System or hardware issue on the Mac end of things.
Thanks to those who helped me troubleshoot this problem in this thread. I'll probably find something about the issue on a Digidesign (Pro Tools) forum.

[MacCheetah3]

Hi
Congrats on at least digging out the cause. Too bad it's not something you can fix.

[DPG4450Guy]

Don't hold your breath.
ProTools mgmt has stated they are moving forward on the WIN side with only incremental improvements on the Mac after a WIN upgrade.
They've been cold towards Apple ever since the Logic purchase.
I think this is a foolish policy (I'm not a musician but have a G4 Sawtooth and a G5 friend(s) that are, and they have decided to build PC boxes just due to this.)
/forums/ubbthreads/images/graemlins/frown.gif
[Sure hope I don't sleep-walk and put the Blaster worm on those boxes via a floppy due to sub-concious angst.]

[Newstetter]

Following up - - -
Apparently the sleep mode is an issue with Pro Tools all over the place...
I found this;
http://xmidi.com/digisleep.html

In reply to:

---

Text from the xmidi.com site.....

The Problem (in some detail):
In Mac OS X, when a user selects 'SLEEP' from the Apple menu, the Mac enters into a state (called forced sleep mode) where the following things happen:
1.The monitor signal ceases (the screen goes black)
2.The cooling fan on the chassis stops
3.The cooling fan on the CPU stops
4.Power is reduced to various components in the system (including the PCI bus and the CPU)
Before Mac OS X actually performs these tasks, it polls certain processes to determine if it's alright to go into forced sleep mode. System level processes (KEXTs to be specific) are allowed to veto such requests. When this happens, the system will not go into forced sleep mode but rather idle sleep mode. Idle Sleep only performs the first task listed above (the monitor screen blacks).
Why do I mention all this? Because Digidesign implemented their Audio drivers in the form of a KEXT that will, indeed, veto the Mac's request to enter forced sleep (some people call this deep sleep).
The Result:
The result of Digidesign's decision to veto all requests for forced sleep simply cripples Mac OS X. Users who frequently use SLEEP are now forced to forego the operation and SHUTDOWN/REBOOT instead. While this might not seem like such a severe tradeoff, it does impose on the usage patterns of Mac users. Simply put: Digidesign should not have the authority to cripple ANY features built into Mac OS X (or any other OS for that matter).
The Solution (for now):
My (very naive) solution is to remove the KEXTs from the system when I know I will not be running Pro Tools 6.x. When the application is launched, it will check for the existence of the following two files:
DigiDal.kext
DigiIO.kext
in either of these two directories:
/System/Library/Extensions/
your home directory
If the files exist in the system directory, they will be moved to your home directory and vice versa. Mac OS will then need to be rebooted for the change to take effect. The app will do this automagically. Once the files are moved (and the OS has rebooted) your Mac will be able to enter forced sleep again but you will not be able to run ProTools. In order to run Pro Tools, simply launch DigiSleep again and the files will be moved from your home directory to the system directory (and rebooted again).
The tradeoff ? I'd sooner reboot my Mac only before and after using Pro Tools 6.x versus every single time I use my Mac. That is why Apple implemented SLEEP in the first place, right?

---

Thought I'd pass this along to others who might be experiencing this problem and/or for anyone else who's interested.