Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!ncsuvx!news
From: sagemma@eos.ncsu.edu (STEVEN ANTHONY GEMMA)
Newsgroups: comp.sys.atari.st
Subject: Re: FAT troubles
Keywords: NeoDesk, FAT, trouble
Message-ID: <1990Nov19.164658.9143@ncsuvx.ncsu.edu>
Date: 19 Nov 90 16:46:58 GMT
References: <1990Nov19.014528.16629@unicorn.cc.wwu.edu>
Sender: news@ncsuvx.ncsu.edu (USENET News System)
Reply-To: sagemma@eos.ncsu.edu (STEVEN ANTHONY GEMMA)
Organization: North Carolina State University
Lines: 33

In article <1990Nov19.014528.16629@unicorn.cc.wwu.edu>,
n8742883@unicorn.cc.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!!

I've had nearly the same thing happen with my setup.  I have Neodesk 2.0 that
I use with my 520ST (recently updated to 1 meg), 1 internal, and 1
external drive.
Sometimes when I switch the disk in drive B, and ask Neodesk to update
the window,
seemingly without even checking the drive, it refreshes itself with the info
from the previous disk.  Closing and opening the window achieve the same
result.
Sometimes I have to change disks several times before it is recognized, or else
I update drive A, and then drive B.  Another, more disturbing result is that
sometimes Neodesk will tell me that drive B contains some folders with 
unprintable names (control characters and such).  It goes on to say that I am
using up -17348542 bytes in 3 items.  At other times I have had nearly 
a gigabyte (!) of disk space used on a standard double-sided disk, or so
Neodesk
says.  I haven't had any problem with the disk being damaged or changed in any
way, however.  When I examine the disk from Atari's desktop, I never have any
problems.

At first, I thought it was my disk drive (Master 3S), but now I'm beginning to
wonder...

-Steve Gemma