Newsgroups: comp.os.msdos.apps Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!news From: smsmith@hpuxa.acs.ohio-state.edu (Stephen M. Smith) Subject: Re: deskview question Message-ID: <1991Apr21.214153.9566@magnus.acs.ohio-state.edu> Sender: news@magnus.acs.ohio-state.edu Nntp-Posting-Host: hpuxa.acs.ohio-state.edu Organization: The Ohio State University References: <6521@bwdls58.bnr.ca> Date: Sun, 21 Apr 1991 21:41:53 GMT Lines: 21 In article <6521@bwdls58.bnr.ca> mlord@bwdls58.bnr.ca (Mark Lord) writes: > >The other window can not allocate the same clusters since they are marked >as in-use in the FAT as they are taken by the first window. However, unless >you are running the SHARE.EXE thingie (or maybe even if you do run it :) ), >nothing prevents deleting the new file from the second window while the first >window is still writing to it. Solution? Don't do it! Here's a little experiment for you people: Start downloading a file in one window, then switch to another window which has a DOS prompt (BIG DOS is a good choice); then enter CHKDSK *without* the /f parameter and you will get the infamous error message which ends with "Convert lost chains to files? (Y/N)". If you use the /f parameter, those clusters which are being written to and reserved for your downloaded file will be gathered into the usual FILES001.CHK file. No harm done, except your file which is downloading is now screwed up royally. Kids, don't try this at home. SS