I have a VB5 application that needs to launch a 16-bit Windows application
and then wait for it to close.

I know that under Windows NT 16-bit Windows and MS-DOS programs run under
Virtual Dos Machines (VDM). In addition 16-bit Windows apps use WOW(Windows
on Win32).  If I use the VB Shell command, the program launches but Shell
returns a 0 for the Process ID.  If I use CreateProcess API call, the
program will only launch if NTVDM and WOWEXEC are alredy running.  If not, I
get an error message from NTVDM that says Config.NT is not setup to start
Windows applications.  I like the way CreateProcess works because it returns
a handle that I can use with WaitForSingleObject to determine if the app
closed.

Has anyone ever done this before?  Let me know if you have any ideas.  I
will update this if I get anywhere.

Here's a 16-bit Windows solution - I don't know if it works in NT, but
it might point you in the right direction.  The 32-bit solution is
completely different.

In declarations section:
Declare Function GetModuleUsage% Lib "Kernel" (ByVal hModule%)

Dim x%
x = Shell("NOTEPAD.EXE")      
While GetModuleUsage(x) > 0  
      DoEvents
Wend

Tom.