I'm sure this was working properly with version 142F but then I saw version 142G was available so I tried to upgrade, now although Wifi works I get a "WIFIGUI.EXE not a Pocket PC program" error if I try to use the WLAN tools. I have tried reverting back to 142F but I still get the problem
Any idea's?
Related
I just tried WM2003 and came back to SER 1.2 without problems - I was told it's not possible without SD card. Am I so lucky?
Funny, I did the very same thing before reading it couldn't / shouldn't be done, makes me think though, what if it had all gone wrong!!!!!!
For those who have tried the WM2003, please advise me whether it's worth my risk (I'm still indecisive) :?
Just tried to upgrade from 1st version of WME2003 to the latest using the upgrade utility, no go. Goes into upgrade mode on PC & PPC, then progress bar screen on PPC goes to white, a few minutes later a error pop-up on PC telling me to reset & run utility again. When I do so same problem. I'm just curious what version on Activesync are you running & on OS on the Desktop
Thanks
erickbryce said:
Just tried to upgrade from 1st version of WME2003 to the latest using the upgrade utility, no go. Goes into upgrade mode on PC & PPC, then progress bar screen on PPC goes to white, a few minutes later a error pop-up on PC telling me to reset & run utility again. When I do so same problem. I'm just curious what version on Activesync are you running & on OS on the Desktop
Thanks
Click to expand...
Click to collapse
Hey Erick,
I had the same problem with the 1st version of WM2003. I was unable to do the upgrade with the utility. It would seem like the version 4.00.01 of WM2003 is far more mature in terms of this sort of functionality. For example, ActiveSync would not connect with the device in standby. This is not the case in the new version of 2003 which goes to show that maybe some processes were not running.
Going by what I experienced with the older WM2003, I did not try an RUU flash to test if the newer version worked, but I won't be surprised if it does. I was running ActiveSync 3.7 with WinXP Pro.
Thanks Sheran. So I guess it's SD card time This is an ActiveSync problem not an OS problem? What do you think? SD card should work right?
The reason I'm suggesting ActiveSync is I am unable to use any ROM utility to flash any ROM version now, which I was able to do before i.e. SERv1.1.
I believe I had the previous version of ActiveSync back then & now ActiveSync freaks-out when I try to use the upgrade utility for any ROM.
erickbryce said:
Thanks Sheran. So I guess it's SD card time This is an ActiveSync problem not an OS problem? What do you think? SD card should work right?
The reason I'm suggesting ActiveSync is I am unable to use any ROM utility to flash any ROM version now, which I was able to do before i.e. SERv1.1.
I believe I had the previous version of ActiveSync back then & now ActiveSync freaks-out when I try to use the upgrade utility for any ROM.
Click to expand...
Click to collapse
I'm thinking this has more to do with the WM2003 1st version (3.04 build 13083) OS rather than your PC OS or even your ActiveSync. I think the reason some people can use the ROM Upgrade Utility is because they are running the newer version of WM2003 (Ver 4.00.01 build 13100) which seems to work well with ActiveSync.
Unfortunately if you install the older version, until I'm told otherwise, the only way to get out of it is to do an SD Card flash.
Thanks again Sheran I tend to use the SD method, wanted to not have to wait for two write processes. Oh well back to the tried and true method, for now 8)
I was running the newer version (build 13100)
Activesync 3.7, Windows XP Proffesional
I just upgraded TMO radio stack to 6.24.00, works flawlessly. Tested the RS with calls, web connections, incoming call while on web ... perfect.
However, ActiveSync will not recognize a partnership with my PDA now. Reverts to Guest every connection.
Reinstalled ActiveSync ... no luck. Soft reset PDA ... no luck. Tried it on a WinXP-HE and Win2K computer, same on both.
Have searched forum & seen a few enteries on this subject but no solutions. Running TMO ROM 4.00.21 & TMO RS6.24.00.
Anybody had this issue & successfully resolved it?
Yeap been there seen that but had forgotten about those problems until I read your post! :wink:
Try downgrading back to 3.7, my sig states what I ended up doing to fix it for me! :wink:
Also you might try turning the device off before you put it in the cradle
so times that helped if I remember correctly.
HTH
Resolved problem by uninstalling ActiveSync 3.7.1, restart Windows, reinstall ActiveSync 3.7.1 and it detects new USB hardware, starts the Partnership wizard and things are okay.
pschoch said:
Socket SDIO WLAN Tools works now! Hanza found out that the smartphone version works on Magneto!
Get it here:
http://www.socketcom.com/support/redirect.asp?URL=ftp://ftp.socketcom.com/wlan/SDIO_WLAN_Sagem.exe
Click to expand...
Click to collapse
Download the Wifi Companion software here
http://www.socketcom.com/support/support_wlan.asp?Type=WiFi
I used the cab file (i has a 3 day trail)
Install the Wlan tools en then install Wifi companion.
Softreset and then put your Wifi on with the Commmanager.
The start Wifi Companion and it must work.
I'm still testing if everything is working OK.
So tried it on your own risk.
If you install Wifi Companion alone you get a error message that he is missing files from Wlantools.
If you remove Wlantools it's not working anymore.
Working for me.
French Rom, and no problem.
More graphical and UI based than Cirond that I used before.
Martinlbb
First test ... looks great.
But I get the following error on start-up: "ActivateDevice failes, code 964 hex". Could be that it throws that error when WLAN is still in off mode when rebooting. Can I keep the WLAN to autoconnect at startup?
But ... costs 25$ ... that's much for a little utility.
you should be getting the error unless you copied a DLL file to make it a full version (or used the wrong version) :wink:
when using the CAB file it works great, for 3 days
I tried installing the SDIO_WLAN_Sagem.exe but it gives me errors when executing it.
Then I installed the wifi companion cab :
Wi-Fi Companion for Windows Mobile 5.0 Drivers and Software (Advanced Users Only)
Select #1. CAB file for Windows 2005.
1.2 MB
and after soft reset all I got was a blocked popup windows (couldn't see the message)
next thing, hard reset
Using just the CAB file works perfectly.
the problem is that most download an other version and use the wrong CAB file or DLL File.
Just install the software without any extra drivers (do not install the SDIO software, only the compagnion)
PS most DLL files out there are for windows 2003 version and do not work
This is driving me nuts. My PDA was running slow so I tried installing the Ruu Wizard 2.17 ROM. It installed, everything seemed fine but I could not Sync with AcitveSync. In fact it will not even recognize the mobile device. It sets it up as a Windows Network ( but I can't access the PDA). I've tried hard resets and reinstalling ActiveSync with no luck. ActiveSync says it cannot detect it. This problem is keeping me from reinstalling the original ROM. Does anyone know how to get AcitveSync to work on this thing? Or can I somehow reinstall the old ROM without AcitveSync? Thanks in advance.
Jason
Sounds like you are using activesync 4,
try upgrading to Activesync 4.1 (avaliable on Microsofts website)
this should fix your problem
Cheers
Steve
I checked and I am using 4.1, still no go. Are there any other Sync programs out there?
Jason
Although it was working with RC2, strangely, it doesn't with RTM, the driver is installed but only the file transfere is working. I can see an icon of my JJ in computer (ex. my computer) and when click on it, i can browse the JJ ram and the storage card only, but there is no any syncing capabilities. Any one has an idea about that problem. May i am going to try the old RC1 trick:
http://www.microsoft.com/downloads/...roductID=7C1FA894-B2C5-41BE-8D97-E145DD2A883B
Still there is no respoonse after 26 viewers, does this mean that there is no one has installed the new vista RTM release or I am asking a selly question?
_____________________________________
JJ with AKU 3.2 1.90.96
Yes, I synced my HERMES with http://www.microsoft.com/downloads/...6a-a72d-4aef-9663-31ce2fefbada&DisplayLang=en this tool, but sometimes don't, lot of crashes...
Just have a try:
disable any Anti-Virus and Firewall softwares.
I tried downloading the sync tools beta, but fiind it hangs outlook (2007).
I'm going to give it a try just running wirelessly and see how I get on.
The same don't know why it's not working...
sergiopi said:
Yes, I synced my HERMES with http://www.microsoft.com/downloads/...6a-a72d-4aef-9663-31ce2fefbada&DisplayLang=en this tool, but sometimes don't, lot of crashes...
Click to expand...
Click to collapse
I tried it, it worked, thanks. The difference is that i followed the trick mentioned above also, i added the registery key WHOS, then installed the WMDC beta program, so, will try to use the WMDC program only without the registery in another installation.
Now I sync 95% of times, I just unchecked in settings-> connections->USB to PC-> use enhanced USB
I have managed to get it working after having reflashed the rom on my phone (probably not required) and re-installing the Windows Mobile Device Centre beta 3.
I think the trick is to make sure your phone can connect to Vista OK before you install the WMDC software and then install the software with the phone connected.
Good luck
Are you also able to flash / upgrade the phone using Vista RTM and MDC beta 3? I'm not