Subj : Re: Doors/Utility Suggestions?
To   : alt.bbs.doors
From : BlueWolf <enter@namehere.com>
Date : Fri Aug 22 2003 04:30 am

>>> I think there's an easier way to arrange this that doesn't require a
>>> larger program like GameSrv.  I think all that's needed is:
>>> 
>>> 1. a 16-bit door (routes user's I/O to a shared file)
>>> 2. a 32-bit program (routes I/O from the shared file to a localhost
>>> socket) 
> 
>>I saw you postted a link to a door.sys <-> door32.sys convertter. ;)
> 
> Err, huh?  No, I didn't post that link.  I posted a
> reply to it saying that I didn't think the converter
> works :(


Sorry, I saw that after I hit the send button.
My mistake.


>>Without the uses of sockets, because I could just pass the handle of
>>the applications along and have it run locally on the computer.  Wouldn't
>>have to go through sockets.  

> I'm not sure I follow?  The setup you originally described
> said your setup is 16bit door -> custom 32bit telnet program -> GameSrv.  
> If you're writing a 32bit telnet program, you'd be using sockets... 
>
> The setup I described simplifies it a bit, 
> basically you'd change that 32bit telnet program
> into a client+server that connects to itself on
> localhost, and then launches the 32bit door...
> this would eliminate the need for GameSrv, and
> also wouldn't need to run constantly (hence much
> more efficient)...


The reason I said to use GameSrv is because it can
run door32.sys door games, but to access it you
have to go threw a telnet connection.  If I do a
dos32 console version of GameSrv (which is beyond
my knowlegde on how to program something like that)
I would have it where you can just load it without
going through a telnet session to run the games.
Like when your in the WFC screen of a bbs package
and locally login-in and run the doors without going
through a modem.  I haven't testted my theory yet though.

I understand what you mean though, because if I
don't do it threw a telnet session the door will
detect that the socket (telnet) is closed and
will close the port.  So, you would have to
run a local(127.0.0.1, localhost) loop so the
door doesn't think the user hung-up and close.

Also, in my orginal setup.  I have it going
threw the localhost to connect to gamesrv
on the same computer.  So, some of the over
head of going outside the local net is there.
but I have it setup so you can put in a IP.
So, say someone has gamesrv setup then you
can put that IP and it connects to there setup
that isn't on your computer and have your users
play on there system, but while on your bbs.

It really does suck though, but it it a workable
work around for the door32.sys problem.


bluewolf.

.