| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Waiting for it |
Hi Keith, Did you resolve your problem with WinExec and Windows-95 ? I had to write a little 16-bit Win-95 program tonight which would change the system date, execute a program and then restore the date when the Exec'd program had terminated. I was able to use WinExec without any problem. FWIW, I had a quick look at the Win-32 reference for CreateProcess and if you want your program to wait until the called program has started you'd have to be a real masochist to use it. There was no reference to WinExec failing, in fact it stated that WinExec made all the right calls to CreateProcess. Personally, I'd only use CreateProcess if you want to get control back before the Exec'd program had hooked into the message queue, opened a window or something similar like needing to control the new process with some sort of synchronisation. For a simple Start/Wait/Continue scenario, WinExec is a lot less work. Especially if you want to send some fake keystoke stuff to the new process. Regards, Brenton @EOT: ---* Origin: TestPoint (3:711/934.7) SEEN-BY: 711/934 712/610 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.