I have a 12 in 1 Card Reader plugged into a USB port in my computer that
I've had for probably a year and a half. It has worked fine up until about
5 months ago. Sometimes when I boot up the computer, the device will be
recognized, be listed as available in Windows Explorer and work fine. Other
times when I boot the computer, it isn't recognized as being there.

Also, there are times when I'm at the computer and for no apparent reason,
I'll hear that "USB Device Disconnected" ding and find that I've lost the
reader...just like it was unplugged.

The device always has power since it's lit up. This isn't a major issue
since I plan on getting a new computer pretty soon and I have a laptop with
a built in card reader, but it is an annoyance! Any ideas? Thanks.

--
Paul
Cleveland, Ohio

Have you tried different ports?

Paul wrote:

> I have a 12 in 1 Card Reader plugged into a USB port in my computer that
> I've had for probably a year and a half. It has worked fine up until about
> 5 months ago. Sometimes when I boot up the computer, the device will be
> recognized, be listed as available in Windows Explorer and work fine. Other
> times when I boot the computer, it isn't recognized as being there.
>
> Also, there are times when I'm at the computer and for no apparent reason,
> I'll hear that "USB Device Disconnected" ding and find that I've lost the
> reader...just like it was unplugged.
>
> The device always has power since it's lit up. This isn't a major issue
> since I plan on getting a new computer pretty soon and I have a laptop with
> a built in card reader, but it is an annoyance! Any ideas? Thanks.
>

"Bob I" <(E-Mail Removed)> wrote

> Have you tried different ports?

Short answer: Yes. And that sometimes works.

Slightly longer answer: Yes. But *why* should that work at all?

And an even longer question:

Why should attaching a USB device that doesn't work in one port to another
port miraculously restore the aforesaid device to life?

--
Bob
http://www.kanyak.com

Power draw? Or perhaps the connectors are a bit iffy, and insert/removal
wipes the surface oxidation and then it will work?

Opinicus wrote:
> "Bob I" <(E-Mail Removed)> wrote
>
>
>>Have you tried different ports?
>
>
> Short answer: Yes. And that sometimes works.
>
> Slightly longer answer: Yes. But *why* should that work at all?
>
> And an even longer question:
>
> Why should attaching a USB device that doesn't work in one port to another
> port miraculously restore the aforesaid device to life?
>

Opinicus wrote:
> "Bob I" <(E-Mail Removed)> wrote
>
>> Have you tried different ports?
>
> Short answer: Yes. And that sometimes works.
>
> Slightly longer answer: Yes. But *why* should that work at all?
>
> And an even longer question:
>
> Why should attaching a USB device that doesn't work in one port to another
> port miraculously restore the aforesaid device to life?
>

Try UVCview, the Microsoft USB viewer.

http://www.microsoft.com/whdc/device...VCViewdwn.mspx

As long as the ports in question, are all visible in the UVCView window,
you should be able to observe whether the 12-in-1 is visible in the
ports you are testing. The problem could either be the info already
stored in your OS USB data structures, or the problem could be
physical, such as bad cables or connectors. (Like some front panel
USB connectors are not USB2 capable, because of signal quality
problems).

Paul

"Paul" <(E-Mail Removed)> wrote in message news:fds6l8$4fu$(E-Mail Removed)...
> Opinicus wrote:
>> "Bob I" <(E-Mail Removed)> wrote
>>
>>> Have you tried different ports?
>>
>> Short answer: Yes. And that sometimes works.
>>
>> Slightly longer answer: Yes. But *why* should that work at all?
>>
>> And an even longer question:
>>
>> Why should attaching a USB device that doesn't work in one port to
>> another port miraculously restore the aforesaid device to life?
>>
>
> Try UVCview, the Microsoft USB viewer.
>
> http://www.microsoft.com/whdc/device...VCViewdwn.mspx
>
> As long as the ports in question, are all visible in the UVCView window,
> you should be able to observe whether the 12-in-1 is visible in the
> ports you are testing. The problem could either be the info already
> stored in your OS USB data structures, or the problem could be
> physical, such as bad cables or connectors. (Like some front panel
> USB connectors are not USB2 capable, because of signal quality
> problems).
>

Does something like this exist for Firewire?

M.I.5¾ wrote:
> "Paul" <(E-Mail Removed)> wrote in message news:fds6l8$4fu$(E-Mail Removed)...
>> Opinicus wrote:
>>> "Bob I" <(E-Mail Removed)> wrote
>>>
>>>> Have you tried different ports?
>>> Short answer: Yes. And that sometimes works.
>>>
>>> Slightly longer answer: Yes. But *why* should that work at all?
>>>
>>> And an even longer question:
>>>
>>> Why should attaching a USB device that doesn't work in one port to
>>> another port miraculously restore the aforesaid device to life?
>>>
>> Try UVCview, the Microsoft USB viewer.
>>
>> http://www.microsoft.com/whdc/device...VCViewdwn.mspx
>>
>> As long as the ports in question, are all visible in the UVCView window,
>> you should be able to observe whether the 12-in-1 is visible in the
>> ports you are testing. The problem could either be the info already
>> stored in your OS USB data structures, or the problem could be
>> physical, such as bad cables or connectors. (Like some front panel
>> USB connectors are not USB2 capable, because of signal quality
>> problems).
>>
>
> Does something like this exist for Firewire?
>
>

Haven't run into one.

Paul