Get Windows PID from DOS session

[jabhawk2]

I an running scheduled jobs on a Windows server that launch a FPD 2.6 session and there are a few NTVDM sessions that hang. Our process logs say that the jobs all ran to completion but we still have the system processes running and taking up resources.

Some jobs are BAT files and some are direct command line foxpro executable calls.

Is there a was from a FP DOS session to get the Windows PID value? If we write out the value to our log we can quickly identify a dead process.

Thanks

 

[DSummZZZ]

NTVDM (NT Virtual DOS Machine) gets loaded any time a 16 bit application is executed. It stays memory resident until you either stop it or reboot, even after the application requiring it has completed.
If you are going to be running that process on a regular basis, it won't hurt to leave NTVDM running. Even though it has used a bit of memroy, it will basically just sit there and do nothing until it is needed again.

To answer your question though, FPD was written to run under DOS, so it wouldn't know anything about Windows. You would have to call an API to get the PID, which from FPD isn't doable without using some other sort of batch file and calling scripting host or some other Windows application. Possibly a VFP app.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[jabhawk2]

I am agreed that FPD cannot reach out and get the PID nativly but the tasks I have issues with are launched from BAT files.

If I have the process Id of that DOS session I can write it out to a log file within the BAT and use that data to later determine which tasks are not closing out correctly and releasing NTVDM.

What I need is a batch command that will return the PID of the DOS session. Any thoughts????
Jon

 

[DSummZZZ]

Well, like I said, using scripting host should work. It can be run from a batch file. (Do a search on Windows Scripting Host or WSH. You will find all sorts of examples)
You could probably keep track of PIDs prior to running your batch processes, then compare with what's running afterward.

But if all you're concerned with is getting rid of those processes, why not use something like "kill" to just kill the running NTVDM processes?

Try this link:

http://support.microsoft.com/kb/197155

-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[ezopaci]

You can get hwnd of the window in which runs ntvdm and then you can (i think) read PID using some winapi.
I have the console utility program which can obtain hwnd of active console, but it can not obtain pid. But source code is open

It was described here.

http://www.tek-tips.com/viewthread.cfm?qid=1365014&page=1

If you use it and modify this code for obtain this, pls. send it to me.


Tomas