Path: utzoo!utgpu!watmath!isishq!f171.n221.z1.FIDONET.ORG!izot
From: izot@f171.n221.z1.FIDONET.ORG (Geoffrey Welsh)
Newsgroups: comp.sys.cbm
Subject: 154I drive problem
Message-ID: <2048.24456DA0@isishq.FIDONET.ORG>
Date: 13 Apr 89 12:52:33 GMT
Sender: ufgate@isishq.FIDONET.ORG (newsout1.25)
Organization: FidoNet node 1:221/171 - Izot's Swamp, Kitchener ON
Lines: 28


 > From: sl161004@silver.bacs.indiana.edu (David Chary)
 > Message-ID: <3738@silver.bacs.indiana.edu>
 
 > Suppose I have a number of files, "FILE A", "FILE B",... "FILE n".
 > When I save FILE K using "@):FILE K", it does what it is told.
 > But later, I want to use FILE G, which I know is a different file.
 > so I load "FILE G" and much to my surprise it is "FILE K"!
 >
 > What is happening to the disk or the drive?
 
   *That* is the infamous "save@" bug, which was rumoured but never proven 
until the Transactor offered a reward for any software that could document it 
and Phil Slaymaker wrote a program that eventually caught it out.
 
   This is not just a 1541 oddity; it dates back to the 2040 drive and comes 
forward as far as the 1571 (the 1581, which required a drastically rewritten 
DOS, doesn't appear to suffer from the problem) and also affects the MSD 
SD-1 and SD-2 drives.
 
   The solution, I'm afraid, is to delete & save in stead of using SAVE@.
 


--  
 Geoffrey Welsh - via FidoNet node 1:221/162
     UUCP: ...!watmath!isishq!171!izot
 Internet: izot@f171.n221.z1.FIDONET.ORG