Custom Query

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (160 - 162 of 3856)

Ticket Resolution Summary Owner Reporter
#637 No Bug StdoutRead function seems to now miss data on public and beta releases fill_hard@…
Description

I updated to the latest Public (3.2.12.1) and found my script no longer worked. On debuging found that StdoutRead failed to return all of the data, it seems to miss the last line.

Thanks for the speedy response to my previous bug report about this problem, I have tried both solution you suggested and I'm still getting the same output as before.

Listing C:\Documents and Settings\TestUser\ New files added to this directory will not be encrypted.

Not

Listing C:\Documents and Settings\TestUser\ New files added to this directory will not be encrypted.

U My Documents

I'm I still doing it wrong ?

Here are my modified scripts.

Modified Script 1:

#include <Constants.au3>

$STDOUTData = "" $Cipher = Run (@SystemDir & "\cipher " & """" & @MyDocumentsDir & """", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)

ProcessWaitClose($Cipher) $STDOUTDATA = StdoutRead($Cipher)

MsgBox (0, "STDOUT Read Data:", $STDOUTData)

Modified Script 2:

#include <Constants.au3>

$STDOUTData = "" $Cipher = Run (@SystemDir & "\cipher " & """" & @MyDocumentsDir & """", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)

While 1

$STDOUTData &= StdoutRead ($Cipher) If @error Then ExitLoop

Wend

MsgBox (0, "STDOUT Read Data:", $STDOUTData)

#638 No Bug StdoutRead function returns null character mid string in default text mode fill_hard@…
Description

I updated to the latest Public (3.2.12.1) and found my script no longer worked. On debuging found that StdoutRead seem to miss the last line of data, this is not the case, it is returning all of the data, but with a null character between the two data segments, even when using the default text option.

I'm sure this is how Cipher.exe is outputing the data. However it has the effect of stopping you seeing the data in the output text string using a msgbox, writing the text to a file using FileWriteLine. It can still be checked for with in the text sting using a StringInStr. If you string the data any text after the null character is lost.

Previous versions gave the complete text output without the null character. Is this a bug or by design ?

$Cipher = Run (@SystemDir & "\cipher " & """" & @MyDocumentsDir & """", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)

Using binary mode you get an output of:

0x0D0A204C697374696E6720433A5C446F63756D656E747320616E642053657474696E67735C753737353136305C0D0A204E65772066696C657320616464656420746F2074686973206469726563746F72792077696C6C206E6F7420626520656E637279707465642E0D0A0D0A000x45204D7920446F63756D656E74730D0A00

#647 No Bug Compiler Parsing pdaughe
Description

The following presents a problem particularly when using the Execute statement:

$A = 1
$A = $A +++++- 1
MsgBox (0, "Test", "A = " & $A)

No syntax or run-time error is given.

Note: See TracQuery for help on using queries.