RE: "Sharing Violation" and "Invalid Handle"

["Earls, JP" <JEarls@nospam.CSBSJU.EDU>]

Apparently I am missing a step here.  You save to A:, then try to save to C:?  I
do this, and it will not save because there has been no change in the file since
I saved to A:.  Yet, I do not get the error messages that you get. 

Try this: If you first save to A: first, then want to save it to C:, you must
make some sort of change in the file, something as simple as space forward,
space backward will do.  

Happy New Year!

J. P. Earls, OSB
English Department
St. John's University
Collegeville, MN 56321
jearls@nospam.csbsju.edu



-----Original Message-----
From: K. K. Collins [mailto:kkcoll@nospam.siu.edu]
Sent: Sunday, December 31, 2000 7:35 PM
To: Multiple recipients of list NOTABENE
Subject: "Sharing Violation" and "Invalid Handle"


Hello All--

Here's a year's-end question about a "feature" (bug?) of NBWin that's just 
about to drive me mad.  It involves the order in which I must, or so it 
seems, save a file.

If I am working on a file and want to save it to a floppy disk in drive A 
as well as to my hard drive (C), things are OK if I save it to C first by 
clicking on the little disk icon or by pressing Ctrl+S, and then save it to 
A on the command line (sa a:), and then abandon it.  But if I happen to 
forget this lockstep and save it to A first, when I try to save it to C 
(either by clicking on the little icon disk, by Ctrl+S or by using the 
command line, either with "sa" or "st"), I wind up with the error message 
"Sharing Violation" or "Invalid Handle," depending upon how I've tried to 
save it to C.  Nothing I can do (or know how to do) will get it saved to C, 
so I have to abandon it, call it up from A, and then save it to C.

Perhaps the permanently frozen midwest has made me a bit over-sensitive to 
this problem, but does it not seem a fairly insane sequence to be held 
to?  Is there something I'm missing here?

Happy New Year to all users of Nota Bene, troubled and untroubled alike--

Ken Collins