HDD activity monitor

[imperialreign]

Anyone know of a good HDD activity monitor? Specifically, something that can monitor what processes are accessing/reading/writing to the HDD.

My father is looking for a utility program, and I just don't have the time to go rootin' up the i-net.

 

[ktr]

a quick google: http://badmofo.org/bmem/

try it out and report back

 

[ktr]

Here is another: http://www.microsoft.com/technet/sysinternals/FileAndDisk/Diskmon.mspx

 

[imperialreign]

a quick google: http://badmofo.org/bmem/

displays a single, multi-colored bar graph at the top of the screen which shows MEM available, virtual MEM, CPU load, and a blinking red "light" that indicates HDD activity. Not much use for me, though.

Here is another: http://www.microsoft.com/technet/sys...k/Diskmon.mspx

yeah, I've had that one layin around on my rig, but haven't been able to get it to work on my fathers - he runs Vista, and it reports that it can't access the HDD because of some security issue or whatever. My father won't let me "adjust" the HDD security settings, so, buggar . . .

 

[keakar]

gotta love that vista lol

 

[ex_reven]

displays a single, multi-colored bar graph at the top of the screen which shows MEM available, virtual MEM, CPU load, and a blinking red "light" that indicates HDD activity. Not much use for me, though.



yeah, I've had that one layin around on my rig, but haven't been able to get it to work on my fathers - he runs Vista, and it reports that it can't access the HDD because of some security issue or whatever. My father won't let me "adjust" the HDD security settings, so, buggar . . .

Maybe try running as administrator.

 

[imperialreign]

Maybe try running as administrator.

yeah, I finally figured that out last night. I honestly didn't figure I'd have to do so, seeing as how my father's user account on that rig is owner/administrator. Maybe it's something MS will fix in a further Vista update or the first service pack. I don't see a point in having to 'run as administrator' when you're logged in as such, y'know?

But, anyhow, I finally got his rig straightened out. He was wondering what was hitting the HDD's so hard during idle and low CPU usage. Turned out it was the DfrgNtfs.exe process that was doing the "behind the scenes" defrag. So I went into registry and turned it off - if it happens again, the file is getting renamed.