Problems running BlackBerry Simulator (fledge) on Windows 7 64 bit

Jan 22, 2010 by

As I already wrote, BlackBerry development is not a lot of fun.  Not only you basically can not develop in Linux and OS X (although there are some workarounds, it makes the process even more painful than it already is). But you will also have problems with 64 bit operating systems. RIM is in a position that they do not officially support 64 bit systems.

The main problem with 64 bit Windows 7 for me was that I can not close the simulator (or actually the “fledge” application that runs the simulators). There are 2 possible solutions to this problem:

  1. Kill the task through task manager
  2. The simulator should close if you are in debug mode and you disconnect the debug session

There is also another inconvenience which is caused by your cautiously guarding Windows system. It will warn you every time that (Oh my!) fledge will change something on your computer. You know – the standard User Control Account message. To avoid that message always popping up, you will have to adjust your setting in User Control Account panel. Hit “Windows” then just type UCA, you will get it. Adjust it to the minimum and you’r good to go.

Related posts:

  1. BlackBerry Eclipse plugin 1.1 will fix some of the annoying problems

Related Posts

Tags

Share This

  • Fernando Manuel Perez Ramos

    i have the same problem, with the simulator and the mds email too, are there any way to fix that?

  • Carl S

    Yep, I know this post is over a year old… but I still have problems with the simulator (BlackBerry Smartphone Simulator 2.11.0.208). I’m currently running Windows 7, and the simulator refuses to close/shut down. I can kill it (usually) via the Task Manager, but then it doesn’t operate correctly if I relaunch it without rebooting Windows.

    Also, you apparently can’t run multiple simulators (phone models) at the same time and have them connect to the MDS. The first one connects fine, but then the others complain that there’s already a version of the current simulator running and network functionality will be disabled. This is a HUGE problem given that RIM moronically decided to make each phone model a different simulator executable instead of simply making them plug-in modules on a single simulator platform. And, of course, given that you can’t close that first simulator before bringing up the second (see problem #1).

    I can’t BELIEVE this is so hard.

  • Mypascal2000

    no wonder RIM is gooing down …. yeah, going down babe

    I worked on bb simulators few years back and always same problems, never fixed and still around ???
    I switched to JavaSun emulator and works smoooooooth so I use bb emulator only if I need to test signature or GPS positions and it is so f…. hard and wast of time, that is unbelievable.

  • http://www.kendallarneaud.me/ Icecappacino

    Damn anyone ever found a solution to this?

    • http://www.inteism.com/ inteist

      It was fixed in the later versions of the BB Java SDK. Works fine for me for quite a while now. Make sure you update to the latest version. Probably will resolve this issue. 

      Also if you use the 5.0, you don’t have to restart the simulator that much, so it’s much less of a problem in that case. You still can run 4.2.1 apps on the 5.0 simulator (if you happen to still target that or maybe 4.5/4.6/4.7 versions) – it’s not a problem as it is backward compatible.