TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Mike Tripp
from: Bob Jones
date: 2003-01-20 16:27:58
subject: Drop 16-bit Max version?

BJ> Since I plan to take the code forward with support for long file
 BJ> names, etc., would anyone object to removing the 
 BJ> 16-bit (DOS and OS/2)
 BJ> compiled versions from future development?  The new future targets in
 BJ> this case would be Win32, OS/2 (32-bit), Unix based (Linux, FreeBSD,
 BJ> maybe NeXT Step / Open Step / Mac OS/X), and possibly a 32-bit DOS
 BJ> extender (if someone is willing to help in this area).

 MT> Excuse me if this a stupid question, as I'm not a C 
 MT> programmer... What is the codependency between 32-bit 
 MT> targets and LFN support?

A the level of 'c' programming, nothing directly.  Indirectly the operating
systems (i.e. MS-DOS / PC-DOS) that worked with the 16-bit Maximus also
have the 8.3 file name issues.....  LFN support will (basically) be
provided by the OS....  Max will just be bumped up to handle longer file
names where original code made assumtions about the 8.3 limit.....  This
means that file name case may come very important on Max systems running
with a case sensitive operating system file system (i.e. Unix based
systems)....  I can almost guarentee you that one of the "bug"
reports I'll get on the initial development effort will be from file name
case insensitivity of the current Maximus environment causing a problem in
the Unix based case-sensitive file systems....  If Max still happens to
compile for the old DOS environment, then LFN support would be available in
Max *if* the OS provided for such... (like through netware or a network
file system mount, etc.)....  Typically that isn't provided....

...
 MT> I have stuck to 2.x to retain "Who's on" and internode 
 MT> chat capabilities from my OS2 box, while local or 
 MT> telnetted in.  I tried, but could never get the named 
 MT> pipes scheme supported between the DOS and Netware 
 MT> combo.

So, you would be continue to be left out due to the code base that is being
moved forward is the 3.x code and not the 2.x code....

...
 MT> So feel free to assign my input the near-zero weight it 
 MT> deserves based on your primary objectives.  I'm happy 
 MT> to see =something= moving forward again even if it ends 
 MT> up leaving me even further behind in the dust.  I'll 
 MT> applaud until you disappear over the horizon and I 
 MT> can't see you any more. ;)

Thanks for your input.  Good luck keeping the antiques running....  

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)
SEEN-BY: 633/267 270
@PATH: 343/41 10/345 379/1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.