..... is an annoying bug that i am experiencing that i can vaguely remember Ex talking aobut, if i recall correctly it effects Win2k and XP users.... all it does is gives me an error message when i r-click on certain items (most of them need identifing) and it crashes the game.

any ideas on how i can stop this happening... i have the latest patch installed and ex's bugfixes already.

I dunno how to stop it but to avoid it you could get things identified at a shop or temple and perhaps download a list of items and stuff so you don't need to right-click on things. Try buying the Walkthrough.

Hmmm oh dear, this does seem like an annoying bug, and walkthroughs and Item lists are a no-no for most of use that like to play the game properly.

I have recently (5 months ago) upgraded to win2k and a bug like this could really put me off reinstalling BG2.

Have you tried all the Win2k patchs\service packs?

Mr Writer, I have win2k, and I have never heard of the bug, so try if it works first...

Well I'm gunna give it a go soon, got to do something during this 12 week holiday.

Last time I tried I got a weird error, kept asking for Disk 5 despite the fact I only have 4 :S

Oh and this may be a ToB question but now I have brought it should I install at the start or complete BG2 then install it?

You probably didn't install all the cds from 1 drive. That can cause the game to ask for a 5th disk.

You can install the expansion right away. This is probably best, because you'll get used to all the changes which influence you directly, but I can't tell what they will be on this forum.

Alas its borked, weather that was my problem or not I will never find out.

My Dog took a taste to the CD's and CD1 now has a huge scratch down it and refuses to work right.

Looks like im saving up for NWN :p

Have you got the patch for SoA?

The original problem - right clicking on certain items - only occurs (as far as I've heard) on XP or 2k systems if they are using NTFS file systems. In other words, the hassle is with the hardware abstaraction layer.

No, I have no idea how to fix it.