RunShell() in the Alaska 2.0

[Eugene Lutsenko]

For some reason, RunShell () in Alaska 2.0 does not start the Eidos system, it starts the archive for unpacking

RunShell("",'__aidos-x.exe',.T.)
RunShell("","Downloads.exe",.F.)

[rdonnay]

Does your Eidos system require command line parameters?

[Eugene Lutsenko]

Parameters are not required

[rdonnay]

Just put some debugging in your code.

Do you use WTF?

[Eugene Lutsenko]

I use it, but very rarely. Just RunShell does not start the Eidos system, but it runs other programs

[rdonnay]

RunShell does not start the Eidos system, but it runs other programs

That does not sound right to me.
I believe you have a mistake in your program.

[Eugene Lutsenko]

I will look more closely

[Victorio]

Eugene

RunShell("",'__aidos-x.exe',.T.)
RunShell("","Downloads.exe",.F.)

You mean, __aidos-x.exe not run and Downloads.exe run ?

I see first row you have apostrophe, second quotation marks, is it ok ? can you try quotation marks on both ?
third parameter .F. sync, .T. async, this look aidos you run async, then run aidos and download paralell, what do downloads.exe not blocking aidos-exe ?
and if you put fourth parameter to .F., not hide, what you see in command line black window ?

[Eugene Lutsenko]

I found out why it seemed that RunShell did not launch the Eidos system. It turned out that he started it, but it was not executed under w10. And all because I set the date of the executable module in the directory of the 19th year, so that the update was downloaded. It was downloaded. And then this executable module that was downloaded just didn't run under w10. Not only does it RunShell, but it doesn't run manually. And with the new executable module made in Alaska 2.0, everything is fine and is updated and launched.