Originally Posted by vinmontRD

Is it me, or have the OS update functions changed somewhat between 4.5.0.102 and 108? As I recall, up through version .102, I could install the OS update on my PC, delete the vendor.xml, run desktop manager, and the app loader it would invoke would immediately recognize the availability of an OS update, offer it, and then update my 8300.

Now it no longer seems to work that way. I first tried this using my old installation of desktop manager 4.6. My Curve (8300) has 4.5.0.102 installed, and I had installed 4.5.0.108 to my PC and deleted the vendor.xml file, as I always do. I fired up desktop manager v4.6, and checked for device updates, blinked once, and went back to the main screen without offering to update the device. First time I've seen this.

So - I uninstalled 4.6, installed 4.7, then went and re-installed the 4.5.0.108 OS to my PC, and once again deleted vendor.xml. Still no joy on running desktop manager -- it simply didn't see the OS update for the 8300.

I re-read the first post in the thread and noted the recommendation to run "loader.exe". I did this, it saw the OS update, and is, in fact, running as I type this.

My question is: if loader.exe sees the update and happily updates my 8300, why will Desktop Manager 4.7 not see the update as well and offer to install it to my 8300?

- Jon