Hello,
I recently finished my mega-mod install(without the Big Picture but containing virtually all compatible major or minor mods such as Tactics/Quest Pack etc. etc.). Things went more smoothly than I'd hoped. However, I noticed a standard problem when trying to install Blucher's Expanded Thief Stronghold - it causes various parse-errors with the previous installation of the BG2 Fixpack so it's not a good idea to combine both - this should be mentioned in the BG2Fixpack. Another thing:- with all the huge numbers of mods, I frequently got a message stating that the dialog.tlk file was too large to be modifiable by WEIDU, thus preventing installation. Due to ingenuity, I managed to work out that I had to try installing other mods(or just running, aset-up of a previous mod without actually reinstalling anything) - that seemed to allow the installation of the former mods without the "dialog.tlk" message appearing again. It would make things simpler if the WEIDU installation were reworked so as to avoid that message recurring.
Installation comments
Started by Strontium Dog, Jul 06 2007 05:00 AM
1 reply to this topic
#2
Azazello
-
- Staff
-
- 1914 posts
The Anti-Spammer
Posted 06 July 2007 - 06:16 AM
The "dialog.tlk 'too big'" message is an old one and can be avoid by having weidu auto-update all the other weidu EXE's in your game folder. Simple thing to do is, after extracting all your mods into the game folder, run this "setup-BG2FIXPACK.exe --update-all" from a DOS window from the game folder. Clear? First, extract not install; 2nd, auto-update; 3rd, install.
The "standard problem" with parse errors is standard depending on which install list you have. Remember, that by the time you start installing mods low in your list, the vanilla files they are looking for have changed significantly. They cannot find a block of code that has been modified by other mods, ergo error. Thankfully, these errors are benign and can be ignored (at least, I've not found a case where they cause a problem).
If you want to know which previous mod(s) changed the code block, check the TP2 of the erroring mod, find out which BCS it was trying to change, then search thru the folders of the all the other mods and determine which also modified the BCS.
Umm, I recommend searching the forums, or better the Web, and see if anyone else has already reported these errors.
The "standard problem" with parse errors is standard depending on which install list you have. Remember, that by the time you start installing mods low in your list, the vanilla files they are looking for have changed significantly. They cannot find a block of code that has been modified by other mods, ergo error. Thankfully, these errors are benign and can be ignored (at least, I've not found a case where they cause a problem).
If you want to know which previous mod(s) changed the code block, check the TP2 of the erroring mod, find out which BCS it was trying to change, then search thru the folders of the all the other mods and determine which also modified the BCS.
Umm, I recommend searching the forums, or better the Web, and see if anyone else has already reported these errors.
