-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working properly #277
Comments
You may need to add more delay. It is only waiting 1/4 second before doing the ipconfig, which might not be enough time for the cmd window to open. |
It works, but I don't know why it opens up Google Chrome and then doesn't work. |
Now it does work, but by changing this: |
Please respond to this question first. |
There isn't a way for the ducky to know if the command has run successfully. It just acts like a keyboard typing in characters. |
Oh, ok but then how should I program my rubber ducky? Should I program it to go slow or fast? Because I have another computer that is slow and in that, I need to put a slower delay In that computer. |
That is the trick with the payloads. sometimes the best thing is to run and time the steps manually to get an idea on how long each step takes. If the goal is to automate some things, it might not matter that it takes as long with the ducky as it does manually. |
is it 250ths of a second for the delay? |
Delay is in milliseconds. |
I am trying to run the pico-ducky, but it runs and then doesn't finish it perfectly,
GUI r
DELAY 250
STRING cmd
ENTER
DELAY 250
STRING ipconfig
ENTER
but it only opens the cmd and then doesn't type ipconfig, and it happens to all of the payloads
The text was updated successfully, but these errors were encountered: