Subj : Re: Door problems
To   : Cisop
From : Digital Man
Date : Sat Sep 24 2005 03:57 pm

  Re: Re: Door problems
  By: Cisop to Digital Man on Sat Sep 24 2005 12:40 am

 >  >   Re: Re: Door problems
 >  >   By: Digital Man to Cisop on Fri Sep 23 2005 02:35 pm
 >  >
 >  >  >  >  > Do the SBJ and SBL doors work? Does SEXYZ (see docs/sexyz.txt fo
 >  > deta
 >  >  >  >  > upgrading)? If none of these programs work, then the cause is mo
 >  >  >  > definitely
 >  >  >  >  > another piece of (security) software on your system.
 >  >
 >  >  >  > I followed up on SBJ and it does work correctly. On my system SBL, 
 >  > an
 >  >  >  > SEXYZ all work fine.
 >  >  >
 >  >  > That's good news.
 >  >  >
 >  >  >  > It is only Doormud and Trivia that do not. I suspect th
 >  >  >  > were both written with the same doorkit.
 >  >  >
 >  >  > They were written by the same author, so definitely.
 >  >  >
 >  >  >  > I noticed a thread in the forums on the doormud site about the same
 >  > probl
 >  >  >  > One of your users was compliling his own copy of SBBS from CVS. At 
 >  > en
 >  >  >  > June, 2005 his doormud stopped working also. The author of doormud 
 >  > no
 >  >  >  > able to find the problem. The sysop had to change over to the door3
 >  > vers
 >  >  >  > They were not able to get the xtrn.dat version to work again after 
 >  > of
 >  >  >  > CVS updates.
 >  >  >
 >  >  > Weird. What OS are you using? I just did a fresh install of v3.13a on
 >  > Window
 >  >  > XP and DoorMUD works fine. Here's the configuration from SCFG:
 >  >  >
 >  >  > Internal Code              DOORMUD
 >  >  > Start-up Directory         ../xtrn/doormud
 >  >  > Command Line               dmud32
 >  >  > Clean-up Command Line
 >  >  > Execution Cost             None
 >  >  > Access Requirements
 >  >  > Execution Requirements     NOT UNIX
 >  >  > Multiple Concurrent Users  Yes
 >  >  > Intercept Standard I/O     No
 >  >  > Native (32-bit) Executable Yes
 >  >  > Use Shell to Execute       No
 >  >  > Modify User Data           No
 >  >  > Execute on Event           No
 >  >  > Pause After Execution      No
 >  >  > BBS Drop File Type         Synchronet      XTRN.DAT
 >  >  > Place Drop File In         Node Directory
 >  >  >
 >  >  > I'll do a fresh install of v3.12a and then upgrade to v3.13a on the sa
 >  > box
 >  >  > and see if there's maybe a problem with upgrading only. <shrug>
 >  >
 >  > I just performed a fresh install of v3.12a, and then upgraded to v3.13a o
 >  > Windows XP box and DoorMUD continues to work. I was pretty sure I did tho
 >  > before the release and verified all the pre-installed continued to work, 
 >  > they are, so I'm not sure what the problem is with your particular
 >  > install/upgrade.
 >  >
 >  I am running windows 2000. I had users in doormud on 09/14/05 at 4:29 P.M. 
 > installed the upgrade on 09/14/05 at 8:43 P.M. No one has been able to get
 > into the game since. The doormud logs still have a 09/14/05 at 4:29 P.M. tim
 > stamp.

And how does your configuration of the door (in SCFG) compare with what I
posted?

When upgrading Synchronet, it doesn't touch any files in the xtrn/doormud
directory, so I don't really have any explanations at this point.

Have you tried re-installing doormud?

                                                  digital man

Snapple "Real Fact" #182:
A rainbow can only be seen in the morning or late afternoon.

.