I hate usbstor.sys!! (subtitle: how to get an external CD-..

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

What is the situation?
Trying to hook up a 2.0 USB mass storage device to a USB 1.1 port.
I've tried a couple different external devices, with the same results.
XP says it cannot locate usbstor.sys when installing the plug and
pray device. In fact, this file does not exist anywhere in my Windows
directory (or any other directory for that matter).

Am I a lazy web user?
Well, sometimes. But I really did many different searches to try to
figure out the problem. Nobody has directly addressed this issue,
even though others have mentioned it.


What do I want from this group?
I really want someone to provide insight into what to do at this
point. Others have pointed out that just copying that file into the
windows/system32/drivers directory doesn't fix it. Can someone
suggest an approach to resolve this issue?

Thanks!

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I don't believe that's a hidden file . . .

>-----Original Message-----
>C:\Windows\ServicePackFiles\i386
>C:\Windows\system32\drivers
>C:\Windows\Driver Cache\i386\sp1.cab
>C:\Windows\ServicePackFiles\i386\sp1.cab
>C:\Windows\Driver Cache\i386\driver.cab
>
>And I don't even have any external drives!
>
>Perhaps you need to enable searching for Hidden Files and
Folders!
>--
>Cari
>MS-MVP Windows Technologies - Printing/Imaging/Hardware
>www.coribright.com
>
>"DrewJ" <drewje@hotmail.com> wrote in message
>news:9b313652.0405201158.18ffcbd8@posting.google.com...
>> What is the situation?
>> Trying to hook up a 2.0 USB mass storage device to a
USB 1.1 port.
>> I've tried a couple different external devices, with
the same results.
>> XP says it cannot locate usbstor.sys when installing
the plug and
>> pray device. In fact, this file does not exist
anywhere in my Windows
>> directory (or any other directory for that matter).
>>
>> Am I a lazy web user?
>> Well, sometimes. But I really did many different
searches to try to
>> figure out the problem. Nobody has directly addressed
this issue,
>> even though others have mentioned it.
>>
>>
>> What do I want from this group?
>> I really want someone to provide insight into what to
do at this
>> point. Others have pointed out that just copying that
file into the
>> windows/system32/drivers directory doesn't fix it. Can
someone
>> suggest an approach to resolve this issue?
>>
>> Thanks!
>
>
>.
>

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Yves Leclerc" <yleclercNOSPAM@maysys.com> wrote in message news:<uJIT2q2PEHA.2452@TK2MSFTNGP11.phx.gbl>...
> If you have SP1 installed, then it should be able to locate the file
> correctly.
>

I do have SP1 installed. My laptop is managed with system policies,
so I cannot reinstall SP1 or even access the Windows Update site.
Corporate america - great.

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

a little rude don't you think.

First of all maybe you should have mentioned this first "My laptop is managed with system policies,
so I cannot reinstall SP1 or even access the Windows Update site." Does the laptop belong to you or a company you work for? If a company contact the company tech support.

Secondly adding a USB 2.0 device to a 1.1 port???

r


----- DrewJ wrote: -----

So, it appears I'm getting the same non-answer that I've found
throughout the newsgroups. Wish someone had a solution to this.

drewje@hotmail.com (DrewJ) wrote in message news:<9b313652.0405201158.18ffcbd8@posting.google.com>...
> What is the situation?
> Trying to hook up a 2.0 USB mass storage device to a USB 1.1 port.
> I've tried a couple different external devices, with the same results.
> XP says it cannot locate usbstor.sys when installing the plug and
> pray device. In fact, this file does not exist anywhere in my Windows
> directory (or any other directory for that matter).
>> Am I a lazy web user?
> Well, sometimes. But I really did many different searches to try to
> figure out the problem. Nobody has directly addressed this issue,
> even though others have mentioned it.
>>> What do I want from this group?
> I really want someone to provide insight into what to do at this
> point. Others have pointed out that just copying that file into the
> windows/system32/drivers directory doesn't fix it. Can someone
> suggest an approach to resolve this issue?
>> Thanks!