LUX v 5.3 for TurboDOS

The files in this library are for **TurboDOS** users only!!

If you're not running TurboDOS - then don't use LUX53TD.MQC
You want the regular LUX52.LBR or whatever the current CP/M
version of LUX is.

This version of LUX has had all non-TurboDOS equates stripped
out to compact and clean-up the code.  We don't use things
like ZCPR or KMD or .SUB files to run non-existent BYE programs.


Installation:

Edit conditionals and assemble LUX53TD.MAC with M80/L80
for your system.  Be sure to set the REMFIL equate to what
you use, I use Remote Access and use command files with
the extent of .REM only - you may be using .COM files.

The MAKELUX.DO is a TurboDOS automated assembly program
for use with DO.COM (if you have TDOS then you have DO.COM)

Assemble a version of XMODEM with the LUXMOD equate TRUE
or use a standard XMODEM above version 1.10 that has the
LBR send capability and include it with the Lux modules
in the specified drive/user area.  The LUX53TD.MAC file
is set and looks for LUXMODEM.COM now

The LUX modules, LUXDIR, LUXTYP, UNARC, LUXCHK, and LUXCRC
have been included in .COM form in this library, if you need
the source for special mods get them from the regular LUX52.LBR

I have included a specially modified version of UNARC.COM
that responds to CTRL-S requests as well as CTRL-C requests.
The distributed UNARC.COM in UNARC12.LBR does NOT respond to
CTRL-S.  And it doesn't page so... use mine!

I have also included TYPELZ.COM which you can use in place of
LUXTYP.COM if you wish the ability to TYPE out CRunched files
as well as SQueezed files and regular ASCII files.  TYPELZ.COM
was assembled from TYPELZ13.Z80 and is set for unlimited line
typing and does NOT respond to ZCPR's wheel byte.  Most of the
un-TYPEable filetypes (ie  ARC, SYS, BAD, ??#, OV?, etc..)
are listed in an exclude table at the beginning of the file
and are NOT typed out.

(You may want to seriously consider using TYPELZ as many of
 the new libraries I've seen have large source files crunched
 now to save space rather than squeezing them.)

---------------------------------------------------------------------------
The LUX53-TD.LBR should contain the following:

-READ.ME	This file
LUX53TD.MQC	Squeezed assembly listing (LUX53TD.MAC)
LUXCHK.COM	LUX module (CHEK)
LUXCRC.COM	"      "   (CRC)
LUXDIR.COM	"      "   (DIR)
LUXTYP.COM	"      "   (TYPE)
MAKELUX.DO	Automated DO file for assembly
MAKELUX5.COM	Produces finished LUX.COM, merges LUX.CO0 & LUX.CO1
TYPELZ.COM	Alternate for LUXTYP if supporting CRunched files
UNARC.COM	Alternate for LUXDIR/LUXTYP when attached to an ARC file
---------------------------------------------------------------------------

Future Revs:

I'm thinking about adding individual ARC member send capability
to the newest version of XMODEM (1.24 at this writing) but as
yet have not done it.  ARC file sends are kinda tricky because
ARC.EXE uses 3 or 4 different methods of file compression which
means that the rec'd file would have to be given a filetype
of .ARC so it could be decompressed properly.  This could be
really confusing to the non-expert or novice remote user.

Consider the file  TEST.ARC,  it contains 3 files:

        TEST.DOC   TEST.EXE   TEST.ASM

How does one keep track of the rec'd individual files?  If
you try to give each one the extent of .ARC it's gunna get
confusing real fast.  Oh well...

At least we now have a simple way to manipulate ARC files
to allow remote users to view DOC files before downloading
a 150k or 250k archive they can't use or didn't want but
didn't know any better.


Have fun...


                    Steve Sanders - Sysop
                    The DataCOM Super Systems(tm)
                    (813) 791-1454  300/1200/2400
                    Clearwater, Florida

                    07/13/86


** TurboDOS is (c) Software 2000, Inc.

{eof}