Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!husc6!uwvax!uwmacc!dan
From: dan@uwmacc.UUCP (dan jatnieks)
Newsgroups: comp.sys.mac
Subject: Help - Kermit eats HD20 space
Message-ID: <511@uwmacc.UUCP>
Date: Fri, 14-Nov-86 22:38:05 EST
Article-I.D.: uwmacc.511
Posted: Fri Nov 14 22:38:05 1986
Date-Received: Sat, 15-Nov-86 07:42:29 EST
Organization: UWisconsin Madison Academic Comp Center
Lines: 39
Keywords: Kermit, Bad filename, Lost disk space


    Background:  Mac Plus, HD20, Kermit 0.834, latest system everything.

	Here's the scoop.  I recently used FTP to get a file from Sumex called
'MACINTOUCH-BENCHMARKS-861028.HQX' and proceeded to try to transfer that
file to my macintosh using Kermit (version 0.834).  Well it just so 
happens that Kermit on the mac really doesn't like that filename because
just as the transfer starts, up pops a dialogue that says "ZCHKI failed: -37".
Oh great, so I click on "OK" and it pops up again.  So I click "OK" and
it pops up again.  And again.  And again.  Rebooting was the only alternative 
I had at that point (as far as I know).  

[ Later I successfully transfered the file by changing the name to 
  "MACINTOUCH-BENCHMARKS.HQX", so it seems that it was indeed the name 
  that was the problem.  Whether it was the "861028" or that it was too
  long or something else I have not checked.]

    That's the first part of the problem.  The second part is that that
problem file was only one in a group that I was transfering using the
wildcard "kermit s *.hqx" on the Unix machine that I was transfering
from.  So before the "hang-up" occured, there had already been about 700K
in 10 files transfered.  When I reboot the mac, there is indeed 700k less
space on my HD20, but none of the files that transfered show up at all.
I assume Kermit doesn't finish closing them until the entire transfer
is complete or some such thing.

    Well, being optomistic (and on a direct line 9600 baud) I tried the
whole thing again.   Exit 700K more of my HD20 space when the exact same
thing happens.  Super, huh?

   O.k. so I eventually figured out how to avoid the problem in this case
(by changing the offending file's name).  My real problem now is to find
a decent way of recovering the lost disk space short of re-init'ing the
HD20.  That is where I am stuck... Anyone with bright ideas (or even
shots in the dark) please let me know.  I already had 18Mb used up on
the disk, and could really use that 1.4Mb for something other than a 
Kermit dump.

danj.