vB Easy Archive - 3.45 and USB Connection

Pages: 1

3.45 and USB Connection
(Click here to view the original thread with full colors/images)

Posted by: r1v3n

I know this has been addressed before, but I cant find it in the myriad of information that we throw around here...

I upgraded my phone to 3.45 using my laptop about 3 weeks ago. I've been away from my home PC due to Annual Training for the ANG, so when I finally got back and tried to sync with Outlook (via ActiveSync), my desktop PC did not recognize my phone. It gave me some error about an unrecognized USB device.

Now, it still works on my laptop, but I dont sync with that. I THINK this was mentioned before and it had to do with an updated smartphone.inf file....?

Is this the issue or am I confusing it with something else?

Posted by: Omega2008

Delete your old partership in ActiveSync and try again...also you may want to uninstall ActiveSync, reboot, install ActiveSync, and reboot again....that may fix your problem.

Posted by: r1v3n

I thought about that, but it doesnt even reach ActiveSync. As soon as it connects, the error balloon in the taskbar pops up and says that there is a problem with the USB device attached. I remember installing the smartphone.inf file on my laptop, but like an idiot I deleted it after installation...

I'll still give the ActiveSyn uninstall a try when I get home from work, but I dont think that will fix my problem...

Posted by: Omega2008

If it won't reconize your phone they you should try reinstalling the Smartphone 2002 or 2003 driver. Or try a different USB port.

Posted by: r1v3n

Quote:

Originally Posted by Omega2008

If it won't reconize your phone they you should try reinstalling the Smartphone 2002 or 2003 driver. Or try a different USB port.

That's what I changed....I upgraded to the Smartphone 2003 driver on my laptop. I'll do a quick search for it...

Posted by: NooM

I don't mean to hijack this thread, but i am having a similar [yet dfferent] problem.

My MPX220 changes into 'car' profile everytime i connect it to the computer, and therefore it is not recognized by activesync [and it just charges, it thinks its a car - it also doesn't charge when connected to my car charger]. I cannot change the firmware or anything on the phone since i cannot connect to it. I don't have a laptop [so no IrDA] and i dont have [nor can afford] a bluetooth dongle right now. i did manage to quickly install PHM Registry Editor once through a friends laptop [through IrDA, but he's now gone abroad for the summer].

Any ideas please?

Posted by: Omega2008

Do a hard reset....a system file has been corupted in your phones registry.

Posted by: NooM

Quote:

Originally Posted by Omega2008

Do a hard reset....a system file has been corupted in your phones registry.

Been there done that. Any ideas on maybe a registry edit that would help me out?

Posted by: Omega2008

It will be a tedius task to find which file is currupted...a hard reset did not fix your problem? It should have...that is odd. I don't know what regisry file or system file that is causing your problems....

Go to HKLU\Control Pannel\Profiles\Car

Make sure that there are no missing entries

Posted by: NooM

What do you have in the registry under the Car profile? all i have is a "1" key. Do you think deleting the car profile would help?

Posted by: Omega2008

YOu can try but there is more than the 1, when you first select the car file there are 3 entries...take note of them and what they are if you going to delete anything.

Posted by: r1v3n

I fixed my issue. I found a copy of the smartfon.inf file and attempted to install it, but that did not work. I checked my laptop and found that my MPx220 was using a the follwoign file :: C:\WINDOWS\system32\drivers\wceusbsh.sys.

When I checked it with the one installed on my PC, I found that it was a newer version dated 12/06/2004, which is a year newer than the one on my PC. I simply replaced the file and it was recognized. Now, this may be the file that is updated by the latest smartfon.inf file, but I could not find (or verify) that it was the latest.

Either way, this fixed my problem. Everything synced fine afterwards...