I gather EE tries to migrate old keys from that for continuity reasons (thanks Dave), and that may well be the problem. I DID have the original NWN copied over, and have run that since the OS install, which I left out of the original post. I did of course try the Steam version when the copy failed, but that did exactly the same thing, i.e. And that's fine, since I'm perfectly capable of adding the Allow rules to the firewall for it, and did when I later tried to go online: but it might be that the game needed to be able to get online the very first time it ran, and is failing to recover properly. So that copy would have silently had incoming connections blocked. Since I installed EE via Steam, which sucks horribly, the first thing I did was copy the EE tree to an SSD instead, and run it from there. I like the firewall idea though, and now I do have a guess as to what might have caused this problem (though it's not a very GOOD guess). (On the plus side, I DID back it up, and the backup DOES have the missing ini file in it). NEVERWINTER NIGHTS DIAMOND CD KEY GENERATOR DOWNLOAD INSTALLI didn't have a Neverwinter folder in Documents - this was a clean install not an upgrade, and I didn't copy the one from the old machine as the EE there is about a year old. The firewall (the stock Windows one) has entries for EE (and the toolset? seriously?) in it to allow incoming - though, note to BD, if you're the one adding those rather than Windows doing it, you should probably also create outgoing rules in case someone's reconfigured the firewall properly, but I haven't done that on this machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |