
Neverwinter Nights 2 Gold
I have migrated to Win 7 about a month before the official launch because my institution has it. (Not widely supported, but hey, I have heard and read enough about the new found stability to use it, without too much concern). And really, I was 97% happy with Win 7 since Day 1. (I can only hope that Microsoft will not fix something that ain’t broke from this point on.) Thus far I have had only two annoyances:
Annoyance #1 has to do with NWN2 Gold. Some how, the toolset (from NWN2 Gold installation) will crash on my office machine (a new Mac Pro running Win7-64) — this is pretty strange as I don’t have the same problem at home (another Win7-64). (Well, I did not have Gold installed at home because I have the OC and all three expansions).
After some search through the forum about the cryptic CLR20c3 error that pops up, it is pretty clear that the “error” was Atari’s and it was introduced into the Gold Disc. Arrgh! NWN Diamond error flashback!!!
Looks like it is either a NET 2.0 (64) problem, or a corrupted Direct X 9c driver. Since it is easier to reinstall Direct X, I went with that first; using the Direct X SDK (Aug 2009) on my machine.
Sure enough, after I re-install Direct X , the NWN2 Toolset worked again. (Yay!)
Now, annoyance #2 has to do with EM’s Epoc Control Panel. Since it is the only thing I need (for research) which will not run on Win7-64, I definitely must have a way to make it work! (Interestingly, all other Epoch tools ran without any glitch. Hence the need for two OS’es mentioned in my last post.)
After installing and removing several versions of Windows (XP, Xp64, Vista32, Vista64, Win7-32, including MS’s very own virtualization manager), I finally “gave in” to Dual Boot, which worked! (Fortunately, I have kept Vista64 on my home machine in parallel to Win7).
Considering that the CP will work with Vista64 but not Win7-64, it is mighty strange! Of course, I am suspecting again for some kind of version control problem. But knowing that EM had a lot to chew during this pre-launch period, I understand that they can not spare anyone to look into this issue. (After all, only a small percentage of their customers are currently using Win7.) So, I will wait.
Fortunately, the EM Forum is quite active on this case, and all Win7 using pre-launch adopters (like me) have been busy trying to find a way for CP to work with Win7. And reporting what does not yet work.
Finally, someone on the forum posted about running CP successfully in Win7 using Sun’s Virtual Box. Okay, something new to learn. Guess what? It worked! But you need to be running Vista64 in a Virtual Box within Win7-64, with lag time involved. Aai-ya-yah!
Thank goodness this workaround was short lived. After EM launch their product and updated the licensing scheme for Researcher (just before Christmas), I found a new CP ready for download on their website.
It worked without any problem on Win7! After comparing the installed files on both version of CP, it looks they have replaced vcredist.exe (old installation) with util_vc90.dll. Was the pre-release CP compiled using a Visual Studio that is not compatible with Win7?
Anyway, the issue is moot and what’s important is that EM got the new program out for all the pre-launch adopters… and in time for a Christmas present, too. Thank you EM!

Bye-bye, Virtual Box!