Kelsenellenelvian

1 = your mobo is WAAAAAAAAY old. You are really pushing it. 2 = Thermal paste NEVER forget it. 3 = Heatsinks are incredibly hard to seat. Carfully make sure it doesn't wiggle or is loose at all.

Then your problems are from it being a DELL OEM version. They add all sorts of crap to those and change many things.

Are you sure your source is CLEAN? Is it free of scratches and not a "downloaded" version?

What a dork! 99% of errors actually happen between the chair and the keyboard. I bet most of your issues are with you not knowing what you are doing or trying to do stuff vLite isn't fully capable of yet.

OK always make sure the drivers you are integrating are official WHQL drivers with a .cat file included.

First questions first = Do you actually HAVE a 64x source to start with?

http://www.ryanvm.net/forum/viewtopic.php?t=5564 This is as close as you get...

Ummmm did you even LOOK in the sticky section?

http://www.msfn.org/board/WPI-641-release-t116453.html

noted and checked!!! Thanks

TaskKillS program.exe It displays no splash screen at all. It can be put in the system32, but you can call it from anywhere as long as you include the full path. So the proper syntax would be = %wpipath%\tools\taskkills dcom-bobby.exe Please give that a try.

We are planning it for this weekend!!

WOW thats a lot of text Anyways it's actually an ability of WPI to log the process and keep that log as a txt file at the root of your systemdrive.

It is most likely the file index proccess running again to re-index all files. Run it like you normally would for a week (7 days) with SP1 installed THEN check the temps and cursor.

Lemme see the WPI_log please...

Clean installs are ALWAYS very nice to play with!!! Thats the only other solution I could offer you as you have (or are trying) everything I could think of.

It really can't hurt to try... You've tried everything else.

Ok sometimes the nVidia cards only run well with the drivers from the manufacturers website so go there and try the drivers they have.

OR dl the extra tools folder and use the "TaskKillS.exe" provided in that it will work n win2k just fine...

I am very sorry but I do think it is a 2byte OS issue. It is either an issue with Microsoft (Since the full installation works) or a conflict with WPI. Please wait untill this weekend and try version 6.5.

MSFN forum rules state:

DX10 install = Bad myth it will only mess your system up and can only be found on warez sites.

Hmmm I am not sure what your issue is. As long as you are sure your answer file is right then the commandline1 should work fine. Try running it in WPI all by itself. (As a seperate command not with frontpage.)

Its prolly cheaper to goto ebay and get a new disk.... Like here http://cgi.ebay.com/Microsoft-Windows-2000...1QQcmdZViewItem