Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » net.micro.cbm » Oh, no! Not the "SAVE/REPLACE" Bug!
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Oh, no! Not the "SAVE/REPLACE" Bug! [message #113869] Tue, 17 September 2013 14:53 Go to next message
wanttaja is currently offline  wanttaja
Messages: 78
Registered: May 2013
Karma: 0
Member
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...
Re: Oh, no! Not the "SAVE/REPLACE" Bug! [message #113878 is a reply to message #113869] Tue, 17 September 2013 14:53 Go to previous messageGo to next message
rfox is currently offline  rfox
Messages: 10
Registered: July 2013
Karma: 0
Junior Member
Message-ID: <719@sdcsvax.UUCP>
Date: Wed, 6-Mar-85 18:37:51 EST
Article-I.D.: sdcsvax.719
Posted: Wed Mar  6 18:37:51 1985
Date-Received: Sun, 10-Mar-85 05:02:14 EST
References: <485@ssc-vax.UUCP>
Distribution: net
Organization: EECS Dept. U.C. San Diego
Lines: 21

> 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.
> 
> 					 Ron Wanttaja
> 					 (ssc-vax!wanttaja)
> 

It seems that you haven't been bitten by the save replace bug but by
another bug called misaligned head. The disk you are using was 
initialized on a drive ( could be the same one ) that was/is aligned
differently and thus things like 1435 blocks free occassionly appear.

I copied stuff on to a disk on a bad drive and now I sometimes trouble
loading anything. Other times I get junk or 1435 free blocks. So I would
reconsider your sending mail to a company about the save @ replace bug
until after you are fully sure about whats happen.

rich
Re: Oh, no! Not the "SAVE/REPLACE" Bug! [message #113882 is a reply to message #113869] Tue, 17 September 2013 14:53 Go to previous message
Anonymous
Karma:
Originally posted by: gentner@sdcsla.UUCP (Don Gentner)
Message-ID: <812@sdcsla.UUCP>
Date: Thu, 7-Mar-85 15:26:12 EST
Article-I.D.: sdcsla.812
Posted: Thu Mar  7 15:26:12 1985
Date-Received: Sun, 10-Mar-85 05:29:23 EST
References: <485@ssc-vax.UUCP>
Distribution: net
Organization: U.C. San Diego, Cognitive Science Lab
Lines: 19

> 

I agree with you, Ron.  The three times I was bitten by save/replace
(I'm a slow learner), I was saving moderate size programs on disks that were
less than half full.  There was plenty of room for temporary copies.

You say that when you tried to load a 4 block file, an entirely different
20 block file came up.
Now I predict that you first did a save/replace on your 4 block file, and
next did a save/replace on your 20 block file.  Further, if you look at
your directory block, you will find that the directory entries for both
files have a pointer to the same block (the start of the 20 block file).
My guess is that for some reason, the BAM was not updated properly when you
saved the 4 block file and thus it was overwritten by the later save.
I've tried examining broken disks without getting any closer than this to
the root problem, but perhaps someone will have more luck.

				Don Gentner
				CSL, UC San Diego
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: New 68000 computer from Commodore : The "Amiga"
Next Topic: KayPro Modem?
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Jul 13 00:47:43 EDT 2020

Total time taken to generate the page: 0.00392 seconds