Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!daveh
From: daveh@ccwf.cc.utexas.edu (David H. Huang)
Newsgroups: comp.sys.apple2
Subject: GS/OS bug?
Message-ID: <44939@ut-emx.uucp>
Date: 1 Mar 91 19:11:19 GMT
Sender: news@ut-emx.uucp
Reply-To: daveh@ccwf.cc.utexas.edu (David H. Huang)
Organization: The University of Texas at Austin
Lines: 24
Originator: daveh@dewey.cc.utexas.edu

I posted this a while ago, but it didn't seem to make it out of Texas...
Apologies if you've seen this before though.

After having some weird problems with a program of mine, I found this
possible bug in GS/OS... If you open a file, write to it, take the
disk out and replace it with another one, then try to close the file,
you get a mount volume box (assuming your SysPrefs allows it). If you
choose Cancel, you get a $20 (bad request) error if the disk isn't
write protected, or a $2B (device is write protected) if the disk is
write protected. This is really weird since GS/OS has no business
trying to write to the disk if the volume name doesn't match. Instead,
it should return with a $45 (volume not found), right?

Any comments about this or suggestions for a work-around would be
appreciated.

BTW, I'm using System Soft 5.0.4, but the same problem exists in 4.0.

Thanks!
-- 
David Huang                                 |
Internet: daveh@ccwf.cc.utexas.edu          | "Slight accidents with funny rays
UUCP: ...!ut-emx!ccwf.cc.utexas.edu!daveh   |   can have serious consequences"
America Online: DrWho29                     |