ckny

Hello! Today I discovered that I have a rather strange standby issue and as I'm not very familiar with how Windows handles power management I was hoping for some advice. What happens is that in power management I have Windows set to go into standby when the power button is pressed. When I turn off the car the m2-atx will wait the 5 seconds, then standby is initiated (I get the blue "preparing to standby" screen and the computer turns off. Then 5 seconds later it will start up again! I have changed my power management setting to turn off the computer now just to be safe but I liked my standby =)

Now I should add that I *believe* standby worked properly in the past however today is the first day that I have my Xenarc wired directly to the m2-atx so I don't know if it's coincidence or if I am just now realizing it and my battery has been a trooper this whole time.

Here's my setup:
Jetway mobo that doesn't support S3, only S1 ( I believe )
Xenarc and USB powered hub directly wired to m2-atx
m2-atx set to 5 second offdelay and 2 hour hardoff
the following usb devices plugged into the hub:
-xenarc touchscreen
-dlink wifi
-gps receiver
-sir-alp1 sirius module

DarquePervert

You probably have some device that's immediately bringing the PC out of standby.
Check power management settings for all your devices and make certain they are not set to bring the computer out of standby.

__________________

SEARCH: It's how information gets found!
How To Ask Questions The Smart Way

[|||||||--] - 80% (I estimate completion in Spring '07)
My Worklog

ckny

Thats what I was assuming however I don't know how to check individual devices' power management settings... can you point me where?

On another note - thank you so much for the help... I know of a few threads I've needed help on and you've quickly come with an answer. It's really appreciated.

2k1Toaster

Just a word of advice, if your mobo only supports S1, that means the CPU is still on, and the RAM is on, which is a significant power draw. Basically it just shuts off the screen and some USB devices.

Go to system porperties (Right click my computer, properties), hardware tab, click Device Manager.

Go to the USB section and check all the hubs/roots by right clicking then properties on each one, and there should be some power tabs. Look for the checkboxes that say "Allow this device to bring the computer out of standby". This is also where you set your TS to not turn off after so long without being pressed with the checkbox "Allow the computer to turn off this devices to save power"

__________________

ckny

Ok I checked all my devices as per the above instructions from toaster and only 1 or 2 had a power tab but both had the option "allow this device to bring the computer out of standby" unchecked.

Anywhere else or anything else I should be checking?

ckny

I figured out that it is the xenarc touchscreen that is bringing the computer out of standby. If I unplug the xenarc's usb cable from my hub then the computer will stay in standby fine. I checked all the power settings under device manager and many don't have a power tab (including the "touchkit" usb controller - which is the xenarc).

Is there any other way to stop this? I checked the touchkits settings under start -> programs and there was no option relating to power.

ckny

After a little more searching I found this thread:
http://www.mp3car.com/vbulletin/newb...uchscreen.html

In it, the problem was mentioned as being the following, but no solution was ever presented. Any ideas?

>>I have a Xenarc 700TSV. When you turn the computer off, hibernate, or standby, the Xenarc goes into it's own standby mode that cuts off the USB connection with the computer.

So, if I put the computer into Standby, then 5 seconds after it shuts down, the Xenarc goes into standby, which cuts off the USB connection, which causes my computer to wake up.

I can never put the computer into standby, because it just wakes up as soon as it loses the signal from the touchscreen.

Is there a way around this?

ckny

nevermind. Updating to the latest drivers on Xenarc's page fixed this issue. Thanks for all the help!