Hi Doug, On Windows, be sure to set the timeout value for the Shell. The default is 0ms. IIRC, -1 = infinite.
Tim -- Tim Jones [EMAIL PROTECTED] Quoting Douglas Anderson <[EMAIL PROTECTED]>: > Anyone run into this? I build a Windows Desktop Application that > contains something like this: > > dim s1 as new shell > s1.Mode = 1 > s1.Execute otherapp.exe > > while s1.IsRunning > app.DoEvents() > wend > > s1.close > > This works great, it executes the command line and waits for it to > finish (or so it would appear). If I use the same code in a Windows > Console Application the s1.running is always stuck on 'running'...It's > like the other application never gives up control or my 'main app' > doesn't believe it has. I can use: > > s1.mode = 0 > > but I have no way of knowing if the app has finished or not as it > releases immediately. > > Any help would be appreciated. > > Doug. > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives of this list here: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
