in ROMD4??-.zip is a NEW 30 Day Key
If you already have a ROMDOOR V4.XX key Make sure you
Don't overwrite it with the temp 30 day key
** DIGI ** ROMDOOR is now released WITHOUT A Seperate DIGI Version
Call Digi Version as "ROMDOOR.EXE DIGI"
I.E.
ECHO OFF
D:\DOORS\ROMDIM.EXE DIGI
to UPGRADE from ROMDOOR V4.00-4.1X
1: BACKUP.. MURPHY's LAW...
2: UNZIP the *.EXE's into ROMDOOR Dir.
3: Copy over the ROMDOOR.HLP file.
4: DELETE PREVON.DAT.
5: Have another Cold BEER
Your Done..
****** Note *****
DELETE your PREVON.DAT before running ROMDOOR again
We've rewritten this dat. file and ROMDOOR / GETON
will error out if a old format exists.
You should nolonger be getting RUNTIME ERROR 100's When going into
MAKEROM or ROMDOOR (after inital upgrade) However if you do:
UPGRADING FROM ROMDOOR V4.XX to ROMDOOR V4.02
Unzip the EXE's and DOC's and HLP's into your ROMDOOR dir
*** DO NOT OVERWRITE YOU ROMDOOR.KEY ******
*** DO NOT OVER WRITE "ANY" ".DAT" FILES
*** DELETE YOUR PREVON.DAT FILE BEFORE RUNNING "ANY EXE"
UPGRADING FROM ROMDOOR 3.XX TO 4.XX
You need to do 3 things after typing UPDROM 30TO40 and before typing
MAKEROM
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
Once this is done type MAKEROM (from within ROMDOOR) you WILL get an
Error "MAKEWILD.DAT Not found. IGNOR it. go to general parameters
edit the correct PAth to your NEW MAKEWILD.DAT. F10 to save
Walla Your Done
-:INTRO:-
This is not a complete documentation for RomDoor v4.0X
but this should point out most of differences. If you have any problems
please let us know by calling ASC Online at (301) 352-8900
-:UPGRADING:-
1) Backup!!! That means backing up all the databases in the ROMxx
directories as well. This version has been out for a while but don't
take any chances.
2) Move or Delete all the .EXEs in your RomDoor directory.
3) Follow the following directions depending on which version of RomDoor
you are upgrading from.
>>> FROM ROMDOOR V3.XX <<<
1: BACKUP.. (this has been tested on several systems
without corruption, but why be the FIRST)
2: Have a cold-one, your 99% done
3: unzip ROMD40X-.zip EXE's into your ROMDOOR Directory
("RDTEXT.DAT" should be the only DAT overwritten)
4: type "UPDROM 30TO40"
5: Edit MAKEROM's Path to your NEW Wildcat Dir.
6: Your Done..
you are now WC 4.0 compatible, can support 250 cd's
do global security updates.
automaticly import in file descriptions. etc..
Please report any and all Bugs, cosmetic fixes. Suggestions to
A.S.C. Online Voice (301) 352-0961
BBS (301) 352-8900
>>> FROM ROMDOOR V2.00-V2.03 <<<
a) Change directories to your RomDoor directory and run UPDROM with
the parameter 20TO30:
C:\ROMDOOR>UPDROM 20TO30
b) Delete the following files since they are only needed if you are
upgrading from v2.10:
UP.EXE
UPDR210.BAT
>>> FROM ROMDOOR V2.10 <<<
a) Check the size of your MAKEROM.DAT if it is anything other 8988
then you will want to run the UPDR210.BAT. (Note that DOS will
give you a error at the end, that is ok since UPDR210.BAT deletes
itself.)
b) If you are running a version previous to v2.10r then there is a
possibility that the information in MakeRom will not be correct.
Check in MakeRom's main parameters to make sure that everything is
in order.
-:NEW FEATURES:-
This is an abridged list of advanced new features, which you need to do
extra work to use them. A complete list of all the features will be
available soon. Play around and you should be able figure out most of
them.
1) If you don't change your CD-ROM disks often then turn the option
"Check CD-ROM" to "NO" located in the "Edit Main Parameters",
"Edit Extra Features" menu. This is useful for sysops with Pioneer
disk changers. No longer will RomDoor scan the disks each and
everytime it loads, instead, RomDoor will scan the disks only if the
file PREVON.DAT doesn't exist. So if you want RomDoor to rescan
there are three ways you can have it do this:
a) Delete the file PREVON.DAT. (RomDoor will rescan next time it
loads.)
b) Run the program GETON.EXE. It will scan the disks and save the
online disks to PREVON.DAT. It will also tell you what drive
letter the disks are in.
c) When you are in RomDoor, press F5 when it is waiting for user
input. That will cause RomDoor to scan the disks as well.
2) If you want to speed up the scanning disk process and want to
eliminate certain drive letters from being scanned then:
a) Load up MAKEROM.EXE.
b) Select "Edit Main Parameters"
c) Select "Edit Drive Assignments"
d) Select "Edit Node 1's CD-ROM drives"
e) You should be presented with a screen which lists out the drive
letters C: - Z:. As well as unit numbers (discussed in #3).
To clear a line press CRTL-Y, then type in the drive letter you
want it to scan. For example if you wanted RomDoor only to scan
drives I: and J: then you would have:
1) Path: I: Unit #: 0
2) Path: J: Unit #: 0
f) Note that you can use this feature to have RomDoor look for a disk
in a subdirectory. (If you have the hard drive space it will
work). For example lets say you copied the entire disk and
subdirectories to D:\CDROM1. Then you would have:
1) Path: D:\CDROM1 Unit #: 0
3) As mentioned above there are now unit numbers, these are mainly for
sysops with Pioneer disk changers. When these are set then RomDoor
will "lock" the units and will only let one node copy a file from a
unit at once. So if you have two Pioneers where drives E: - J: are
on the first CD-ROM player and drives K: - P: are on the second
player then you will have the following setup:
1) Path: E: Unit #: 1
2) Path: F: Unit #: 1
...
6) Path: J: Unit #: 1
7) Path: K: Unit #: 2
8) Path: L: Unit #: 2
...
12) Path: P: Unit #: 2
Note that RomDoor will never lock a unit number with a value of 0.
4) RomEdit's update feature has been greatly improved and shouldn't take
much longer than a minute or two for a single disk. The purpose of
the feature is to compare the disk to RomDoor's database.
a) Load up ROMEDIT.
b) Press ALT-U.
c) Enter in the path to the CD, for example if the CD was your I:
drive then press enter I:.
d) For the "Freshen Action" you have the option to freshen the size
and/or date.
e) For the "Not Found Action" you have the option to "Flag" or
"Delete" the files that are in the database but not on the CD-ROM
disk. "Flagging" the files means that when RomEdit encounters a
file it can't locate on the disk then it sets a flag in the
database. It also adds the file to the third key so you can get a
list in RomEdit of only the deleted files.
Once the entire disk has been compared to the database RomEdit sets a
flag in the CDRECS.DAT file which tells RomDoor that the CD-ROM has
been checked by RomEdit. So now when a user tries to mark a file on
the disk it first looks to see if the not found flag is set and if it
isn't it automatically assumes the file exists and marks the file
without checking the CD-ROM disk. This improves preformence on a
Pioneer 6-Pack dramaticly and your users will be greatful.
5) v3.00 now allows you to create a text file database of your RomDoor
database. The main reason for doing this is that since the text file
is sequential then RomDoor can read the file in large blocks and so
that less disk access is needed. Doing this improves the text search
by nearly 15 times. The only downfall is that it will take up more
space on your hard drive. To use the "QuickSearch" databases simple
run QUICKEXP. The parameters for it are the CD-ROM disks that you
want to create "QuickSearch" databases for. So if you wanted to
create a "QuickSearch" database for CDs 2,4,5 and 6. You could type:
QUICKEXP 2,4-6
Currently QUICKEXP is very unattractive but that really doesn't
matter since it does what it needs to do. After QUICKEXP has run it
will have created a file called ROMSRCH.DAT in your ROMxx
directories. That is the "QuickSearch" database. If you decide that
you are running low on hard drive space and want to delete it, feel
free to since when RomDoor starts a text search it checks for the
existence of the file, if RomDoor doesn't find the file then RomDoor
won't use it. The typical size of the ROMSRCH.DAT is about half the
size of the ROMFILES.DAT in that ROMxx directory.
