11-24-2008 05:36 AM
Solved! Go to Solution.
11-24-2008 07:18 AM
This should stop Desktop Manager from connecting to the Internet to get the latest Vendor.xml which also prevents you from being able to install another carrier's OS onto your device.
One note. I haven't looked at this lately, but in the past attempting to modify an installation of Desktop Manager can often fail. This is because if you installed by simply running the EXE you download from the BlackBerry site, it actually extracts to your Temp directory, and installs from there. The MSI file needed to allow changes in the installation is supposed to be copied to another location - typically in a directory under Windows or Program Files, but older versions did not do this, so when you went to make a change in the installation, if the file was deleted from your Temp directory, it would stop and ask for the MSI file and not be able to proceed until you point to it.
However, the EXE you download is really just a self extracting Zip file, and can be easily extracted with WinZip or any other typical un-archiving utility. Whenever I install Desktop Manager, I first extract the EXE to a permanent location, and then run BlackBerrySetup.exe. This means the MSI will always be available when I need to modify the installation (which I do surprisingly often since I also support BlackBerries at work). Typically this isn't a problem with regular users which is probably why the problem was never fixed (at least as late as version 4.5 anyway).
03-15-2009 05:32 PM
Have you had any instances where this doesn't work? I've done what you suggest (3 times over!) and although I now have the red cross in the right place DTM still checks for updates whenever I connect the phone. I followed your instructions to the letter, including unzipping the install set to a permanent location before doing the install. I've also done it on a second pc and got exactly the same result.
03-25-2009 01:24 PM