|
PureBytes Links
Trading Reference Links
|
I don't know that it necessarily needs to be defragmented that often, it
was just a convenient timeframe in which to do it. I'm not doing anything
very intensive during those hours. Sometimes, I'm even asleep. I do know
that while I was defragging on a weekly basis, when I looked at the state
of fragmentation of my C: drive it was often quite bad. I suspect it may
be related to browsing on the web which creates tons of temporary files
which I aperiodically clean out with the Windows Washer 2.6 from
www.webroot.com.
The other thing I've noticed with this defragger on NT is that it doesn't
seem to be able to get everything defragged in one pass. It seems to have
to do it 5 or 6 times before it is as clean as it is going to get. Under
MSDOS, the Norton defragger used to clean it all up in one go, but there
must be some added complexity with NTFS that prevents this.
I'm also not 100% sure that defragging by itself is what fixed the
remaining crash problem, it just happens to be the last thing I did to try
to optimize my machine. Maybe the fact that I'm now running Windows Washer
at least daily helps too, though I don't see how it could. I've always had
at least 800 MB free on my C: drive.
At 09:11 AM 9/13/99 -0700, you wrote:
>On Sun, 12 Sep 1999, Ullrich Fischer wrote:
>
> > I have a fair bit of crap (err...ah... excellent 3rd party software) on my
> > NT machine and it still works just fine with TS2Ki, eSignal, eudora email,
> > Lotus 123, Excel, MSword, and 3-4 IE 5.0 browser windows running. The key
> > to stability on my system was to add Diskeeper 5.0 from Executive
> Software
> > with automatic defrag set to happen between 1am and 6am every night. I
>
>Any ideas as to why it requires such frequent defrags to be stable? One
>would think that just one day of operation would not produce much
>fragmentation. And why should TS2k be *so* sensitive to defrags?
|