In my new position at Eastern Michigan University, I see more diversity in computing than I ever have, particularly in platforms, and specifically (lately) in smartphones.
To help make sure our hosted Zimbra solution is working well for the greater University community, we try to be more than just open to new devices…we actually want to test them.
We are using Zimbra’s Mobile Sync for synchronizing mobile devices. This is basically an implementation of Microsoft’s Exchange Activesync, which works great for devices that use or have licensed the EAS technology, like Windows Mobile, Apple’s iPhone, Palm’s Pre, and some Android phones. However, RIM’s Blackberry would typically use a Blackberry Enterprise Server (BES) to synchronize Blackberry devices with Zimbra. (In fact, Zimbra has an add-on to allow BES to communicate with Zimbra called the Zimbra Mobile Connector for BlackBerry Enterprise Server
As our Zimbra solution is hosted, we’ve chosen a different (read: less expensive) route to support Blackberries: Notifysync
, which is basically an EAS client that runs on the Blackberry.
We ran acrossed a bug in Notifysync recently, and do not have any ‘extra’ Blackberries to test on. After a bit of searching, I ran across the Blackberry Smartphone Simulators
. Perfect for my needs.
However, the simulators, as with all Blackberry software, run on Java. And haven’t exactly been developed for Windows 7 (with the UAC) or for the x64 platform.
It turned out to be a formidable task to get the simulator running. And as such, I’m hoping this post will save you some time and effort. Here’s how I got the RIM Blackberry Smartphone Simulator for the 9630 running on Windows 7 x64, step by step. I had a little help from a post on the forums.crackberry.com site
– thanks for that, vedasmantra!
How I got the BlackBerry Emulator running on Windows 7 x64
- Install 64-bit Java SDK (I used jdk-6u17-windows-x64.exe)
- Install BlackBerry MDS simulator (I used Blackberry_Email_MDS_22.214.171.124.exe)
- Install a BlackBerry Simulator (I used Blackberry_Simulators_126.96.36.199_9630.exe)
- Change permissions on C:\Program Files (x86)\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.2\MDS to give Modify permissions to the user / group who will run the emulator
- Change permissons on C:\Program Files (x86)\Research In Motion\BlackBerry Smartphone Simulators 4.7.1\188.8.131.52 (9630) to give Modify permissions to the user / group who will run the emulator
- Modify the C:\Program Files (x86)\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.2\MDS\run.bat file to
Launch the MDS from Start > All Programs > Research in Motion > Blackberry Email and MDS Services Simulators 4.1.2 > MDS
Launch the Tour 9630 simulator from Start > All Programs > Research in Motion > Blackberry Smartphone Simulators 4.7.1 > 184.108.40.206 > 9630
Closing the simulator can be a bit tricky. You can’t use the typical Windows X or the File > Exit in the simulator. Instead, create two files in C:\Program Files (x86)\Research In Motion\BlackBerry Smartphone Simulators 4.7.1\220.127.116.11 (9630):
controllerc.txt should include:
Stop9630.bat should include:
cd "\Program Files (x86)\Research In Motion\BlackBerry Smartphone Simulators 4.7.1\18.104.22.168 (9630)"
FledgeController.exe < controllerc.txt
Just run Stop9630.bat to close the simulator. You can even put this file on the desktop.
And a huge important note if you want the Blackberry’s internet connection to work the second time you launch the emulator:
After launching the emulator for the second time, you will need to make sure it is using the 1x/EVDO network (not GPRS). You can get there through Blackberry > Manage Connections > Mobile Network Options. Change the Network Technology to 1XEV (from Global).