GORRIEDE@UREGINA1.BITNET (Dennis Robert Gorrie) (12/18/89)
Sorry , I should have been more specific in my earlier message. I am still using the OLD version of CygnusEd, I just sent for the new one. While using the OLD version, some times I would crash the computer, because of another unreliable program I was using at the same time. The cause of the crash was completely due to my use of this other program. However, I would find these files called CygnusEdTempA.623 and so on. They are blank directory entries. I have even used programs like Diskmaster and CLIMATE to try and delete them. As you know, using these programs avoids any typing or naming errors, so that is not the problem. BTW the file length is zero (I think). I found I can repeat the error if I save a file from CED, and then reboot too quickly. It seems that it accesses the drive, waits for 2 secs, and then accesses it again. So anyways, some times while running some buggy program or another, I crash the computer, and if I am also running CED, I get these undeletable files with the name CygnusEdTemp.xxx . And I cannot delete them, no matter what program I use (delete, climate, diskmaster,diskutil, ect). Not that they cause any problems, its just strange. Perhaps DiskSalv could clean them up. +-----------------------------------------------------------------------+ |Dennis Gorrie 'Chain-Saw Tag... | |GORRIEDE AT UREGINA1.BITNET Try It, You'll Like It!'| +-----------------------------------------------------------------------+
a464@mindlink.UUCP (Bruce Dawson) (01/14/90)
The cygnusedtempa.623 files are temporary files to avoid destroying the
file you were saving if the system crashes mid-save. If you were working on an
important file and the system crashed halfway through saving on top of it, due
to the design of the file system, you would lose the entire file. So, we save
it under a temporary name, then delete the old and rename. So, better the
'cygnusedtempa.623' file being zero length and undeletable than your project.
Also, it is worth noticing that we do _not_ write out the file, wait a few
seconds and then access the disk again. All of the disk access is done as
quickly as possible, with no delays. What you are seeing is the normal
behaviour of the filing system. In an attempt to be more efficient it will
wait a couple of seconds for more data before doing the final write. You
should _always_ wait several seconds after the last disk activity before
rebooting to make sure that all is _truly_ done, otherwise you risk losing
data.
.Bruce Dawson.
P.S. If the system crashes while editing/saving and you lose data, don't
forget about recovercedfiles, which will attempt to locate the files in memory
after you reboot.