home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
New Horizons Shareware Collection
/
HORIZONS1.BIN
/
DMAN342.INS
< prev
next >
Wrap
Text File
|
1994-07-10
|
819KB
|
6,836 lines
This file contains some common problems users of the program
have encountered and the remedy for them. It will continue
to grow as more errors are reported.
Error: Unable to locate <path to caller info file> or BBS type not recognized.
If you run Wildcat, this will come out as "Unable to locate
C:\WC30\WCWORK\NODE1\" (notice the DOOR.SYS is missing). This
error will occur when you attempt to run DoorMan.
Fix : Run DoorEdit, go into Global Defaults, Door Defaults, and specify
a default caller info file. The file you specify here is the
one DoorMan will look for when it attempts to run.
-------------------------------------------------------------------------------
Error: No Commands to run this door!
This error will occur when you attempt to run a door from within
DoorMan.
Fix : Run DoorEdit, go into the Door Menu, Change Door, select the
category then the door you just ran. When the Define Door screen
comes up, hit the up arrow key and then Enter. This will put you
in the Run Command Editor. Should be nothing there. You have to
enter some run commands (or Load in an existing Bat file) so
DoorMan will know how to run the door.
-------------------------------------------------------------------------------
Error: Division by Zero in Line....
This error may occur when you run DMSTATS.
Fix : DoorMan has to create a DOORMAN.DAT file before DMSTATS will work.
It creates this file after you have entered a door from within
DoorMan, stayed one minute or more, then exit. If you do this and
it still hasn't created that file, go Change the door you ran in
DoorEdit so that Sysop Stats is set to Yes.
-------------------------------------------------------------------------------
Error: Door works fine in local mode, but not via modem.
Fix : Double check your port and IRQ settings in Global Defaults ->
Node Information in DoorEdit. If they're right, double check
the location of the caller info file for that node. If it is
right, then contact me immediately!
-------------------------------------------------------------------------------
Error: Unable to Locate Run-Time Module DMANRTM.
Fix : This should NEVER happen as long as the DMANRTM.EXE file is
in the DoorMan directory. However, if it does, simply put
a copy of that file in your path and the message will never
show up again!
-------------------------------------------------------------------------------
Error: DoorMan locks up my system when running under Novell.
Fix: In DoorEdit, Global Defaults, BBS Information, the last
question asks if you are using Novell. If so, then this
flag MUST be set to Yes. If it is, and the program still
won't work, contact me!
-------------------------------------------------------------------------------
Error: The DoorEdit Run Command Editor won't save anything and Shell
to Dos leaves me with a blank screen.
Fix : Odds are you're using an EGA card right? If so, then there
is a fix. The autodetect routine for graphics in the library
I use doesn't seem to be ablet to detect EGA properly. What
I have done is add a command line switch to DoorEdit to force
video modes and ignore the auto detect. Simply run DoorEdit
using either a 1, 2, or 3. So far, DOOREDIT 1 has worked on
every EGA system I've seen. If it doesn't, then try 2 or 3.
If it still won't work, let me know!
-------------------------------------------------------------------------------
Error: I keep getting Error #62 "Input Past End of File" when
trying to run certain doors.
Fix : I think I've nuked this one! There are three programs known
to cause this error. This only applys if you are using
DOOR.SYS as your default info file. If you run DoorMaster
as a Run Command you may get this error. If you run Murder
Mansion you may get this error. Same goes for Adventurer's
Maze. These three programs are reading in the 52 line
DOOR.SYS created by your system and writing back out 31 or 32
line DOOR.SYS files. DoorMan is expecting 52 lines! If it
is DoorMaster causing the problem, simply stop using it!
There's no need for it since DoorMan will create just about
any caller info file you could want. If it's one of the
doors causing the problem, put the following in the Run
Run Commands for those doors:
COPY <path to info file>\DOOR.SYS DOOR.BAK
<command to run door>
COPY DOOR.BAK <path to info file>\DOOR.SYS
Del DOOR.BAK
That should fix it.
-------------------------------------------------------------------------------
Error: There are doors in the menus, but when I try to select them
nothing happens.
Fix: I've hit this one four times now. Take a closer look at the
menu. Odds are, each door has a yellow L out to the right
of it. This means the door is LOCKED! If a door is locked,
NO ONE will be able to get into it including you. Simply go
into DoorEdit and change Locked: for each door to No.
-------------------------------------------------------------------------------
Error: Some graphs contain only the first 3-4 lines.
Fix: Check to make sure the subject in DMGRAPH.CFG still
exists! For instance, if you change the name of a
category or door, the old name will no longer exist
so any graph of that category or door will no longer
work.
-------------------------------------------------------------------------------
Error: Door is unable to locate the caller info (drop) file.
Fix: Double check the default info file in DoorEdit - Global
Defaults - Door Defaults. The name of the file listed
there is the one DoorMan will look for when you run it.
If that is right, then double check the path to caller
info file for that node.
-------------------------------------------------------------------------------
Error: JNS Software doors won't run when I use Test Door.
Fix: The newest versions of Rusty's games require that
certain environment variables be set. Specifically,
NODEID and PORTID. When you run DoorMan drom your
board, odds are these variables will be set. If you
run DoorEdit from a DOS prompt and try test door, odds
are they will not be set. You can either go try the
door via DoorMan, or, set the proper environment
variables before entering DoorEdit.
-------------------------------------------------------------------------------
Error: I get a "Cannot Execute..." error when trying to test
some/all doors.
Fix: This is a memory problem. DoorEdit is getting large!
When you try to use Test Door, DoorEdit leaves all of
itself in memory (230k or so). Therefore, there's not
much room left to run a door. I am working on getting
it to swap out, but I have yet to find the proper code
to do so for the language I'm using. As soon as I do,
then it will be "fixed".
-------------------------------------------------------------------------------
Error: Applies to Wildcat Only. When running DoorMan from DOS
I get Unable to Locate C:\WC30\WCWORK\NODE1\DOOR.SYS
Fix: Wildcat deletes the DOOR.SYS file when a user exits the
door. Therefore, if you try to run DoorMan from a DOS
prompt there won't be a DOOR.SYS there. You must either
run DoorMan from Wildcat, or put a valid DOOR.SYS in the
NODE directory before trying to run DoorMan.
-------------------------------------------------------------------------------
Error: Using a high speed modem, 2400 baud callers get garbage on
their screen when going into certain doors.
Fix: Some doors have a problem with low baud rates on locked
ports. The first thing to try is to set Locked Baud to
yes for the door in DoorEdit (and make sure you have a
locked rate defined for that node in Node Information)
then try the door again. This will fix the problem on
most doors. If it is already set to yes, then try
setting it to No. If neither setting works, then see if
the door itself has a Fossil setting. If so, try that
on both Yes and No. Even if you don't run a fossil, I've
seen a few doors start working even if a fossil is not
present! If that doesn't work and you're not running a
fossil driver, I suggest you get one (either X00 or BNU)
and try running it. There are VERY few doors that won't
run with a fossil present, and there are numerous that
won't run without one! So, you're better off to run one
anyway. If that doesn't work, call me! I have yet to
find a door I couldn't make work.
-------------------------------------------------------------------------------
Error: I get an "Invalid Baud Rate" error from Operation Overkill.
Fix: Set L.Baud to Yes for that door and make sure you have a
Locked Baud defined for that node. OOII can't handle certain
baud rates. Specifically, 4800, 7200, 14400, 12000, or 16800.
If you pass it 19200 or possibly 38400 it'll work fine.
-------------------------------------------------------------------------------
Error: Callers report not being able to use their Mouse when in
RIP mode.
Fix: The caller is using QMPro in RIP mode. There are problems
with QMPro's RIP support. Ask the caller to try RIPterm.
-------------------------------------------------------------------------------
Error: Screen goes blank in RIP mode on the callers end, the keys
still function, but the menu does not show up.
Fix: If the caller is using QMPro, try RIPterm. If using RIPterm,
then call me! I have had this reported on 3 different systems,
and each time the caller was using QMPro. I have tested
extensively with RIPterm and have never had a problem!
Until such time as I can duplicate the problem on my system,
I can't fix it...
-------------------------------------------------------------------------------
Error: Wildcat Door Usage utilities don't work any more!
Fix: Most of these utilities read the ACTIVITY.001 file to determine
door usage. If you tell DoorMan to append to the SysOp log
if will write the usage to this file. However, the Wildcat 3.x
format is not 100% compatable with these utilities! In order
to make them work again, you need to use the following setup
in DoorEdit - Global Defaults - Logging Information:
Append to SysOp Log:Yes
SysOp Log Format :Custom
Custom Enter Format: * DOOR #: 1 executed at @T
Custom Exit Format : * @U returned from DOS or DOOR at @T
This will mimic Wildcat EXACTELY. The only drawback is that
all entries will show Door #1 as being used. There is no way
to mimic the door numbers at this time. Therefore, you will have
and accurate measurement of Total Door Usage, but not individual
door usage. For this, I suggest using DMStats and/or DMGraph.
-------------------------------------------------------------------------------
Error: I have a registered DOORMAN.KEY but the program keeps telling
me that it's not registered!
Fix: Starting with version 3.40, the DOORMAN.KEY is no longer used.
In its place is a registration code. The code is found in
DoorEdit - Global Defaults - BBS Information. With version
3.40 I have included a program called KEY2CODE which will read
your registered DOORMAN.KEY and create a valid registration
code. Just run that program and you'll be set. If you did
not upgrade to 3.40, you may have missed the KEY2CODE program.
If so, it is available on my system. Simply call Bumpkinland
and I will send it to you.
-------------------------------------------------------------------------------
Error: I have a valid registration code but the program keeps telling
me it's not registered!
Fix: The registration code is developed using two pieces of data.
Specifically, it uses your REAL name and your BBS name. Both
of these items are read in from the defaults and are found in
DoorEdit - Global Defaults - BBS Information. If you change
either of these fields, your registration code will no longer
work! Also, if you used a different name when you logged on
to my system to register or when you filled out the regform,
your code will not work. The names listed in DoorEdit HAVE to
be the same names you used when you logged on, or the names you
put in the regform!
MZ╘ º