Windows variables - (Moved)

[priedols]

Iam remaking .bat file to autoit

I have problems with windows variables

What is the best solution for theese code?

set dirpath=%~dp0
call "%dirpath%System\config.bat"


SET PATH_ORIG=%PATH%
SET PATH=%PATH%;%dirpath%System\bin;%path_to_perl%

 

[Melba23]

Moved to the appropriate forum, as the Developer General Discussion forum very clearly states:

Quote

General development and scripting discussions. If it's super geeky and you don't know where to put it - it's probably here.

---

Do not create AutoIt-related topics here, use the AutoIt General Help and Support or AutoIt Technical Discussion forums.

Moderation Team

[Exit]

;~ set dirpath=%~dp0
$dirpath = @WorkingDir & "\"

;~ call "%dirpath%System\config.bat"
ShellExecuteWait($dirpath & "system\config.bat")

;~ SET PATH_ORIG=%PATH%
$PATH_ORIG = EnvGet("PATH")

;~ SET PATH=%PATH%;%dirpath%System\bin;%path_to_perl%
EnvSet("PATH", EnvGet("PATH") & ";" & $dirpath & "System\bin;" & EnvGet("path_to_perl"))

 

Edited April 29, 2019 by Exit

[priedols]

How I can read path_to_perl frpm config.bat file.

Path_to_perl is windows variable.

With just Envget("path_to_perl") it doesn't work.

 

Thx for making my code simpler.

[Nine]

23 hours ago, priedols said:

SET PATH=%PATH%;%dirpath%System\bin;%path_to_perl%

What do you mean, windows variable ?  Is it an environment variable ?  @Exit code is correct, based on your code.

[priedols]

I define path_to_perl in config.bat, so i want get it from config.bat

[priedols]

7 minutes ago, Nine said:

What do you mean, windows variable ?  Is it an environment variable ?  @Exit code is correct, based on your code.

I define path_to_perl in config.bat, so i want get it from config.bat

[Nine]

How do you define it in the config.bat file ?  Show your code...

[priedols]

Just now, Nine said:

How do you define it in the config.bat file ?  Show your code...

SET path_to_perl=%path_to_inpass%\System\perl\bin
 

This is written in config.bat

[Nine]

So this is an environment variables, so what do you get when you do :

MsgBox ($MB_SYSTEMMODAL,"",EnvGet("path_to_perl"))

 

[priedols]

1 minute ago, Nine said:

So this is an environment variables, so what do you get when you do :

MsgBox ($MB_SYSTEMMODAL,"",EnvGet("path_to_perl"))

 

I got nothing

[priedols]

Just now, priedols said:

I got nothing

 

2 minutes ago, Nine said:

So this is an environment variables, so what do you get when you do :

MsgBox ($MB_SYSTEMMODAL,"",EnvGet("path_to_perl"))

 

 

In the begining of code i execute I run config.bat file, to get theese variables

[Nine]

Ah, do the same in autoit script then or read config.bat file (FileRead) and parse the content to find the variables you need...

[Earthshine]

so how do you call the bat? are you passing in the path to perl?

you could always look it up in the registry

[priedols]

I want to read from .bat file becouse theese variables are for other files too.

[priedols]

2 minutes ago, Earthshine said:

so how do you call the bat? are you passing in the path to perl?

you could always look it up in the registry

EnvSet("dirpath", @ScriptDir)
ShellExecuteWait(EnvGet("dirpath") & "\System\config.bat")

[Earthshine]

give us all your code AND the batch file. tired of the guessing game. i would look up the perl path from registry. 

Edited April 30, 2019 by Earthshine

[priedols]

3 minutes ago, Earthshine said:

give us all your code AND the batch file. tired of the guessing game. i would look up the perl path from registry. 

I can't give all code.

[Nine]

The issue you have is that newly created environment variables are discarded at the end of the DOS session.  You can manually test it by starting a DOS session (cmd.exe) set a variable, exit, come back, and the variable you just created is not there anymore.  I believe it is the same with ShellExecuteWait ().  So the best solution would be (as I already told you) to read the config.bat file and parse it. Or like @Earthshine told you, read it from registry...

[priedols]

1 minute ago, Nine said:

The issue you have is that newly created environment variables are discarded at the end of the DOS session.  You can manually test it by starting a DOS session (cmd.exe) set a variable, exit, come back, and the variable you just created is not there anymore.  I believe it is the same with ShellExecuteWait ().  So the best solution would be (as I already told you) to read the config.bat file and parse it. Or like @Earthshine told you, read it from registry...

Ok, thx.