Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!subnet.sub.net!mcshh!bkr
From: bkr@mcshh.hanse.de (Bjoern Kriews)
Newsgroups: comp.sys.atari.st
Subject: Re: someone explain, PLEASE!
Summary: tuneup
Message-ID: <8583@mcshh.hanse.de>
Date: 24 Jan 91 22:57:15 GMT
References: <14803@milton.u.washington.edu>
Lines: 31

In article <14803@milton.u.washington.edu>, ramsiri@blake.u.washington.edu (Enartloc Nhoj) writes:
> I tried this four times... because i couldn't believe it.
> 
> I was having problems with 3 bombs when calling STalker from 
> within STeno:  STalker boots from C:\, while STeno i loaded
> from MULTIDESK run as a program (not acc).  Mind you, i have
> had them working together before.. but since i ran TUNEUP
> earlier in the day to optimize my C:\ drive (i never have
> used the optimize option before, always copied, zeroed, copied)
> .. things have gotten strange:
> 

> problems with STalker after using TuneUp Optimizer

The first time a friend of mine used this option, it destroyed
several binaries on his HD. I don't know which version he used,
perhaps the problem is fixed now.


I can't explain your situation - the only (IMHO) possible explanation
would be that your fat is so much garbled that it always points to the
old data - even if this would be true - strange !

solution: before you start to copy/zero, backup and try another
Optimizer/Cleaner named Harddisk Sentry - very reliable - gets 
things back to work in most cases.


* bjoern@drdhh.hanse.de - Bjoern Kriews, Hamburg, FRG
*
* make love...