Subj : Problem running "The Pit" version 4 and above
To   : alt.bbs.doors
From : xhumeka
Date : Thu Sep 08 2005 01:27 pm

Hi Everyone,

I am having a very frustrating time getting version 4 and above of "The
Pit" to work on my Synchronet (Win32) bbs.

Version 3.53 works fine - both single node and multinode.  The only
problem with versions earlier than 4 is that multinode battles aren't
supported.

Now comes the problem - version 4.15 and above has the UART comm
problem.  Everything works PERFECTLY for single node use, but as soon
as another node tries to run the door, I get the well known
fossil/comm/uart error message.

So fine, I'll try versions of 4 that DON'T have this glitch - versions
4.03 and 4.05 both apparently work fine with fossil drivers.  Here
comes my biggest problem - both versions (4.03 and 4.05) FREEZE when
they are first launched.  Here's what happens:

-User launches door
-On server, the dosxtrn.exe window appears on my taskbar (this is
normal, all doors will execute this, but here's where it stalls).
-NOTHING will happen until I click on the dosxtrn.exe window on my
taskbar (as sysop from server).  Once I click this window, it instantly
changes to full-screen, and the door then continues to load properly.
Even if I do nothing but click on the window and allow it to go full
screen, then hit alt-enter to switch it back to a window, it still
allows the door to load.

No matter how long I wait, nothing will happen until I click on the
dosxtrn.exe window.  It almost seems like the window needs to be active
in order for the door to load - but this is unlike other versions of
the pit so it doesn't make sense to me.

Other doors work fine, even version 3.53 and 4.15 and 4.17 of the pit -
the dosxtrn window will appear on my taskbar, but I don't need to click
it to get it to work properly.

Only versions 4.03 and 4.05 seem to have this problem, and I have tried
it on different computers with different operating systems (xp and
2000) with the exact same problem.

I have seen other synchronet systems (same version as mine) run the pit
version 4.05, so there must be some way around this... anyone have any
suggestsion?  I'd REALLY like to get this running!

.