What Microsoft doesn't want you to read - NT and USB devices

[joy]

Several people have asked the question
"Is there a freeware app that allows the use of USB devices on NT4."

Rather than Microsoft's party line (no support, yada, yada, yada) I'd
like to share a SUCCESS STORY and solicit others to post theirs.

I recently tried Woodhead's beta USB driver at
www.geocities.com/mypublic99/
Worked great to read/write to a 132 meg+ flash key device purchased
at Fry's electronics. After I installed the .sys files, and started
the device per instructions, I simply pressed F5 to refresh the file
directory list in Explorer. You can also see the device in a DOS box.
For me, it was Z:

Specs: Toshiba Laptop Tecra 8100, Windows NT. SP6 . USB port is built
in.

Along with the .sys files, there are .reg files. If you are paranoid,
like me, look at these registry files and/or backup before you click
to update. As far as interrupts and conflicts, I have not seen any
so far.

Does anyone else have a USB on Windows NT success story to share?

 

[Chris Dubea]

Several people have asked the question
"Is there a freeware app that allows the use of USB devices on NT4."

Rather than Microsoft's party line (no support, yada, yada, yada) I'd
like to share a SUCCESS STORY and solicit others to post theirs.

I recently tried Woodhead's beta USB driver at
www.geocities.com/mypublic99/
Worked great to read/write to a 132 meg+ flash key device purchased
at Fry's electronics. After I installed the .sys files, and started
the device per instructions, I simply pressed F5 to refresh the file
directory list in Explorer. You can also see the device in a DOS box.
For me, it was Z:

Does anyone else have a USB on Windows NT success story to share?

I have a USB - NT failure to share. I downloaded a similar looking
driver from a Chinese author several years ago. After installing it,
my NT installation was COMPLETELY hosed. Reinstallation did not
repair the damage. I had to reformate the partition and reinstall
everything from scratch.

The moral of the story is BEWARE. Don't try this in a NT box with
critical data. You might regret it.

Chris

 

[joy]

One should, of course, perform due diligence on such software. Steps
might include looking at the source code, if available (woodhead's
code is), examining the registry changes in the .reg file, searching
for postive/negative reports on BBS, google groups, etc., determining
how often the software has been updated, and its status-alpha/beta/GA
and corresponding with the author.

Sorry you had a bad experience, Chris - but one has to ask the due
diligence steps that you performed, and how rigorous those steps were.

Joy