02-28-2012 05:46 AM
I am using a Mac with OSX Lion 10.7.2. I downloaded tablet simulator and when I install it, I get this error: You are not allowed to execute multiple instances of the installer at the same time. The installer will now quit.
It's a little confusing because clicking on the .dmg does not bring anything up on my machine. I need to click on the installer which is mounted on my machine to install.
Any ideas? I'm trying to install 2.0.0-7109-201201041944.
Side note: Am I still eligible for the playbook if I registered as a developer yesterday and submit my app before March?
03-22-2012 01:10 PM
Ok this is a step by step walkthrough:
1- Download the dmg simulator for Mac from here: http://us.blackberry.com/developers/resources/simu
2- Double click the downloaded BlackBerryPlayBookSimulator-Installer-2.0.0-7971-M
3- Double click on BlackBerryPlayBookSimulator-200, should appear on your desktop. It should open in Finder now.
4- Double click BlackBerryPlayBookSimulator-Installer-2.0.0-7971-2
5- Press 'Next", then scroll down to accept the terms, then "Next" again
6- Choose where you want it to be installed, then press "Install"
You should now find it in the folder you chose. Double click it, and it should open in VMware Fusion (assuming you have it). If you don't have it, you can downlaod it here: http://downloads.vmware.com/d/info/desktop_e
Let me know if there was anything not clear in the above.
03-23-2012 10:59 AM
Did a full restart not solve this issue?
Try launching the Activity Monitor and see if another instance of the BlackBerry Simulator Installer is running.
07-14-2012 08:22 PM
I get the exact same error. I had prevously had a simulator working. I got a new mac, so used migration assistant to move thing over. Simulator settings did not carry over. When I try to reinstall it provides that same error (as if I were already running the installer). Tried to install 2.1.0 and the 3.0 for BB10. Neither simulator will install. Both throw the same message. rebooting (number of times over a week) does nothing. Even claring out old simulator references in VMware Fusion does nothing.
Anyone get a fix yet?
02-20-2013 07:15 PM