Originally posted by: skriefal
Yep. Multi-threaded applications can have problems even on a single-processor system. But the potential for problems increases when they are run on multi-processor or hyperthreaded systems. Ideally, any multi-threaded applications should be fully tested on multi-processor systems to weed out the greatest number of threading bugs. But it seems that usually doesn't happen.
Back to the OP's question... it seems that the
start command does not provide options to set affinity. But there's a command-line program that came with the Windows 2000 Resource Kit that allows you to force a program to run in uni-processor mode, which should accomplish the same thing. The program is called imagecfg.exe. You should be able to find a copy of the program on an NT 4.0 CD or the Win2k Resource Kit CD. I also found a link
here...