For the past few weeks, most days when I come down to my office, the T60p is powered off.
I looked in the System Event log and in the Symantec/Norton log, but nothing sticks out as obvious.

Nothing needs to be changed nor has anything been changed from what I always run.ryengineer wrote:1. Look into Power options and see if something needs to be changed.
I have two batteries in, both are fully charged.ryengineer wrote:2. If the machine entirely runs on your adapter, make sure it's working properly.
I'm in my home office, no elec problems that I know, and the batteries would take over if there were...ryengineer wrote:3. Ask your co-workers (if any) about any possible wiring problem in the place.
ryengineer wrote:4. Lastly if someone else has access to your office (like friends, co-workers, janitors), make sure they aren't fooling around.
How do I do that? I didn't see that option in any power settings...dsalyers wrote:1) Is the power manager set to shut off the machine after a period of inactivity?
Good idea. I think they were 100% yesterday and they now show 99%. I don't know this is a clue or if they just flux between 100% and 99% normally.dsalyers wrote:2) Is the battery level drained when you come in? I ask this because I diagnosed a similar problem were an employee had plugged their desktop into an outlet that was controlled by a switch. When the cleaning people left for the night they would turn off all of the switches, which included the one his machine was plugged in.
Code: Select all
:top
time /t >> timestamp.log
ping 127.0.0.2 -n 60 -w 1000 > nul
goto :top
It's fairly new, <3 months. I only noticed it after I went thru a metal detector that I've never been thru before.mitchellst wrote:I'm betting it's a hardware issue. If you can't find a solution, I'd send it somewhere to get it repaired (assuming it's under warranty). I'm not really sure what would cause that. I guess it could be overheating. It may just need a new fan.
That's not definitive proof that you had a power loss. It just means outlook wasn't shutdown properly.Outlook does tell me that my PSTs were not closed properly...
I leave my T60p lid open with Windows XP running.GomJabbar wrote:Two other things that might cause this...

Strange...Yesterday, I wrote:I run NAV (AntiVirus) @ 9pm, Connected (Backup) @ 10:45p and Ghost (Backup) @ midnight.
I just changed NAV to 4am, to see if that does anything...
Code: Select all
[02/22/07 22:28:11] TRACE [5176][02/24/07 08:30:13] TRACE [2184]: RPC_CLIENT::init connect 2: Winsock error '10061'Thanks for looking up the error.jeffm wrote:Winsock error 10061 is WSAECONNREFUSED:
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.
ThanksGomJabbar wrote:Here are some possible things I think might be causing this.
Interesting. Symantec/NAV didn't find it, but I'll search their DB for that specific virus.GomJabbar wrote:1st: you have been infected with a Virus such as Sassar.
Do you consider the Windows Firewall good?GomJabbar wrote:2nd: you are not running a good Firewall, or else it is not properly configured.
Weekly.GomJabbar wrote:3rd: you have not kept your copy of Windows thoroughly up to date with the security updates.
NAV. Weekly.GomJabbar wrote:4th: you do not have a good AntiVirus program, or you haven't been keeping it up to date.
Looks interesting. Are you a member? Is the answer good enough to pay for?GomJabbar wrote:Take a gander at the following thread I pulled up on a quick Google search.
http://www.experts-exchange.com/OS/Micr ... 58211.html
Thank you very much, for the detailed explaination.GomJabbar wrote:... The Code you posted above with the Winsock error makes me think that your computer is trying to connect with the internet, or someone on the internet is trying to connect to your computer. This could be a possible indication of a Virus infection or a DOS attack.
True, you're right on both accounts. It's BOINC specific and I was trying to connect.jeffm wrote:That's a WinSock client error - meaning your computer was attempting to make the connection.
I believe that stdoutgui.txt is BOINC specific - so BOINC was trying to make the connection and reported the error.
Perfect!jeffm wrote:You might be able to answer the first question by turning on firewall logging:
http://support.microsoft.com/kb/875357
Users browsing this forum: soundforger and 13 guests