AutoHotkey Community

Still works OK. What were the bugs? Could you explain in a bit more details?

The main issue seems to be with calling PeekNamedPipe too frequently. On my system the errors seemed to appear when the CPU load hit 99-100% when calling PeekNamedPipe. More often than not when/if there was a sudden increase. Increasing the sleep value reduced the frequency of calls to PeekNamedPipe and seemed a bit more stable but the sleep times seemed to vary a bit and CPU load still ended up reaching at or near 100% and causing an error.

To try and avoid the variable sleep time issue I added a time comparison to enforce a minimum time between calls to PeekNamedPipe. If enough time hasn't elapsed between calls, the function continues to sleep until enough time has passed to give pipe operations a bit more time to complete. The time between calls I added seemed like a comfortable setting on my system but I haven't tested with slower machines yet... To test I did multiple runs with a few applications running and 3 test scripts running at the same time with loops of 400 each. Everything seemed to run ok. The CPU usage showed 100% but the system still seemed quite responsive and didn't give any output errors.

It seemed a bit more accurate with the testing I had done but it may not have really been the case...

Yes. The functions wouldn't work when initialized with 0 and having no content.

I am trying to use this function with cmdline.exe from here:
http://www.autohotkey.com/forum/viewtopic.php?t=1814

(to get command line parameters that were used to launch a process)

...but the returned text is incomplete: It starts off ok, then the text jumps to a bit about half way down the proper output and ends there. Any ideas?

Hi evl,

Thanks for the feedback . Could you please post a small script that shows the issue that I can use to test with and try and duplicate your results?

I tried with the script in the first post and Laszlo's script on the 3rd page, calling the function like:



Laszlo's script actually returns a line or two more text, but still very incomplete.

Thanks. I've been experimenting with it a bit here too. The .dll version of CMDret doesn't work well with this application either. The results seem to be inconsistent. Running multiple times will display anything from a couple items only to the full list. I also tried creating a batch file with a few other commands to see if the process was finishing before the output could be read. Output from commands executed before cmdline.exe seem to display ok but anything after cmdline.exe in the batch file is not displayed. I'll have to do a bit more testing to try and determine the cause. Maybe cmdline.exe kills the pipe while generating its results ?...

From doing a bit more testing it appears that the output has likely been added to the CMDout variable ok using the code in the first post but it is possible that the output contains a character or characters that AHK does not handle properly that may be causing the output to appear truncated. In other words, for example , if the 50th character is a NULL character (maybe...), then nothing after that character would be displayed as AHK may assume that it has reached the end of the variable's contents (unless I'm misunderstanding...). The last version posted by Laszlo doesn't handle the way the output is added to the output variable the same way and might cut off the results at a different point in the output.

A patch for this is possible but might not be very efficient. Thanks for pointing this out evl .

Does anyone have any suggestions on an efficient way to test for and remove characters that cause the output to get truncated?

Updated the code and download in the first post.

Version 1.08 beta
- Fixed truncated output when output contained null characters (Thanks evl)

Please let me know if this version fixes the issue .

It seems to have fixed it

Edit *deleted*

(I had some problems with it working, but i found out it was becuase I had a wireless card and an ethernet cable plugged in See this post for more info.)

_________________

"Power can be given overnight, but responsibility must be taught. Long years go into its making."

Does anyone know when CMDret-AHK function will be directly included in AutoHotkey? Thanks.

It's still on the to-do list but I don't know when. Certainly Corrupt's DllCall implementation will help a lot when the time comes -- not to mention everyone's testing, comments, and refinements.

just a minor addition to allow dir to start in:



bw.. great work guyz

_________________

546F206C69766520
6973204368726973742C0D746F2064696520
6973206761696E2E0D285068696C20313A323129

Thanks for the reminder .

There are a few other additions currently planned:
- Optional StdIn
- Optionally split StdOut & StdErr output
- Stream output to control

If you (or anyone else) has any other ideas, comments, suggestions, etc... please don't hesitate to join the discussions. The amount of time spent on this project is usually determined by the amount of interest in it...

Thanks . and thanks to everyone that has contributed to this project