🚀 go-pugleaf

mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:

> In <1993Jan1.120522.28801@actrix.gen.nz> Steve.Withers@bbs.actrix.gen.nz writ
> 
> 
> >OS/2 v2.x is an excellent platform for what Kevin is trying to do. There is 
> >OS/2 version of Maximus that does the job very well.
> > 
> >You would need at least 6 megs with OS/2 v2.0.......though the upcoming V2.1
> >runs better in less memory. I have the beta for OS/2 2.1 running pretty well
> >on a 386DX/25 with 4 meg of RAM on a PC at work. 
> > 
> >There are several BBS's here in Wellington running Maximus on OS/2. The nice
> >part about is the vastly superior multi-tasking of OS/2 over Windows. This
> >shows especially when dealing with modems and comms programs. DOS comms run 
> >under OS/2 but native OS/2 programs are definitly superior to anything aroun
> >for smooth multi-tasking - like Maximus for OS/2. 
> 
> Note that this does, however, have the problem of not allowing the use
> of most 'doors' (which are written to run on DOS) or of a lot of the
> Opus-compatible utilities that Maximus on DOS should be able to run.
> 
I'm sure there are ways to do this.  As for the doors they should be able to
be run by shelling out a command.com /c doorprogram and OS/2 will just load
a temporary DOS session for that program under the OS/2 session.  I've done
some experimenting with this with normal programs and they worked just fine,
but not in a BBS environment.  Besides, as long as the OS/2 and DOS versions
use the same file formats, then the DOS sysop utils that do file maintenance
will still work running in a DOS session (unless the sysop uses longer file
names than DOS allows).

Greg

.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.
.   TCS Consulting Services   P.O. Box 600008   St. Paul, MN  55106-0008    .
.   ..!srcsip!tcscs!zeta                 ..!src.honeywell.com!tcscs!zeta    .
.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.