|
hmmm i cant see many possibilities to be hardware related. My graphics card is a GF 7800 GTX bought last august
|
|
|
|
|
I always get the "white rectangle around menu bar items" glitch as soon as I make any changes to the theme.
|
|
|
|
|
|
hi!!
i am having xp home edition.i want to shut down my pc at a specified time.
how can i do that?
|
|
|
|
|
Here are a couple of programs that might help:
Auto Exit
Auto Shutdown
Trinity: Neo... nobody has ever done this before.
Neo: That's why it's going to work.
|
|
|
|
|
vishal dhir wrote: how can i do that?
Add schedule task with SHUTDOWN -s -f command.
Check shutdown -? for more options.
Knock out 't' from can't,
You can if you think you can
|
|
|
|
|
hi to all!!
whenever i keep a system time on my laptop it changes after 1 or 2 days and shows wrong time......
kindly help me out!!!
|
|
|
|
|
You may well have a time server on your network somewhere which is configured incorrectly. If your laptop is a member of an Active Directory domain, its clock will be automatically synchronized with a domain controller; if you are the administrator, ensure that the DC's clock is set correctly. Consider using an internet time server (NTP protocol) to keep the clock synchronized with an external time source.
|
|
|
|
|
... or maybe just your motherboard battery is empty...
|
|
|
|
|
hi to all!!
whenever i keep a system time on my laptop it changes after 1 or 2 days and shows wrong time......
kindly help me out!!!
|
|
|
|
|
|
I would like to know what the recommended max length for a filename/path for Windows XP is...if there is one?
-- Thanks!
|
|
|
|
|
There are many areas of Windows which still struggle with paths longer than 259 characters, including the drive specification. However, other parts of Windows can cope and will allow you to create paths longer than this.
|
|
|
|
|
<--------------------------------------------------------------------------->
(not to scale)
|
|
|
|
|
|
|
I have a problem with Windows 2003 Server shutting down too quickly. I have a service running on the server, and Windows 2003 shuts down without waiting for the service to stop, the service will typically have about 2 seconds to finish before Windows shuts down. I have checked the registry values HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout, HKEY_CURRENT_USER\Control Panel\Desktop\HungAppTimeout, and HKEY_CURRENT_USER\Control Panel\Desktop\WaitToKillAppTimeout and they are all set to 20000, corresponding to 20 seconds (though I guess only the WaitToKillServiceTimeout is really relevant since this is a service). I have also tried reporting updated status with SERVICE_STOP_PENDING and updated dwWaitHint and dwCheckPoint to the service control manager, but this also seems to be ignored. I have made comparative tests on Windows XP Professional, and XP seems to respect the registry settings for service timeouts, but Windows 2003 apparently does not. I have searched for a solution, and I have seen it is quite common to have the opposite problem (i.e. Windows taking too long to shut down), but I haven't seen any solution to my problem. Could it be that there is some setting that overrides the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout setting? Does anyone have an idea what might be the cause of this?
I don't know whether this is relevant, but I log on to the Windows 2003 machine using Remote Desktop Connection. There is no screen, keyboard, mouse etc connected to the server.
I'm grateful for any help,
Soren
|
|
|
|
|
You are handling SERVICE_CONTROL_INTERROGATE correctly, I assume?
In a service I wrote, I saw similar behaviour until I reported updated status (incrementing checkpoint#) in response to this.
The logon mechanism shouldn't matter, as it's a service.
You don't know how lucky you are. A couple of machines of ours take ages to shut down (approx 15 minutes) even though they "aren't doing anything" (that is, one of the services was blocking shutdown until I disabled it, since it's never used on the machines).
Steve S
Developer for hire
|
|
|
|
|
I do handle SERVICE_CONTROL_INTERROGATE, but the handler function is never called with the SERVICE_CONTROL_INTERROGATE control code when the service is stopping. The handler function returns almost immediately, so the service control dispatcher is in control of this thread and my service would be able to respond to a SERVICE_CONTROL_INTERROGATE if it was issued. The only thing that the control handler function does before returning is setting the status of the service to SERVICE_STOP_PENDING and starting a thread that handles everything else needed to safely stop the service (including periodically updating the state of the service with updated wait hint and checkpoint).
I don't know if it is supposed to be possible to interrogate a service while it is shutting down. When I use SC.EXE to interrogate my service while it is shutting down, SC returns with the following error message:
[SC] ControlService FAILED 1061:
The service cannot accept control messages at this time.
As I already mentioned though, my service control handler function returns control to the service control dispatcher almost immediately after receiving SERVICE_CONTROL_STOP or SERVICE_CONTROL_SHUTDOWN, so my service would be able to handle interrogation requests if they were delivered. It is still possible to use the SC.EXE query command for the service, but that command doesn't interrogate the service, it just reports the latest updated status information from the service control manager.
|
|
|
|
|
With Win2003 on our server, I noticed that selection "unplanned shutdown" as opposed to "planned shutdown" seems to trigger a chain of events, causing the server to act differently.
I am under the impression that an "unplanned shutdown" is enforced more vigourously than a "planned shutdown", but that might just be my time-perception acting up.
It is definitely taking longer to start-up after an "unplanned shutdown".
Could this have something to do with your problem?
Cheers,
Sebastian
--
Contra vim mortem non est medicamen in hortem.
|
|
|
|
|
This doesn't seem to make any difference on the servers I have access to, I usually use 'Planned', but I have also tested with 'Unplanned'.
Soren
|
|
|
|
|
I do things slightly differently, in that the handler function doesn't return until the service has stopped, but like your thread, periodically updates the service state.
According to the (somewhat sketchy) documentation, this shouldn't make any difference, but apparently is doing.
Steve S
Developer for hire
|
|
|
|
|
Hello,
I am looking for an Operating System that is the closest to windows server 2003 execept the price, even A linux is fine as long as its relatively easy to install.
Thanks
Al968
Avast Antivirus-<url>http://www.avast.com<url>
|
|
|
|
|
Ubuntu Linux is supposed to be incredibly easy to install. I've heard a lot of good things about it!
Trinity: Neo... nobody has ever done this before.
Neo: That's why it's going to work.
|
|
|
|
|
Which ever linux variant OS you feel comfortable with is probably your best bet. To make the linux server look like a windows server, look into using SAMBA on the linux server.
Phil
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
