dosExecute plugin

[Afrow UK]

Check the readme again. Tip: Use Exec not Wait.

Stu

[Afrow UK]

I have uploaded a new version of the plug-in.

* Added Unicode build (just noticed there was already a Unicode build in this thread but never mind - this version has been tested at least).
* Uses new plug-in API (/NOUNLOAD not necessary with /ASYNC).
* Added /DISABLEFSR switch to disable WOW64 file system redirection on Windows x64 for the internal ExecDos thread (the old version would fail if the executable was in system32).

http://nsis.sourceforge.net/ExecDos_plug-in

Stu

[HaMsTeYr]

Afrow, I noticed that the log files are encoded in UTF-8. Is there anyway to change that to UTF16-LE?

I'm writing a piece of code at the moment, and I'm trying to read Unicode characters into the stack, via an external file. I'm using the NSIS Unicode build at the moment.

I have tried executing to function instead of out to log, but it seems that only outputting it out to the log keeps the Unicode characters as they are.

I can think of only a few ways to do this, like a FileRead that works for UTF-8 (Using FileRead screws up the characters, and FileReadUTF16LE is no better.)

Another alternative is to stick of course, with FileReadUTF16LE, but the file has to be encoded in UTF-16 LE as well, if not it also becomes a garbled mess.

I know it may seem like asking for much, but would you happen to know any way around this?

[Afrow UK]

Someone asked for an x64 build of the plug-in (included as ExecDos64.dll along with the 32-bit ANSI/Unicode builds). Built using latest plug-in API source from SVN. Tested using the NSIS x64 build from https://bitbucket.org/dgolub/nsis64.

http://nsis.sourceforge.net/ExecDos_plug-in

Stu

[systracer]

Hi, in my tests ExecDos does not support unicode (ASCII is OK) using /tofunc. For example, I am making a cmd file with the following content:

@echo Тестовое сообщение (Test message)

ExecDos::exec '"$SYSDIR\cmd.exe" /c $EXEDIR\Test.cmd' "" "$EXEDIR\Test.txt"
Pop $0

Here Test.txt contains the correct encoding and the message can be read. And in what encoding the cmd file was, the result will be in this (I tried 866 and 1251).

But if I use the following code:

Function Test
Pop $0
FileWrite $R0 '$0' ; or FileWriteUTF16LE /BOM
FunctionEnd

FileOpen $R0 "$EXEDIR\Test.txt" w
GetFunctionAddress $R1 Test
ExecDos::exec /tofunc '"$SYSDIR\cmd.exe" /c $EXEDIR\Test.cmd' "" $R1
Pop $0
FileClose $R0

The result is always bad.

Test.cmd is Windows 866:
1) FileWrite: "???????? ????????? (Test message)"
2) FileWriteUTF16LE /BOM: "ﾒﾥ￡￢ﾮﾢﾮﾥ ￡ﾮﾮﾡ￩ﾥﾭﾨﾥ (Test message)"

Test.cmd is Windows 1251:
1) FileWrite: "???????? ????????? (Test message)"
2) FileWriteUTF16LE /BOM: "ￒ￥￱￲￮￢￮￥ ￱￮￮￡￥￭￨￥ (Test message)"

Please help fix the problem.

[systracer]

Is this plugin no longer supported? Unfortunately, I couldn't find a better plugin for transferring output to a function, and this one has problems with Unicode.

[Anders]

What happens if you just use MessageBox in the Test callback? Is it correct?

What if you do cmd.exe /U /C ...?

[systracer]

Anders, thanks for the answer!

Test.cmd in Windows 866, cmd /c + MessageBox = "ﾒﾥ￡￢ﾮﾢﾮﾥ ￡ﾮﾮﾡ￩ﾥﾭﾨﾥ (Test message)"
Test.cmd in Windows 866, cmd /u /c + MessageBox = "5AB>2>5 "
Test.cmd in Windows 1251, cmd /c + MessageBox = "ￒ￥￱￲￮￢￮￥ ￱￮￮￡￥￭￨￥ (Test message)"
Test.cmd in Windows 1251, cmd /u /c + MessageBox = "e%EQNBNE "
Test.cmd in Windows UTF8, cmd /c + MessageBox = "￐ﾢ￐ﾵ￑ﾁ￑ﾂ￐ﾾ￐ﾲ￐ﾾ￐ﾵ ￑ﾁ￐ﾾ￐ﾾ￐ﾱ￑ﾉ￐ﾵ￐ﾽ￐ﾸ￐ﾵ (Test message)"
Test.cmd in Windows UTF8, cmd /u /c + MessageBox = "h%2h%a%d%d%h%[%h%ﾓ%h%[%h%a% "

[Anders]

Testing with cmd is not ideal. I assume you are really going to execute a real application? Does this app write utf-16 to stdout? Or does it write using the active code page and you need the plug-in to convert?

[systracer]

I work with cmd files, so I am giving them as an example. There is no problem without /tofunc, which is why I report this problem.

[Anders]

The Unicode version of the plug-in is broken as far as I can tell.

Just by looking at the code, the only Unicode handling seems to be that the stdin string is converted from Unicode to CP_ACP and written to the pipe with WriteFile.

There is no handling of the output as far as I can tell.

You can try contacting the author. In the mean time, write it directly to a file instead.

ExecDos::exec '"c:\UnicodeConTest.exe"' "" "$temp\outtmp.txt" ; UTF16-LE passes through untouched

The output when sent to the function or a window/details seems to be converted although I'm not sure where.