I know many have seen this error lately.. And I just got it to...
but it all goes back to... the USBSER.SYS issue... (see the USBSER.SYS link at
http://mark.cdmaforums.com )
SO CHECK YOUR DRIVER IN DEVICE MANAGER!!! Device Manager -> Right Click Moto USB Modem... from the pop-up click Properties... On the Driver Tab, click the Driver Details Button. See what it says...
It probably shows USBSER.SYS as one of the drivers, and there is your problem... If it shows USBSERMPT.SYS, then I'd be very suprised...
NOTE: this is NOT the same as "folder has been locked by your provider"
There is a reason why the bottom of my Using MSU instead of PST page (item #2a on the HOW TO's at
http://mark.cdmaforums.com) has the following on the bottom...
Quote:
|
Note: The Moto USB Modem driver installed by MSU re-introduces the USBSER.SYS issue. So, after you are done with MSU, if you are having problems using BitPim or MPT via USB Cable, re-run BVRP's driver tool...
|
Why am I posting this?
I hadn't been using the USB cable for MPT, and I don't use BitPim often at all since MPT works, and I enabled BT OBEX FT's on my E815...
I had bitpim v9.04 installed on my laptop, which also has MSU, MPT, Quicklink MobilePhonebook, Skinner4Moto, P2KCommander v3.26, P2KSeem for V710.. and the Motorola Driver Installer... and like 3 other programs commonly used for "hacking"...
In preparation of getting a LG VX8500 (aka Chocolate), yeah, I know, I'm going to the dark side

... I decided to update bitpim, and read my phone book and everything from my E815 into BitPim, since the LG Phone obviously WONT WORK with MPT...
So, I un-installed BitPim v9.04, and installed BitPim 9.05... Hooked up my E815, followed the BitPim setup instructions on my pages... Clicked the GET PHONE DATA button... told it to read Phone Book, Calendar, Wall Paper, Ring Tone, and SMS... I selected REPLACE ALL for all... then clicked OK...
Within SECONDS... It started reading "fundamental phone info" followed by the /MyToneDB.DB file... and gave me the error right away!!
I checked my driver.. and sure enough.. USBSER.SYS
How to Fix...
There are two ways...
First/easiest way...
Unplug the phone from the PC, exit all apps, run the BVRP's DRIVERTOOL... Plug the phone back in... Let windows add new hardware wizard find/install the driver. (if it doesn't point it to c:\documents and settings\[USERID] where [USERID] = the windows logon id of the person who ran the drivertool exe)...
2nd way... (assumes you have previously run the DRIVERTOOL...)
Device Manager -> Right Click Moto USB Modem... from the pop-up click Update Driver. Choose "install from list or specific location (advanced)" and click NEXT... Choose "don't search I will choose" and click NEXT... Click the HAVE DISK button... On the install from disk window, click the BROWSE button. Navigate to the c:\documents and settings\[USERID] folder (where [USERID] = windows logon id of the person who ran the driver tool)... select the USBMOT2000.INF and click OK.. click OK again. From the driver choices, I had TWO listed v3.4.0.0 drivers listed ... one dated 10/17/05 and the other dated 3/22/06.. I picked the 3/22/06 and click NEXT. The wizard will continue and install the drivers. Watch the progress box as it installs, you should see the USBSERMPT.SYS as one of the files it copies just before it completes.
Now that that is done... double check which driver is in use... Device Manager -> Right Click Moto USB Modem... from the pop-up click Properties... On the Driver Tab, click the Driver Details Button. See what it says...
If its the USBSERMPT.SYS, then you can Re-config BitPim... browsing for the port again... and try it.
NOTE: Motorola Phone Tools V4.21a includes a NEWER version of the driver tool. Download it here ->
DriverTool-421a.exe for what is different see ->
MPT Drivertool thread...
V3M uses want to use this v421 version!!
NOTE: I can reproduce this error at will with my E815 by switching back and forth between the USBMOT2000.INF from BVRP's driver tool (which uses the USBSERMPT.SYS), and the USBMOT2000.INF that comes with MSU, PST, Radiocomm, etc (which uses the "stock" windows USBSER.SYS file)