RE: why System command returns right away?

[Tom Allebrandi]

Is WinRunner a GUI program? That is, does it create windows and things like that?   Try opening a MS-DOS Prompt/Command Prompt on 98 and NT and typing the command in by hand. My guess is that you will find that on NT/2000, you don't get another command prompt until WinRunner exits, BUT, that on 98 you will find that you get a command prompt back immediately. I've noticed this before about GUI apps on 9x.   I think that system() does the same thing that an MS-DOS Prompt/Command Prompt does and that's why you may be having the problem.   I'm a little surprised that Create Process() would be doing it however. What are you giving it as parameters?   --- tom tom all Brandi [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ted Zeng Sent: Tuesday, February 12, 2002 5:44 PM To: [EMAIL PROTECTED] Subject: why System command returns right away? I run activeperl on Win98 SE, where the script has a line system ( "..."); The command run WinRunner and a WinRunner script. the command lasts for a couple of min., but the perl script continues right away.   It doesn't have this problem on NT4, Win2000.   I also try to Win32:Process:Create to do the same and have the same problem.   How can the script waits until the command is finished before continue?   ted zeng Adobe Systems