P
Hi List,
I have an application that controls an x-ray analyzer through a legacy MS-DOS Application.
Everything works fine until the user close my VB application, the child MS-DOS application won't close.
It shows up in the task list with the "Winoldap" name, and prevents the VB application from re-connecting to the analyzer.
If the operator goes into the win95 task list and presses the "End task" button then another window comes up "Unable to end task", and then the "End task" button works.
Can I put some code in my VB application to ensure this MS-Dos child process is closed properly.
Pierre R. Hinse CET My opinions are my own.
BESTECH Engineering Business mailto:[email protected]
tel:705 675 7720x203 Personal mailto:[email protected]
fax:705 675 5507 http://www.bestech.com
I have an application that controls an x-ray analyzer through a legacy MS-DOS Application.
Everything works fine until the user close my VB application, the child MS-DOS application won't close.
It shows up in the task list with the "Winoldap" name, and prevents the VB application from re-connecting to the analyzer.
If the operator goes into the win95 task list and presses the "End task" button then another window comes up "Unable to end task", and then the "End task" button works.
Can I put some code in my VB application to ensure this MS-Dos child process is closed properly.
Pierre R. Hinse CET My opinions are my own.
BESTECH Engineering Business mailto:[email protected]
tel:705 675 7720x203 Personal mailto:[email protected]
fax:705 675 5507 http://www.bestech.com