Bob

 BJ> As Andrew Clarke has reminded me, the old Maximus
 BJ> source code is built to compile in both 16 bit and 32 
 BJ> bit environments.  This causes for some interesting 
 BJ> code maintenence issues relative to current operating 
 BJ> systems.

 BJ> Since I plan to take the code forward with support for long file names, 
 BJ> etc., would anyone object to removing the 16-bit (DOS 
 BJ> and OS/2) compiled versions from future development?

Probably not...

 BJ> The new future targets in this case would be Win32, 
 BJ> OS/2 (32-bit), Unix based (Linux, FreeBSD, maybe NeXT 
 BJ> Step / Open Step / Mac OS/X), and possibly a 32-bit 
 BJ> DOS extender (if someone is willing to help in this 
 BJ> area).

Particularly if the 32 bit DOS extender is involved.  If the 32 bit
extender is involved, it would be particularly interesting if the Rational
4G extender were to be used in that it's the same one which is used for the
Btrieve 6.15 code which has upward portability into all the Pervasive stuff
that sprang from it.  That all the way into LINUX now as well with SQL and
all that too.

On another thought.. but related to what will come ..

ARRL is going forward with a complete press for Ham Radio WI-FI using
802.11 whatever.  Hams are *NOT* limited to the power levels of the public
stuff,thus as it was noted tonight in the ARRL bulletin, the future for
experimentation may really be "Hinternet" at 2400 Mhz and a lot
of exeperimenation.

They forecast a rather large offering of everything from pix, to video
links, to massive audio channels and so on from the technical
experimentation from this group.  If MAX is to be moved into the future for
what it could become, then the first choice needs to be to line it up for
handling far more than just messaging and message bases and files as
well,no?

If compiler cross platform tools and techniques exist to do a really
demonstrable job on things that had potential interfaces from common source
code to all this .. that might really get interesting.  I guess the idea is
not to paint one's self into a corner which is convenient, yet limited in
future view!

Just a thought.

I for one would LOVE to see a simply defined and common source video code
operation come out of this which could be used for other programming as
well in cross platform development.  I need to learn as much as I can out
of this and would be studying how this is done, even if I'm not good enough
to actually be a part of the compilation and creation crew.  It'll be a
real chance for me to learn from you and the crew.

--> Sleep well; OS/2's still awake! ;)

Mike {at} 1:117/3001

--- Maximus/2 3.01