Help with a bat file

Ok need help again...the damn toolset wont run on my pc due to windows v(p)ista. i had a .bat file my friend had sent me the line of code for to force it to run on one cpu, and when i used it the toolset ran fine.

or anyone out there know the command line for a bat file that will force it to run in single cpu mode?

I'm on Vista with a dual-core laptop.

I don't use a batch file for the toolset, but do have an extra line in my nwtoolset.ini file...it's in the main NWN directory/folder.

Open the file in Notepad, and under the [Start Up] section, try adding the line:
CPU Affinity=0

Save the file, and next time you run the toolset, it should only be using the first cpu core.

The Amethyst Dragon wrote:I'm on Vista with a dual-core laptop.

I don't use a batch file for the toolset, but do have an extra line in my nwtoolset.ini file...it's in the main NWN directory/folder.

Open the file in Notepad, and under the [Start Up] section, try adding the line:
CPU Affinity=0

Save the file, and next time you run the toolset, it should only be using the first cpu core.

I have a similar setup (dual-core laptop w/ Vista), and I use the above line in my ini file as well.

I get about 20 fps most of the time with the lowest video settings.

Svair wrote:
I have a similar setup (dual-core laptop w/ Vista), and I use the above line in my ini file as well.

I get about 20 fps most of the time with the lowest video settings.

What section of the file do ya have that? Anything if it'll help. I'm running Vista myself as well.

For the nwn client edit, it's the nwnplayer.ini, under the [Game Options] section, and would be entered as Client CPU Affinity=0

MannyJabrielle wrote:For the nwn client edit, it's the nwnplayer.ini, under the [Game Options] section, and would be entered as Client CPU Affinity=0

Sweet, thanks! Editing now.

Edit: It's already set that way, lol.

Hmm...i decided to try one last thing i hadnt tried, i took the individual nwntoolset.exe file...pinned it to quicklaunch...right cliked on properties and selected xp compatibility mode and it seems to have worked...which is puzzling as it didnt last time i tried it. Guess ill have to work in it and see if it maintains its non crashability.