12-17-2008 06:59 PM
I'm trying to get the Javaloader.exe working on the BB9000 with v184.108.40.206. I have successfully been able to load a single version of my code with the Desktop Manager, but this is a pain as it wants to do other updates all the time too. I'd really prefer using the Javaloader.exe app from the command line, as it's quicker and simpler.
I've read some of the other posts about this, here's my sequence of operation and the javaloader command line:
1) Build the project...
2) Sign the project.cod file...
3) Create an ALX file
4) Run Javaloader.exe from the application directory with ">javaloader -usb load application.cod"
When doing this, javaloader responds as if all went smooth, no errors and indicates how many bytes transfered.. All looks good.
When looking at the results of ">javaloader -usb info -v application.cod", the previous version of the project is still there! What's going on!....
Anyone have the same experience? Any ideas why I need to use the Desktop manager instead of Javaloader?
Solved! Go to Solution.
12-17-2008 07:21 PM
I had this also. I fixed the issue by downloading the latest version of Desktop Manager - there was apparently a newer driver installed that is needed by javaloader.
Hit the same issue recently on the Storm and had to update Desktop once again.
12-17-2008 08:33 PM
Thanks, that got it...
There might be variations in the Desktop software packages and/or just needed a particular order....
Seemed like the same version, but everything works now...