EdMellott
05-28-2008, 04:26 PM
BibleWorks, like many programs, provides options to create personal settings for a number of parts of the program. One can change fonts and sizes to meets one's specific preferences and needs. Most of these settings are stored in an initialization file that reflects the version of the program in use. For BibleWorks 7 the name of the file in question is BW700.INI, and it is stored in the BibleWorks 7 folder. When BibleWorks loads, it reads this file and puts in place the various settings stored in the file.
Occasionally, this file may be disrupted or deleted. This may occur for a number of reasons. When BibleWorks cannot find the file, it will create a new one based on program defaults. The result of this is that when the program opens, it appears much like it did when it was first installed. One will be prompted again to register the program, the Getting Started screen will again display, and all settings changed previously will be as they were before.
The reasons this condition may occur are many. As suggested above, the file may sometimes become corrupted. Another reason may be that some changes made may be incompatible with other changes. When changes are made in the program, they are often not put into place until the program has been closed and restarted. (Changes made to fonts are an example of this.) At times, updates to the BibleWorks executable file have caused the file to be deleted. Yet another possibility is when the program crashes. Among the Shutdown Options, deletion of the initialization file is included.
When the initialization file has been deleted, there will be no way of recovering it short of a Windows System Restore. That is a drastic response to this condition, and should be taken only as a last resort. Perhaps a better way to address this is to perform some preventative maintenance. In this case, it would be to simply make a copy of the said initialization file.
The file, as noted previously, is stored in the BibleWorks 7 folder, which itself is found in the Program Files folder. Simply find the file BW700.INI (or the initialization file for the version of BibleWorks in use, e.g. BW600.INI or BW500.INI) and make a copy of it to some other location on the hard drive or to a location on removeable media. For earlier releases of BibleWorks 5 this file will likely be found in the Windows folder. Simply perform a FIND action for BW500.INI. When it is found, make a copy of it to another location.
To restore this file, when needed, simply copy the file back to its original location. If BibleWorks opens in its default configuration, close it again. Copy the backed up file to its original location, then open BibleWorks again. This measure may not work in all circumstances, but it may "save the day" on many occasions.
Last Update - ELM/May 28, 2008
Occasionally, this file may be disrupted or deleted. This may occur for a number of reasons. When BibleWorks cannot find the file, it will create a new one based on program defaults. The result of this is that when the program opens, it appears much like it did when it was first installed. One will be prompted again to register the program, the Getting Started screen will again display, and all settings changed previously will be as they were before.
The reasons this condition may occur are many. As suggested above, the file may sometimes become corrupted. Another reason may be that some changes made may be incompatible with other changes. When changes are made in the program, they are often not put into place until the program has been closed and restarted. (Changes made to fonts are an example of this.) At times, updates to the BibleWorks executable file have caused the file to be deleted. Yet another possibility is when the program crashes. Among the Shutdown Options, deletion of the initialization file is included.
When the initialization file has been deleted, there will be no way of recovering it short of a Windows System Restore. That is a drastic response to this condition, and should be taken only as a last resort. Perhaps a better way to address this is to perform some preventative maintenance. In this case, it would be to simply make a copy of the said initialization file.
The file, as noted previously, is stored in the BibleWorks 7 folder, which itself is found in the Program Files folder. Simply find the file BW700.INI (or the initialization file for the version of BibleWorks in use, e.g. BW600.INI or BW500.INI) and make a copy of it to some other location on the hard drive or to a location on removeable media. For earlier releases of BibleWorks 5 this file will likely be found in the Windows folder. Simply perform a FIND action for BW500.INI. When it is found, make a copy of it to another location.
To restore this file, when needed, simply copy the file back to its original location. If BibleWorks opens in its default configuration, close it again. Copy the backed up file to its original location, then open BibleWorks again. This measure may not work in all circumstances, but it may "save the day" on many occasions.
Last Update - ELM/May 28, 2008