Solve : START with affinity option on windows XP?

1.	Solve : START with affinity option on windows XP?
Answer» I know that at least in Windows Vista the START command has an affinity option to start a process with a specific processor affinity mask. For example: START "Title" /affinity 1 cmd.exe That option is not available for me on Windows XP Home SP3. Which is a shame because I only need it on XP (to start NTVDM). Any way to make this work? Since NTVDM is a system file I don't want to change it with imagecfg or the like.In the upper right you see a searcdh box for this forum. Type in "NTVDM" WITHOUT the quotes and find lots of threads about that. Also: Troubleshooting MS-DOS-Based Programs in WindowsActually you'll find no threads at all about how to set the affinity of the NTVDM process. Or MUCH about affinity masks for that matter. Nor does the MS article you linked explain that. If you need to know why I want to do that you can read this article. Anyway, I found a utility to set the affinity of a process on the web that does the job. So problem solved.Thanks for sharing the links with us. Sorry we could not help here. Now we have some info about ""affinity option". Could you give an SIMPLE example of how ""affinity option" is a useful tool for XP? We would like that for our database here at CH. Quote from: Geek-9pm on April 16, 2010, 10:18:21 AM Could you give an simple example of how ""affinity option" is a useful tool for XP? We would like that for our database here at CH. The links pretty well illustrate that. Quote The links pretty well illustrate that. Yep. You are right. I had no idea of what all that was about until I read the first link over very carefully. There are people out there doing serious work with 16 bit programs. A modern high-performance PC can actually hang a process using the NTDVM. If anybody has strange random program hangs using NTDVM, read the links given by Kolya. A real world case of a problem and a solution using Windows tools and third party stuff. And MS is aware of the issue, says the link. This will NOT very likely be fixed in XP because it is near end-of-life. Quote from: Geek-9pm on April 16, 2010, 11:05:26 PM And MS is aware of the issue, says the link. This will NOT very likely be fixed in XP because it is near end-of-life. Consider that the "real world" example used a relatively ancient version of FoxPro... FoxPro is still being released as part of modern versions of Visual Studio. (I think) Quote from: BC_Programmer on April 16, 2010, 11:07:19 PM Consider that the "real world" example used a relatively ancient version of FoxPro... FoxPro is still being released as part of modern versions of Visual Studio. (I think) Now you HIT a nerve. MS has all but killed FoxPro. We could start a whole new thread about "Why MS hates FocPro." Or something like that. Quote from: Geek-9pm on April 16, 2010, 11:32:03 PM Now you hit a nerve. MS has all but killed FoxPro. We could start a whole new thread about "Why MS hates FocPro." Or something like that. what are you talking about? http://msdn.microsoft.com/en-us/vfoxpro/default.aspx A Service pack was released this month for it. It's not part of Visual studio anymore, though. It certainly outlived VB-COM.Thanks for the link. Good information. Still, after reading that, and some related links, IMO MS hates FoxPro. Or, to put it another way. If Microsoft were a parent. And FoxPpro was a 16 year old daughter. The Child Protection Service would find the parent ... guilty of mental and emotional trauma to the child.The parrot isn't for NOTHING, eh? Quote from: Geek-9pm on April 17, 2010, 12:47:25 PM If Microsoft were a parent. And FoxPpro was a 16 year old daughter. The Child Protection Service would find the parent ... guilty of mental and emotional trauma to the child. You do write nonsense sometimes, Geek-9PM.

Answer»

I know that at least in Windows Vista the START command has an affinity option to start a process with a specific processor affinity mask. For example:
START "Title" /affinity 1 cmd.exe

That option is not available for me on Windows XP Home SP3. Which is a shame because I only need it on XP (to start NTVDM). Any way to make this work?

Since NTVDM is a system file I don't want to change it with imagecfg or the like.In the upper right you see a searcdh box for this forum. Type in "NTVDM" WITHOUT the quotes and find lots of threads about that.
Also:
Troubleshooting MS-DOS-Based Programs in WindowsActually you'll find no threads at all about how to set the affinity of the NTVDM process. Or MUCH about affinity masks for that matter. Nor does the MS article you linked explain that.
If you need to know why I want to do that you can read this article.

Anyway, I found a utility to set the affinity of a process on the web that does the job. So problem solved.Thanks for sharing the links with us.
Sorry we could not help here. Now we have some info about ""affinity option".

Could you give an SIMPLE example of how ""affinity option" is a useful tool for XP?
We would like that for our database here at CH. Quote from: Geek-9pm on April 16, 2010, 10:18:21 AM

Could you give an simple example of how ""affinity option" is a useful tool for XP?
We would like that for our database here at CH.

The links pretty well illustrate that. Quote

The links pretty well illustrate that.

Yep. You are right. I had no idea of what all that was about until I read the first link over very carefully. There are people out there doing serious work with 16 bit programs. A modern high-performance PC can actually hang a process using the NTDVM.

If anybody has strange random program hangs using NTDVM, read the links given by Kolya. A real world case of a problem and a solution using Windows tools and third party stuff.

And MS is aware of the issue, says the link. This will NOT very likely be fixed in XP because it is near end-of-life. Quote from: Geek-9pm on April 16, 2010, 11:05:26 PM

And MS is aware of the issue, says the link. This will NOT very likely be fixed in XP because it is near end-of-life.

Consider that the "real world" example used a relatively ancient version of FoxPro... FoxPro is still being released as part of modern versions of Visual Studio. (I think) Quote from: BC_Programmer on April 16, 2010, 11:07:19 PM

Consider that the "real world" example used a relatively ancient version of FoxPro... FoxPro is still being released as part of modern versions of Visual Studio. (I think)

Now you HIT a nerve.
MS has all but killed FoxPro.
We could start a whole new thread about "Why MS hates FocPro."
Or something like that. Quote from: Geek-9pm on April 16, 2010, 11:32:03 PM

Now you hit a nerve.
MS has all but killed FoxPro.
We could start a whole new thread about "Why MS hates FocPro."
Or something like that.

what are you talking about?

http://msdn.microsoft.com/en-us/vfoxpro/default.aspx

A Service pack was released this month for it. It's not part of Visual studio anymore, though. It certainly outlived VB-COM.Thanks for the link. Good information.
Still, after reading that, and some related links, IMO MS hates FoxPro.

Or, to put it another way.
If Microsoft were a parent.
And FoxPpro was a 16 year old daughter.
The Child Protection Service would find the parent ...
guilty of mental and emotional trauma to the child.The parrot isn't for NOTHING, eh? Quote from: Geek-9pm on April 17, 2010, 12:47:25 PM

If Microsoft were a parent.
And FoxPpro was a 16 year old daughter.
The Child Protection Service would find the parent ...
guilty of mental and emotional trauma to the child.

You do write nonsense sometimes, Geek-9PM.

Solve : START with affinity option on windows XP?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment