Having Problems Getting The RIP Playroom To Run?

  99% of the people who call with problems with this door have the SAME
problem, that being Error 62, Input Past End Of File. This is caused by
either your .cfg file, or your filelist.dat file not having the appropriate
number of lines in it. 

 In the config file, a lot of folks miss the blank line at the end if they
are using a standard IRQ, or they are using a text editor that either
deletes blank lines at the end of files, or leaves and EOF that can be
mistaken by some folks as a blank line. 

  I heartily recomend the use of a tiny little program called SLED for the
editing of batch files, config files, etc. It's fairly simple to use, yet
has a lot of functions that come in quite handy for more experienced users,
and it is VERY small. 

  But no matter WHAT you use, if you encounter this problem, I have one very
simple recommendation. Normally, your .cfg file would look like this:

---- Begin
C:\BBS
            <- Blank Line Here!
---- End

  If that doesn't work for you <because whatever editor you are using kills
blanks at the end, or whatever> try this:

--- Begin
C:\BBS
            <- Blank Line Here!
-           <- Extra line with one character on it!
--- End

  Everyone who's come to me with this problem has tried this and fixed
the problem. :) The program does not CARE how many lines it has, as long as
it has ENOUGH lines.. :)

 If the problem is in your filelist.dat, then you simply need to make sure
there ARE 20 lines in that file, and, if necessary, adding the same extra
line as above for cranky editors! :)

 The only other error anyone has reported to us was an Error 53, File Not
found. This simply means that either your .cfg or your filelist.dat is
not being found, or perhaps because of a typo on the command line for
the config file name, or perhaps putting in a  screen name that doesn't
exist <again, probably a typo!>, or a typo or mistake in the path to
where the door.sys is found. You should NOT add door.sys to the first line
of the config file, IE C:\BBS\DOOR.SYS. The program knows what it is looking
for and that will surely cause a problem when it goes looking for a door.sys
in a dir called door.sys. ;)

 Please, if you have any problems running this door, check for these
problems first. AND, if you encounter ANY other problem, please feel
free to contact us for assistance. WE're pretty friendly folks <Just Ask
Della!> And we don't bite! <gryn>

                      Cliff & Susana

                     FireHawk Software


