7 Installing and Uninstalling BibleWorks |
|
This chapter describes how to install and uninstall BibleWorks. As related topics, see the Setup chapter for information on configuring BibleWorks using on a network, and the Getting Help chapter on getting updates.
Installing BibleWorks
Backing Up Files
Central European Fonts
File Types Used by BibleWorks
Installing BibleWorks
To start the installation of BibleWorks 9, insert Disc 1 into your DVD drive. Onscreen instructions should appear in a few seconds. If the instructions do not appear, proceed as follows:
- In Windows Vista or Windows 7 click on
“Run autorun.exe” in the Autoplay window that opens up automatically. If
the Autoplay window does not appear, click on the round Start icon in
the lower left corner of your screen and, in the Start Search field,
enter
x:setup
where “x” is the letter for your DVD drive. - In Windows XP or Windows 2000, click on
Start | Run
Then enter
x:setup
where “x” is the letter for your DVD drive.
A User Account Control
dialog box may open requesting permission to continue. Click Continue to
begin the installation.
Uninstalling Old Versions
Before installing BibleWorks 9 you should uninstall any previous versions of BibleWorks that you have installed. If the Setup Program detects the presence of a previous version of BibleWorks, it will give you the option of uninstalling that version. Unless you have good reasons to do otherwise, we recommend that you always uninstall the old program. The uninstall program will not delete any files that have been added or changed since the old program was installed, so no great harm can come from uninstalling it and it will free up a lot of disk space.
If you choose NOT to uninstall the old version you should be aware that the BibleWorks 9 Setup Program will delete the Uninstall (or Maintenance) program for the OLD version when it installs the new version. This is to prevent the old Uninstall program from uninstalling parts of the program that the old and new versions have in common, and thus damaging your new installation. If you need to delete the old version later you can just delete the old directory, making sure to back up any files that you need. The advantage of uninstalling the old version first is that it leaves the changed and new files behind, thus relieving you of the need to filter through them later. It is simpler just to let the new Setup Program uninstall the old version.
Note that on some systems the uninstaller for the older version may display error messages. You may safely ignore these and proceed with the BibleWorks 9 installation after the uninstall process is complete. It will leave the old installation partially installed but this does no real harm. If you want to fully uninstall the old version contact BibleWorks Customer Support for assistance.
Reconfiguring or Uninstalling BibleWorks 9 after Installation
To uninstall or reconfigure BibleWorks, open up the Windows Control Panel and double click on the "Add/Remove Programs" icon. Then locate BibleWorks 9 in the menu that is presented and click on the "Change/Remove" Button. You should never uninstall BibleWorks simply by deleting the BibleWorks directories.
After you uninstall your old version of BibleWorks, a stub directory will be left behind. It will contain any files that were changed after you installed the previous version. These files may contain notes and other files created under the older version that you may want to copy over to the new installation directory.
Activating
BibleWorks and Add-on
Databases
BibleWorks comes with all the basic tools that most people will need. We have always recommended that users invest their scarce financial resources in print books rather than electronic books. That is why BibleWorks has relatively few add-on modules compared to other companies. There are a few cases, however, where certain kinds of books benefit greatly from being in electronic form, enough in most cases to justify having copies in both print and electronic media. This is particularly true of lexicons and grammars. For that reason we try to provide users with standard works of a grammatical and lexical nature.
When you purchase an external module you use an installation program similar to the one you used to install BibleWorks. But all the installation program does is copy the files to your hard drive. You must still "activate" the module so BibleWorks knows that you have the right to use it. During the installation you are presented with a window for entering the module activation codes.
Program and module activation is done by selecting File | Activate Database on the BibleWorks main menu. The Activation Manager includes the following buttons at the bottom of the window for activating and managing your resources:
-
Activate all resources - This button enables you to activate all the resources at one time over the Internet. This is the recommended method for activating your resources.
-
Manually
activate all - This button opens a window that enables you to
create an email message containing your activation information. You can
then send the email message to BibleWorks Customer Support for
activation. This method will take significantly longer than activating over the
Internet using the Activate all resources button. You can also contact
Customer Support by telephone, but there are no advantages to this
method and it will be slower than activating over the Internet. -
Options - This button enables you to save your activation codes to a text file for backup purposes. You can also use this button to restore your backup codes.
Some modules may be available by download from the Internet. You will have to download the file from the Internet by using the BibleWorks Updater, then insert your installation disc and enter the module activation code in the activation code window. Then you will use the Activation Manager window to activate the new module.
When you install BibleWorks the following directory structure is set up on your Hard Drive:
|
Program Directory |
c:\Program Files\BibleWorks 9 |
|
Database Files |
c:\Program Files\BibleWorks 9\databases |
|
Timeline Files |
c:\Program Files\BibleWorks 9\timeline |
|
User Databases |
c:\Program Files\BibleWorks 9\userdb |
|
GSE Files |
c:\Program Files\BibleWorks 9\ase |
|
Diagrammer Files |
c:\Program Files\BibleWorks 9\diagram |
|
NT Diagrams Data |
c:\Program Files\BibleWorks 9\gntdgm |
|
Initialization Files |
c:\Program Files\BibleWorks 9\init |
|
Note Files Videos and related HTML Map Module Data |
c:\Program Files\BibleWorks 9\notes c:\Program Files\BibleWorks 9\images c:\Program Files\BibleWorks 9\videos c:\Program Files\BibleWorks 9\mapdata |
|
Temp |
c:\Program Files\BibleWorks 9\temp |
|
Patches |
c:\Program Files\BibleWorks 9\patches |
The "temp" and "patches" folders will not be created until you need them. The patches folder holds program and database updates that you download from the Internet. The "temp" folder holds temporary configuration files used by the BibleWorks editor.
Your setup may be slightly different if you specified a different installation directory. For a list of file types that are used by BibleWorks (depending on your setup selections) see File Types Used by BibleWorks.
A shortcut will be installed on your Start / All Programs menu. You can use this shortcut to start BibleWorks.
When you run BibleWorks for the first time, two files, bw900.ini and bwdir.ini, will be installed in your BibleWorks directory. This location is where configuration changes for the program are stored.
If you need to configure BibleWorks to serve multiple users on a network, see the topic entitled Configuring BibleWorks for Use on a Network.
Backing Up Files
It is always a good idea to do full system backup before installing major programs. If you choose not to do this you should at least be careful to backup all files from previous installations of BibleWorks that you might want to keep. These include:
|
Timeline Files (*.era and .tl) |
Synopsis Files (*.sdf) Context files
(*.swc) |
As a safety precaution, if you attempt to install BibleWorks in a directory containing a previous installation of BibleWorks you will be warned that some user-defined files may be overwritten or deleted. You will be offered the option of having the files backed up by the installation program. You can also exit the Setup Program and check yourself for files that you may want to keep, or you can proceed with the installation.
Central European Fonts
If the Windows Central European and/or Cyrillic TTF fonts are not on your system, BibleWorks will install its own Central European (bweess.ttf, bweeti.ttf) and/or Cyrillic (bwcyrl.ttf) fonts. Display quality will be better if you install the Windows Arial CE and/or Arial CYR fonts. To do this you will need to install the Windows Multi-Language Support Module. For details on how to do this see the section on Installing Support for Cyrillic and Central European fonts.
File Types Used by BibleWorks
The following is a list of file types used by BibleWorks:
|
Extension(s) |
Description |
|
afm, pfm, |
Postscript font files (four files, each with a different extension, for each font) |
|
asc, txt |
ASCII text files, readable in any text editor, used for a variety of purposes |
|
bes |
Temporary files used to store location, top line, etc. information for BW editor files between sessions. Can be safely deleted without loss of data |
|
bna, bnb |
Book Name Alias files |
|
bwc |
Saved BibleWorks Command Line |
|
bww |
Editor files |
|
bso |
Book Sort Order files used in the Verse List Manager |
|
chm,
hhc, |
BibleWorks HTML Help files |
|
clr |
Color Filter Files |
|
cnt, hlp |
BibleWorks Winhelp Help files |
|
cws |
Compound Word Definition files used by the Command Line |
|
dat |
BibleWorks ancillary database files used for a variety of purposes |
|
dbu,dbx, |
Version Database files. Each version in BibleWorks will have files with the last four extensions. Beginning with Version 5, BibleWorks Version Databases will also have a .dbu file |
|
def |
crc.def contains a list of CRCs for installed files. It is used by the check.exe program as directed by Tech Support |
|
dgm |
Diagrammer files |
|
dwd |
Diagrammer Widget Definition file |
|
era, erc, tl |
Database files used with the BibleWorks Timeline |
|
erd |
Ermie database files |
|
exe |
Program Executables. The BibleWorks program is called bw900.exe |
|
fmp |
Font mapping files used in the Font Options tab to export text to other fonts |
|
gz |
Base files used during the updating process |
|
hst |
Verse and word history information |
|
id |
bwver.id contains the installed BibleWorks Version ID. It is used by the Web Update feature |
|
ini |
Initialization file (contains user-modifiable settings) |
|
map |
bw900.map contains the executable link map file for bw900.exe. It is given to Tech Support when requested to assist in isolating bugs |
|
mdb |
Morphology Database Files. They contain lemma and form usage statistics for the various Morphology Version Databases |
|
pbn |
Downloaded patch files |
|
qf |
Graphical Search Engine query files |
|
sdf |
Synopsis Definition Files used by the Synopsis Window |
|
sdx |
Cross Reference Index files for the HTML modules |
|
swc |
Search window context files |
|
ttf |
TrueType Font files |
|
udb |
User DataBase files used for a variety of purposes |
|
vls |
Verse List files |
|
vmf, vmc |
Verse Mapping Files (also see *.dbu files entry above) |
|
vrc, vrt |
Flashcard compiled (*.vrc) and source (*.vrt) files |
|
wdc |
Word occurrence data file, one for each Bible version |
|
xrd |
X-Refs tab cross-reference files |