Adding Command Line Parameter

[water]

Strange. I have UPX enabled and it works fine here.

I have the same Windows version you have "Microsoft Windows [Version 6.1.7601]".

As this is my first CUI script there might be some stuff I - yet - don't understand.

Edited March 19, 2012 by water

[johnmcloud]

You have Windows 7 x64? 3.3.8.0? It's a bug? What i need to do?

Too many question

[UEZ]

Why you are using a for/next loop with step 2?

Try this:

$sTitle = "Test Script"
If $CmdLine[0] > 1 And $CmdLine[1] = "/name" Then
    MsgBox(64, "Passed Parameters", "/name is " & $CmdLine[2])
Else
    MsgBox(16, "Error", "Wrong parametes are given. Try asd.exe /name <parameter2>")
EndIf

Br,

UEZ

Edited March 19, 2012 by UEZ

[water]

I run 3.3.8.1.

UPX is a compressor so maybe your anti virus program gets nervous

I would suggest to disable UPX for this script.

[water]

Why you are using a for/next loop with step 2?

Because if he has more parameters in the format "/parametername value" the script can evaluate the parameters pair by pair.

[johnmcloud]

It's not my script, i don't have idea how $CmdLine works and why not work the ConsoleWrite

Same problem:

#AutoIt3Wrapper_Change2CUI=y
$sTitle = "Test Script"
If $CmdLine[0] > 1 And $CmdLine[1] = "/name" Then
ConsoleWrite("Passed Parameters" & $CmdLine[2])
Else
MsgBox(16, "Error", "Wrong parametes are given. Try asd.exe /name <parameter2>")
EndIf

[johnmcloud]

I run 3.3.8.1.

UPX is a compressor so maybe your anti virus program gets nervous

I would suggest to disable UPX for this script.

I don't have antivirus installed on the test machine, it's not on LAN or Internet

EDIT: Tested 3.3.8.1, nothing change

Edited March 19, 2012 by johnmcloud

[UEZ]

I tested it on Win7 x64 running it as x86 and x64 on AutoIt v3.3.8.1 and it is working properly.

Strange....

Br,

UEZ

[water]

I would stick with the solution you mentioned which works for you:

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_Change2CUI=y
#AutoIt3Wrapper_Res_requestedExecutionLevel=asInvoker
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

[johnmcloud]

Work also with:

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Change2CUI=y
#AutoIt3Wrapper_Res_requestedExecutionLevel=asInvoker
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

The problem is i don't need to set it "manually", with copy-paste. But i need to click on Compile --> Create CUI. Than if i build it work

Why i have:

#AutoIt3Wrapper_Res_requestedExecutionLevel=asInvoker

I have only selected Create CUI

Edited March 19, 2012 by johnmcloud

[water]

I think it has to do with UAC in Window 7.

You activate a selectbox and get 2 entries in your script - fine.

The script then works - fine too.

So I would stick with this two entries.

[johnmcloud]

It's TOTALLY crazy!

If i add #RequreAdmin the ConsoleWrite on CMD don't work, again....

If i remove it work, but i need it. Man....without admin rights some command don't work.

One word: Crazy.

[water]

#RequireAdmin starts a new process (according to the docu).

If you run this modified version you will see that a second console window pops up and the text "Finished!" is displayed there.

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_Change2CUI=y
#AutoIt3Wrapper_Res_requestedExecutionLevel=asInvoker
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
#RequireAdmin
$sTitle = "Test Script"
If Mod($CmdLine[0], 2) <> 0 Then Exit MsgBox(16, $sTitle, "Invalid number of parameters! has to be a multiple of 2!")
If $CmdLine[0] = 0 Then Exit MsgBox(16, $sTitle, "No parameters passed!")
For $i = 1 To $CmdLine[0] Step 2
    If $CmdLine[$i] = "/name" Then MsgBox(64, "Passed Parameters", "/name is " & $CmdLine[$i+1])
Next
ConsoleWrite("Finished!")
MsgBox(16, "", "Wait ...")

Edited March 19, 2012 by water

[johnmcloud]

So i have an alternative to #RequireAdmin?

I need cmd with admin privilege for launch command, i can't use RunAs because need to work on other pc, so i'using RunWait

Or i need to giveup of ConsoleWrite on cmd? Thats the problem, the script work fine until ConsoleWrite.

Edited March 19, 2012 by johnmcloud

[water]

I don't think so. If you require admin privileges then you require them.

The only problem is, that the output is written to a second console window.

Do you need the console output just to inform the user?

[johnmcloud]

For /? how-to-use and confirm operation, i can make MsgBox but it's better to make output in the same window like a real command line interface.

[water]

The only way I can think of to achieve what you want is to split your code into two scripts.

Script one runs with user privileges and does all the console writing.

If a function that requires admin privileges is used script 2 with #RequireAdmin is called.

A bit complicated, I know ...

[johnmcloud]

It's not a bad idea...i'll test it but i don't know how to call a second script, the extension isn't .au3 if i remember right. Or better to use #include?

Please post a stupid example

Second problem, i don't know how to merge the classic script (Func fileopendialog) and cmd. If i double click on it do fileopendialog, if i open i cmd with parameter do other command. How to do that?

Thanks for your time

Edited March 20, 2012 by johnmcloud

[water]

You have two scripts and compile both to an exe. Script 1 then uses function "Run" or "RunWait" to call the second exe.

[johnmcloud]

I have try to create a simply UDF:

The UDF

#include-once
#RequireAdmin

Func _Test($handle)
MsgBox(0,0,$handle)
EndFunc   ;==>_Test

The script

#include <Test.au3>

MsgBox(0,0,"Is admin?")
_Test("asd")

When i'm open the script, it open like admin not only when i call the UDF...

The .exe solution can't work in my case, i can't create 4 exe's for operation

Other solution or maybe is wrong the UDF?

Edited March 20, 2012 by johnmcloud