Here is a Listing of Questions and answers to ROMDOOR Problems
Hopefully you'll be able to find answers to your questions here
Rather than incurring cost for a LD call
Common Questions.
Q: I want to edit my ROMDOOR Prompts how can I ?
A: Load either WC 3.9X MKWCTEXT.exe or Wc4.X WCPROMPT.EXE
and edit it with That..
NOTE your ROMDOOR is loding is Hard Coded.
Q: Whenever Romdoor EXITS, I get FileLocks and unable to open
NODEINFO.DAT, WHY ?? I'm Running NOVELL NETWARE Lite.
A: ENSURE you have ROMDOOR configured as a multiuser Door.
If your running more than 1 node, this needs to be set to YES
ROMDOOR Reads NODEINFO.DAT. Reads/Writes to USEREC.BIN,
SYSINFO.DAT, DOOR.SYS, and directly to Wildcat/PCBOARD's MEssage
Bases. Also When ROMDOOR first Loads, it checks to see what
Conference # you have set to write to in MAKEROM, it ensures
the conference is their, and can be written to ((not corrupted)).
Q: Does ROMDOOR Support RIP ?
A: ROMDOOR will display RIP menue's, However it doesn't recoginize
RIP replies from end-users ((mouse clicks) Not YET Atleast.
Q: What are some of the command Line options for ROMDOOR ??
A: ROMDOOR DIGI FOR DIGI Brds Only
ROMDOOR FOSSIL For Fossil Drivers Only
ROMDOOR NOLOG Do Not Log to Activity Logs
ROMDOOR LOCAL Will Not count D/L's, or List Activity
Automatcially Sets you to Node #1
Q: Robin, I've followed the instructions in ROMDOOR and I'm able to
Get it to work locally fine. but when users go into ROMDOOR
I get an error 8906 why ??
A: ROMDOOR is not finding you Comport (8906 is a ASYNC comm error)
this is usually associated with the SET environments in your CAT.BAT
or other BBS.BAT file
you need to have these:
For WILDCAT
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
For OTHER BBB's
SET NODEID=4
SET PORTID=3F8
SET IRQID=6
SET NODEPATH=C:\MAJOR\NODE4 (IMPORTANT)
SET NODEPATH=C:\PCB\NODE%PCBDIR% (IMPORTANT) we support
Wild %
Q: ROMDOOR won't Allow more than 1 person in the door at the same
Time. (or gives me a ERROR Something Something) Why ?
A: You either have your BBS set up for non-multi player door
or Your not loading SHARE.EXE.
*** Note Even if your not running LANTASTIC, NOVELL, or are a
*** Single line We recommend you load Share Anyways.
your Changing to ROMDOOR instead of calling it from your DROP
Dir. i.e.
ECHO OFF
D:\ROMDOOR\ROMDOOR.EXE (Notice no Change Dir.)
*** Or your not using your SET COMMAND i.e.
SET WCMDM=ZOOM1
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
Q: In my WC 4.XX DIGI Version, When a user exits ROMDOOR and tries
to D/L a file they get crappie transfer rates..
Also the next caller gets a crappie transfer rate..
Diags show CTS / RTS turned Off after ROMDOOR Loads. WHY ???
A: Not sure Why this has to Do with ASYNC pro when it closes the
Comport. in Wildcat Versions PRIOR to V 3.91 this was not a
Problem because Wildcat RESET the comports after a Door
/ and when a user logged off. AFTER V3.91 they no longer do this.
Not sure why. the other BBS S/W do it...
We're working on this now.. and should be fixed this month
(Nov.)... this problem occurs with the 3 other MAJOR CD-ROM
doors also..
**** NOTE this is For ONLY WILDCAT V3.91-4.01
and ROMDOOR V4.00-4.02
Q: When a User Types [V]iew nothing happens WHY ???
A: Wildcat has moved all your Batch files. to \wildcat\batch
either add this dir. into your path statement or copy your
ViewComp.bat to your \wildcat dir..
Q: When I ran ROMCHK I get and ERROR BAD KEY, or ROMCHK won't
Run with an Unregistered ROMDOOR. ROMDOOR is registered
Why the ERROR ??
A: 2 possible reasons.
1: you've Overwritten your Registered Key when you Upgraded to a
New release.
2: Your Running ROMDOOR V4.00 or 4.01 ROMCHK.
V4.00 had a problem recognizing the new Keys..
D/L the latest Version of ROMDOOR...
or latest ROMDOOR Upgrade...
Q: I'm getting an ERROR 100 when I try to load MAKEROM
This is a new install Why the error ??
A: This is caused from MAKEROM. finding either a old copy of
MAKEWILD.DAT in your path, or finding it in \WC30
and expecting to see a WC 4.0 version.
To fix this You need to do 3 things
1: Rename your \WC30 Directory
2: Clear your path statement out
Type PATH=C:\<cr> (from the DOS prompt)
type PATH<cr> to verify it's clear
This will remove any reference to \WC30
(ROMDOOR looks for MAKEWILD.DAT in \WC30 if not found, it looks
in your path statement for a call to \wc30 if their (or finds an
old MAKEWILD.DAT in your path you WILL get a RUNTIME error 100
3: DELETE PREVON.DAT (if it exists)
Once this is done type MAKEROM (from within ROMDOOR) you WILL get an
Error "MAKEWILD.DAT Not found. IGNORE it. go to general parameters
edit the correct Path to your NEW MAKEWILD.DAT. F10 to save
Walla Your Done
Q: I seem to be having a problem with the new ROMDOOR program.
The older 3.11 was working fine , but this newer version is not
writing to my activity log on my Wildcat 3.9 software. I am given
the option to pick from Wildcat only, no log , ROMDOOR only or
Wildcat and ROMDOOR.
A: D/L ROMD402.zip or the Newest Released ROMDOOR.
This was a minor bug in the first release of ROMDOOR
It's fixed Now
Q: ROMDOOR. I currently have twelve other CDs installed with ROMDOOR
and I haven't had one ounce of trouble. Here's where the problem
lies with this one particular CD. I'm needing 819 file areas and
I can't get ROMDOOR "Set max. file areas for CD" to go above 256.
Any Ideas? Thanks in advance...
A: If we were to increase the file areas above 256 to 1000 the
amount of diskspace per CD' database would increase by 500K
(per database) and needed memory when loading ROMDOOR would
increase by 18K (18K doesn't sound like Much but when your trying
to tweak out the 95K needed for ROMDOOR to work smoothly 18K is
allot.). To work around this ROMDOOR allows you to have multiple
dir.'s per area gang up the Dirs. into specific areas.
Q: Hi Robin, I tried my new key for romd40x and where its says
registered to: there is a blank space.
A: ROMDOOR doesn't display the registered Too in local mode
(it also doesn't record any D/L's to Wildcat in local mode)
Q: Also a couple of questions: I tried to set up the database for
pier 5 and it doesn't display properly. Do I need to set up rom3x
first and then upgrade to 40x or do I need to upgrade the database
I downloaded and if so what is the command line.
A: No you Don't have to run a special upgrade line. Premade does
that. When you run PREMADE (to import in PREMADE Database)
PREMADE will show you two screens listing the databases. Pay
close attention to which one displays correctly. This is where
your able to import in Premades from ROMDOOR V2.XX and 3-4.XX
Q: Last I want to set up ROMDOOR on a different computer to make
databases. What are the necessary wc! files needed to run with
bare minimum. I don't want to set up another complete wc! to do
this.
A: To run it just for Database Imports. NO WC files are needed
just configure it for "Other Door.sys BBS" and run it in the
Local Mode "ROMDOOR LOCAL"
Q: I'm running "OTHER DOOR.SYS" ROMDOOR works fine
Locally but won't except callers on-line WHY NOT ??
A: quick Checks.. Monitor when ROMDOOR loads what it says
i.e. SECURITY LEVEL DOOR.SYS not found
for Security level you have Door.sys
Depending on your BBS type this will either be a Number
or a name. Look in your BBS to see what the security
levels in a DOOR.SYS is ((you can usually look in the
Door.sys drop file and get this info also ))
Another possibility is you don't have the SET commands in your
BBS BAT loader. (check further for example of SET commands.)
*** NOTE for local login you need a security level of 1000 or
SYSOP
Q: I have XXXXXXX Media '93 and XXXXXX Media '94 and
both disks have the name "XXXXXXX", so the result is that
ROMDOOR reads '94 and thinks '93 is in too...
there is even an ID file on the '94 disk but even with entering
that into ROMDOOR it still says '93 is on too.
A: ROMDOOR reads Vol. label's FIRST, then Unique File Names
ROMDOOR is finding vol. label "XXXXXXX" multiple times and assumes
you have multiple copies of this disk, To fix this,
remove the VOL. labels from BOTH Disks, and put in
"UNIQUE FILES TO LOOK FOR" preferable in different sub-dirs.
Q: I just upgraded from a single node, ROMDOOR will not allow
More than 1 user in it at a time WHY ??
A: You either have your BBS set up for non-multi player door
or Your not loading SHARE.EXE.
*** Note Even if your not running LANTASTIC, NOVELL, or are a
*** Single line We recommend you load Share Anyways.
Q: Can I Run DIGI and Non-Digi version of ROMDOOR
A: YES, Just ensure you load the regular ROMDOOR.exe for
your ASYNC (Non-Digi) nodes, and ROMDIM.exe for your
Digi Nodes, (ROMDIM.EXE can be renamed)
Q: I Run a DIGI brd, and ROMDOOR only recognizes 1-2 ports Why ?
A: 1 of 2 things.
1: Your not running the DIGI version of ROMDOOR (ROMDIM.exe)
2: You haven't used your SET Environments in your BBS batch file
i.e.
SET WCMDM=ZOOM1
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
*** Note, NO trailing "\"'s and ALL CAPS
*** For "OTHER DOOR.SYS" you don't need to put in WC i.e.
SET NODEID=4
SET IRQID=6
SET NODEPATH=C:\PCB\NODE1
Q: ROMDOOR isn't recognizing my other PORTS / NODES
A: You haven't used your SET Environments in your BBS batch file
i.e.
SET WCMDM=ZOOM1
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
*** Note, NO trailing "\"'s and ALL CAPS
*** For "OTHER DOOR.SYS" you don't need to put in WC i.e.
SET NODEID=4
SET IRQID=6
SET NODEPATH=C:\PCB\NODE1
Q: I have several CD-ROMS but when I'm in ROMDOOR I don't
See them, or only some of them.
A: First thing Ensure you have a registered Version of ROMDOOR
Or a good 30 day key,(Unregistered ROMDOOR only supports 1 CD)
Second: Ensure YOU have given yourself access to these Disks
Via MAKEROM, "EDIT Security Level"
Third, Run GETON.exe, GETON will return the CD's it finds
On-line. IF GETON doesn't recognize all your On-line CD's
Or doesn't show the correct CD's :
Make sure you have entered a "CORRECT" Volume label
or a "UNIQUE File to find.
**** Also Some CD's have the same Volume Labels
in this case go blank the VOL. Label info
and put in a unique File name.
Q: I receive B-Tree errors whenever a User does a search,
or listing on a particular CD.
A: Most likely that particular CD's Database has become corrupt
Run "FIXROM ??" (?? is the CD-ROM number to run on)
FIXROM will rebuild that database.
Q: Dang, you Don't have a Premade for my disk, How do I make a
Database
A: First, Ensure the Disk you have is BBS Compatible
I.E. Has a FILES.BBS in each Area, or at least A Dir. with
a Unique text file for each area.
Second. Go into MAKEROM, Enter "EDIT CD-ROM INFO"
Highlight on an empty slot Depress Enter.
Type in The Disks Name
The Volume Label (or a unique File name)
F-10 to save
Then enter EDIT CD-ROM Areas
(MAKEROM will ask you for the # of areas)
Go to area #1, enter in a Area Name
choice Group (if you have that set)
Enter in the Path(s) to that area
Begin with a "\" F-10 to save
Edit the remaining area.
Then type ALT-Q
For Quick Import.
Enter in the Path to that CD
File to look for (usually FILES.BBS)
Then the text defined file to use
Walla Done,
Don't forget to hit enter on "MAKE PREMADE Database"
to share with your fellow sysops
* Making / Installing a new database now only takes 15-30 mins *
Q: I'm Unable to do a Zipped File Listing
PKZIP says NOTHING to DO
A: In MAKEWILD under BBS ID make sure it's a DOS NAME No Spaces
I.E. A.S.C. On-line BBS ID is "ASC", ZIP files are D\L as
ASC.ZIP
Q: I'm Unable to get ROMDOOR to POST MESSAGE, or ALLOW FILE REQUEST
A: Make sure Allow FILE Request is set to YES in MAKEROM, And Users
Have access to that disk.
Q: I have these set to yes, and they have access, but it still
Won't write a MESSAGE
A: Next Time a user is in ROMDOOR hit the F-9 Key
You Need "AT LEAST" 95K of free Memory for ALL ROMDOOR's
Features to WORK.. (Also if this is LESS than 75K ROMDOOR
will have trouble Freeing up RAM on Exit)
Q: My System will Sometimes return a DOS error, or the server will
Randomly LOCKUP after ROMDOORS' been heavily used for hours.
A: In your Autoexec.BAT where MSCDEX.EXE is, ENSURE you have your
/M: set to MIN 32 (PER LASER, and 38 Per pioneer 6 pack)
We have it set to 512 and use the /E to load in upper memory
I.E. MSCDEX.EXE /D:MSCD001 /L:H /V /M:512 /E
/L: DRIVE LETTER
/V: VERBOSE INFO
/M: SECTOR BUFFERS
/E: USE UPPER MEMORY
Here is a Listing of Questions and answers to ROMDOOR Problems
Hopefully you'll be able to find answers to your questions here
Rather than incurring cost for a LD call
Common Questions.
Q: Robin, I have a problem. When I first put the registered key
in Romdoor the color menu worked. Now it only comes up with
the old menu. Any idea.. Thanks
A: Several things..
Are you sure you put the correct registration key into ROMDOOR's dir..
(Reason expired Key will not show extra menu, and only cd-rom #1
will work)..
other option.
you nolonger have ROMDOOR pointing to ROMDOOR.BBS (or SCR, or ASC
whatever), or it's corrupted...
if ROMDOOR sees a corrupted Display file it defaults..
Q: I seem to be having a problem with the new Romdoor program.
The older 3.11 was working fine , but this newer version is not
writing to my ativity log on my Wildcat 3.9 software. I am given
the option to pick from Wildcat only, no log , Romdoor only or
Wildcat and Romdoor.
A: D/L ROMD402.zip or the Newest Released ROMDOOR.
This was a minor bug in the first release of ROMDOOR
It's fixed Now
Q: RomDoor. I currently have twelve other CDs installed with RomDoor
and I haven't had one ounce of trouble. Here's where the problem
lies with this one particular CD. I'm needing 819 file areas and
I can't get RomDoor's "Set max file areas for CD" to go above 256.
Any Ideas? Thanks in advance...
A: If we were to increase the file areas above 256 to 1000 the
amount of diskspace per cd' database would increase by 500K
(per database) and needed memory when loading ROMDOOR would
increase by 18K (18K doesn't sound like Much but when your trying
to tweak out the 95K needed for ROMDOOR to work smoothly 18K is
alot.). To work around this ROMDOOR allows you to have multiple
dir's per area gang up the Dirs into specific areas.
Q: Hi Robin, I tried my new key for romd40x and where its says
registered to: there is a blank space.
A: ROMDOOR doesn't display the registered Too in local mode
(it also doesn't record any D/L's to Wildcat in local mode)
Q: Also a couple of questions: I tried to set up the database for
pier 5 and it doesn't display properly. Do I need to set up rom3x
first and then upgrade to 40x or do I need to upgrade the database
i downloaded and if so what is the command line.
A: No you Don't have to run a special upgrade line. Premade does
that. When you run PREMADE (to import in PREMADE Database)
PREMADE will show you two screens listing the databases. Pay
close atention to which one displays correctly. This is where
your able to import in Premades from ROMDOOR V2.XX and 3-4.XX
Q: Last I want to set up romdoor on a different computer to make
databases. What are the necessary wc! files needed to run with
bare minimum. I don't want to set up another complete wc! to do
this.
A: To run it just for Database Imports. NO WC files are needed
just configure it for "Other Door.sys BBS" and run it in the
Local Mode "ROMDOOR LOCAL"
Q: I'm running "OTHER DOOR.SYS" ROMDOOR works fine
Locally but won't except callers online WHY NOT ??
A: quick Checks.. Monitor when ROMDOOR loads what it says
i.e. SECURITY LEVEL DOOR.SYS not found
for Security level you have Door.sys
Depending on your BBS type this will either be a Number
or a name. Look in your BBS to see what the security
levels in a DOOR.SYS is ((you can usually look in the
Door.SYS drop file and get this info also ))
Another possiblity is you don't have the SET commands in your
BBS BAT loader. (check further for example of SET commands.)
*** NOTE for local login you need a security level of 1000 or
SYSOP
Q: I have XXXXXXX Media '93 and XXXXXX Media '94 and
both disks have the name "XXXXXXX", so the result is that
ROMDOOR reads '94 and thinks '93 is in too...
there is even an ID file on the '94 disk but even with entering
that into Romdoor it still says '93 is on too.
A: ROMDOOR reads VOl label's FIRST, then Unique File Names
ROMDOOR is finding vol label "XXXXXXX" multiple times and assumes
you have multiple copies of this disk, To fix this,
remove the VOL labels from BOTH Disks, and put in
"UNIQUE FILES TO LOOK FOR" preferable in differnt sub-dirs.
Q: I just upgraded from a single node, ROMDOOR will not allow
More than 1 user in it at a time WHY ??
A: You either have your BBS set up for non-multi player door
or Your not loading SHARE.EXE.
*** Note Evenif your not running LANTASTIC, NOVELL, or are a
*** Single line We recommend you load Share Anyways.
Q: Can I Run DIGI and Non-Digi version of ROMDOOR
A: YES, Just ensure you load the regular ROMDOOR.exe for
your ASYNC (Non-Digi) nodes, and ROMDIM.exe for your
Digi Nodes, (ROMDIM.EXE can be renamed)
Q: I Run a DIGI brd, and ROMDOOR only recognizes 1-2 ports Why ?
A: 1 of 2 things.
1: Your not running the digi version of ROMDOOR (ROMDIM.exe)
2: You haven't used your SET Enviroments in your BBS batch file
i.e.
SET WCMDM=ZOOM1
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
*** Note, NO trailing "\"'s and ALL CAPS
*** For "OTHER DOOR.SYS" you don't need to put in WC i.e.
SET NODEID=4
SET IRQID=6
SET NODEPATH=C:\PCB\NODE1
Q: ROMDOOR isn't recongizing my other PORTS / NODES
A: You haven't used your SET Enviroments in your BBS batch file
i.e.
SET WCMDM=ZOOM1
SET WCNODEID=4
SET WCPORTID=3F8
SET WCIRQID=6
SET WCNODEPATH=C:\WILDCAT\WCWORK\NODE4 (IMPORTANT)
*** Note, NO trailing "\"'s and ALL CAPS
*** For "OTHER DOOR.SYS" you don't need to put in WC i.e.
SET NODEID=4
SET IRQID=6
SET NODEPATH=C:\PCB\NODE1
Q: I have several CD-ROMS but when I'm in ROMDOOR I don't
See them, or only some of them.
A: First thing Ensure you have a registered Version of ROMDOOR
Or a good 30 day key,(Unregistered ROMDOOR only supports 1 CD)
Second: Ensure YOU have given yourself access to these Disks
Via MAKEROM, "EDIT Security Level"
Third, Run GETON.exe, GETON will return the cd's it finds
Online. IF GETON doesn't recognize all your Online cd's
Or doesn't show the correct CD's :
Make sure you have entered a "CORRECT" Volumn label
or a "UNIQUE File to find.
**** Also Some CD's have the same Volumne Labels
in this case go blank the VOL. Label info
and put in a unique File name.
Q: I receive B-Tree errors whenever a User does a search,
or listing on a particular CD.
A: Mostlikely that particular CD's Database has become corrupt
Run "FIXROM ??" (?? is the CD-Rom number to run on)
Fixrom will rebuild that database.
Q: Dang, youDon't have a Premade for my disk, How do I make a
Database
A: First, Ensure the Disk you have is BBS Compatible
I.E. Has a FILES.BBS in each Area, or atleast A Dir with
a Unique text file for each area.
Second. Go into MAKEROM, Enter "EDIT CD-ROM INFO"
Highlight on an empty slot Depress Enter.
Type in The Disks NAme
The Volumne Label (or a unique File name)
F-10 to save
Then enter EDIT CD-ROM Areas
(MAKEROM will ask you for the # of areas)
Go to area #1, enter in a Area Name
choice Group (if you have that set)
Enter in the Path(s) to that area
Begin with a "\" F-10 to save
Edit the remaining area.
Then type ALT-Q
For Quick Import.
Enter inthe PATh to that CD
File to look for (usually Files.bbs)
Then the text defined file to use
Walla Done,
Don't forget to hit enter on "MAKE PREMADE Database"
to share with your fellow sysops
* Making / Installing a new database now only takes 15-30 mins *
Q: I'm Unable to do a Zipped File Listing
PKZIP says NOTHING to DO
A: In MAKEWILD under BBS ID makesure it's a DOS NAME No SPaces
I.E. A.S.C. Online BBS ID is "ASC", ZIP files are D\L as
ASC.ZIP
Q: I'm Unable to get ROMDOOR to POST MESSAGE, or ALLOW FILE REQUEST
A: Make sure Allow FILE Request is set to YES in MAKEROM, And Users
Have access to that disk.
Q: I have these set to yes, and they have access, but it still
Won't write a MESSAGE
A: Next Time a user is in ROMDOOR hit the F-9 Key
You Need "ATLEAST" 95K of free Memory for ALL ROMDOOR's
Features to WORK.. (Also if this is LESS than 75K ROMDOOR
will have trouble Freeing up RAM on Exit)
Q: My System will Sometimes return a DOS error, or the server will
Randomly LOCKUP after ROMDOOR'S been heavely used for hours.
A: In your Autoexec.BAT where MSCDEX.EXE is, ENSURE you have your
/M: set to MIN 32 (PER LASER, and 38 Per pioneer 6 pack)
We have it set to 512 and use the /E to load in upper memory
I.E. MSCDEX.EXE /D:MSCD001 /L:H /V /M:512 /E
/L: DRIVE LETTER
/V: VERBOSE INFO
/M: SECTOR BUFFERS
/E: USE UPPER MEMEORY
