can't connect to sleeping 10.1 box

tom keyes wrote on :
First time I tried to connect to my OS10.1/G4 from home I couldn't do it. My IP was totally off the net, couldn't even ping it. I came in this morning and tried from another G4 in the office, still no luck. Then I went to my desk, hit a key to wake the G4, and then connected with no problem. Somehow it goes off-line whe asleep. I had both energy saver and screen saver on but G4 was just showing a blank dark screen so i suppose screensaver goes off when sleep starts. is it the combination of both 'savers' that puts me off line? is this a known 10.1 problem? Another thing I'm getting on waking from overnight sleep is blank white spaces where classic app windows were and I have to restart classic. How about that one? TIA for any hints....tom
Ralph Wade Phillips replied on :

Howdy!

"tom keyes" keyes@redacted.invalid wrote in message news:111020010903251559%keyes@redacted.invalid

First time I tried to connect to my OS10.1/G4 from home I couldn't do it. My IP was totally off the net, couldn't even ping it. I came in this morning and tried from another G4 in the office, still no luck. Then I went to my desk, hit a key to wake the G4, and then connected with no problem. Somehow it goes off-line whe asleep. I had both energy saver and screen saver on but G4 was just showing a blank dark screen so i suppose screensaver goes off when sleep starts. is it the combination of both 'savers' that puts me off line? is this a known 10.1 problem? Another thing I'm getting on waking from overnight sleep is blank white spaces where classic app windows were and I have to restart classic. How about that one? TIA for any hints....tom

    Uhhh ... "Whenever my SO is sleeping, s/he can't run the vacuum

cleaner."

    Think about it, if it's sleeping, how WILL it answer?
If you want it to be up all the time, disable sleep.  Nothing wrong

with the screensaver, but DON'T SLEEP IT!

    (This is just about Homer Simpson "D'oh!" time.)
RwP

Doug Brown replied on :

In article 9q48kb$l4th4$1@redacted.invalid, "Ralph Wade Phillips" ralphp@redacted.invalid wrote:

Howdy!

"tom keyes" keyes@redacted.invalid wrote in message news:111020010903251559%keyes@redacted.invalid

First time I tried to connect to my OS10.1/G4 from home I couldn't do it. My IP was totally off the net, couldn't even ping it. I came in this morning and tried from another G4 in the office, still no luck. Then I went to my desk, hit a key to wake the G4, and then connected with no problem. Somehow it goes off-line whe asleep. I had both energy saver and screen saver on but G4 was just showing a blank dark screen so i suppose screensaver goes off when sleep starts. is it the combination of both 'savers' that puts me off line? is this a known 10.1 problem? Another thing I'm getting on waking from overnight sleep is blank white spaces where classic app windows were and I have to restart classic. How about that one? TIA for any hints....tom

    If you want it to be up all the time, disable sleep.  Nothing wrong

with the screensaver, but DON'T SLEEP IT!

I agree.

I think this problem only occurs with "deep sleep", though. My Blue and White G3 (10.0.4), while asleep, can still do stuff on the internet. I can hear the join and part noises coming from the IRC client I use, and when I wake it back up I can see the lines that I've missed. Not sure why mine does this, but it does.

Doug

Steven Kan replied on :

What about wake-on-LAN? Does the hw support this?

If so, what ports trigger the wake, and is it configurable?

Thanks!

tom keyes replied on :

In article 9q48kb$l4th4$1@redacted.invalid, Ralph Wade Phillips ralphp@redacted.invalid wrote:

If you want it to be up all the time, disable sleep. Nothing wrong with the screensaver, but DON'T SLEEP IT!

    (This is just about Homer Simpson "D'oh!" time.)

I guess so, Homer, unless you knew that sleepers usually wake when they hear their IP called. That's how it worked with 10.0.x

Doug Brown:

I think this problem only occurs with "deep sleep", though.

I agree. It ought to be possible to make the system wake from any sleep when you try to log on but I'm not clear on the situation with 10.1. Again, the surprise to me was that I was using the same settings that had led to no problems with 10.0.x....tom

Tim McNamara replied on :

tom keyes wrote:

Subject: Re: can't connect to sleeping 10.1 box From: tom keyes keyes@redacted.invalid Date: Thu, 11 Oct 2001 16:05:52 -0400

In article 9q48kb$l4th4$1@redacted.invalid, Ralph Wade Phillips ralphp@redacted.invalid wrote:

If you want it to be up all the time, disable sleep. Nothing wrong with the screensaver, but DON'T SLEEP IT!

    (This is just about Homer Simpson "D'oh!" time.)

I guess so, Homer, unless you knew that sleepers usually wake when they hear their IP called. That's how it worked with 10.0.x

Not on mine (10.0.3 and 10.0.4). I had to set it for the system to never sleep and then set the display and hard disk on their own sleep schedules. This didn't change with 10.1. If the system goes fully to sleep, the only way it wakes up is to touch a key on the keyboard.

BTW, my other Unix system (NetBSD 1.4.2) doesn't sleep. As far as I can tell it doesn't even offer the option. You just turn off or disconnect the display and let it run headless, but the system is always wide awake.

OS 8 and OS 9 both woke from sleep enough to respond to TCP/IP queries for file sharing, although the display remained off. "Sleep" may have meant something different in those OSes, though.

Kevin McMurtrie replied on :

In article macg3-6300CE.09143111102001@redacted.invalid, Doug Brown macg3@redacted.invalid wrote:

In article 9q48kb$l4th4$1@redacted.invalid, "Ralph Wade Phillips" ralphp@redacted.invalid wrote:

Howdy!

"tom keyes" keyes@redacted.invalid wrote in message news:111020010903251559%keyes@redacted.invalid

First time I tried to connect to my OS10.1/G4 from home I couldn't do it. My IP was totally off the net, couldn't even ping it. I came in this morning and tried from another G4 in the office, still no luck. Then I went to my desk, hit a key to wake the G4, and then connected with no problem. Somehow it goes off-line whe asleep. I had both energy saver and screen saver on but G4 was just showing a blank dark screen so i suppose screensaver goes off when sleep starts. is it the combination of both 'savers' that puts me off line? is this a known 10.1 problem? Another thing I'm getting on waking from overnight sleep is blank white spaces where classic app windows were and I have to restart classic. How about that one? TIA for any hints....tom

    If you want it to be up all the time, disable sleep.  Nothing wrong

with the screensaver, but DON'T SLEEP IT!

I agree.

I think this problem only occurs with "deep sleep", though. My Blue and White G3 (10.0.4), while asleep, can still do stuff on the internet. I can hear the join and part noises coming from the IRC client I use, and when I wake it back up I can see the lines that I've missed. Not sure why mine does this, but it does.

Doug

Deep sleep is disabled on the Yosemite G3. All the hardware is there but it's not used. You'll find a tiny switching power supply behind the power button with a cable runing to the DRAM bank. The rumor I heard is that bugs in the hardware sometimes cause RAM corruption during sleep.

The Ultra ATA port has problems too. You'll get rare but catastrophic data corruption during heavy drive use if you replace the factory drive.

That's version 1.0.0 hardware for ya.

Doug Brown replied on :

In article mcmurtri-0ADD61.21351111102001@redacted.invalid, Kevin McMurtrie mcmurtri@redacted.invalid wrote:

In article macg3-6300CE.09143111102001@redacted.invalid, Doug Brown macg3@redacted.invalid wrote:

I think this problem only occurs with "deep sleep", though. My Blue and White G3 (10.0.4), while asleep, can still do stuff on the internet. I can hear the join and part noises coming from the IRC client I use, and when I wake it back up I can see the lines that I've missed. Not sure why mine does this, but it does.

Deep sleep is disabled on the Yosemite G3. All the hardware is there but it's not used. You'll find a tiny switching power supply behind the power button with a cable runing to the DRAM bank. The rumor I heard is that bugs in the hardware sometimes cause RAM corruption during sleep.

Right - which is why I said it probably only occurs with deep sleep, because I don't experience it.

The Ultra ATA port has problems too. You'll get rare but catastrophic data corruption during heavy drive use if you replace the factory drive.

Hmm, I thought this was only if you added a slave drive because the IDE chip on Rev1's can cause corruption.

That's version 1.0.0 hardware for ya.

Yep, but this system has been super-reliable for me, and I'm very happy with it.

Doug

zoara replied on :

Doug Brown macg3@redacted.invalid wrote:

    If you want it to be up all the time, disable sleep.  Nothing wrong

with the screensaver, but DON'T SLEEP IT!

I agree.

I think this problem only occurs with "deep sleep", though. My Blue and White G3 (10.0.4), while asleep, can still do stuff on the internet. I can hear the join and part noises coming from the IRC client I use, and when I wake it back up I can see the lines that I've missed. Not sure why mine does this, but it does.

You sure that it's not that just the display is asleep?

    -z-
Doug Brown replied on :

In article 1f16gsm.wt3h1q1ai6sb6N%not@redacted.invalid, not@redacted.invalid (zoara) wrote:

Doug Brown macg3@redacted.invalid wrote:

I think this problem only occurs with "deep sleep", though. My Blue and White G3 (10.0.4), while asleep, can still do stuff on the internet. I can hear the join and part noises coming from the IRC client I use, and when I wake it back up I can see the lines that I've missed. Not sure why mine does this, but it does.

You sure that it's not that just the display is asleep?

Yes - because the amber light on the G3 blue and white's power button comes on. In 10.1, though, I get disconnected from the net before it finishes sleeping, and the amber light doesn't go on either - stays green...oh well.

Doug

ZnU replied on :

In article 3BC5E935.C467C734@redacted.invalid, Steven Kan steven@redacted.invalid wrote:

What about wake-on-LAN? Does the hw support this?

If so, what ports trigger the wake, and is it configurable?

The hardware supports it, but it doesn't seem that OS X does yet.

John W. Baxter replied on :

In article znu-827A92.17281712102001@redacted.invalid, ZnU znu@redacted.invalid wrote:

In article 3BC5E935.C467C734@redacted.invalid, Steven Kan steven@redacted.invalid wrote:

What about wake-on-LAN? Does the hw support this?

If so, what ports trigger the wake, and is it configurable?

The hardware supports it, but it doesn't seem that OS X does yet.

Oh, good...that means when the OS does implement it we we can get our quota of Code Red and Nimda probes during what should be machine sleep times. (The only reason I have my unexciting web server open to the Net is so I can glance at the logs now and then and get an idea of Code Red and Nimda probing activity.)

--John

Magn0lia replied on :

In article 111020011605523718%keyes@redacted.invalid, tom keyes keyes@redacted.invalid wrote:

I agree. It ought to be possible to make the system wake from any sleep when you try to log on but I'm not clear on the situation with 10.1. Again, the surprise to me was that I was using the same settings that had led to no problems with 10.0.x....tom

There was a lot of hardware that wouldn't fully sleep under 10.0; if your machine was one of those, then this would have worked under 10.0 and not under 10.1.

René A. Vega replied on :

Magn0lia wrote:

In article 111020011605523718%keyes@redacted.invalid, tom keyes keyes@redacted.invalid wrote:

I agree. It ought to be possible to make the system wake from any sleep when you try to log on but I'm not clear on the situation with 10.1. Again, the surprise to me was that I was using the same settings that had led to no problems with 10.0.x....tom

There was a lot of hardware that wouldn't fully sleep under 10.0; if your machine was one of those, then this would have worked under 10.0 and not under 10.1.

Well actually, sleep mode in 10.0.x was faked. The system just turned off the monitor and spun down the hard drive, which is why network activity still worked. 10.1 implemented real sleep, meaning the processor and most of the motherboard is powered off. In that state, network activity does nothing (well, at least until wake on LAN activity eventually gets supported).

Rene'

tom keyes replied on :

In article 3BCCF039.412CB762@redacted.invalid, René A. Vega draco@redacted.invalid wrote:

Well actually, sleep mode in 10.0.x was faked. The system just turned off the monitor and spun down the hard drive, which is why network activity still worked. 10.1 implemented real sleep, meaning the processor and most of the motherboard is powered off. In that state, network activity does nothing (well, at least until wake on LAN activity eventually gets supported).

Well, I guess we got to the bottom of that. Thanks to all....tom