JB>  NoDsp Mex             m\dorinfo                Normal "I"
JB>        Xtern_Dos       \bbs\bbs_lod             Normal "I
JB>Land of Devastation"
 GC> I have a terrible time with doors. My last effort kept telling me it
yeah. been there, done that 4 years ago :)
 GC> couldn't find DORINFO. The path to c:\max\misc was set in the program's
 GC> .cfg. My menus.ctl entry looked like this:
hey Duder! i'm an old-fart-Maximus sysop :) and i'm gonna tellz ya that once 
the dropfile creating MEC's in your c:\max\misc (eg. dorinfo.mec) is 
linked/run, it will plonk the created dropfile (ie. dorinfo1.def) in your 
C:\MAX\MISC directory :) now you can customise anything in which these MEC's 
create (such as destination) on your Hdd by editing them! i personally GET 
the damn dorinfo.mec to create the dropfile in my C:\MAX\ directory for 
convenience. 
ie. in your *.MECs (eg. misc\dorinfo.mec)
---------------------------------------------------
        [delete]c:\max\dorinfo1.def
        [open]c:\max\dorinfo1.def
---------------------------------------------
now, your "CAN'T FIND DORINFO" problem probably has a simple cause.. and its 
probably because the damn door you want to run can't look for dropfiles in 
other directories reliably besides its own. OR your door program is 
configured to use some RemoteAccess dropfile, OR its looking for 
node-specific dropfiles such as dorinfo1.def or dorinfo2.def.
for security reasons, i have my batch files as 'generally' as follows:
---------------------------------------------------
(1)     @echo off
(2)     copy c:\max\door*.* c:\aichat
(3)     c:
(4)     cd\aichat
(5)     aichat /a /d
---------------------------------------------
NB: i'm using Door.Sys (line 2; copy c:\max\door*.*)
line 1 - your normal "@echo off" command :) as i don't want crap on my local 
screen output
line 2 - i always copy the required type of dropfile into the directory of 
the program
line 3,4 - i always try and get into the door's directory before running it
line 5 - run the f'ker with any commandlines etc.
i don't know why most people bother with "MEXing c:\max\m\dorinfo" or 
"linking \misc\dorinfo" as Maximus _should_ (not DOES or Would..) essentially 
create atleast the DORINFO dropfile on the fly once a "Xtern_" 
statement is encountered.. BECAUSE (read on)...
handy tip: in you MAX.CTL go to your "Outside Information" section and 
uncomment/enable (take away any "%" signs) for "Uses Leaving Misc\Leaving". 
now, go edit your Misc\Leaving.Mec.
my Misc\Leaving.Mec is:
---------------------------------------------------
        [cyan]please wait..
        [mex]c:\max\m\dorinfo
        [link]c:\max\misc\doorsys
---------------------------------------------
you can put in all the other niffty dropfile MECs supported by Maximus but i 
doubt you'd need'em because most programs'll use Dorinfo or Door.sys. i 
personally run EVERYTHING on Door.Sys (because i don't wanna put-up with 
gorilla vomit dorinfo1, dorinfo2, dorinfo10, dorinfo8.def etc) unless the 
stupid door won't accept it and needs some WWIV crap like chain.txt or 
Wildcat gibberish like Callinfo.bbs or someother... :) btw; i'd recommend 
using the MEXed version of Dorinfo (ie. \m\dorinfo) than the dodgy 
\misc\dorinfo because the MEXed version will include'n'check and produce the 
correct dorinfoX.def.
 GC> Display File            misc\DORINFO               Normal "XXXX"
 GC> NoDsp Xtern_DOS         c:\max\XXXX.bat           Limited "XXXX"
 GC> Do you see anything majorly wrong here? (That's from memory. Maybe there
 GC> should be an unscore between Display and File).
erm yes :) that underscore is a mandatory substitute for any spaces (ascii 
000/nul) needed in your menus.ctl. either way, Maximus should've reported the 
error/missing underscore during silt.
hope this attempt at an accurate/comprehensive treatise for the setup of 
doors for Maximus helps ya or somebody :)
--- Squish/386 v1.11
(3:713/622)
---------------