cmh@burl.UUCP (Hinton Marlow ) (08/01/85)
The Mystery: A BASIC program saved to disk (1541) has mysteriously disappeared and foul play is suspected. The filename exists in the directory but on LOAD"file",8 and RUN (or LIST) the program is replaced by another one listed on the disk. Repeated attempts mysteriously replace the named file with a known imposter. Is it a case of murder or kidnapping? Pertinent Facts: Most often files are saved and loaded under Simon's Basic (I love it). The disappearing file has Simon's Basic code in it (although many of the others on the disk do as well). LOADing the file without Simon produces the same result. The file has been SAVEd and REPLACEd several times (so too have many of the others). The disk is a year old (about) but clean. I've VALIDATED it and INITIALIZED the disk in an effort to recover with no apparent results. I've received no ransom notes or extortion threats from the disk drive. The police aren't interested. The Job (if you elect to accept it): Help me recover the file (or if she's dead :(, explain why she died why she's still listed as a member on the disk). Be gentle, my technical knowledge of the C64 and 1541 is limited. Reward: A hearty thanks and the satisfaction that you've solved one of the most baffling mysteries of the century. THANKS Wink Swain d/b/a Marlow Hinton Local "greppie" makes good!
rwh@aesat.UUCP (Russ Herman) (08/02/85)
> A BASIC program saved to disk (1541) has mysteriously disappeared and > foul play is suspected. The filename exists in the directory but on > LOAD"file",8 and RUN (or LIST) the program is replaced by another one > listed on the disk. Repeated attempts mysteriously replace the named > file with a known imposter. ... > > The file has been SAVEd and REPLACEd several times (so too have many > of the others). Sounds like the old "save with replace" bug, now incontrovertibly demonstrated to exist. Don't EVER use the @filename notation in a SAVE statement: purge the file separately first. Also, unless you have REL or USR files on the disk, validate it after each few file purges. Make sure you never run your disks out of space, and if you wind up with any "*" files, do a OPEN 8,8,8,"filename,type,M:CLOSE8 and a validate as soon as possible. Never lost a file yet... -- ______ Russ Herman / \ {allegra,ihnp4,linus,decvax}!utzoo!aesat!rwh @( ? ? )@ ( || ) The opinions above are strictly personal, and ( \__/ ) do not reflect those of my employer (or even \____/ possibly myself an hour from now.)
dwl10@amdahl.UUCP (Dave Lowrey) (08/05/85)
> ..... Also, unless you have REL or USR files on the disk, > validate it after each few file purges....... You CAN safely do a Validate with USR and REL files on the disk. The only time you don't want to validate is when blocks are being used, that aren't allocated in the BAM. -- ------------------------------------------------------------------- Dave Lowrey "To vacillate or not to vacillate, that is the question.... ....or is it?" ...!(<sun,cbosgd,ihnp4}!amdahl!dwl10 [ The opinions expressed <may> be those of the author and not necessarily those of his most eminent employer. ]