01-24-2011 01:05 AM
I have the latest JDK and JREs and have the tablet simulator running on VM player. The developement mode is on and I have the IP address. I was able to compile the sample sketch program and it generated a bar file. But when i enter
blackberry-deploy -password xx -installApp -device 192.168.52.128 -package bin\sketchPadStandard.bar
it says installing...
doesn't give any details. Any ideas as to why this is happening?
Solved! Go to Solution.
01-24-2011 01:38 AM
Have you try to restart / reset the simulator? I've experienced same problem (unable to install *.bar on simulator), and it works after I restared my PlayBook simulator.
01-24-2011 11:49 AM
blackberry-deploy is a utility provided by the BlackBerry Tablet OS SDK. A copy of this SDK would have been installed as part of the WebWorks SDK for PlayBook installation. The version of the Tablet OS SDK should match that of the simulator being used (currently both version 0.9.2).
Can you confirm that the version of the sim you are using is up to date?
Otherwise, have you also installed a separate copy of the Tablet OS SDK (for AIR development)? If so, the call to "blackberry-deploy" may be using this version of the SDK (in which case, verify that the versions are correct).
01-24-2011 12:02 PM
Also make sure the simulator is set to "Development Mode" in the settings. And make sure that the date/time of the simulator match that of your PC
01-25-2011 06:12 AM
im attaching screenshots of my version information so that you can confirm.Tablet SIM seems to be 188.8.131.52 while SDK is both 184.108.40.206 and 0.9.2 in the config file. Maye I'm checking the wrong file for the version info.
Also regarding the tip about the time.I looked up how to set time an all but the clocks of simulator and my PC seem to be in Sync.And yes the SIM is set to development mode.
01-27-2011 03:37 AM
the issue was with the version of Simulator.downloaded the newer version (beta2) And it worked.
Oh and another thing, i tried to create a VM with a 2GB HD and it wouldn't boot(the older version did somehow). When i increased the HD size all was fine tho.