Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!ch1
From: ch1@cisunx.UUCP (Chris  Helferty)
Newsgroups: comp.sys.apple
Subject: Re: BinSCII problems
Message-ID: <16682@cisunx.UUCP>
Date: 13 Mar 89 17:49:34 GMT
References: <1163@cmx.npac.syr.edu>
Reply-To: ch1@unix.cis.pittsburgh.edu (Jon M. Pearsall)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 31

In article <1163@cmx.npac.syr.edu> dgruest@cmx.npac.syr.edu (David Gruest) :
>
>I seem to be having trouble getting binscii.
>I give it the path name of the txt file i wish to convert back to prodos
>then the path of a second 5 1/4 drive, It spins away and processes the
>text file (i assume) and then stops.  It doesn't write out the binary
>file.
>

I also have been having trouble getting Binscii to work with some of the
posted files.  I was never able to get the recent posting of a terminal
emulator (ZLink?) to unpack and a couple of other things which I forget
since I deleted them since they were apparently not going to unpack for
me.  I was only able to get Hyper C to unpack after concatenating the 8
files into 1 single file.  This is only with *some* binscii`ed files (or
should I say *most* ?).  Some things have gone just fine such as the
recent clock.system file and program selector.  The symptoms are the
same as those posted above.  I give Binscii the pathname of the file to
unpack.  It checks the drive to make sure it's there then asks me for
the destination.  I give it the prefix for the second drive and then it
checks for the existence of this drive.  After finding it, it goes back
to the first drive and begins to unpack.  Except it never writes to the
destination drive.  Or any drive for that matter.  It only reads from
the packed file and that is all.  Then it just stops as if everything
went ok.  I've done other things like giving a destination file name but
then it just comes back with a file not found error (and I have to quit
the program and restart it to clear this bug (a small bug I gather)).
I have an older version of Prodos (version 1.1.1).  Is this the problem?
Any one else getting hassles?  Whatever happened to executioner?

						Jon M. Pearsall