Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!umich!sharkey!cfctech!teemc!ka3ovk!ki4pv!cdin-1!dsinc!netnews.upenn.edu!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Missing files after system crash
Message-ID: <6383@cps3xx.UUCP>
Date: 9 Feb 90 23:39:25 GMT
References: <29750@andante.UUCP>
Reply-To: cookr@cpsin1.UUCP (Robert W Jr Cook)
Organization: Engineering, Michigan State Univ., E. Lansing
Lines: 24

In article <29750@andante.UUCP> bwb@andante.UUCP (Bruce Ballard) writes:
>The problem: Your app writes one or more files,
>then a static charge or a tripping
>over the power cord causes the machine to go down.
>Upon reboot, your files are missing from the desktop.
>
>The reason: ??

    The volume buffer is held in memory until such a time the OS deems
    the data worthy enough to write out (or something like that). 

>The solution: ??

    Use FlushVolume (or whatever it is, IM not handy at the moment...)
    to put this info on the disk.

    Any other comments on this problem?  When does the OS decide to
    write the buffer?  This has always been greek to me...

Robert Cook
"cookr@cpsin1.msu.edu"

Disclaimers:  I may not always say the right things, but at least what I
              say is mine, and no one else.