walle Posted July 1, 2008 Share Posted July 1, 2008 (edited) Solved Edited July 3, 2008 by walle Link to comment Share on other sites More sharing options...
ChrisL Posted July 1, 2008 Share Posted July 1, 2008 If thats an example your reading the error stream not the stdout stream, why do you need to run it as @comspec? Why not just call unrar.exe directly with the command line options? [u]Scripts[/u]Minimize gui to systray _ Fail safe source recoveryMsgbox UDF _ _procwatch() Stop your app from being closedLicensed/Trial software system _ Buffering Hotkeys_SQL.au3 ADODB.Connection _ Search 2d Arrays_SplashTextWithGraphicOn() _ Adjust Screen GammaTransparent Controls _ Eventlogs without the crap_GuiCtrlCreateFlash() _ Simple Interscript communication[u]Websites[/u]Curious Campers VW Hightops Lambert Plant Hire Link to comment Share on other sites More sharing options...
walle Posted July 3, 2008 Author Share Posted July 3, 2008 If thats an example your reading the error stream not the stdout stream, why do you need to run it as @comspec? Why not just call unrar.exe directly with the command line options? Ah, my bad, wrote wrong. But, the problem still remains. Local $iPID = Run("C:\Documents and Settings\DIR\My Documents\Burnbuddy\unrar.exe" & " vb " & "E:\DVDR\DIR\sub-rtcrp.rar", "", @SW_HIDE, 4 + 2) Local $sStdOutRead = "" While ProcessExists($iPID) $sStdOutRead &= StdoutRead($iPID) sleep(500) WEnd msgbox(0,"",$sStdOutRead) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now