Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!metro!grivel!gara!jbell
From: jbell@gara.une.oz.au (Justin Bell)
Newsgroups: comp.sys.cbm
Subject: Re: @: (save/replace) bug?
Summary: When a disk is near full it cannot work because it writes the new file
	 then scratches the old.
Message-ID: <5701@gara.une.oz.au>
Date: 20 Mar 91 01:53:27 GMT
Article-I.D.: gara.5701
References: <1991Mar20.095745.9860@cc.newcastle.edu.au>
Organization: University of New England, Armidale, Australia
Lines: 20

In article <1991Mar20.095745.9860@cc.newcastle.edu.au>, c8923075@cc.newcastle.edu.au (Chris (Polar) Baird) writes:
> 
> Could someone please explain what the 'save/replace' bug was on the
> 	original (grey) 1541? How it happens, why it happens, does it
> 	still exist, or does anybody really know?
> -- 
>   }`oo'{
>     `'    Chris "Polar" Baird
> Impoverished BSc Undergrad @ Newcastle Uni (OZ!)
>        C8923075@cc.newcastle.edu.au

     There is a way round this by including at the end of a basic program 
   a subroutine that erases the original program and writes the new one.

   I have not got the details now but e-mail me if you would like an 
   in-depth explanation, or have a look at the 1990 Australian Commodore
   & Amiga review Commodore ANNUAL.


   :)    jbell@gara.une.oz.au