Maybe a third of the time I put my system to sleep for the night I wake the next morning, wake it up, and find that Classic is gone and needs to be relaunched.
Has anyone else had this happen to them? Is there a fix for this?
Stan Randle wrote:
Maybe a third of the time I put my system to sleep for the night I wake the next morning, wake it up, and find that Classic is gone and needs to be relaunched.
Has anyone else had this happen to them? Is there a fix for this?
Check System Preferences --> Classic --> Advanced (Tab) and make sure Classic sleep is set to 'Never'.
Classic sleeps without incident on all of my Macs, so I don't have any further ideas here.
-John Steinbergemail: manbytsdog at hotmail dot com | http://nexstar.50megs.com/
In article 1f912nw.kmtusa10gc6sgN%stanman2171@redacted.invalid, Stan Randle stanman2171@redacted.invalid wrote:
Maybe a third of the time I put my system to sleep for the night I wake the next morning, wake it up, and find that Classic is gone and needs to be relaunched.
Has anyone else had this happen to them? Is there a fix for this?
There's a setting in Classic Preferences to put Classic to sleep. You might want to see if that has anything to do with it.
Matthew Russotto russotto@redacted.invalid wrote:
There's a setting in Classic Preferences to put Classic to sleep.
What does it actually mean for Classic to go to sleep? That concept confuses me.
At any rate, I set Classic sleep to "Never" (thanks John S.) and we'll see if that does anything.
Stan Randle stanman2171@redacted.invalid wrote:
There's a setting in Classic Preferences to put Classic to sleep.
What does it actually mean for Classic to go to sleep? That concept confuses me.
Well, when Classic goes to sleep it does not shut it down. It just "freezes" or stops that process, so it becomes inactive and takes almost no CPU-time. That way it'll be in the background and wake to life whenever you want to start a Classic application. Waking up the Classic Environment takes about 10 seconds on my iBook 500.
It's wierd if Classic just dies for you when the computer goes to sleep. That's not supposed to happen, and I doubt turning off Classic sleep will help the situation.
In article 1f91tor.1algcdx3m25nmN%onar@redacted.invalid, onar@redacted.invalid (Onar Vikingstad) wrote:
It's wierd if Classic just dies for you when the computer goes to sleep. That's not supposed to happen, and I doubt turning off Classic sleep will help the situation.
It's a bug; I've seen it as well. Check the Apple discussion forums for more examples.
--Marc
In message 1f91tor.1algcdx3m25nmN%onar@redacted.invalid, onar@redacted.invalid (Onar Vikingstad) wrote:
Stan Randle stanman2171@redacted.invalid wrote:
There's a setting in Classic Preferences to put Classic to sleep.
What does it actually mean for Classic to go to sleep? That concept confuses me.
Well, when Classic goes to sleep it does not shut it down. It just "freezes" or stops that process, so it becomes inactive and takes almost no CPU-time. That way it'll be in the background and wake to life whenever you want to start a Classic application. Waking up the Classic Environment takes about 10 seconds on my iBook 500.
It's wierd if Classic just dies for you when the computer goes to sleep. That's not supposed to happen, and I doubt turning off Classic sleep will help the situation.
I concur with that, although I didn't test this. Having the ability to put Classic to sleep from OS X when it's been inactive (btw, what is Apple's definition of inactive? The menubar clock is always running...) after some time is very welcome, since this sucker always takes 5 to 10% of the CPU time when no applications are running.
And yes, from time to time, I have this problem when I put my Pismo to sleep. In my case, Classic drops into Macsbug so an ExitToShell will sometime keep it running.
-Laurent.