Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site ssc-vax.UUCP
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!edsel!bentley!hoxna!houxm!vax135!cornell!uw-beaver!ssc-vax!wanttaja
From: wanttaja@ssc-vax.UUCP (Ronald J Wanttaja)
Newsgroups: net.micro.cbm
Subject: Oh, no! Not the "SAVE/REPLACE" Bug!
Message-ID: <485@ssc-vax.UUCP>
Date: Mon, 4-Mar-85 11:51:12 EST
Article-I.D.: ssc-vax.485
Posted: Mon Mar  4 11:51:12 1985
Date-Received: Wed, 6-Mar-85 02:56:00 EST
Distribution: net
Organization: Boeing Aerospace Co., Seattle, WA
Lines: 25



After a long, drawn out discussion about the infamous "save and replace"
command on the 1541, the conclusion seemed to be:

"It's safe, as long as there is enough space left on the disk to temporarily
save the program before the earlier version is killed."

After an experience I had last friday, may I politely comment, "Bullsh*t".

I was using the command again, after a long lapse after being bit once,
and the stupid SOB started mis-loading files, then started having serious
trouble finding other ones.  For instance, when I tried to load a file
4 blocks long, an entirely different one 20 blocks long came up.  The
directory listing showed over 200 blocks free, and I had been carefully
validating the disk on a regular basis.

I've heard there's some company offering a reward for disks trashed by
the save/replace function; anybody have an address?

					 Ron Wanttaja
					 (ssc-vax!wanttaja)

The difference between genius and stupidity is
that genius has limits...