Re: BINSCII problems

["thedm" <thedm@idir.net>]

The Problem I had was that the only download protocol available to me was
binary.  You can still use it after downloading it binary, you just have to
edit the BINSCII.txt before you EXEC it and remove the FIRST character of
every line. This character is something that gets added when you download a
txt file in binary. Remove that and exec it and will compile just fine. I
fought with this for DAYS.

TheDM


Dirk Froehling <dirk@gaga.maschinenbau.uni-dortmund.de> wrote in article
<dirk-2703971553170001@muffin.maschinenbau.uni-dortmund.de>...
> In article <33373195.B01@ix.netcom.com>, jcreid@ix.netcom.com wrote:
> 
> >I, too, have had problems trying to get Binscii to work.  I've
> >followed the instructions to the letter on two different Apples(a IIc+
> >and a Mac LCII with IIe card) and I get the same results.  I thought I
> >had the answer last night when I viewed the program with SimpleText on
> >the Mac.  The Mac treats carriage return/line feeds a bit differently. 
> >I've had this problem before when copying files between PC's and Macs. 
> >Anyway I fiddled with the files and still got the same errors.  Even
> >running the small program that Nathan supplied in the FAQ did not
> >correct anything.  The BINSCII.SYS file never gets created.
> 
> Look at the other threat, I didn't make it, too. But just forget BINSCII,
> unwrap the Binscii files on the Mac with ProTYPE.
> 
> I remember a guy at a computer club meeting about four years ago,
> who got it running by changing something in BINSCII.TXT, but I don't
> know what.
> 
> Dirk
> 
> -- 
> | Dirk Froehling - Germany, Uni Dortmund, FB Maschinenbau, LS Mechanik |
> | dirk@gaga.maschinenbau.uni-dortmund.de           GEnie: D.FROEHLING1 |
>