NFS PU Locks at..... [Archive] - Racerplanet Network Forums

View Full Version : NFS PU Locks at.....


Nalorin
01-23-2002, 12:03 PM
I am on win2k, w/ sp2, and I have tried everything I can think of to try to get it to run...

I am running a GeForce2 MX400 with the 23.11 Detonator4 drivers

But even with all that I have tried, it still locks at the First Loading Screen (when it is loading to get into the game). =((

I have tried before to play with the thrash driver....does nothing...

My friend has a Kyro II on win2k...no problem....my other friend a V5 5500 on win2k.....few problems.... another with a Radeon 7200 on win98.....none of them can figure out the problem with my system....I had the same problem when I had my Rage Fury Pro GFX card.


HELP!!!!=[:help:=[

MATT
01-23-2002, 02:37 PM
Let me guess, you've got 256 MB of RAM or more, right? I'll bet your game just sits there at the loading screen while your HDD LED light on your PC case goes bezerk, eh? This problem is not a video card problem (although it's possible that once you get into the game, the game may crash on tracks like Normandie. There's a few known problems with NFS5 and GeForce-family cards... and even some TNT cards as well, I believe. Most EA games have been geared towards 3Dfx Voodoo cards, just FYI. The nvidia TNT and GeForce family cards still work, though.. and for the ones that don't work fully, there are fixes for those as well.)

I have a .txt file on my desk with how to solve this memory leak problem. It's actually more for Windows XP, but most steps are just like Windows 2000. I wrote all of it myself simply because I get questions to this exact problem so many times that it's just a lot easier to copy/paste the same thing over and over rather than type it all out :P

Here it is:

Windows 2000 and XP both have problems with machines that have 256 MB of system RAM or more. When starting up the game, a memory leak develops and it starts filling your harddrive with useless info until there's no room left and you get a virtual memory error.

You can cure this by either turning down the pagefile/virtual memory or completely turning it off (with 256 MB of RAM and more, you probably could do without virtual memory anyway...)

To get to the pagefile settings, go to your control panel, then double click on the System icon. Now that you're in the System properties, click on the "Advanced" tab. You'll see three sections there labeled: "Performance," "User Profiles" and "Startup and Recovery." Each one has a "Settings" button. Click the "Settings" button for the "Performance" section (For Windows 2000, it's a button named "Performance Options" instead of "Settings")

Another window will pop up. It will have two Tabs: "Visual Effects" and "Advanced" (Windows 2000 doesn't have two tabs. It's only one window)

Click on the "Advanced" tab. (Windows 2000 users, ignore this)

Down at the bottom, there will be a section named "Virtual Memory." Click on the "Change" button. You can select "Custom size" and type in 128 MB minimum and 256 maximum (works for my machine) or you can just simply turn off the pagefile completely (which is how I have mine set right now.) It'll be a safer bet to click on "No Paging File" probably.

Note for Windows 2000 users: You cannot completely disable the page file using this method. You can still turn down the settings to 128 minimum and 256 maximum (or whatever you like... just don't put it higher than the default because that's when the memory leak starts.)

Click "OK" and "OK" and you'll be asked to restart. Do so, and once rebooted back into Windows, try the game again. It should work :)