Sign in to follow this  
Followers 0
ReFran

Runs with Scite (beta run) but not direct

8 posts in this topic

#1 ·  Posted (edited)

Hello,

I've a Script which runs fine if I edit it in SciTE and run it via "Beta run". If I run it direct I get a system error msg (find.exe product an error and will be closed ...).

$vFilename = "Boot.ini"
$vFileDir = "C:\"
$xGet = Run(@ComSpec & " /c find /c ""/Outlines"" """&$vFileName &"""", $vFileDir, @SW_HIDE, 2 + 4)
ProcessWaitClose("find.exe",10)
MsgBox(0,"Out",StdOutRead($xget))

I tried also the form given in the help file. But with the same result. A compareable command with another command-line tool works fine.

Perhaps someone can test/correct it?

MfG. Reinhard

PS: I think Valik will be enjoyed that I didn't put it under "Bug Reports". At least that I've learned ;-).

Edited by ReFran

Share this post


Link to post
Share on other sites



Beta is not associated in the registry with Au3 files by default. This is why Scite has a two way setup for public release and beta operation so you can operate with beta scripts.

The public release will not like your use of Run() or StdOutRead as it is not native to it.

Share this post


Link to post
Share on other sites

.... The public release will not like your use of Run() or StdOutRead as it is not native to it.

Mmmh ...

.... and what means that to me?

Share this post


Link to post
Share on other sites

You are using functions or parameters that were never released with AutoIt v3.1.1 final.

The registry points to the 3.1.1 final directory. So you either use Scite to run your beta scripts, or you could do an approach like overwrite the 3.1.1 directory with a beta version, that would give you external beta operation then. Another idea is to use my shell extension program with has beta run and compile here. Only ideas that I have at present.

Share this post


Link to post
Share on other sites

Mmmh ...

.... and what means that to me?

Right mouse click on a file.au3 file and then selecting "Run Script" will run the latest Production version of AutoIt3 and that version of AutoIT does not support this parameter in the Run command.


Visit the SciTE4AutoIt3 Download page for the latest versions        Beta files                                                          Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

I changed my file-association to "Run with Beta" (....85), "Run Script". That's not the problem and the behaviour in beta and the latest official release is the same.

" ... and that version of AutoIT does not support this parameter in the Run command".

The parameter I took from the beta-helpfile. Also if I took only StdOutRead (run(................,2) there is no difference. Also my other command only using another exe works fine.

$xGet = Run(@ComSpec & " /c " &$pdfAsm &" -b" &$vFileDirShort _
                &" -M" &stringReplace($vFileName," ","?") &" -gN", @SystemDir, @SW_HIDE, 2) ProcessWaitClose ( "mbtPdfAsm.exe", 10)
    $line = StdoutRead($xGet)

I know I can do it with piping it into a file ( > out.tmp). But I think it will be slower.

Thank you both, Reinhard

Share this post


Link to post
Share on other sites

I would try putting a removing the last 2 paramters from the Run function (don't hide the window and don't capture STDOUT or STDERR) and place a Sleep(5000) function after the Run function, then watch the console window and see what it actually happening with your call to FIND.


Yes yes yes, there it was. Youth must go, ah yes. But youth is only being in a way like it might be an animal. No, it is not just being an animal so much as being like one of these malenky toys you viddy being sold in the streets, like little chellovecks made out of tin and with a spring inside and then a winding handle on the outside and you wind it up grrr grrr grrr and off it itties, like walking, O my brothers. But it itties in a straight line and bangs straight into things bang bang and it cannot help what it is doing. Being young is like being like one of these malenky machines.

Share this post


Link to post
Share on other sites

I would try putting a removing the last 2 paramters from the Run function (don't hide the window and don't capture STDOUT or STDERR) and place a Sleep(5000) function after the Run function, then watch the console window and see what it actually happening with your call to FIND.

Thanks for the hint, Dave. I tested it. Without the optional parameters it works fine. Also if I use CMD switch /k with @SW_Minimize it works fine. I tested also to filter the output of finde.exe with more.exe only to involve another tool into the process. But when I use STDOUT switch (,2) it runs only via SciTE - not direct - independent from the lines after the run command.

It's just curios, also the differences between SciTE and direct execution. But I think sometimes it happens and I will look for an other solution.

Best regards, Reinhard

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0