Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!bloom-beacon!athena.mit.edu!dcw
From: dcw@athena.mit.edu (David C. Whitney)
Newsgroups: comp.sys.apple
Subject: Re: BinSCII problems
Message-ID: <9663@bloom-beacon.MIT.EDU>
Date: 7 Mar 89 18:43:46 GMT
References: <1163@cmx.npac.syr.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: dcw@athena.mit.edu (David C. Whitney)
Organization: Massachusetts Institute of Technology
Lines: 32

In article <1163@cmx.npac.syr.edu> dgruest@cmx.npac.syr.edu (David Gruest) writes:
>
>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.
>
>Can anyone tell me what's wrong?

I'll tell you: my User Interface sucks. It's hardly intuitive - but it
was very easy to write. Here's the deal: When BinSCII asks for a
pathname, it's asking for the complete or partial pathname of the file
you wish to (un)convert. When it asks for a prefix, it wants to know
where to dump the results of the processing. For example, if you had a
BinSCII file sitting in your downloads directory and you want it to
unpack to your testing directory, you'd type:

Enter pathname -> /disk/downloads/newfile
Enter prefix -> /disk/downloads/testing

I am going to give v1.0.2 a good look over and then post it. It is
essentially the same as v1.01, except that it prints out what it's up
to (ie, unpacking n bytes into file <x>). I *do* intend to write a
nice User Interface (similar in form to ShrinkIt's UI), but that takes
time, and time is precious when you're a tooling MIT undergrad.


Dave Whitney	A junior in Computer Science at MIT
dcw@athena.mit.edu  ...!bloom-beacon!athena.mit.edu!dcw  dcw@goldilocks.mit.edu
I wrote Z-Link. Send me bug reports.           I use a //GS. Send me Tech Info.
"This is MIT. Collect and 3rd party calls will not be accepted at this number."