defragging

  • Thread starter Thread starter Linea Recta
  • Start date Start date
L

Linea Recta

When I use Norton Speeddisk 2003, after defragging I still have red blocks
scattered all over the place, marked as "unmovable". Why is this? (I have
added the swapfile in the list to put first).


--
regards,

|\ /|
| \/ |@rk
\../
\/os
 
The red blocks are used by Windows system files. You cannot move them, to
do so will render them unstable.

Having said that though, some of the red blocks you see are also lost
clusters which aren't movable.
 
What I really meant was, that I can't imagine any good reason why any file
couldn't be moved to another location on the hard disk without affecting its
functionality.


--
regards,

|\ /|
| \/ |@rk
\../
\/os
 
Thanks, I'll have a look into it. So these files ARE movable after all? What
strange issue...


--
regards,

|\ /|
| \/ |@rk
\../
\/os
 
Linea said:
What I really meant was, that I can't imagine any good reason why any file
couldn't be moved to another location on the hard disk without affecting its
functionality.
Click to expand...

Yes and no. Disk Defragmenter is overly cautious about moving system
files, based on the idea "better safe than sorry".
 
[This followup was posted to alt.os.windows2000 and a copy was sent to the
cited author.]

mccm.vos- said:
Thanks, I'll have a look into it. So these files ARE movable after all? What
strange issue...
Click to expand...

Some files are always in use while Windows is normally running.
Diskeeper has a boot-time defragmentation routine that can defrag the MFT
and pagefile during bootup, before most of Windows is loaded. For Win2K,
this during that screen with the bar on the bottom. A text screen will pop
up with the running program. If you've ever had CHKDSK run on bootup, it's
like that.

Speedisk used to use it's own driver, but Symantec, probably prodded by
Microsoft, dumped that and now it uses the standard Windows API.
 
Speedisk used to use it's own driver, but Symantec, probably prodded by
Microsoft, dumped that and now it uses the standard Windows API.
Click to expand...

As part of the usual saying for software: "If it works, take it out" ?
 
chris17 said:
As part of the usual saying for software: "If it works, take it out" ?
Click to expand...

The issue is the fact that MS occasionally makes changes to the NTFS
format. It's risky to bypass Windows to make changes.
 
Andrew Rossmann said:
The issue is the fact that MS occasionally makes changes to the NTFS
format. It's risky to bypass Windows to make changes.
Click to expand...

isnt it risky running windows full stop ? :-P

alan

-- linux rules
 
Back
Top