| Author |
Message |
PeterWhite
Posts: 2
Phone Model:
lgvx7000
Service Provider:
verizon |
 
Thu Feb 03, 2005 3:16 pm |
---------------------------------------------------------------------- ----------
Hi all!
I just got my data cable and the driver that came with it doesn't work. I get the "USB device has Malfunctioned" error when I plug in the cable to my computer, and in Device Manager, I get the yellow !? next to USB devices. Anyone know where I can get another driver? Every other USB device I plug into the same port works fine. Thanks! Pete
|
 |
Advertisement
|
|
|
|
|
zcarmanron
Posts: 74
Phone Model:
LG VX7000
Service Provider:
Verizon |
Sat Feb 05, 2005 1:16 pm |
Just go to futuredial.com and click through to the downloads. They feature a great driver on their site that seems to work for almost every cable.
Another thing to check out, make sure you are plugging the cable in to the same port everytime. If you go to a different port, it will try to recognize it as a 'new' device each time.
Hope that works out for ya!
|
|
msaj80
Posts: 3
Phone Model:
LG VX7000
Service Provider:
Verizon Wireless |
Sat Mar 12, 2005 1:29 pm |
|
i am also having a problem. i bought the cable & installed the driver through the LG website and got the bitpim software. it uploads all my pics & ringtones but the only thing is that it's not letting me upload ALL my contacts. wth??? HELP!
|
|
razorbak214
Posts: 21
Phone Model:
lg7000
Service Provider:
verizon |
Tue Jun 21, 2005 6:26 pm |
|
i had the cable and driver trouble too. i got new computer with windows xp and downloaded newest version of bitpim and i have no problems. my old computer has windows 98 and i gave up after about 2 weeks of down loading drivers.
|
|
Prowler723
Posts: 31
Phone Model:
VX7000
Service Provider:
Verizon |
Tue Jun 21, 2005 8:13 pm |
|
lol same here. I was running 98se, and couldnt for the life of me get bitpim to recognize my phone. upgraded to xp last weekend and it worked. this comes of course after i got another data cable off of ebay (which i still havent received) thinking the problem was my cable. shouldve known it was just a driver issue
|
