Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!ucsdhub!sdcsvax!ucsd!ucbvax!ISUMVS.BITNET!GR.SLK
From: GR.SLK@ISUMVS.BITNET (Steve Kunz)
Newsgroups: comp.sys.apple
Subject: BINSCII Data File Types
Message-ID: <8903101045.aa00838@SMOKE.BRL.MIL>
Date: 10 Mar 89 15:32:13 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 33


 >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. ...
 >
 >[... instructions on paths/prefixes deleted ...l
 >
 >Dave Whitney    A junior in Computer Science at MIT
 >dcw@athena.mit.edu ...!bloom-beacon!athena.mit.edu!dcw dcw@goldilocks.mit.edu

I had trouble with this, too.  Turned out I was using the parms right - just
downloading the "text" files to process with BINSCII wrong.

BINSCII encoded "text" files are BINary ASCII-character files, not Apple "TXT"
files.  If you download a BINSCII encoded file from somewhere with KERMIT, for
example, you must set the file-type to BINARY.  If the file is downloaded in
TEXT mode, KERMIT will set the X'80' bit on in every byte and BINSCII will spin
through it without writing anything (or saying anything is wrong).  Ship the
same thing down as BINARY and it works.

-------------------------------------------------------------------------------
Steve Kunz:  GR.SLK@ISUMVS.BITNET, GRSLK@CCVAX.IASTATE.EDU
-------------------------------------------------------------------------------