Newsgroups: comp.sys.atari.st
Path: utzoo!utgpu!watserv1!maytag!aftermath!ljdickey
From: ljdickey@aftermath.waterloo.edu (L.J.Dickey)
Subject: Re: FAT troubles
Organization: University of Waterloo
Date: Wed, 21 Nov 90 12:02:58 GMT
Message-ID: <1990Nov21.120258.21926@aftermath.waterloo.edu>
Keywords: NeoDesk, FAT, trouble
References: <1990Nov19.014528.16629@unicorn.cc.wwu.edu> <27343@cs.yale.edu>
Lines: 25

In article <27343@cs.yale.edu> fischer-michael@cs.yale.edu (Michael Fischer) writes:
>In article <1990Nov19.014528.16629@unicorn.cc.wwu.edu> n8742883@unicorn.WWU.EDU (Perry Pederson) writes:
>>
>>	Today I was working with unarcing some files while using
>>NeoDesk 3.0 as my desktop.  I put a new disk in the drive and pressed
>>the ESCape key to tell NeoDesk to read the new disk info and display
>>the directory.  The window refreshed itself with the same info-- for
>>some reason, the FAT had been written from the disk that was just in
>>the computer to the new disk I just inserted!!
>>...
>>	Any suggestions on what could have happened would be appreciated.
>
>What happened is pretty clear.  TOS failed to recognize the new disk,
>so it continued using its cached copies of the FAT and directory from
>the old disk.  I'm surprised that the new disk was clobbered unless
>you actually attempted to write something on it. 
>
>Why it happened is more of a mystery.

I am wondering if it could have happened because he was using
two disks with the same serial number.  Perhaps one disk one
had been formatted by making a full copy of everthing on another
disk.  Or both were formatted on an IBM PC