GR.SLK@ISUMVS.BITNET (Steve Kunz) (03/10/89)
>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 -------------------------------------------------------------------------------
SEWALL@UCONNVM.BITNET (Murph Sewall) (03/11/89)
>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. I did send Dave a message earlier today asking if BinSCII cared about the 8th bit (downloading in ProDOS with Kermit 3.85 works fine for me, but older <before 3.84?> versions of Kermit did have the 8th bit wrong in ProDOS <it's supposed to be OFF in ProDOS, on in DOS 3.3 :->). It seems to me that it should be possible for BinSCII to take care of the 8th bit problem itself (?), as apparently the current version IS sensitive to whether it's correct or not (I suspect that's why loading it into the Mouse Talk editor and saving it produces a workable file). Evidently, BinSCII doesn't care whether the file type is TXT or BIN; that's a plus. Murph Sewall Vaporware? ---> [Gary Larson returns 1/1/90] Prof. of Marketing Sewall@UConnVM.BITNET Business School sewall%uconnvm.bitnet@mitvma.mit.edu [INTERNET] U of Connecticut {psuvax1 or mcvax }!UCONNVM.BITNET!SEWALL [UUCP] -+- I don't speak for my employer, though I frequently wish that I could (subject to change without notice; void where prohibited) According to the American Facsimile Association, more than half the calls from Japan to the U.S. are fax calls. FAX it to me at: 1-203-486-5246