Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!sri-unix!rutgers!ames!ucbcad!ucbvax!decvax!tektronix!orca!pogo!rickc From: rickc@pogo.TEK.COM (Rick Clements) Newsgroups: comp.sys.cbm Subject: Re: C64 Manual****Saving Files Message-ID: <3635@pogo.TEK.COM> Date: Wed, 19-Aug-87 15:28:08 EDT Article-I.D.: pogo.3635 Posted: Wed Aug 19 15:28:08 1987 Date-Received: Sat, 22-Aug-87 10:07:02 EDT References: <295@dsacg3.UUCP> <2214@cbmvax.UUCP> <252@uwslh.UUCP> Reply-To: rickc@pogo.UUCP (Rick Clements) Organization: Tektronix, Inc., Beaverton, OR. Lines: 27 Summary: Must ALWAYS specify the drive number In article <252@uwslh.UUCP> lishka@uwslh.UUCP (Christopher Lishka) writes: >In article <2214@cbmvax.UUCP> eric@cbmvax.UUCP (Eric Cotton) writes: >>A word of caution here: It is not advisable to use save-with-replace on >>the old 1541 disk drives. Delete the file first and then save the new >>version. >> Eric Cotton >> Commodore-Amiga >Hmmmm... I *have* been using the @0: command on my old 1541 drive >since I have had it (four or five years now), and have NEVER had any >problems. I also thought that a Commodore Representative posted a >message saying that as long as one specified the drive number (i.e. >the 0 in @0:) that the porblem would NOT occur; the problem only >occurred when one used '@:' (i.e. without specifiying which drive). Using "@0: instead of "@:" is not enough. If an other operation does not specify the drive number (the 0) the problem can still occur. The problem is the drive can try to reference the non-exisant drive 1. It then allocates a buffer for the sectors in use on that drive. Then, the right chain of events can cause the drive to loose track of the sectors in use on drive 0. This can cause a lot of strange probems. I had a disk with two files sharing a common end. I do not use the save and replace. Because, I do not trust programs written by someone else to always use the drive number. I lost enough data the first time this happened.