happybox Posted March 6, 2013 Share Posted March 6, 2013 I have tried Nano and gedit on linux, and notepad on windows. No matter how I format the command, I get one of this error: -Loading : script.txt -script.txt [FAILED] Or something along those lines. Quote Link to comment Share on other sites More sharing options...
skysploit Posted March 6, 2013 Share Posted March 6, 2013 Can you post the syntax that you are using for the encoder? Have you tried running it through http://www.iducke.com/Encoder/IDE? Quote Link to comment Share on other sites More sharing options...
happybox Posted March 6, 2013 Author Share Posted March 6, 2013 Can you post the syntax that you are using for the encoder? Have you tried running it through http://www.iducke.com/Encoder/IDE? java -jar encoder.jar -i script.txt And I am actually testing that currently. I am not even to the point of debugging the errors I most likely will have with the run. Quote Link to comment Share on other sites More sharing options...
happybox Posted March 6, 2013 Author Share Posted March 6, 2013 The ducky works flawlessly once the bin is generated. I would rather be able to use a terminal, but if I am not able to fix it I can live with an online generator. Quote Link to comment Share on other sites More sharing options...
ApacheTech Consultancy Posted March 6, 2013 Share Posted March 6, 2013 (edited) Try running it through the Duck Encoder v2.4, available in the stickies. If it works on that then please give feedback. The new release has been greatly altered since that one, it would be good to know if I've broken anything. Can you post the actual text file you are trying to encode? Can you also please run the faulty code in debug mode and post the resulting stack trace? A screenshot will suffice if you can't cut and paste. java -jar encoder.jar -i script.txt --debug Edited March 6, 2013 by ApacheTech Consultancy Quote Link to comment Share on other sites More sharing options...
Solution happybox Posted March 6, 2013 Author Solution Share Posted March 6, 2013 Try running it through the Duck Encoder v2.4, available in the stickies. If it works on that then please give feedback. The new release has been greatly altered since that one, it would be good to know if I've broken anything. Can you post the actual text file you are trying to encode? Can you also please run the faulty code in debug mode and post the resulting stack trace? A screenshot will suffice if you can't cut and paste. java -jar encoder.jar -i script.txt --debug java.io.FileNotFoundException: script.txt ETC. Thanks, new to java and did not realize there was a debug command. I still have the problem of the directory of ducklings not automatically read, with ./ducklings/script.txt it worked. This is good enough, thanks. Quote Link to comment Share on other sites More sharing options...
ApacheTech Consultancy Posted March 7, 2013 Share Posted March 7, 2013 So, you didn't have script.txt in the same directory as encoder.jar? You do need to fully qualify the path to the input file; there's no "default" input file at this time. If using duckling macros, you don't need to have the .txt script in the ducklings subdirectory, it will work from any directory, so long as it's qualified (absolute or relative). The ducklings are imported with an "all or nothing" approach. if they're not imported properly, the program will exit with an error. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.