Drivers won't install

Paul wrote:
> desertgal wrote:
>> I'm trying to install the drivers for my LG phone but Windows XP
>> won't let me. Following a suggestion in an earlier post I looked for
>> C:\WINDOWS\setupapi.log & opened it in notepad. It shows the
>> installation attempt but says "Error 0xe000022f: The third-party INF
>> does not contain digital signature information." so the drivers
>> didn't install. I find this message for the software from 2
>> different sources. How do I get Windows to either ignore the unsigned
>> drivers or ask permission to install them? I really want to get the
>> pics off my unusable cell phone.
>>
>> Thanks.
>
> There is a suggestion in this article.
>
> [URL="http://support.microsoft.com/kb/327756"]http://support.microsoft.com/kb/327756[/URL]
>
> I didn't know there was such a setting, but in the Control Panel
> called System, there is an option to change the signing requirement.
>
> Start : Control Panel : System : Hardware : Driver Signing :
>
> Mine is set to "Warn", and I don't think I've ever touched
> that setting. So it has probably been like that since the OS
> was installed.
>
> Paul
Thanks Paul. I didn't know this existed. It was set to warn but it
didn't warn me about the drivers. I've set it to Ignore & I'm going to
try installing the drivers again. Will let you know what happens.
 >> Stay informed about: Drivers won't install 

desertgal wrote:
> Paul wrote:
>> desertgal wrote:
>>> I'm trying to install the drivers for my LG phone but Windows XP
>>> won't let me. Following a suggestion in an earlier post I looked
>>> for C:\WINDOWS\setupapi.log & opened it in notepad. It shows the
>>> installation attempt but says "Error 0xe000022f: The third-party INF
>>> does not contain digital signature information." so the drivers
>>> didn't install. I find this message for the software from 2
>>> different sources. How do I get Windows to either ignore the
>>> unsigned drivers or ask permission to install them? I really want
>>> to get the pics off my unusable cell phone.
>>>
>>> Thanks.
>>
>> There is a suggestion in this article.
>>
>> [URL="http://support.microsoft.com/kb/327756"]http://support.microsoft.com/kb/327756[/URL]
>>
>> I didn't know there was such a setting, but in the Control Panel
>> called System, there is an option to change the signing requirement.
>>
>> Start : Control Panel : System : Hardware : Driver Signing :
>>
>> Mine is set to "Warn", and I don't think I've ever touched
>> that setting. So it has probably been like that since the OS
>> was installed.
>>
>> Paul
> Thanks Paul. I didn't know this existed. It was set to warn but it
> didn't warn me about the drivers. I've set it to Ignore & I'm going
> to try installing the drivers again. Will let you know what happens.
>
Ok tried again & still nothing. The log fie says the install was
successful but it shows as Storage/Removable Media instead of as a modem
& the pc doesn't come up with a window about new hardware. It shows the
Modem Drivers in Add Remove programs. Also, nothing is showing up in
Device manager under usb or ports & it should show in both places when
connected. I don't get it, this is frustrating. Forgot to add, every
time I install or uninstall the drivers I do a restart.
 >> Stay informed about: Drivers won't install 

desertgal wrote:
> desertgal wrote:
>> Paul wrote:
>>> desertgal wrote:
>>>> I'm trying to install the drivers for my LG phone but Windows XP
>>>> won't let me. Following a suggestion in an earlier post I looked
>>>> for C:\WINDOWS\setupapi.log & opened it in notepad. It shows the
>>>> installation attempt but says "Error 0xe000022f: The third-party INF
>>>> does not contain digital signature information." so the drivers
>>>> didn't install. I find this message for the software from 2
>>>> different sources. How do I get Windows to either ignore the
>>>> unsigned drivers or ask permission to install them? I really want
>>>> to get the pics off my unusable cell phone.
>>>>
>>>> Thanks.
>>>
>>> There is a suggestion in this article.
>>>
>>> [URL="http://support.microsoft.com/kb/327756"]http://support.microsoft.com/kb/327756[/URL]
>>>
>>> I didn't know there was such a setting, but in the Control Panel
>>> called System, there is an option to change the signing requirement.
>>>
>>> Start : Control Panel : System : Hardware : Driver Signing :
>>>
>>> Mine is set to "Warn", and I don't think I've ever touched
>>> that setting. So it has probably been like that since the OS
>>> was installed.
>>>
>>> Paul
>> Thanks Paul. I didn't know this existed. It was set to warn but it
>> didn't warn me about the drivers. I've set it to Ignore & I'm going
>> to try installing the drivers again. Will let you know what happens.
>>
> Ok tried again & still nothing. The log fie says the install was
> successful but it shows as Storage/Removable Media instead of as a modem
> & the pc doesn't come up with a window about new hardware. It shows the
> Modem Drivers in Add Remove programs. Also, nothing is showing up in
> Device manager under usb or ports & it should show in both places when
> connected. I don't get it, this is frustrating. Forgot to add, every
> time I install or uninstall the drivers I do a restart.
>

Does the phone manual mention any "modes" you put the phone in ?

If a phone is being used for networking, then perhaps a modem type
device showing up would be appropriate. If the phone was being
used for storage (camera pictures), maybe USB Mass Storage or MTP
protocol would be used. The camera interface may have some thing
you have to do, to enable either of those.

I don't own a cellphone, and have no experience with them. (I
didn't get a Palm Pilot when they were popular either )

For a USB device, there is the UVCView utility from Microsoft,
for looking at USB configuration data. That allows looking at the
raw device declaration. But you're already seeing that, in a way,
by looking at Device Manager. So I'm not sure that looking at
this is really going to help you.

(Click any dated link here, to start a download of an archived copy
of UVCView. Microsoft used to offer this for download, but removed
it from their site. You can get it here.)

[URL="http://web.archive.org/"]http://web.archive.org/[/URL]*/[URL="http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe"]http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe[/URL]

Screenshot similar to UVCView.

[URL="http://www.die.de/blog/content/binary/usbview.png"]http://www.die.de/blog/content/binary/usbview.png[/URL]

Microsoft bundles another tool with your OS. You can use
Start:Run and enter "msinfo32.exe" as the program to run. I
have WinXP Pro SP3 and it has that program included. Look
under "Components". The info looks a lot like Device Manager,
only packaged slightly different.

C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32.exe

If you have something in Storage/Removable Media, perhaps you
are close to seeing your pics. Is a new drive letter showing up
in the file explorer ? Do you see a blank entry in Disk Management ?
Look for some evidence this new Storage entry is working. The
file system should be recognizable, as they're probably using
some flavor of FAT file system.

If the camera uses MTP protocol, then you need to do a little reading
I consider protocols like this to be consumer unfriendly. And
you won't catch me buying a product using this. I look for
USB Mass Storage protocol instead, as it presents fewer barriers.
In any case, if your camera manual mentions this protocol, there
is some info here.

[URL="http://en.wikipedia.org/wiki/Media_Transfer_Protocol"]http://en.wikipedia.org/wiki/Media_Transfer_Protocol[/URL]

Paul
 >> Stay informed about: Drivers won't install 

Paul wrote:
> desertgal wrote:
>> desertgal wrote:
>>> Paul wrote:
>>>> desertgal wrote:
>>>>> I'm trying to install the drivers for my LG phone but Windows XP
>>>>> won't let me. Following a suggestion in an earlier post I looked
>>>>> for C:\WINDOWS\setupapi.log & opened it in notepad. It shows the
>>>>> installation attempt but says "Error 0xe000022f: The third-party
>>>>> INF does not contain digital signature information." so the
>>>>> drivers didn't install. I find this message for the software from
>>>>> 2 different sources. How do I get Windows to either ignore the
>>>>> unsigned drivers or ask permission to install them? I really want
>>>>> to get the pics off my unusable cell phone.
>>>>>
>>>>> Thanks.
>>>>
>>>> There is a suggestion in this article.
>>>>
>>>> [URL="http://support.microsoft.com/kb/327756"]http://support.microsoft.com/kb/327756[/URL]
>>>>
>>>> I didn't know there was such a setting, but in the Control Panel
>>>> called System, there is an option to change the signing requirement.
>>>>
>>>> Start : Control Panel : System : Hardware : Driver Signing :
>>>>
>>>> Mine is set to "Warn", and I don't think I've ever touched
>>>> that setting. So it has probably been like that since the OS
>>>> was installed.
>>>>
>>>> Paul
>>> Thanks Paul. I didn't know this existed. It was set to warn but it
>>> didn't warn me about the drivers. I've set it to Ignore & I'm going
>>> to try installing the drivers again. Will let you know what happens.
>>>
>> Ok tried again & still nothing. The log fie says the install was
>> successful but it shows as Storage/Removable Media instead of as a
>> modem & the pc doesn't come up with a window about new hardware. It
>> shows the Modem Drivers in Add Remove programs. Also, nothing is
>> showing up in Device manager under usb or ports & it should show in
>> both places when connected. I don't get it, this is frustrating.
>> Forgot to add, every time I install or uninstall the drivers I do a
>> restart.
>>
>
> Does the phone manual mention any "modes" you put the phone in ?
>
> If a phone is being used for networking, then perhaps a modem type
> device showing up would be appropriate. If the phone was being
> used for storage (camera pictures), maybe USB Mass Storage or MTP
> protocol would be used. The camera interface may have some thing
> you have to do, to enable either of those.
>
> I don't own a cellphone, and have no experience with them. (I
> didn't get a Palm Pilot when they were popular either )
>
> For a USB device, there is the UVCView utility from Microsoft,
> for looking at USB configuration data. That allows looking at the
> raw device declaration. But you're already seeing that, in a way,
> by looking at Device Manager. So I'm not sure that looking at
> this is really going to help you.
>
> (Click any dated link here, to start a download of an archived copy
> of UVCView. Microsoft used to offer this for download, but removed
> it from their site. You can get it here.)
>
> [URL="http://web.archive.org/"]http://web.archive.org/[/URL]*/[URL="http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe"]http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe[/URL]
>
>
> Screenshot similar to UVCView.
>
> [URL="http://www.die.de/blog/content/binary/usbview.png"]http://www.die.de/blog/content/binary/usbview.png[/URL]
>
> Microsoft bundles another tool with your OS. You can use
> Start:Run and enter "msinfo32.exe" as the program to run. I
> have WinXP Pro SP3 and it has that program included. Look
> under "Components". The info looks a lot like Device Manager,
> only packaged slightly different.
>
> C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32.exe
>
> If you have something in Storage/Removable Media, perhaps you
> are close to seeing your pics. Is a new drive letter showing up
> in the file explorer ? Do you see a blank entry in Disk Management ?
> Look for some evidence this new Storage entry is working. The
> file system should be recognizable, as they're probably using
> some flavor of FAT file system.
>
> If the camera uses MTP protocol, then you need to do a little reading
> I consider protocols like this to be consumer unfriendly. And
> you won't catch me buying a product using this. I look for
> USB Mass Storage protocol instead, as it presents fewer barriers.
> In any case, if your camera manual mentions this protocol, there
> is some info here.
>
> [URL="http://en.wikipedia.org/wiki/Media_Transfer_Protocol"]http://en.wikipedia.org/wiki/Media_Transfer_Protocol[/URL]
>
> Paul
I know that the older phone is set in usb mode, the newer ones I can't
find a setting. I've got instructions for installing the phone drivers
but XP isn't doing what it's supposed to do, all it will install is the
usb data cable & it uses the built in drivers for that. The irritating
thing is that the software was installed & worked fine before I had to
have XP reinstalled, also it recognizes our other phone which is a
Samsung, but not the LG's.
Nothing is showing up in Device Manager except the usb cable, the
Storage/Removable media is mentioned in the setupapi.log but nowhere else.
 >> Stay informed about: Drivers won't install 

desertgal wrote:

> I know that the older phone is set in usb mode, the newer ones I can't
> find a setting. I've got instructions for installing the phone drivers
> but XP isn't doing what it's supposed to do, all it will install is the
> usb data cable & it uses the built in drivers for that. The irritating
> thing is that the software was installed & worked fine before I had to
> have XP reinstalled, also it recognizes our other phone which is a
> Samsung, but not the LG's.
> Nothing is showing up in Device Manager except the usb cable, the
> Storage/Removable media is mentioned in the setupapi.log but nowhere else.
>

So what is the model number of the LG phone ?

Paul
 >> Stay informed about: Drivers won't install 

"Paul" wrote in message
> desertgal wrote:
>
>> I know that the older phone is set in usb mode, the newer ones I can't
>> find a setting. I've got instructions for installing the phone drivers
>> but XP isn't doing what it's supposed to do, all it will install is the
>> usb data cable & it uses the built in drivers for that. The irritating
>> thing is that the software was installed & worked fine before I had to
>> have XP reinstalled, also it recognizes our other phone which is a
>> Samsung, but not the LG's.
>> Nothing is showing up in Device Manager except the usb cable, the
>> Storage/Removable media is mentioned in the setupapi.log but nowhere
>> else.
>>
>
> So what is the model number of the LG phone ?
>
> Paul

Just read through this thread, and wondered if it's anything to do with COM
/ serial port settings. i.e. my ancient Motorola "clam" cell-phone,
requires a Motorola lead with the "smaller" RS232 serial plug on the PC
end. ....never bought one 'cause camera on it can only take 640x480 vga
pics. !

regards, Richard
 >> Stay informed about: Drivers won't install 

RJK wrote:
> "Paul" wrote in message
>
>> desertgal wrote:
>>
>>
>>> I know that the older phone is set in usb mode, the newer ones I can't
>>> find a setting. I've got instructions for installing the phone drivers
>>> but XP isn't doing what it's supposed to do, all it will install is the
>>> usb data cable & it uses the built in drivers for that. The irritating
>>> thing is that the software was installed & worked fine before I had to
>>> have XP reinstalled, also it recognizes our other phone which is a
>>> Samsung, but not the LG's.
>>> Nothing is showing up in Device Manager except the usb cable, the
>>> Storage/Removable media is mentioned in the setupapi.log but nowhere
>>> else.
>>>
>>>
>> So what is the model number of the LG phone ?
>>
>> Paul
>>
>
> Just read through this thread, and wondered if it's anything to do with COM
> / serial port settings. i.e. my ancient Motorola "clam" cell-phone,
> requires a Motorola lead with the "smaller" RS232 serial plug on the PC
> end. ....never bought one 'cause camera on it can only take 640x480 vga
> pics. !
>
> regards, Richard
>
>
>
Paul,

One of the phones is a VX5200, that's the older one. The other 2 are
VX5400, one of them has damaged screens & that's the one I'm trying to
get the info off of.

Richard,

I don't think it masters what port I plug into to install the drivers.
The program I use to transfer files searches for the phone & uses
whatever port it's on. Theoretically, these LG phones are easier to
transfer to & from than Motorola's, my son had a Razr & I had to do a
lot of changes tot eh programing to be able to transfer things but till
now I've not had a problem with the LG's.
I have the data cables specific to the phones, they have unique plugs on
the phones themselves but a normal usb on the other end.
 >> Stay informed about: Drivers won't install 

desertgal wrote:
> RJK wrote:
>> "Paul" wrote in message
>>
>>> desertgal wrote:
>>>
>>>
>>>> I know that the older phone is set in usb mode, the newer ones I
>>>> can't find a setting. I've got instructions for installing the
>>>> phone drivers but XP isn't doing what it's supposed to do, all it
>>>> will install is the usb data cable & it uses the built in drivers
>>>> for that. The irritating thing is that the software was installed &
>>>> worked fine before I had to have XP reinstalled, also it recognizes
>>>> our other phone which is a Samsung, but not the LG's.
>>>> Nothing is showing up in Device Manager except the usb cable, the
>>>> Storage/Removable media is mentioned in the setupapi.log but nowhere
>>>> else.
>>>>
>>>>
>>> So what is the model number of the LG phone ?
>>>
>>> Paul
>>>
>>
>> Just read through this thread, and wondered if it's anything to do
>> with COM / serial port settings. i.e. my ancient Motorola "clam"
>> cell-phone, requires a Motorola lead with the "smaller" RS232 serial
>> plug on the PC end. ....never bought one 'cause camera on it can only
>> take 640x480 vga pics. !
>>
>> regards, Richard
>>
>>
> Paul,
>
> One of the phones is a VX5200, that's the older one. The other 2 are
> VX5400, one of them has damaged screens & that's the one I'm trying to
> get the info off of.
>
> Richard,
>
> I don't think it masters what port I plug into to install the drivers.
> The program I use to transfer files searches for the phone & uses
> whatever port it's on. Theoretically, these LG phones are easier to
> transfer to & from than Motorola's, my son had a Razr & I had to do a
> lot of changes tot eh programing to be able to transfer things but till
> now I've not had a problem with the LG's.
> I have the data cables specific to the phones, they have unique plugs on
> the phones themselves but a normal usb on the other end.
>
>

VX5400
[URL="http://www.lgmobilephones.com/phone.aspx?id=336"]http://www.lgmobilephones.com/phone.aspx?id=336[/URL]

I did a bit of digging, but at this point, the one thing that stands
out, is you say the phone is showing as Mass Storage. And I get the
impression it is supposed to show up as a USB Serial port and use
some kind of AT command set.

Click any one of the dated links here, to download an archived copy
of UVCView (a USB viewer application). It may show what USB config
info the phone is presenting.

[URL="http://web.archive.org/"]http://web.archive.org/[/URL]*/[URL="http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe"]http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe[/URL]

The device description should be on the right, when the phone is
plugged in. If the phone is a composite device, the various
sub-devices probably have sections further down in the right
hand pane. The viewer application should work if the phone is
plugged directly into the computer (no external USB hub).

[URL="http://www.die.de/blog/content/binary/usbview.png"]http://www.die.de/blog/content/binary/usbview.png[/URL]

Since you have two VX5400 phones, you should compare how they show
up in Device Manager. Maybe the working phone will show as some
kind of USB serial. And the broken phone will show as
USB mass storage (like it is preparing itself for a flash upgrade
or something). As long as both phones support USB "serial numbers"
and have unique serial numbers, the response from Windows should
be unique for them (Windows should treat them separately as far
as I know and not confuse them).

I downloaded and installed the LG modem driver, in my VirtualPC
Win2K image, and looking in the install directory

C:\Program Files\LG Electronics\LG USB Modem Driver

The software looks like it is mainly for older OSes. In other words,
the USB standards support is better in WinXP, so the driver has less
to do. So I don't think the driver will fix it.

There is a free syncing application called BitPIM, and by clicking
the "tarball" button at the bottom of this page, you can get source
code. There is a directory with individual phone entries in it.
Some phones have sequences, to get them to change modes (from
OBEX to AT). The VX5400 file seems pretty simple, with no modes,
so the serial AT communications mode might be all it supports.

[URL="http://bitpim.svn.sourceforge.net/viewvc/bitpim/releases/1.0.6/src/"]http://bitpim.svn.sourceforge.net/viewvc/bitpim/releases/1.0.6/src/[/URL]

[URL="http://www.bitpim.org/"]http://www.bitpim.org/[/URL]

Bitpim cannot work, if the phone is not showing properly in Device
Manager, so at this point, I wouldn't even waste time downloading
the executable and trying it. If the phone doesn't show properly,
even the VZNavigator probably wouldn't work with it.

Paul
 >> Stay informed about: Drivers won't install 

Paul wrote:
> desertgal wrote:
>> RJK wrote:
>>> "Paul" wrote in message
>>
>>>
>>>> desertgal wrote:
>>>>
>>>>
>>>>> I know that the older phone is set in usb mode, the newer ones I
>>>>> can't find a setting. I've got instructions for installing the
>>>>> phone drivers but XP isn't doing what it's supposed to do, all it
>>>>> will install is the usb data cable & it uses the built in drivers
>>>>> for that. The irritating thing is that the software was installed
>>>>> & worked fine before I had to have XP reinstalled, also it
>>>>> recognizes our other phone which is a Samsung, but not the LG's.
>>>>> Nothing is showing up in Device Manager except the usb cable, the
>>>>> Storage/Removable media is mentioned in the setupapi.log but
>>>>> nowhere else.
>>>>>
>>>>>
>>>> So what is the model number of the LG phone ?
>>>>
>>>> Paul
>>>>
>>>
>>> Just read through this thread, and wondered if it's anything to do
>>> with COM / serial port settings. i.e. my ancient Motorola "clam"
>>> cell-phone, requires a Motorola lead with the "smaller" RS232
>>> serial plug on the PC end. ....never bought one 'cause camera on it
>>> can only take 640x480 vga pics. !
>>>
>>> regards, Richard
>>>
>>>
>> Paul,
>>
>> One of the phones is a VX5200, that's the older one. The other 2 are
>> VX5400, one of them has damaged screens & that's the one I'm trying
>> to get the info off of.
>>
>> Richard,
>>
>> I don't think it masters what port I plug into to install the
>> drivers. The program I use to transfer files searches for the phone
>> & uses whatever port it's on. Theoretically, these LG phones are
>> easier to transfer to & from than Motorola's, my son had a Razr & I
>> had to do a lot of changes tot eh programing to be able to transfer
>> things but till now I've not had a problem with the LG's.
>> I have the data cables specific to the phones, they have unique plugs
>> on the phones themselves but a normal usb on the other end.
>>
>>
>
> VX5400
> [URL="http://www.lgmobilephones.com/phone.aspx?id=336"]http://www.lgmobilephones.com/phone.aspx?id=336[/URL]
>
> I did a bit of digging, but at this point, the one thing that stands
> out, is you say the phone is showing as Mass Storage. And I get the
> impression it is supposed to show up as a USB Serial port and use
> some kind of AT command set.
>
> Click any one of the dated links here, to download an archived copy
> of UVCView (a USB viewer application). It may show what USB config
> info the phone is presenting.
>
> [URL="http://web.archive.org/"]http://web.archive.org/[/URL]*/[URL="http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe"]http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe[/URL]
>
>
> The device description should be on the right, when the phone is
> plugged in. If the phone is a composite device, the various
> sub-devices probably have sections further down in the right
> hand pane. The viewer application should work if the phone is
> plugged directly into the computer (no external USB hub).
>
> [URL="http://www.die.de/blog/content/binary/usbview.png"]http://www.die.de/blog/content/binary/usbview.png[/URL]
>
> Since you have two VX5400 phones, you should compare how they show
> up in Device Manager. Maybe the working phone will show as some
> kind of USB serial. And the broken phone will show as
> USB mass storage (like it is preparing itself for a flash upgrade
> or something). As long as both phones support USB "serial numbers"
> and have unique serial numbers, the response from Windows should
> be unique for them (Windows should treat them separately as far
> as I know and not confuse them).
>
> I downloaded and installed the LG modem driver, in my VirtualPC
> Win2K image, and looking in the install directory
>
> C:\Program Files\LG Electronics\LG USB Modem Driver
>
> The software looks like it is mainly for older OSes. In other words,
> the USB standards support is better in WinXP, so the driver has less
> to do. So I don't think the driver will fix it.
>
> There is a free syncing application called BitPIM, and by clicking
> the "tarball" button at the bottom of this page, you can get source
> code. There is a directory with individual phone entries in it.
> Some phones have sequences, to get them to change modes (from
> OBEX to AT). The VX5400 file seems pretty simple, with no modes,
> so the serial AT communications mode might be all it supports.
>
> [URL="http://bitpim.svn.sourceforge.net/viewvc/bitpim/releases/1.0.6/src/"]http://bitpim.svn.sourceforge.net/viewvc/bitpim/releases/1.0.6/src/[/URL]
>
> [URL="http://www.bitpim.org/"]http://www.bitpim.org/[/URL]
>
> Bitpim cannot work, if the phone is not showing properly in Device
> Manager, so at this point, I wouldn't even waste time downloading
> the executable and trying it. If the phone doesn't show properly,
> even the VZNavigator probably wouldn't work with it.
>
> Paul
The thing is, neither phone shows in device manager because XP never
installs the drivers for the phone, just the one for the usb data cable
& it uses the built in XP driver. XP doesn't even "see" the phone so
the add hardware wizard never runs, it only "sees" the usb data cable.

The phone has never showed in device manager as anything, it just isn't
there cause XP is blocking the install.

I have BitPim & that's what I've always used to transfer files to & from
the phone. As you said, no software will work if XP won't install the
phone drivers.
 >> Stay informed about: Drivers won't install 

desertgal wrote:

> The thing is, neither phone shows in device manager because XP never
> installs the drivers for the phone, just the one for the usb data cable
> & it uses the built in XP driver. XP doesn't even "see" the phone so
> the add hardware wizard never runs, it only "sees" the usb data cable.
>
> The phone has never showed in device manager as anything, it just isn't
> there cause XP is blocking the install.
>
> I have BitPim & that's what I've always used to transfer files to & from
> the phone. As you said, no software will work if XP won't install the
> phone drivers.
>

Get out UVCView and copy/paste the info from the phone.

Paul
 >> Stay informed about: Drivers won't install 

Paul wrote:
> desertgal wrote:
>
>> The thing is, neither phone shows in device manager because XP never
>> installs the drivers for the phone, just the one for the usb data
>> cable & it uses the built in XP driver. XP doesn't even "see" the
>> phone so the add hardware wizard never runs, it only "sees" the usb
>> data cable.
>>
>> The phone has never showed in device manager as anything, it just
>> isn't there cause XP is blocking the install.
>>
>> I have BitPim & that's what I've always used to transfer files to &
>> from the phone. As you said, no software will work if XP won't
>> install the phone drivers.
>>
>
> Get out UVCView and copy/paste the info from the phone.
>
> Paul
Hope this is what you need. It doesn't show the phone at all, just the
data cable.


English product name: "USB Data Cable"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x01
Open Pipes: 2

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB
Video Class
bInterval: 0x0A

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB
Video Class
bInterval: 0x0A

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0xFF -> This is a Vendor Specific Device
bDeviceSubClass: 0xFF
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = ( Bytes
idVendor: 0x0DF7 = Mobile Action Technology Inc.
idProduct: 0x0800
bcdDevice: 0x0000
iManufacturer: 0x01
English (United States) "MobileAction Technology Inc."
iProduct: 0x02
English (United States) "USB Data Cable"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0029 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x04
*!*ERROR: no String Descriptor for index 4!
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0x32 = 100 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF -> Vendor Specific Device
bInterfaceSubClass: 0xFF
*!*CAUTION: This appears to be an invalid bInterfaceSubClass
bInterfaceProtocol: 0xFF
*!*WARNING: must be set to PC_PROTOCOL_UNDEFINED 0 for this class
iInterface: 0x00
*!*ERROR: 0xFF is the prerelease USB Video Class ID

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0100
bCountryCode: 0x00
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0025

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB
Video Class
bInterval: 0x0A

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB
Video Class
bInterval: 0x0A
 >> Stay informed about: Drivers won't install 

desertgal wrote:
> Paul wrote:
>> desertgal wrote:
>>
>>> The thing is, neither phone shows in device manager because XP never
>>> installs the drivers for the phone, just the one for the usb data
>>> cable & it uses the built in XP driver. XP doesn't even "see" the
>>> phone so the add hardware wizard never runs, it only "sees" the usb
>>> data cable.
>>>
>>> The phone has never showed in device manager as anything, it just
>>> isn't there cause XP is blocking the install.
>>>
>>> I have BitPim & that's what I've always used to transfer files to &
>>> from the phone. As you said, no software will work if XP won't
>>> install the phone drivers.
>>>
>>
>> Get out UVCView and copy/paste the info from the phone.
>>
>> Paul
> Hope this is what you need. It doesn't show the phone at all, just the
> data cable.
>
>
> English product name: "USB Data Cable"
>
> ConnectionStatus: Current Config Value:
> 0x01 -> Device Bus Speed: Low
> Device Address: 0x01
> Open Pipes: 2
>
> ===>Endpoint Descriptor<===
> bLength: 0x07
> bDescriptorType: 0x05
> bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
> bmAttributes: 0x03 -> Interrupt Transfer Type
> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
> Video Class
> bInterval: 0x0A
>
> ===>Endpoint Descriptor<===
> bLength: 0x07
> bDescriptorType: 0x05
> bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
> bmAttributes: 0x03 -> Interrupt Transfer Type
> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
> Video Class
> bInterval: 0x0A
>
> ===>Device Descriptor<===
> bLength: 0x12
> bDescriptorType: 0x01
> bcdUSB: 0x0100
> bDeviceClass: 0xFF -> This is a Vendor Specific
> Device
> bDeviceSubClass: 0xFF
> bDeviceProtocol: 0x00
> bMaxPacketSize0: 0x08 = ( Bytes
> idVendor: 0x0DF7 = Mobile Action Technology Inc.
> idProduct: 0x0800
> bcdDevice: 0x0000
> iManufacturer: 0x01
> English (United States) "MobileAction Technology Inc."
> iProduct: 0x02
> English (United States) "USB Data Cable"
> iSerialNumber: 0x00
> bNumConfigurations: 0x01
>
> ===>Configuration Descriptor<===
> bLength: 0x09
> bDescriptorType: 0x02
> wTotalLength: 0x0029 -> Validated
> bNumInterfaces: 0x01
> bConfigurationValue: 0x01
> iConfiguration: 0x04
> *!*ERROR: no String Descriptor for index 4!
> bmAttributes: 0x80 -> Bus Powered
> MaxPower: 0x32 = 100 mA
>
> ===>Interface Descriptor<===
> bLength: 0x09
> bDescriptorType: 0x04
> bInterfaceNumber: 0x00
> bAlternateSetting: 0x00
> bNumEndpoints: 0x02
> bInterfaceClass: 0xFF -> Vendor Specific Device
> bInterfaceSubClass: 0xFF
> *!*CAUTION: This appears to be an invalid bInterfaceSubClass
> bInterfaceProtocol: 0xFF
> *!*WARNING: must be set to PC_PROTOCOL_UNDEFINED 0 for this class
> iInterface: 0x00
> *!*ERROR: 0xFF is the prerelease USB Video Class ID
>
> ===>HID Descriptor<===
> bLength: 0x09
> bDescriptorType: 0x21
> bcdHID: 0x0100
> bCountryCode: 0x00
> bNumDescriptors: 0x01
> bDescriptorType: 0x22
> wDescriptorLength: 0x0025
>
> ===>Endpoint Descriptor<===
> bLength: 0x07
> bDescriptorType: 0x05
> bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
> bmAttributes: 0x03 -> Interrupt Transfer Type
> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
> Video Class
> bInterval: 0x0A
>
> ===>Endpoint Descriptor<===
> bLength: 0x07
> bDescriptorType: 0x05
> bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
> bmAttributes: 0x03 -> Interrupt Transfer Type
> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
> Video Class
> bInterval: 0x0A

The fact that the data cable ID is still showing, means the
driver can't contact the phone for some reason. Or that
particular Mobile Action driver doesn't recognize a VX5400 phone
and know what to do with it.

*******

OK, I'm confused. I thought a "data cable" was just a passive
USB cable, with the connector on one end selected based
on the phone. Sometimes the phone connector has multiple
functions, with more than USB wires on it (audio for headphones?).
Which is why there is more than one model of passive USB cable.
The phone end may have more pins than are necessary for USB.

(Examples for LG phones)

[URL="http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0"]http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0[/URL]

Now, I found this interesting. It turns out the Mobile Action is some
kind of bridge device. If the Mobile Action driver was working
on your computer, the USB ID apparently magically changes. And
if it is a bridge, perhaps UVCView cannot see the phone as a result.

[URL="http://www.natox.be/ma8280p/"]http://www.natox.be/ma8280p/[/URL]

I can't tell now, what protocol is on the other end of that cable.
Why have a bridge, when USB works perfectly well ? It implies
the phone is not actually USB.

Does this mean your data cable has malfunctioned ? Or does it
imply that both phones are failing to meet their end of the
protocol, whatever it is ?

I presume the Mobile Action driver has to figure out what USB ID
to fake, such that the proper USB ID is returned for the other
software to use. So the Mobile Action driver must query the phone
some how, to figure that out. Then the Mobile Action does a
USB bus reset, after which, the new USB identity is shown to
the computer. Then, whatever software is relying on seeing an
LG phone identity, should work.

It makes me wonder, whether some other interconnection method
might work instead. Like, if the phone really was USB, would
connecting the phone directly with a passive cable work ?

[URL="http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1"]http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1[/URL]

When I look through the Mobile Action FAQ collection, there is
mention of a "Prolific USB to serial" cable. Which suggests
at least one of the Mobile Action cables is just a USB to
serial (RS232) protocol.

[URL="http://global.mobileaction.com/support/support_Faq.jsp"]http://global.mobileaction.com/support/support_Faq.jsp[/URL]

What is the Mobile Action model number of the data cable ?

In this cell phone adapter schematic, it appears the phone
uses a logic level interface, rather than true
bipolar RS232 levels. So maybe the thing really is weird,
and needs adaptation.

[URL="http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif"]http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif[/URL]

Post the Mobile Action model number, so I can try and find it
on their site.

Paul
 >> Stay informed about: Drivers won't install 

Paul wrote:
> desertgal wrote:
>> Paul wrote:
>>> desertgal wrote:
>>>
>>>> The thing is, neither phone shows in device manager because XP
>>>> never installs the drivers for the phone, just the one for the usb
>>>> data cable & it uses the built in XP driver. XP doesn't even "see"
>>>> the phone so the add hardware wizard never runs, it only "sees" the
>>>> usb data cable.
>>>>
>>>> The phone has never showed in device manager as anything, it just
>>>> isn't there cause XP is blocking the install.
>>>>
>>>> I have BitPim & that's what I've always used to transfer files to &
>>>> from the phone. As you said, no software will work if XP won't
>>>> install the phone drivers.
>>>>
>>>
>>> Get out UVCView and copy/paste the info from the phone.
>>>
>>> Paul
>> Hope this is what you need. It doesn't show the phone at all, just
>> the data cable.
>>
>>
>> English product name: "USB Data Cable"
>>
>> ConnectionStatus: Current Config Value:
>> 0x01 -> Device Bus Speed: Low
>> Device Address: 0x01
>> Open Pipes: 2
>>
>> ===>Endpoint Descriptor<===
>> bLength: 0x07
>> bDescriptorType: 0x05
>> bEndpointAddress: 0x81 -> Direction: IN -
>> EndpointID: 1
>> bmAttributes: 0x03 -> Interrupt Transfer Type
>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>> Video Class
>> bInterval: 0x0A
>>
>> ===>Endpoint Descriptor<===
>> bLength: 0x07
>> bDescriptorType: 0x05
>> bEndpointAddress: 0x02 -> Direction: OUT -
>> EndpointID: 2
>> bmAttributes: 0x03 -> Interrupt Transfer Type
>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>> Video Class
>> bInterval: 0x0A
>>
>> ===>Device Descriptor<===
>> bLength: 0x12
>> bDescriptorType: 0x01
>> bcdUSB: 0x0100
>> bDeviceClass: 0xFF -> This is a Vendor Specific
>> Device
>> bDeviceSubClass: 0xFF
>> bDeviceProtocol: 0x00
>> bMaxPacketSize0: 0x08 = ( Bytes
>> idVendor: 0x0DF7 = Mobile Action Technology Inc.
>> idProduct: 0x0800
>> bcdDevice: 0x0000
>> iManufacturer: 0x01
>> English (United States) "MobileAction Technology Inc."
>> iProduct: 0x02
>> English (United States) "USB Data Cable"
>> iSerialNumber: 0x00
>> bNumConfigurations: 0x01
>>
>> ===>Configuration Descriptor<===
>> bLength: 0x09
>> bDescriptorType: 0x02
>> wTotalLength: 0x0029 -> Validated
>> bNumInterfaces: 0x01
>> bConfigurationValue: 0x01
>> iConfiguration: 0x04
>> *!*ERROR: no String Descriptor for index 4!
>> bmAttributes: 0x80 -> Bus Powered
>> MaxPower: 0x32 = 100 mA
>>
>> ===>Interface Descriptor<===
>> bLength: 0x09
>> bDescriptorType: 0x04
>> bInterfaceNumber: 0x00
>> bAlternateSetting: 0x00
>> bNumEndpoints: 0x02
>> bInterfaceClass: 0xFF -> Vendor Specific Device
>> bInterfaceSubClass: 0xFF
>> *!*CAUTION: This appears to be an invalid bInterfaceSubClass
>> bInterfaceProtocol: 0xFF
>> *!*WARNING: must be set to PC_PROTOCOL_UNDEFINED 0 for this class
>> iInterface: 0x00
>> *!*ERROR: 0xFF is the prerelease USB Video Class ID
>>
>> ===>HID Descriptor<===
>> bLength: 0x09
>> bDescriptorType: 0x21
>> bcdHID: 0x0100
>> bCountryCode: 0x00
>> bNumDescriptors: 0x01
>> bDescriptorType: 0x22
>> wDescriptorLength: 0x0025
>>
>> ===>Endpoint Descriptor<===
>> bLength: 0x07
>> bDescriptorType: 0x05
>> bEndpointAddress: 0x81 -> Direction: IN -
>> EndpointID: 1
>> bmAttributes: 0x03 -> Interrupt Transfer Type
>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>> Video Class
>> bInterval: 0x0A
>>
>> ===>Endpoint Descriptor<===
>> bLength: 0x07
>> bDescriptorType: 0x05
>> bEndpointAddress: 0x02 -> Direction: OUT -
>> EndpointID: 2
>> bmAttributes: 0x03 -> Interrupt Transfer Type
>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>> Video Class
>> bInterval: 0x0A
>
> The fact that the data cable ID is still showing, means the
> driver can't contact the phone for some reason. Or that
> particular Mobile Action driver doesn't recognize a VX5400 phone
> and know what to do with it.
>
> *******
>
> OK, I'm confused. I thought a "data cable" was just a passive
> USB cable, with the connector on one end selected based
> on the phone. Sometimes the phone connector has multiple
> functions, with more than USB wires on it (audio for headphones?).
> Which is why there is more than one model of passive USB cable.
> The phone end may have more pins than are necessary for USB.
>
> (Examples for LG phones)
>
> [URL="http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0"]http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0[/URL]
>
>
> Now, I found this interesting. It turns out the Mobile Action is some
> kind of bridge device. If the Mobile Action driver was working
> on your computer, the USB ID apparently magically changes. And
> if it is a bridge, perhaps UVCView cannot see the phone as a result.
>
> [URL="http://www.natox.be/ma8280p/"]http://www.natox.be/ma8280p/[/URL]
>
> I can't tell now, what protocol is on the other end of that cable.
> Why have a bridge, when USB works perfectly well ? It implies
> the phone is not actually USB.
>
> Does this mean your data cable has malfunctioned ? Or does it
> imply that both phones are failing to meet their end of the
> protocol, whatever it is ?
>
> I presume the Mobile Action driver has to figure out what USB ID
> to fake, such that the proper USB ID is returned for the other
> software to use. So the Mobile Action driver must query the phone
> some how, to figure that out. Then the Mobile Action does a
> USB bus reset, after which, the new USB identity is shown to
> the computer. Then, whatever software is relying on seeing an
> LG phone identity, should work.
>
> It makes me wonder, whether some other interconnection method
> might work instead. Like, if the phone really was USB, would
> connecting the phone directly with a passive cable work ?
>
> [URL="http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1"]http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1[/URL]
>
>
> When I look through the Mobile Action FAQ collection, there is
> mention of a "Prolific USB to serial" cable. Which suggests
> at least one of the Mobile Action cables is just a USB to
> serial (RS232) protocol.
>
> [URL="http://global.mobileaction.com/support/support_Faq.jsp"]http://global.mobileaction.com/support/support_Faq.jsp[/URL]
>
> What is the Mobile Action model number of the data cable ?
>
> In this cell phone adapter schematic, it appears the phone
> uses a logic level interface, rather than true
> bipolar RS232 levels. So maybe the thing really is weird,
> and needs adaptation.
>
> [URL="http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif"]http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif[/URL]
>
>
> Post the Mobile Action model number, so I can try and find it
> on their site.
>
> Paul
The cable is specific to the phone model, the number on the cable is
MA-8072P. I've used it before with no problem until XP was
reinstalled. The plug on the phone end is small & flat, not square like
a regular usb. The software I have for the phone is updated for the
VX5400 & downloaded from the MA site.
 >> Stay informed about: Drivers won't install