SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 20 | March | 2005 ]

>> Next Message >>


Date: Sun, 20 Mar 2005 10:45:36 PST8
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: usb drivers

Content Type: text/plain

Jon Harrison wrote:

> What is the difference between usbuhcd.sys and usbohcd.sys? Does it
> matter which one is used?
>
> I have eCS v1.1 running on a P3 using usbuhcd.sys and it sees my
> camera's memory card in a SanDisk 12-in-1 card reader. The same
> reader in eCS v1.2 on an ASUS SMP system does not read the memory
> card but does assign a drive to the device.

Jon,

I can only give you the headlines on this, not any fine details, but
there seem to be 3 varieties of USB chipset. Different computers
(with built-ins) or different USB cards can have different chipsets.
I believe that my two systems each have 2 of the 3 chipset types
represented, though not necessarily the same two in each case. This
setup (for eCS) is an attempt to accomodate the various
possibilities. IMO, it is best -- or most easily -- handled when eCS
is installed, and whatever you have should be detected by the
installer, which then sets your Config.Sys accordingly.

No amount of retrofit finagling on my part was able to set up a
working USB stack for eCS 1.0. Tthe 1.1 install got it close enough
that a little tweaking after the fact resulted in one that was usable,
if not ideal. The 1.1 install got it quite usable right out of the
box, though I still see some minor anomalies that don't crop up on
WinBlows.

> I added usbuhcd to the ASUS but it didn't change the problem.

Very possibly not relevant for that system. You should generate a
report with PCI049VKD (available on Hobbes), showing just what your
system has, and keep it for future reference.

> Furthermore, usbmon does not show any device in the ASUS system.

Even if it was working normally, that is not absolute proof of
anything. Some USB devices just ain't gonna work for us, period . .
. at least as things stand today. The USB site at OS2WARP.BE (not
sure of that URL, but easy enough to find) has a list of various USB
devices that are known to work, which comes in handy before you fork
over the green.

> Finally, the usb drivers in the P3 (the ones that work) are dated
> Sep 03 and the ones in the Asus are dated May 04.

Sometimes this matters, sometimes not.

HTH.

Jordan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


>> Next Message >>

Return to [ 20 | March | 2005 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.