Re: BINSCII problems...

[rubywand@aol.com (RUBYWAND)]

In article <Pine.SUN.3.91.960220134102.10187D-100000@owens>, Cyrus Roton
<croton@ridgecrest.ca.us> writes:

>
>Several people seem to be missing the point here. You can not run BINSCII

>until you HAVE binscii.

   Certainly, this could be a firm barrier to further Binscii experiences.

>I, too, tried downloading the exec file and using 
>it. I does not work as advertised. It creates a binary BINSCII file, 
>which is about the same size a the system binscii file (which I have on 
>another disk). But, that binary file will not BRUN and the Prodos 
>Exerciser can not read the file type so I can change it to "sys". The 
>exerciser tells me that there is some problem with the file. In other 
>words, there seems to be some problem with that exec file, BINSCII.V103X 
>which is found on grind (I mean on "ground")
>

    Maybe BINSCII.V103X on Ground' really is messed up. Maybe not. One
possible source of difficulty is that ShrinkIt-GS self-extracting files
are type $B3 GS/OS applications. They expect to be executed under GS/OS.

    As a check: Binscii version 1.0.3 (which I obtained on the Chuck Orem
"Modemming Disk")  should be a type $FF file with auxtype $2000 and length
= 3633 bytes.
     


Rubywand