Run command sets RP_WIN64PROCESS=0

[Grovkillen]

Code: Select all

Let>RP_WIN64PROCESS=1
Run>cmd /c
//RP_WIN64PROCESS=0 after the command is executed... 

Seems like a bug?

EDIT: The manual tells me (in text) that the RP_WIN64PROCESS is used to temporarily set the process to 64 bit. No other parameter is working this way and to me it would be more clear if the variable was named RP_TEMP_WIN64PROCESS or something. But I can see why it's a good way of having a temp variable. Perhaps other variables could be used this way too, like the CF_OVERWRITE which could be reset to whatever it was before the CopyFile command was executed.

[Dorian (MJT support)]

I'm waiting for Marcus to confirm, but I think this may be by design, as the help file describes it as temporary...

"If attempting to run a 64 bit system process residing in the System32 folder on Windows x64 you can set RP_WIN64PROCESS to 1 to temporarily disable file system redirection."

[Grovkillen]

I see, but it's not like everything else is behaving and need to be more clear in the instruction manual in my humble opinion.

[Dorian (MJT support)]

Point taken.