home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!udel!darwin.sura.net!sgiblab!munnari.oz.au!uniwa!john
- From: john@gu.uwa.edu.au (John West)
- Newsgroups: comp.sys.cbm
- Subject: Re: 2 Q's: BMI & SAVE@
- Date: 25 Jan 1993 09:59:57 GMT
- Organization: The University of Western Australia
- Lines: 26
- Message-ID: <1k0dmtINN9ij@uniwa.uwa.edu.au>
- References: <1993Jan17.192438.12044@netcom.com> <C17In9.28u@fulcrum.co.uk> <1993Jan22.062624.23025@netcom.com> <30370@optima.cs.arizona.edu> <1993Jan24.043922.20002@netcom.com>
- NNTP-Posting-Host: mackerel.gu.uwa.edu.au
-
- fuzzy@netcom.com (Fuzzy Fox) writes:
-
- >>>OPEN 15,8,15,"S0:fname" : CLOSE 15
- >>>SAVE "fname",8
-
- >>Well This is the reason doing a simple scratch and save DOESN'T work.
- >>If you don't want this nasty bug to appear, you should ALWAYS use a
- >>"0:" in EVERY I mean EVERY command. In order for the above 'patch' to
- >>work correctly it should read:
-
- >Huh?? If you always SCRATCH the file then SAVE, you will not run into
- >the @-save bug, because you're NOT USING @-save!! :)
-
- For the very simple reason that the bug can appear in more than one place.
- It is only known as the save@ bug because that is where it is most commonly
- seen.
- As far as I can tell from what people have been saying, the bug is caused by
- a failure to correctly load/store the BAM if the drive number is omitted. It
- would seem that the drive occasionally tries to access the wrong BAM (the
- ROM in the 1541 was written for a 2-drive unit, then bashed for a single drive.
- They didn't quite get it right.
- scratch-save is safer than save@, but it will still fail from time to time.
-
- John West
- --
- For the humour impaired: Insert a :-) after every third word
-