the good news is that none of those errors (with the possible exception of the first one) are of any importance and can all be ignored.
when you delete yr previous installation, prior to starting a new one, do you delete *everything* in yr BGII - SOA directory? (or at least rename yr BGII - SOA directory?) it looks like BD-weidu is trying to reinstall itself and is not finding a weidu.log to tell it what order to use: when a mod is installed, it backs up all the changed files in a /backup folder within the mod folder. you've gotta empty all the backup folder (or extract fresh versions of the mods from the .rars/ .exes) before you try a new install, or the extraneous stuff in the backup folder can cause all manner of funkiness. in this instalnce, you seem to be ok.WARNING: parsing log [WeiDU.log]: Sys_error("WeiDU.log: No such file or directory")
[SETUP-BD-TOB.TP2] parsed
I have used this strategy so far;
0) Unrar/unzip/run selfextractingarchive.exe into a single folder
1) from the command screen run "modfolder/weidu.exe --update-all"
2) Uninstall BG2-SOA-TOB
3) Delete the folder
4) Install BG1 + ToSC + Patch (actually I will not be installing and reinstalling BG1 anymore ) + BG2 + ToB + Patch
4) Copy the contents of "modfolder" into BG2 fodler
5) Run the installers in order
BTW, would copying all the contents of weidu.archive along with the mods cause any problems? I wouldn't think so...
Ok, thank you...these can all be ignored: all it's saying is that weidu can't read one of the entries in yr State.IDS file. the worst that can happen is that one particular script block (here, one where a Beholder is detecting illusions) won't run: the rest of the script will work fine. best case scenario is that weidu couldnt find it but compiled it anyway; and then, ingame, it'll work as normal. either way, can be ignored. what's it caused by? something in one of the earlier mods (or some extraneous crap inside a backup folder) has incorrectly patched State.IDS (with a typo, or in the wrong location), and so weidu is not finding the reference it's looking for. as i said - especially eeing as it's only one state - you can happily ignore this.[BPv176/BAF/NEW_BAF/BEHHIV02.BAF] PARSE ERROR at line 504 column 54-54
Near Text: )
[StateCheck] argument [STATE_ILLUSIONS] not found in [State.IDS]
Again, thank you...again, typo. whether it's a BP typo - and i've not seen anyone else report it - or (judging from the bizarre name: Erinyes.bcs is a compiled script for the erinyes demon; erinyes.baf is an uncompiled script; erinyes.bcs.baf is just garbage) it's err, an artifact of yr install, i'm not sure. can be ignored anyways (there's no ingame file called erinyes.bcs.baf, so the fact that weidu can't find it doesn't affect yr install).[ERINYES.BCS.BAF] ERROR at line 57 column 37-37
Near Text: )
Parsing.Parse_error
likewise, the Quest Pack errors can be installed: at best, they're debug info for the mod author, and of no relevance to an end-user.
Well, although I have yet to learn much about the inner mechanics of weidu and IE and everything else (the life, the universe and everything ) I was a bit suspicious of this error too Again, thank you...not entirely sure why weidu is trying to copy Thumbs.db, but the fact that it failed is actually a good thing...ERROR: COPY ~NeJ/jah/pics/Thumbs.db~ ~override/Thumbs.db~ FAILED: cannot open target
OKagain, of no relevance to an end-user, and can be safely ignored.WARNING: REPLACE ignoring specified WEIGHT for state 36 (-1). Using weight from DLG (4). Use SET_WEIGHT if you want to change state weights. [6]
Well, I have been quite suspicious when I have seen that at the beginning of NEJ my character says something and the dialogue options are one extra long sentence I cannot remember about and its dublicate Anyways, It seems everything is working for now... Now I'm planning to refine my installations and make sure I won't have to begin the whole game again when it crashes - I'm not saying it will; think of the worst to come, you can never get disappointed - at the Sword Coastall in all, it looks like you've got a functioning install (seventh time's a charm! ) so the next thing to do is start playing and see if it works - it looks like it should. the things to look out for: crashes when you enter new areas - usually indicates part of the install failed (but this is not common, and these days, isn't (usually) caused by user error, so perusing the forums would give you a good idea of any crashes to expect); and incorrect or nonsensical dialogue (these usually are user error, but, err, oh well) eg a character, instead of saying 'hello' or something else expected, starts speaking spell description. otherwise, you look good to go.
Well, have I said thank you yet?
Cheers...
Mehmet