Article View: comp.bbs.misc
Article #758Re: Windows 3.1 and BBS software
From: fred j mccall 575-3539
Date: Wed, 06 Jan 1993 21:37
Date: Wed, 06 Jan 1993 21:37
45 lines
2951 bytes
2951 bytes
In <wiuwwB3w165w@tcscs.UUCP> tcscs!zeta@src.honeywell.com (Gregory Youngblood) writes: >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). I believe that the problem is that there is no way to give the serial port as input to the shelled DOS session -- because the OS/2 application window running the BBS has it. Multitasking OS's won't let you hand hardware assets around like that. I've been told that there is a way around this using OS2YOU, but I've never used that so couldn't state this absolutely. -- "Insisting on perfect safety is for people who don't have the balls to live in the real world." -- Mary Shafer, NASA Ames Dryden ------------------------------------------------------------------------------ Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
Technical Details
Message-ID:
<1993Jan6.213753.9390@mksol.dseg.ti.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccallReferences:
<1993Jan4.165729.11541@mksol.dseg.ti.com> <wiuwwB3w165w@tcscs.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccall From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539) Newsgroups: comp.bbs.misc Subject: Re: Windows 3.1 and BBS software Message-ID: <1993Jan6.213753.9390@mksol.dseg.ti.com> Date: 6 Jan 93 21:37:53 GMT References: <1993Jan4.165729.11541@mksol.dseg.ti.com> <wiuwwB3w165w@tcscs.UUCP> Organization: Texas Instruments Inc Lines: 45