Perhaps the UK distributor updated the CDs to the latest patch, and accidentally or deliberately bumped the version number up. Either that or amazon.uk has a supplier in the future. <img src="/ubbthreads/images/graemlins/silly.gif" alt="" />
In the first act have you been to the second BF dungeon yet? (it is available a ways into the act, so probably not) There was a bug in the original release that would leave the first 2 levels empty. Depending on whether you hit that bug or not, you would know if you have a pre or post patched game. Even easier, do the inventory tabs work as independent toggles, so you can have 1, some or all categories displayed at the same time (original release) or are they tabs where only 1 can be shown at a time (patch 1.40 or later)?
I created a couple files containing the CRC values of all the files in a clean install, as well as after the 1.45 patch. You could check against your install, to see if they match. If so, then somehow the listed version number is incorrect. Files that changed include div.exe, protect.dll and resource.dat in the Beyond Divinity folder, the '
..\Beyond Divinity\Localizations\hints.txt' file as well as several files in the '
..\Beyond Divinity\Acts\Act#\Dialogs\Battlefields' and '
..\Beyond Divinity\savegames\Bd_act#_start' folders.
The values for the div.exe file
v1.10 - 3,916,800 bytes, CRC32 014BEA89
v1.45 - 4,115,456 bytes, CRC32 B1AB5C38
From a different post:
The install program should report any problems, such as CRC errors, during install. However, if it fails to do so, or a file becomes corrupt after installation, the integrity of the files can still be verified using a program such as
FileCheck;
download (194KB). This is a small freeware program (no install required) to calculate the CRC-32 values (the cyclic redundancy check used in zip files) of a number of files. It can also compare a previously calculated CRC file with a set of files/folders.
After doing a clean install of BD and rebooting, I deleted the files in the '
..\Beyond Divinity\DirectX9' folder (since they are not needed if/once DirectX 9 is installed). Then I used FileCheck to create a crc file of the game folders, installed the 1.45 patch and did so again, both before starting the game. If you compare the appropriate CRC file to your install, it should tell you if there are any corrupt files. You do not need to worry about moving any saved games out of the
savegames folder or deleting the files in the dynamic folders, since new files will not be tested by FileCheck, just those listed in the crc file. If you have started the game and changed any options, there will be differences reported in the
config.div and
keylist.txt files. In my install the '
..\Beyond Divinity\Editor\dgen_themes.000' file was also reported to be different.
There are several files in the
Beyond Divinity folder created when the game is started or options are changed, including
init.cfg, mapids.000, persist.dat, sinfo.000, slashed-d3d6.cfg, slashed.cfg, sound.cfg and
starlog.txt. A couple other files are also added, but another crc file including these wouldn't help much, since most or all are system or option dependent, so these files would usually be reported as different regardless of being valid or corrupt.
At least the
config.div,
slashed.cfg and
slashed-d3d6.cfg files in the
Beyond Divinity folder can be deleted, and the configuration program / game will recreate them the next time it is started.
Beyond Divinity CRC files (190 KB)
[*] These crc files are based on the UK English version; the North American version should be the same, I think, and the Australian version not too different (it uses a different copy protection).
[*] FileCheck expects the files to be in the original locations to verify, so if you installed BD to a location other than the default (
C:\Program Files\Larian Studios\Beyond Divinity), open the CRC file in Wordpad (for example), and do a search-and-replace so the file/folder paths match your install.
If your CRC values match, it is not the game itself, but likely a conflict with something else in your system or a problem in the saved game folder. When examining the list of 'errors' FileCheck produces, potential problem files would be those with an error trying to read, or with a large size difference (especially zero byte files) from the known good install.
