G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I'm working on a clients computer:
PIII 933, 133 FSB, 256K Cache
128 MB RAM
60 GB HDD
Gigabyte motherboard

The problem I'm having is one I've never experienced before, the
hardware clock runs at a normal pace, but the clock and everything in
Windows XP runs in super turbo mode, minutes pass in seconds, it has
become impossible to double click even at the lowest speed setting in
the mouse panel. I've checked if it was overclocked, or if the cpu was
misidentified, but it all checks out fine. I've seen posts about the
whole windows clock moves 4 fast ticks, one long one, but this is much
worse than that in a matter of a minute over a whole windows hour has
passed on the clock.

Any help would be greatly appreciated.
Coco_Munky a la Monkey Island


--
coco_munky
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"coco_munky" <coco_munky.1s8z1m@pcbanter.net> wrote in message
news:coco_munky.1s8z1m@pcbanter.net...
>
> I'm working on a clients computer:
> PIII 933, 133 FSB, 256K Cache
> 128 MB RAM
> 60 GB HDD
> Gigabyte motherboard
>
> The problem I'm having is one I've never experienced before, the
> hardware clock runs at a normal pace, but the clock and everything in
> Windows XP runs in super turbo mode, minutes pass in seconds, it has
> become impossible to double click even at the lowest speed setting in
> the mouse panel. I've checked if it was overclocked, or if the cpu was
> misidentified, but it all checks out fine. I've seen posts about the
> whole windows clock moves 4 fast ticks, one long one, but this is much
> worse than that in a matter of a minute over a whole windows hour has
> passed on the clock.
>
> Any help would be greatly appreciated.
> Coco_Munky a la Monkey Island
>
>
> --
> coco_munky

First thing to try is remove clients computer from TARDIS and try again.
 

Kenny

Distinguished
Feb 9, 2001
379
0
18,780
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

You have achieved what other overclockers long for all their lives!


"coco_munky" <coco_munky.1s8z1m@pcbanter.net> wrote in message
news:coco_munky.1s8z1m@pcbanter.net...
>
> I'm working on a clients computer:
> PIII 933, 133 FSB, 256K Cache
> 128 MB RAM
> 60 GB HDD
> Gigabyte motherboard
>
> The problem I'm having is one I've never experienced before, the
> hardware clock runs at a normal pace, but the clock and everything in
> Windows XP runs in super turbo mode, minutes pass in seconds, it has
> become impossible to double click even at the lowest speed setting in
> the mouse panel. I've checked if it was overclocked, or if the cpu was
> misidentified, but it all checks out fine. I've seen posts about the
> whole windows clock moves 4 fast ticks, one long one, but this is much
> worse than that in a matter of a minute over a whole windows hour has
> passed on the clock.
>
> Any help would be greatly appreciated.
> Coco_Munky a la Monkey Island
>
>
> --
> coco_munky
 

Rick

Distinguished
Oct 14, 2003
1,084
0
19,280
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Keith S wrote:
> "coco_munky" <coco_munky.1s8z1m@pcbanter.net> wrote in message
> news:coco_munky.1s8z1m@pcbanter.net...
>
>>I'm working on a clients computer:
>>PIII 933, 133 FSB, 256K Cache
>>128 MB RAM
>>60 GB HDD
>>Gigabyte motherboard
>>
>>The problem I'm having is one I've never experienced before, the
>>hardware clock runs at a normal pace, but the clock and everything in
>>Windows XP runs in super turbo mode, minutes pass in seconds, it has
>>become impossible to double click even at the lowest speed setting in
>>the mouse panel. I've checked if it was overclocked, or if the cpu was
>>misidentified, but it all checks out fine. I've seen posts about the
>>whole windows clock moves 4 fast ticks, one long one, but this is much
>>worse than that in a matter of a minute over a whole windows hour has
>>passed on the clock.
>>
>>Any help would be greatly appreciated.
>>Coco_Munky a la Monkey Island
>>
>>
>>--
>>coco_munky
>
>
> First thing to try is remove clients computer from TARDIS and try again.
>
>
The Doctor would not like that :)