I think you have to set the card to only allow waking up by "network-admin-stations" (something like that, I had to translate from dutch).
Although I must admit that my server sometimes keeps awake for no clear reason. After a reboot it functions ok again (for a while)
Device manager on my English XP calls it "only allow management stations to bring the computer out of standby"
Not a good description, as it doesn't say how or why it knows what a management station is (especially if powered down in hibernate). I guess it could be more a BIOS selections rather than XP.
I think my longest time for the server not needing a full reboot for deep standby and restarting is around two weeks - longer than that and it doesn't do to sleep. Every 6 months it needs XP restoring to keep standby working ;(
I've (almost) never had any problems with this solution. Didn't even check the
"only allow management stations to bring the computer out of standby".
I have however set a very long lease time on the IP addresses served by my DHCP server (1 week).
I only need to reboot when a Windows update requires it.
Of course it also depends on what the other machines in the network do. If they, in any way, access the GBPVR machine, they will of course cause it to wake up, e.g. if they have mapped shares or so...
FWIW, when I started to do this, I had problems getting Hibernate to work well. When I googled on this, I found that this is a BIOS problem, i.e. how well the Hibernate and Suspend are implemented... I did a few tests, and it seems that it indeed differs from machine to machine (or BIOS to BIOS) when it comes to functionality/stability... For example, on my GBPVR computer (home built) Suspend works fine but Hibernate works erratically. On my computer at work (Dell), Suspend doesn't work at all (wakes up immediately), but Hibernate works fine. So it may be an idea to test both... For environmental (and electrical bill) reasons I would prefer Hibernate, but Suspend will have to do for now...
Hmmm - is anyone having problems with standby after connecting a PCH?
I've noticed that my server hasn't gone into standby since I got the PCH up and running (and left on)
I looked and with mvpmcx2 up and running the mvpmcx2 file is open and a guest and root session are logged in from the PCH. No standby.
Dropping back to the PCH interface (with the remote power button) drops the open file on the server, but both users are still connected. No standby.
Removing power from the PCH and in 5 minutes, the server went to sleep.
Given the differences everyone has with individual BIOS and with custom sleep/suspend/hibernate settings other answers might not be applicable but my machine does go into sleep mode.
If you have set your machine to not suspend based on disk activity you might want to turn off GBPVR debug logging. I've never been a fan of having it stay on once things are working anyway and now the verbosity level seems to be getting higher and higher with every release.
The fact that you have a share connected really shouldn't make any difference to suspend and you really should power off the PCH anyway.
I'll have to do some more testing - it's a slow process though with all the waiting..
With the old MVP, when it had finished playing a recording and dropped back to the menu, the server went to sleep if no one pressed remote MVP keys.
I don't think disk activity keeps my machine awake, I can be logged in remotely and doing stuff and it will shut down if there is no local keyboard or mouse activity. I normally have it turned off as well though.
Quote:and you really should power off the PCH anyway.
I've been leaving it on to keep your software running and the WAF factor up. The normal "end of day" routine is for them to just switch the TV off and disappear.
My IDE to SD car adapter has arrived, so I may experiment with moving the mvmmc share to local disk on the PCH to see what happens.
Well it's not the shares that's keeping the server awake. Kill them off at the server and nothing happens. However, restart recording service and 5 minutes later it goes to sleep.
With thanks to those taking the time to document things on here and on the wiki - I've got things running from a USB stick and now the server goes into standby when the PCH is idle at the main menu.
In an earlier post, I said killing off shares made no difference - what I didn't realise was that it reconnected shortly afterwards!.
Thanks all.
PS my IDE<>SD adapter won't format (in the PCH) it works everywhere else and I see a few people have the problem as well on the NMT forum. Ah well, all good fun.
My thanks to t'other Martin for making ether-wake available.
I've added it into the startmeup file and my server now wakes up when running the gbpvr interface on the PCH. Note - of course you need the scripts on a hard drive or USB stick, not on the share that is asleep