12 Hrs and still defragmenting

[Guest]

I have a laptop with intel core 2 duo 2.0 Ghz cpu and 2GB RAM, my laptop was
damn slow so I started the disk defragmenter and 12 Hrs and still
defragmenting 60 gb hdd with 20 gb free space?
Any ideas what may be going wrong? or is this normal for the lovely Windows
Vista?

 

[Paul Smith]

I have a laptop with intel core 2 duo 2.0 Ghz cpu and 2GB RAM, my laptop
was
damn slow so I started the disk defragmenter and 12 Hrs and still
defragmenting 60 gb hdd with 20 gb free space?
Any ideas what may be going wrong? or is this normal for the lovely
Windows
Vista?

The Windows Vista defragger runs at background priority, its geared around
running automatically in the background instead of being run automatically
and thrashing the disk until its finished.

12 hours however still seems on the high end. How slow is "damn slow"?

--
Paul Smith,
Yeovil, UK.
Microsoft MVP Windows Shell/User.
http://www.dasmirnov.net/blog/
http://www.windowsresource.net/

*Remove nospam. to reply by e-mail*

 

[Frolov Alexandr]

Frustrated here as well
lack of information in both gui based and console versions of built in
defragmentator programs made me nervous.
so i downloaded a 30 day trial diskeeper 2007 and guess what? works as slow
as buit in.
my guess would be that they all use same api and that's where the problem
lies
i mean there is no way your 60gb disk could be not defragmented in 12 hours.

well at least diskeeper provides some feedback on what it is currently busy
with.
i don't really understant what was the point of gimping defrag utility in
vista.
in nt 4 there was no built in defrag hence everyone and his dog was using
third party utilities
win2k brought defragmentation to OS and it was good enough

now we have Aero on one side and hours long working defrag without any
feedback. that's a lot of frustration

Frolov Alexander

 

[Richard Urban]

Just forget about defrag. It occurs automatically in the background at low
priority and yields it resources to anything else you may be doing. It will
finish when it finishes. Not to worry so much about nothing.

It was implemented this way because there were far to many people who
"never" defragged their hard drives. They didn't know they had to.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

 

[Frolov Alexandr]

Frustrated here as well
lack of information in both gui based and console versions of built in
defragmentator programs made me nervous.
so i downloaded a 30 day trial diskeeper 2007 and guess what? works as slow
as buit in.
my guess would be that they all use same api and that's where the problem
lies
i mean there is no way your 60gb disk could be not defragmented in 12 hours.

well at least diskeeper provides some feedback on what it is currently busy
with.
i don't really understant what was the point of gimping defrag utility in
vista.
in nt 4 there was no built in defrag hence everyone and his dog was using
third party utilities
win2k brought defragmentation to OS and it was good enough

now we have Aero on one side and hours long working defrag without any
feedback. that's a lot of frustration

Frolov Alexander

 

[Dana Cline]

I'd look for other causes. Take a look in the bios to see what the settings
are for the hard disk. Bring up Task Manager to see what's actually using
all the CPU. Turn off (disable) the Windows Search process - that takes a
lot of cycles...

Dana Cline - MCE MVP