Subj : Re: DoorMUD To : Richard Cini From : IB Joe Date : Thu Oct 01 2020 07:21 am On 30 Sep 2020, Richard Cini said the following... RC> > g0> If you have doormud installed in c:\doormud then you would do: RC> > g0> RC> > g0> Data: c:\doormud\dmud32d -n %N -d %Pdoor32.sys RC> > g0> RC> external command from what was in the dmud manual to the above, and I RC> get further along, but now I get an error "Unable to read door RC> information file". My setup is going to be used as a RC> dial-up demo for a computer museum, so it's older -- 1.07.3 running on RC> Windows 98SE with a Digi AccelPort board. The board itself works fine, RC> and I can get Pimpwars running, but dmud is a challenge. RC> RC> Thanks! I have quoted above some of the information needed. I quoted what g00r00 told me to used to get the door running. I don't know how you're doing it but the above can be broken down in to 2 pieces to better understand how to get the door to work.... 1st, c:\doormud\dmud32d.exe , points where the exe file to get the door working... 2nd, -n %N -d %Pdoor32.sys... is the info needed to tell the door where the door info files are... -n %N tells the program what node you are on.... current mystic BBSes use that, prior version and or other BBSes my use something else. The next is -d %Pdoor32.sys .... this is the argument that points to the directory where your door files are... current versions of Mystic would take that %P and translate that as \mystic\temp1 or \mystic\temp2 or \mystic\temp3... and so on... depending on the node you are on. The ending to that statement door32.sys is the door info file. Lets just say that your software doesn't use the %P argument you can execute the door like this... c:\doormud\dmud32d -n %N -d \mystic\temp%N\door32.sys The error you're getting sounds like the door isn't able to find the door info files .... The -d \mystic\temp%N\door32.sys part... IB Joe AKA Joe Schweier SysOp of Joe's BBS -=JoesBBS.com=- --- Mystic BBS v1.12 A46 2020/08/26 (Windows/64) * Origin: Joe's BBS, JoesBBS.com, Telnet:23 SSH:22 HTTPS:80 (1:342/201) .