Subj : FileMgr To : Maurice Kinal From : Bob Jones Date : Sat Nov 01 2003 04:14 pm BJ> My main BBS system (BinkleyTerm 2.60 / Maximus/2 3.0x ) is running BJ> under OS/2 at this time. I'm interested in getting Max ported to BJ> Linux so that I can switch the main BBS (within two years?) to BJ> running under Linux. MK> Looks to be a solid plan. If so then I'd strongly MK> suggest concern should be put to gcc/glibc MK> compatibility and most definetly to the concept of MK> multiuser/networking as opposed to the more traditional MK> single user/sysop mentality of DOS that has been the MK> hallmark of all the BBS software I have seen to date. MK> I mean that although a administrator is still a viable MK> concept more emphasis is needed where multiusage is MK> concerned where it pertains to an OS such as Linux or MK> any other Unixie OS. First thing is to get a port of Maximus running. I have some ideas concerning what you are getting at per multi user -- DOS vs multi-tasking OS stance, but those ideas would probably be a major rewrite of code for the current maximus design..... And not going to happen short term. Now maybe a Max version 4 with a different style / concept of administration might be the trick... Concerning GCC, it has ports to OS/2 (EMX) and to Win32 platforms, so, depending on how the code is written, Unix / Linix / *BSD and OS/2 and Win32 platforms can be supported from the same code -- assuming some guidelines and design ideas are followed. BJ> So, ultimately, Linux... Short term (?) OS/2. MK> No problem. I will check. I am thinking gcc. That's MK> the only thing that makes sense to me given all the MK> legal aspects going on at the moment. If compiling under and for OS/2 and/or Win32 targets, Open Watcom is another free C compiler. A number of OS/2 utilities have been compiled with two support compilers under that environment. [Old, no longer supported compilers include IBM's C compiler (VAC) and older (commercial) Watcom compilers. Current OS/2 support compilers include ports of GCC (EMX) and Open Watcom, both of which are "free" software....] BJ> And, while I haven't looked, I assume this is BJ> something like MFM that BJ> we are talking about..... Looks like Bo has something running for BJ> .TIC file processing..... MK> Errrr ... this is news to me. I am not sure what is MK> required wrt anything Unixie here. As to what I've MK> seen in the way of *.TIC files from my uplink a simple MK> shell script can easily handle them. Maybe I am MK> missing something here? Ok.... I guess I need to explain my comment. I assume your file manager is like MFM (Maximus File Manager) under DOS and OS/2 (and probably Win32). It did not handle .TIC files. It did manage files in defined Maximus file areas. Unforutnately, I've hit the limits of reasonable management with that tool in my setup..... On the other hand, Bo has something he has started for handling .TIC files. While end node users could handle .TIC processing with simple scripts, it gets a bit more complicated when you want to run as a hub, handle CRC checks, dupe checks, etc. I am not expecting RAID functionallity in FileMgr. I am expecting equivalent functionallity (possibly different) to MFM in FileMgr. Take care...... Bob Jones, 1:343/41 --- Maximus/2 3.01 * Origin: Top Hat 2 BBS (1:343/41) .