Xref: utzoo comp.windows.ms:13104 comp.os.msdos.misc:2227
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!munnari.oz.au!bruce!monu0.cc.monash.edu.au!monu4!ins845b
From: ins845b@monu4.cc.monash.edu.au (mr  k.l. lentin)
Newsgroups: comp.windows.ms,comp.os.msdos.misc
Subject: Re: unmoveble blocks in Norton Speed disk
Message-ID: <1991May26.013900.22227@monu0.cc.monash.edu.au>
Date: 26 May 91 01:39:00 GMT
References: <10545@castle.ed.ac.uk>
Sender: news@monu0.cc.monash.edu.au (Usenet system)
Organization: Monash University, Clayton, Vic 3168, Australia
Lines: 28

In article <10545@castle.ed.ac.uk> own@castle.ed.ac.uk (O Morgan) writes:
>Some time ago there was some talk (panic) about large chunks of some
>peoples hard disks being highlighted as "unmoveable" when trying to
>unfragment the disk with Norton Speed disk.  Did anyone ever figure why
>this happens? At the time people thought it was a Windows shareware
>utility, though I think this was later disproved.  Though I have no
>clear idea why this is happening, I suspect it has something to do with
>Windows 3. 
>
>I'm only asking because I just did an SD, and virtually the whole of my
>hard disk is marked as "unmoveable blocks", which isn't very reassuring.
>
>Does anyone know why this happens (I thought only hidden and system
>files where unmoveable) and how to cure the problem?  
>
What you're saying sounds right. Only hidden and system (and read only maybe)
files are unmovable PLUS any others you tell norton are unmovable. Theres an
option On the menu to display unmovable files. You may find some surprises in
there!

Another point is that you cuold have 1 large unmovable file that is very
fragmented and norton will show each block that the file resides in as
unmovable when in fact it will move part of that block. When displaying the
screen, an unmovable cluster takes prefernece over an unused or used cluster
in the same block.

|/
|\evin