The obvious solution is to fix the application, or upgrade to a later
version that does synchronization and serialization properly.
Try starting CMD.EXE, setting it’s affinity, and then launching your app
from within that window.
Gary
-----Original Message-----
From: xxxxx@matrox.com [mailto:xxxxx@matrox.com]
Sent: Tuesday, April 03, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to disable dual cpu
automatically before launching an application
Hi,
I have an application that does not behave well when ran on
dual cpu
systems. I am looking for a simple workaround to disable one
cpu just prior
to lauching this application (ie: a batch file, or some
other trick).
I have considered other alternatives like:
-
insert /onecpu in the boot.ini line => but this disables
dual cpu for
all app’s which is not desired. -
Start the app in question - do “ctrl-alt-del”, select the
process, and
right click to use the “set affinity” to disable one cpu =>
does not work
since the app is already started and damage is already done.
I would appreciate any suggestions.
Thanks!
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com