From: "Geo." 

Stage 4 is checking file data and it was definitely holding the cpu at 100%
but I don't know if that's because of something with the drive or because
of chkdsk, ending chkdsk ended the cpu usage.

Once I get W2K on this sucker I'll test it again to see if it still happens.

It just seems strange to me that for hours while chkdsk was running the cpu
stayed at 100% and nothing in taskmanager, none of the processes showed any
significant cpu usage. Somethins broke.

Geo.

"Mike N."  wrote in message
news:locmb05v8p5npg4sk4unr7b00jqc5dc2s1{at}4ax.com...
> On Sun, 30 May 2004 21:50:56 -0400, "Geo."
 wrote:
>
> >Anyway, chkdsk is happily running along in stage 4 of 5 and I bring up
> >taskmanager to see cpu graphs, which as expected show the cpu running at
100%,
> >then I go to the process tab and to my surprise every process is at 0% cpu
> >usage???
>
>   I don't remember if stage 4 of 5 is CPU-bound, but I would expect 0% CPU
> usage while it is disk I/O bound.

--- BBBS/NT v4.01 Flag-5