A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » The Basics
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Control of ATI events



 
 
Thread Tools Display Modes
  #1  
Old March 12th 10, 02:25 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
Ads
  #2  
Old March 12th 10, 04:28 PM posted to microsoft.public.windowsxp.basics
Jose
external usenet poster
 
Posts: 3,140
Default Control of ATI events

On Mar 12, 9:25*am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
  #3  
Old March 12th 10, 04:28 PM posted to microsoft.public.windowsxp.basics
Jose
external usenet poster
 
Posts: 3,140
Default Control of ATI events

On Mar 12, 9:25*am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
  #4  
Old March 12th 10, 05:04 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.
  #5  
Old March 12th 10, 05:04 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.
  #6  
Old March 12th 10, 05:15 PM posted to microsoft.public.windowsxp.basics
John John - MVP
external usenet poster
 
Posts: 780
Default Control of ATI events

William B. Lurie wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?


Don't disable it, try it first set to "Manual" Start in the Services
Management console (In the Start Menu Run box enter services.msc).

John
  #7  
Old March 12th 10, 05:15 PM posted to microsoft.public.windowsxp.basics
John John - MVP
external usenet poster
 
Posts: 780
Default Control of ATI events

William B. Lurie wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:

Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".

The other is TCpip code 4201....Network Control Test.

I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.

You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.

If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.

You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?


Don't disable it, try it first set to "Manual" Start in the Services
Management console (In the Start Menu Run box enter services.msc).

John
  #8  
Old March 12th 10, 10:16 PM posted to microsoft.public.windowsxp.basics
Jose
external usenet poster
 
Posts: 3,140
Default Control of ATI events

On Mar 12, 12:04*pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:


Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".


The other is TCpip code 4201....Network Control Test.


I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? *Disable it and reboot if you
are not using a scanner or camera. *Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? *Just disable WIA if you are not using it. *It is just
another running service you may not need.


You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.


If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. *If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.


You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.
  #9  
Old March 12th 10, 10:16 PM posted to microsoft.public.windowsxp.basics
Jose
external usenet poster
 
Posts: 3,140
Default Control of ATI events

On Mar 12, 12:04*pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:


Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".


The other is TCpip code 4201....Network Control Test.


I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.


What is the status of your WIA service? *Disable it and reboot if you
are not using a scanner or camera. *Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? *Just disable WIA if you are not using it. *It is just
another running service you may not need.


You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.


If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. *If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.


You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.


Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.
  #10  
Old March 13th 10, 12:11 AM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.

Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......

But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.
  #11  
Old March 13th 10, 12:11 AM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.

Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......

But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.
  #12  
Old March 13th 10, 11:53 AM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

William B. Lurie wrote:
Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the
reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......

But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.


And now, early in the morning, these results:
With hibernate set for 1 hour, it goes to hibernate on schedule properly.
With hibernate set for 2 hours, it does *not* go to hibernate,
and there are no events recorded for Apps or Security but under
System I get a 7036 every hour (approximately) as follows:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 3/13/2010
Time: 3:07:43 AM
User: N/A
Computer: COMPAQ-2006
Description:
The Windows Image Acquisition (WIA) service entered the running state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I just checked and I have WIA showing as "Started....Manual".

So it seems to be WIA that's preventing hibernation if set
for more than 1 hour. Next step? Give me the link to the hibernate
fix that is in SP3?
  #13  
Old March 13th 10, 11:53 AM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

William B. Lurie wrote:
Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the
reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......

But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.


And now, early in the morning, these results:
With hibernate set for 1 hour, it goes to hibernate on schedule properly.
With hibernate set for 2 hours, it does *not* go to hibernate,
and there are no events recorded for Apps or Security but under
System I get a 7036 every hour (approximately) as follows:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 3/13/2010
Time: 3:07:43 AM
User: N/A
Computer: COMPAQ-2006
Description:
The Windows Image Acquisition (WIA) service entered the running state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I just checked and I have WIA showing as "Started....Manual".

So it seems to be WIA that's preventing hibernation if set
for more than 1 hour. Next step? Give me the link to the hibernate
fix that is in SP3?
  #14  
Old March 13th 10, 12:43 PM posted to microsoft.public.windowsxp.basics
William B. Lurie
external usenet poster
 
Posts: 811
Default Control of ATI events

William B. Lurie wrote:
William B. Lurie wrote:
Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But
if I
set hibernate at 2 hours, it never goes to hibernate, and the
reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? Disable it and reboot if you
are not using a scanner or camera. Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? Just disable WIA if you are not using it. It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?

I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the
culprit.

Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.

Just disable the service from the XP Services applet.

Click Start, Settings, Control Panel, Administrative Tools, Services.

A shortcut to the Services applet is:

Click Start, Run and in the box enter:

services.msc

click OK.

Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. Reboot and
check the service again to be sure it is not running and then check
your Event Log. Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!

If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. Are you using
any of the software I listed before? I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.

If my system doesn't Hibernate when I think it should, it is always my
fault somehow.

You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". Ah-ha!

Didn't I send you a link one day with the SP2 Hibernate hotfix? I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......

But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.


And now, early in the morning, these results:
With hibernate set for 1 hour, it goes to hibernate on schedule properly.
With hibernate set for 2 hours, it does *not* go to hibernate,
and there are no events recorded for Apps or Security but under
System I get a 7036 every hour (approximately) as follows:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 3/13/2010
Time: 3:07:43 AM
User: N/A
Computer: COMPAQ-2006
Description:
The Windows Image Acquisition (WIA) service entered the running state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I just checked and I have WIA showing as "Started....Manual".

So it seems to be WIA that's preventing hibernation if set
for more than 1 hour. Next step? Give me the link to the hibernate
fix that is in SP3?


It occurred to me, Jose, that you might want to see the full
Events Log for System.....it does include more information,
and some Tcpip entries:

Type Date Time Source Category Event User Computer
Information 3/13/2010 6:11:48 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 6:11:44 AM Tcpip None 4201 N/A COMPAQ-2006
Information 3/13/2010 5:10:19 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 4:09:01 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 3:07:43 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 2:06:26 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 2:06:24 AM Tcpip None 4201 N/A COMPAQ-2006
Information 3/13/2010 1:23:48 AM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/13/2010 1:23:46 AM Tcpip None 4201 N/A COMPAQ-2006
Information 3/12/2010 10:16:49 PM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/12/2010 9:46:28 PM Service Control Manager None 7036 N/A
COMPAQ-2006
Information 3/12/2010 9:46:24 PM Tcpip None 4201 N/A COMPAQ-2006
Information 3/12/2010 8:46:07 PM Service Control Manager None 7036 N/A
COMPAQ-2006
__________________________________________________ ___________________
  #15  
Old March 13th 10, 01:30 PM posted to microsoft.public.windowsxp.basics
Jose
external usenet poster
 
Posts: 3,140
Default Control of ATI events

On Mar 13, 6:53*am, "William B. Lurie" wrote:
William B. Lurie wrote:
Jose wrote:
On Mar 12, 12:04 pm, "William B. Lurie" wrote:
Jose wrote:
On Mar 12, 9:25 am, "William B. Lurie" wrote:
I have found that if I set hibernate time at 1 hour, then overnight
it goes to hibernate and gives no error messages in 'Events'. But if I
set hibernate at 2 hours, it never goes to hibernate, and the
reason is
in the Event Log:
Two events occur periodically. One is Service Control Manager being
called, every hour. and it gives a 7036 code..."Windows Image
Acquisition Service" (WIA) entered the running state".
The other is TCpip code 4201....Network Control Test.
I'd like to find out first how to set the WIA to some longer period,
and more about the Network Control Test.
What is the status of your WIA service? *Disable it and reboot if you
are not using a scanner or camera. *Is that message preceded by a WIA
being sent a start message and only happens on reboot or do you see it
every hour? *Just disable WIA if you are not using it. *It is just
another running service you may not need.
You may also want to remind folks that you are still running SP2 which
is known to have problems with hibernation that were resolved with
SP3.
If you use Hibernate (or Stand By) and XP starts the idle timer
beginning the countdown... anything that happens that uses 10% of CPU
time (while it is waiting) will reset the timer to zero and the
countdown starts over. *If you set Hibernate for 2 hours and something
happens every hour to reset the timer, you will never Hibernate
automatically.
You need to see what things you might have running that could reset
the timer - for example: email, Skype, AVG, IM, RSS feeds, Internet
Browsers, periodic automatic updates of third party programs,
scheduled malware updates or scans, backups, scheduled tasks
(defrags), etc. that might be resetting the idle timer for you - even
when you think you are not really doing anything.
Good advice as always, Jose. I tried to find out how to disable WIA
to try to pin it down, but I couldn't find it. If it's in the startup
list from 'msconfig' I couldn't find it there, but I'll admit that
there are a half-dozen or so items that I couldn't identify. What
does it look like?


I've been expecting the Events list to point to events that happen
quietly in the background, and that's what led me to WIA as the culprit.


Good point about SP3; I recall that it interfered with something
and so I went back to SP2. I'd be willing to spend the time to upgrade
back to SP3 and see if it runs clean.


Just disable the service from the XP Services applet.


Click Start, Settings, Control Panel, Administrative Tools, Services.


A shortcut to the Services applet is:


Click Start, Run and in the box enter:


services.msc


click OK.


Locate the WIA Service (is that status Started = running?), right
click and change the Properties Startup type to Manual. *Reboot and
check the service again to be sure it is not running and then check
your Event Log. *Mine is Disabled, but I will never use a device that
needs any kind of image acquisition on this computer!


If you can regularly hibernate after one hour with no problems but
never after two hours, I suspect something is going on between hour 1
and hour 2 that resets your idle interval back to zero. *Are you using
any of the software I listed before? *I forgot to add MagicJack - that
will also keep you from Hibernating if you don't set it up right.


If my system doesn't Hibernate when I think it should, it is always my
fault somehow.


You can clear the Event Logs you know - that may make your
troubleshooting a little easier to start fresh. *Set up your two hour
window, clear the logs, wait more than two hours (missing the window)
then look in the logs and see what things were logged when you thought
you were doing "nothing". *Ah-ha!


Didn't I send you a link one day with the SP2 Hibernate hotfix? *I
will have to look for it again if you never got a chance to try it.
The hotfix is included with SP3, but I think you can just get the
Hibernate hotfix for SP2.

Hang loose, Jose......I'm following you, but slowly and
keerfully and it takes hours to find out if a change does
anything. I'll be back.......


But no, I don't recall the Hibernate Hotfix..... And I have no MagicJack
and believe that I have cut off all automatic updates.


And now, early in the morning, these results:
With hibernate set for 1 hour, it goes to hibernate on schedule properly.
With hibernate set for *2 hours, it does *not* go to hibernate,
and there are no events recorded for Apps or Security but under
System I get a 7036 every hour (approximately) as follows:

Event Type: * * Information
Event Source: * Service Control Manager
Event Category: None
Event ID: * * * 7036
Date: * * * * * 3/13/2010
Time: * * * * * 3:07:43 AM
User: * * * * * N/A
Computer: * * * COMPAQ-2006
Description:
The Windows Image Acquisition (WIA) service entered the running state.

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

I just checked and I have WIA showing as "Started....Manual".

So it seems to be WIA that's preventing hibernation if set
for more than 1 hour. Next step? Give me the link to the hibernate
fix that is in SP3?


I don't know why WIA would want to restart (yet), but that is
interesting.

Keep in mind that we are trying to get an out of date system to behave
and that may not be an achievable goal.

Disable the WIA Service, reboot, check it again in Services and test
again. Always reboot with changes so there is no question of do you
need to reboot.

The Hibernate hotfix reads like it does not apply to you but you can
try it if your system still misbehaves after you have tested with WIA
Disabled.

http://support.microsoft.com/kb/909095/

SP3 includes the Hibernate fix and a fix for WIA, but there is no
downloadable hotfix for the WIA fix and reading doesn't sa it fixes a
problem where it wants to restart - it just says the SP3 fixes a WIA
"vulnerability".

You can read about the SP2 - SP3 updates here and find the Hibernate
and WIA info and do some searches to see if they might apply to you:

http://support.microsoft.com/kb/946480

Do you have any cameras, webcams, scanners attached now or ever in the
past? If you don't Disable WIA - it is one of many built in Services
that a lot of people don't need or ever use. I search for all that
junk and figure out if I need it or not and disable anything that
could take up even a small speck of memory or CPU time.

Do you have any of the other softwares installed I mentioned before?
Anything that might be set to wake up once an hour to check for
updates or something to do?

I would hope that you only make one change at a time so you will know
what fixes your issue. You will have to wait 1+ hour for every
adjustment! You can download the Hibernate fix first if you want but
I don't think the Hibernate hotfix is your issue since you saw WIA
start after one hour. That might be what is resetting your Hibernate
countdown timer.

I do not have any SP2 system to test with but will look around a
little more at why WIA might start itself when it is set to manual. I
don't ever use WIA, I will not be setting up an SP2 system, etc. so I
may not be of much more help!

I will set my SP3 WIA from Disabled to Manual and wait a while and see
if it starts itself and maybe figure out what is going on.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 10:47 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.