Re: Need Ninjaforce's assembler off caltech

[nparker@cie-2.uoregon.edu (Neil Parker)]

In article <d122256@pro-palmtree.cts.com> jpoore@pro-palmtree.cts.com (James
Poore) writes:
>According to my ISP, Lynx will only transfer Text files (or binscii encoded
>system files), and is not set up to do binary transfers.  Not being a
>Netspert, I dont know if there are different versions of Lynx on different
>ISP's, so I am not sure this is 100% correct.

Well...that depends.

Lynx can definitely FTP binary files.  But in order to do so, it uses a
scheme whereby it looks at the suffix of the file's name to decide whether
to do an ASCII or binary transfer.  Lynx comes with knowledge of a number
of suffixes hardwired into the source code, and some more suffixes can be
listed in a system-wide configuration file (/usr/local/lib/lynx.cfg on my
machine).  Unfortunately, these default suffix lists don't include most of
the commonly-used Apple II suffixes.

That's where your private ".mime.types" (or "MIME.TYPES" on VMS) file comes
in.  Any suffix that you put in your .mime.types file will be FTPed in
binary mode.  My .mime.types file includes these lines:

application/x-Shrinkit shk SHK sdk SDK
application/x-BinaryII bny BNY bqy BQY bxy BXY

That's sufficient for most Apple II FTPing.

But in order to use the .mime.types feature, you'll need an ISP that will
provide you with space to save your own files on the ISP's machine.  Some
ISPs aren't willing to do that.  If your ISP won't give you any file space,
then your only recourse is to try to talk them into putting the Apple II
suffixes into the system-wide lynx.cfg file.  (Or switch to a different
ISP, of course.)

               - Neil Parker
-- 
Neil Parker                       | No cute quote, no cute ASCII art, no cute
nparker@cie-2.uoregon.edu         | disclaimer, no deposit, no return....
nparker@cie.uoregon.edu           | (This space intentionally left blank:
http://cie-2.uoregon.edu/~nparker |                                           )