PDA

View Full Version : Wizard and Windows Mobile Device Center in Vista 5472


liv3wire
30-07-2006, 11:19 AM
Any of you guys managed to get this to work? Plugged my wizard and picked up as Generic RNDIS, i browsed to the activesync4.1 directory on my xp drive and used the RNDIS driver from there, as windows couldnt see any other, it installed fine, however i get nothing when i plug the wizard in, Windows Mobile Device Center dont pop up. Any ideas guys??

fahlis
30-07-2006, 12:34 PM
Hi,

Yes I have it working with both USB / BT :=)

Try this procedure.

1. Download this file.

http://www.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/5460.x86fre.dogfood.060628-0900.reinstall_847432eec73e750d6d8056881f52a39fbc9 4587a.exe

2. Extract it using winrar.This will give you a file "wmupdate.msi"

3. Now be sure to logon to Vista as the built in admin and run "wmupdate.msi" and after that reboot and again login as built in admin, let it complete the install.

4.Login as your regular user, connect you phone and all should work:=)


/Fahlis

kltye
30-07-2006, 12:44 PM
Hi,

Yes I have it working with both USB / BT :=)

Try this procedure.

1. Download this file.

http://www.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/5460.x86fre.dogfood.060628-0900.reinstall_847432eec73e750d6d8056881f52a39fbc9 4587a.exe

.....


/Fahlis

Hi,

I'm running 5472 as well, but the update (from the file name) looks like it's mean for build 5460. Are you sure this is compatible with 5472? I just wanna make sure because I had just reinstalled my OS and don't want to go through the trouble of breaking it ;) Of course, there's always system restore, but it can be a PITA for me sometimes.

liv3wire
30-07-2006, 01:40 PM
tried it but dont seem to work, setup starts then vista picks up a new device, out of interest what does your wizard show up as in device manager? It couldnt auto find a driver, so i browsed to activesync dir and there was loads of MS drivers, also HTC drivers, i tried to choose HTC pocket pc but didnt work, its obviously not the Wizard drive its after as the wizard wasnt even plugged in.

kltye
30-07-2006, 03:01 PM
tried it but dont seem to work, setup starts then vista picks up a new device, out of interest what does your wizard show up as in device manager? It couldnt auto find a driver, so i browsed to activesync dir and there was loads of MS drivers, also HTC drivers, i tried to choose HTC pocket pc but didnt work, its obviously not the Wizard drive its after as the wizard wasnt even plugged in.

Oh yeah, now I remember... 5472 was being a real pain with my MDA. I can't remember what I did exactly to fix the driver issue, but I believe I just pointed it to the root directory of the CD that came with the phone when it prompted for drivers. Just be persistent with it, and it should finally install :P

BTW, the file provided above works! It does install an older build of WMDC, but it doesn't seem to affect anything. The build provided with 5472 only works if you choose "quick connect", instead of establishing a partnership.

fahlis
31-07-2006, 10:52 AM
setup starts then vista picks up a new device, out of interest what does your Wizard show up as in device manager?

I had the Start CD that came with the device put in and it found the drivers needed from that auto.

And sure enough the provided file is for an older build but for me at least it does work.

And it shows up as "your username Windows Mobile-based device" in WIndows Explorer..see attached snapshot"

/fahlis

fahlis
31-07-2006, 10:53 AM
setup starts then vista picks up a new device, out of interest what does your Wizard show up as in device manager?

I had the Start CD that came with the device put in and it found the drivers needed from that auto.

And sure enough the provided file is for an older build but for me at least it does work.

And it shows up as "your username Windows Mobile-based device" in WIndows Explorer..see attached snapshot"

/fahlis

fahlis
31-07-2006, 10:57 AM
Oh I just looked at my initial reply and one thing I forgot to mention :(

I had to run the wmupdate.msi i file from a command prompt, and that also had to be started with administrator priviliges.


/fahlis