🚀 go-pugleaf

In article <1993Jan6.213753.9390@mksol.dseg.ti.com> mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:
> >> 
> >> >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.
....
> >> 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
....
> 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.

If the OS/2 BBS software was multi-threaded, a thread may be able to spin off
(spawn?) another which could be the Door program.....and received the serial
port input. Multi-threaded BBS software could monitor any number of serial
ports and kick off quite a few doors with out any great problems. I have read
the OS/2 redbooks on this general subject and it seems that - conceptually -
this is consistent with what i read. 
 
OS/2 apps have the potential to blow the DOS equivalents away. We just have to
write the software. 
 
A group here in Wellington is being organised to write just such a BBS....:-)

Steve
-- 
Steve Withers - Wellington, New Zealand |      
Steve.Withers@bbs.actrix.gen.nz         |        Space for rent.
+64 4 478 4714                          |   - cheap rates, nice location. 
**** Happy user of OS/2 b2.1 ****       |