MsgBox miss output if the binary has many zeros at ending...

[oceanwaves]

Hi guys,

  The code as below:

#include <WinAPI.au3>

Local $iRead = 0
$hFile = _WinAPI_CreateFile("test.txt", 2, 2); the file content is :"just unicode."
$tBuffer = DllStructCreate("byte text[1000]")
;$tBuffer = DllStructCreate("char text[1000]")
$pBuffer = DllStructGetPtr($tBuffer, "text")
_WinAPI_ReadFile($hFile, $pBuffer, 1000, $iRead)

;you can see that has many zeros...
MsgBox(4096, "", DllStructGetData($tBuffer, "text") & @CRLF & _
        StringToBinary("just unicode.") & @CRLF)

$s = BinaryToString(DllStructGetData($tBuffer, "text"))

; In here, just output one string "just testing", no StringToBinary("just unicode.") & @CRLF
MsgBox(4096, "", $s & @CRLF & _
    StringToBinary("just unicode.") & @CRLF); it's missed..

I found the last MsgBox output only string, not as my expectation result. So why? Thanks for your help advance.

[Melba23]

oceanwaves,

Windows regards Chr(0) as an "end of string" marker. As the MsgBox function calls the Windows API to display the required text, Windows truncates the test at the first Chr(0) it finds. Simple really.

M23

[oceanwaves]

 

oceanwaves,

Windows regards Chr(0) as an "end of string" marker. As the MsgBox function calls the Windows API to display the required text, Windows truncates the test at the first Chr(0) it finds. Simple really.

M23

 

Thanks for your reply. It means I have to remove these zeros by manual. Because when I try to compare (BinaryToString($OriginalString)-->normal ver) with (BinaryToString($s)--->Includes many zeros ver), system thinks the 2 strings are different, but actually they are the same after translated from bingary to string, at least from human views....

[Melba23]

oceanwaves,

It really helps if you post the code you use - just saying "system thinks the 2 strings are different" when I cannot tell which two strings you are comparing is not much of a clue.

M23

[oceanwaves]

oceanwaves,

It really helps if you post the code you use - just saying "system thinks the 2 strings are different" when I cannot tell which two strings you are comparing is not much of a clue.

M23

HI M23,

  Appreciate your nice help. . The code as below:

#include <WinAPI.au3>
Local $iRead = 0
$hFile = _WinAPI_CreateFile("test.txt", 2, 2); the file content is :"just unicode."
$tBuffer = DllStructCreate("byte text[1000]")
;$tBuffer = DllStructCreate("char text[1000]")
$pBuffer = DllStructGetPtr($tBuffer, "text")
_WinAPI_ReadFile($hFile, $pBuffer, 1000, $iRead) ;you can see that has many zeros...
MsgBox(4096, "Binary", DllStructGetData($tBuffer, "text") & @CRLF & _
        StringToBinary("just unicode.", 1) & @CRLF)
$s = BinaryToString(DllStructGetData($tBuffer, "text"))
MsgBox(4096, "$s", $s)
If $s == "just unicode." Then MsgBox(4096, "", "equal!!!"); Never pop up, why?

The last statement will not be performed. Yes, because they have different "Binary", maybe someone will say. But after using BinaryToString funcion, they looks like be same. So for the string comparison, Autoit actual using binary caomparison?

[Melba23]

oceanwaves,

The 2 strings are not identical. The string $s is as many bytes as there are in the buffer converted to ASCII - the literal string to which you compare it is much shorter. Try adding this at the end of that script and see what you get:

$iLen_1 = StringLen($s)
$iLen_2 = StringLen("just unicode.")
ConsoleWrite($iLen_1 & " - " & $iLen_2 & @CRLF)

So there is no chance that the comparison will ever be True.

What exactly are you trying to do with all this anyway?

M23

[oceanwaves]

oceanwaves,

The 2 strings are not identical. The string $s is as many bytes as there are in the buffer converted to ASCII - the literal string to which you compare it is much shorter. Try adding this at the end of that script and see what you get:

$iLen_1 = StringLen($s)
$iLen_2 = StringLen("just unicode.")
ConsoleWrite($iLen_1 & " - " & $iLen_2 & @CRLF)

So there is no chance that the comparison will ever be True.

What exactly are you trying to do with all this anyway?

M23

 

Hi M23,

  Last week, I tried to understand Windows named pipes, and refer to example script under Autoit3/examples/GUI/advance. During the modify and debug example script, I found this problem..I supporse I received some message from clinet and maybe I need compare with something then decide what do we do...balabalabala....

   However, I really appreciate your answers  with patience. Now I know I need remove the zero by myself.