skimpniff

Check the forum post labeled "slowing down the keystrokes" (or something to that effect).

STRING_DELAY 50 worked fine for me whereas 1 was still too fast. I worked my way up to 3 and it was still too quick, so I just made the leap to 50 out of frustration and it worked. A lower number would probably work, I just wanted to be able to effectively test the scripts. Once I confirm they work properly, I will work on fine tuning the timing. I imagine it could be a variation in the way our VM's are setup. Theoretically, a normal computer wouldn't need the STRING_DELAY, right? I haven't seen this issue anywhere else in the forums other than referencing VM's.

After some experimentation I have found the answer. To insert the delay between STRING character inputs, the proper syntax is STRING_DELAY N (where N is the time delay) I found STRING_DELAY 50 to work perfectly, ie. GUI d DELAY 500 PRINTSCREEN DELAY 100 MENU DELAY 300 STRING V DELAY 40 STRING D DELAY 300 GUI r DELAY 700 STRING_DELAY 50 mspaint ENTER DELAY 1200 CTRL v DELAY 500 CTRL s DELAY 1000 STRING_DELAY 50 %userprofile%\a.bmp ENTER DELAY 500 ALT f DELAY 400 STRING K DELAY 100 STRING F DELAY 1000 ALT F4 DELAY 300 GUI d

No love here eh? To clarify, I am not trying to add DELAYS to slow down the script execution, just to slow down how fast the duck types the actual keystrokes. It is entering incomplete commands because the VM Bus is unable to keep up.

My question is the same as above, regarding the STRINGDELAY for slowing down the text input. I have the same problem, my VM bus can't keep up with the duck speed. So would a simple STRINGDELaY n preceding the command e.g STRINGDELAY 5 STRING SomeText be sufficient or does a more detailed breakout need to be done, as in STRING S STRINGDELAY 5 STRING o STRINGDELAY 5 STRING m Thanks for the assist.

Was there ever an answer figured out for this?

I have found the answer further in the forum, my apologies for not looking further before asking.For reference see the post on page 2 titled "slowing down key strokes"

I am getting a similar problem. I am not sure if it is because i am testing in a VM, but when I test the wallpaper script it appears that the string is being typed to0 quickly. on some occasions mspaint is typed incorrectly, leaving some of the letters out, on other occasions the userprofile string is not getting some of the characters entered. obviously this means the commands are not getting executed as unrecognized text is being entered. can this be solved by changing the delays or is it simply the VM is not responding quick enough to keep up with the ducky? Any ideas? I don't want to try testing more complicated scripts until i can work the little bugs out first.