Jump to content

lester

Active Members
  • Posts

    74
  • Joined

  • Last visited

Recent Profile Visitors

1,690 profile views

lester's Achievements

Newbie

Newbie (1/14)

  1. Wonderful project. Important question: Assuming a PC/server already has an IP address assigned to it via DHCP on a cable, isn't there going to be a conflict when the lan turtle is inserted into, for example, the back of a pc's/server's usb port -- does the pc/server still ask for an address even though it is already connected to a network with an established connection? I believe this conundrum needs to be clarified a bit. Thank you.
  2. found the solution in case anyone else has this problem. Need to download the latest as of this date, tarball, at: http://sourceforge.net/projects/dfu-programmer/files/dfu-programmer/0.6.2/
  3. When attempting to compile dfu-programer-0.5.4 on Ubuntu, getting many errors when "making". ./configure no problem. Any help much apprerciated. make all-recursive make[1]: Entering directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4' Making all in src make[2]: Entering directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4/src' gcc -Wall -g -O2 -I/usr/include/libusb-1.0 -lusb-1.0 -o dfu-programmer main.o arguments.o atmel.o commands.o dfu.o intel_hex.o util.o main.o: In function `main': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:58: undefined reference to `libusb_init' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:108: undefined reference to `libusb_release_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:121: undefined reference to `libusb_close' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:131: undefined reference to `libusb_exit' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:79: undefined reference to `libusb_set_debug' dfu.o: In function `dfu_transfer_out': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' dfu.o: In function `dfu_transfer_in': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: undefined reference to `libusb_control_transfer' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: undefined reference to `libusb_control_transfer' dfu.o: In function `dfu_transfer_out': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' dfu.o:DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: more undefined references to `libusb_control_transfer' follow dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:388: undefined reference to `libusb_get_device_list' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:394: undefined reference to `libusb_get_device_descriptor' dfu.o: In function `dfu_find_interface': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:677: undefined reference to `libusb_get_config_descriptor' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:415: undefined reference to `libusb_open' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:417: undefined reference to `libusb_set_configuration' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:445: undefined reference to `libusb_close' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:451: undefined reference to `libusb_free_device_list' dfu.o: In function `dfu_find_interface': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:716: undefined reference to `libusb_free_config_descriptor' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:419: undefined reference to `libusb_claim_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:436: undefined reference to `libusb_release_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:426: undefined reference to `libusb_free_device_list' dfu.o: In function `dfu_make_idle': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:814: undefined reference to `libusb_reset_device' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:431: undefined reference to `libusb_free_device_list' collect2: error: ld returned 1 exit status make[2]: *** [dfu-programmer] Error 1 make[2]: Leaving directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4' make: *** [all] Error 2
  4. Trying to get a grip on the different firmwares and read all about them here: http://code.google.com/p/ducky-decode/wiki/Which_Firmware but still trying to understand which one would allow a user to insert ducky, run HID program PLUS download a stored program residing on the ducky onto the target? Does such a duck exist? Thank you!
  5. solved. Saw that I used the older encoder. Now up to date. Thanks!
  6. Hello All! Need to know: 1) how to determine my duckie's firmware, and; 2) how to determine if I have latest duckencode. 3) What is maximum size of mini sdcard I can use on the duckie? Does it matter? This because I am having problems with compilation and figure the best thing is to at least rule out firmware and encoder. Thank you!
  7. This is the full file. There never was a colon in the code (the snippet of code in the first posting, above, was incorrect, my mistake, I included a colon in the posting question but actually in the real code there is no colon): REM Target: WINDOWS VISTA/7 REM Encoder V2.4 REM Using the run command for a broader OS base. DELAY 3000 GUI R DELAY 1000 STRING cmd /Q /D /T:7F /F:OFF /V:ON /K DELAY 500 ENTER DELAY 750 ALT SPACE STRING M DOWNARROW REPEAT 100 ENTER Is there some command I can run to find out what my firmware is and if I'm running the latest encoder?
  8. When running the hide command window script, I get an error on compilation stating: Error on line: 14 Line 14 contains the command: REPEAT: 100 removing this command allows successful compilation. Runing the duck on an Windows XP machine. Any advice?
  9. I notice the USB Rubber Ducky has been unavailable for purchase for sometime. Any idea when it will become available? Thanks!
  10. So you are saying with the Anker which seems to run forever, using an 8 gig or 16 gig flash drive is a non issue? In other words I could simply use it and not expect problems?
  11. Kinda new to this but what's wrong with going out to an electronics store and purchasing an even larger thumb drive say 8 or 16 gigabytes? What are the inherent issues with going bigger and better? Or do the Domain.com usb's have something better about them? Regarding power, I have an Anker 10000mAh charger and it seems to last forever.
  12. Okay I've unchecked that and it seems to be working properly. Thanks! Here's a stupid questions: what's the difference between "Automatic (DHCP)" and "Automatic (DHCP) addresses only" in the IPv4 settings tab? I can't slice the semantic differences here and can't find an answer through Google. I was wondering if this might have something to do with the problem. Thank you.
  13. Hello, I'm running linux mint and have never had a problem connecting to a wireless access point on wlan0 and keeping the connection for hours. However, once connected to the wireless access point and then plugging in the network cable that runs from the Mark IV with the most recent version of pineapple OS, my wireless connection is disrupted or disconnected altogether. Any obvious reasons why this might happen? I run the script wp4.sh and everything connects properly, but shortly thereafter I lose my wifi signal on the laptop. An ifconfig still shows the wlan0 with the proper ip address from the wireless router, but I cannot ping anything or access the net. Help appreciated.
×
×
  • Create New...