BS> * Somekind of working 'maxpipe' (shouldn't be hard).
 BS> * To get MEX working (has annoyed Wes that it 
 BS> doesn't, since he announced the port)
 BS> * Filetransfers, if it was up to be should the old 
 WG> libery be replaced 
 BS> by the 'lrzsz' zmodem/xmodem/ymodem utilities.
 BS> * Somekind of Serial driver (wes is working on right now afaik).
 WG>  
 WG>  - What's maxpipe?

I haven't used it, but both Binkley 2.60 (and Binkley XE, since it is
derived from 2.60) and Maximus (2.0 on?) allow for the use of maxpipe under
OS/2 (and later Win32 Max?).  If I understand things correctly, you could
think of Unixed named pipes as what was implemented under OS/2....  So,
this should be relatively simple to implement for pipes that are used.  I'm
not sure if a keyword will need to be added under Linux to turn off
creation of the named pipes when they are not used (or direct them to
/dev/null when not used).

 WG>  - MEX: Grr. :)



 WG>  - File transfers: Do they work right now? Also, using external sz/rz
 WG>    should just be a matter of tweaking the configuration files properly;
 WG>    I seem to recall a max command-line option to start without internal
 WG>    protocols.

I haven't tested file transfers yet because I'm still running max with the -k switch.

 WG>  - Serial: coming soon. I'm currently working on the comm plug in system,
 WG>    once that is working, and serial plug-in should be simple.

Interesting.....  We should look at what BinkleyTerm XE for Linux uses for
the serial port handling and use something similar....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01