I just updated to KRZRs, and am quite happy with them, except that Motorola Phone Tools hangs when trying to recognize them. I have the latest version (v4.36c), and everything worked with my previous V265s. Now, when I connect either KRZR, they're recognized as "Motorola K1m/L7c" and the driver files begin to get copied. The process hangs up at the completion of the copying of mqdmwhnt.sys. After several minutes, a message pops up saying that my 'phone couldn't be recognized, and would I like update the phone list and re-detect it. I allow this, and am then informed that I have the latest version.
After this, my USB bus appears to be in a hung state, as Windows (XP Pro) will not shut down normally; rather, I have to do a hard manual power-off, then restart to restore full system functionality.
I have tried removing and reinstalling Phone Tools (with a restart in between, just for yuks) with my ant-virus (ZoneAlarm Security Suite) disabled. I have also tried using different USB ports. The behavior is always the same.
I've also verified that the KRZRs have the latest firmware revision.
I requested technical assistance from Avanquest and received a couple of simplistic suggestions that had no effect on the problem. Now, my further requests for help are simply ignored.
John Miller wrote:
> I just updated to KRZRs, and am quite happy with them, except that Motorola
> Phone Tools hangs when trying to recognize them. I have the latest version
> (v4.36c), and everything worked with my previous V265s. Now, when I
> connect either KRZR, they're recognized as "Motorola K1m/L7c" and the driver
> files begin to get copied. The process hangs up at the completion of the
> copying of mqdmwhnt.sys. After several minutes, a message pops up saying that
> my 'phone couldn't be recognized, and would I like update the phone list and
> re-detect it. I allow this, and am then informed that I have the latest version.
>
If MPT allowed access to your v265, you must have done a seem edit to
make it possible.
I suggest you visit www.howardforums.com, Verizon forum, and seek
information on the Verizon version of this phone. You might yet need a
seem edit to make MPT work with the phone.
"Quaoar" <quaoar@marcabfleet.com> wrote in message
news:fP2dnbnPFOYOFEnYnZ2dnUVZ_vninZ2d@comcast.com. ..
John Miller wrote:
> I just updated to KRZRs, and am quite happy with them, except that
> Motorola
> Phone Tools hangs when trying to recognize them. I have the latest
> version
> (v4.36c), and everything worked with my previous V265s. Now, when I
> connect either KRZR, they're recognized as "Motorola K1m/L7c" and the
> driver
> files begin to get copied. The process hangs up at the completion of the
> copying of mqdmwhnt.sys. After several minutes, a message pops up saying
> that
> my 'phone couldn't be recognized, and would I like update the phone list
> and
> re-detect it. I allow this, and am then informed that I have the latest
> version.
>
If MPT allowed access to your v265, you must have done a seem edit to
make it possible.
I suggest you visit www.howardforums.com, Verizon forum, and seek
information on the Verizon version of this phone. You might yet need a
seem edit to make MPT work with the phone.
Q
Actually, no seem edit was necessary for the V265; however, MPT's ability to
transfer photos and ringtones was disabled.
John Miller wrote:
> "Quaoar" <quaoar@marcabfleet.com> wrote in message
> news:fP2dnbnPFOYOFEnYnZ2dnUVZ_vninZ2d@comcast.com. ..
> John Miller wrote:
>> I just updated to KRZRs, and am quite happy with them, except that
>> Motorola
>> Phone Tools hangs when trying to recognize them. I have the latest
>> version
>> (v4.36c), and everything worked with my previous V265s. Now, when I
>> connect either KRZR, they're recognized as "Motorola K1m/L7c" and the
>> driver
>> files begin to get copied. The process hangs up at the completion of the
>> copying of mqdmwhnt.sys. After several minutes, a message pops up saying
>> that
>> my 'phone couldn't be recognized, and would I like update the phone list
>> and
>> re-detect it. I allow this, and am then informed that I have the latest
>> version.
>>
>
> If MPT allowed access to your v265, you must have done a seem edit to
> make it possible.
>
> I suggest you visit www.howardforums.com, Verizon forum, and seek
> information on the Verizon version of this phone. You might yet need a
> seem edit to make MPT work with the phone.
>
> Q
>
> Actually, no seem edit was necessary for the V265; however, MPT's ability to
> transfer photos and ringtones was disabled.
>
> - John
>
>
MPT actually was not disabled. The v265 was disabled, and only a seem
edit would restore the transfer capability. ...unless you have a special
firmware in the v265 that I've not heard of.
you can also pick your phone manually. Under tools,general setup,
click on the communication tab, change modem. Don't detect, let me
chose. under CDMA, you can select the k1mm. This will allow you to
send pictures to your phone, bacause the multimedia studio will appear
in the window. I tried to send mp3 and ringtones through with no
success, but was able to send pictures through. You can do music using
verizon's VCAST. Still working on ringtones. Waiting on memory chip.
On Sun, 04 Mar 2007 00:23:59 -0700, Quaoar <quaoar@tenthplanet.net>
wrote:
>John Miller wrote:
>> "Quaoar" <quaoar@marcabfleet.com> wrote in message
>> news:fP2dnbnPFOYOFEnYnZ2dnUVZ_vninZ2d@comcast.com. ..
>> John Miller wrote:
>>> I just updated to KRZRs, and am quite happy with them, except that
>>> Motorola
>>> Phone Tools hangs when trying to recognize them. I have the latest
>>> version
>>> (v4.36c), and everything worked with my previous V265s. Now, when I
>>> connect either KRZR, they're recognized as "Motorola K1m/L7c" and the
>>> driver
>>> files begin to get copied. The process hangs up at the completion of the
>>> copying of mqdmwhnt.sys. After several minutes, a message pops up saying
>>> that
>>> my 'phone couldn't be recognized, and would I like update the phone list
>>> and
>>> re-detect it. I allow this, and am then informed that I have the latest
>>> version.
>>>
>>
>> If MPT allowed access to your v265, you must have done a seem edit to
>> make it possible.
>>
>> I suggest you visit www.howardforums.com, Verizon forum, and seek
>> information on the Verizon version of this phone. You might yet need a
>> seem edit to make MPT work with the phone.
>>
>> Q
>>
>> Actually, no seem edit was necessary for the V265; however, MPT's ability to
>> transfer photos and ringtones was disabled.
>>
>> - John
>>
>>
>
>MPT actually was not disabled. The v265 was disabled, and only a seem
>edit would restore the transfer capability. ...unless you have a special
>firmware in the v265 that I've not heard of.
>
>Q