USB storage devices on ASUS A7V333 / W4-4.52
Andrew Stephenson
20GB USB HDD. Having visited Google and scanned for plausible
keywords, it looks like this is a black art, so pointers as to
good incantations would be appreciated.
Essentials:
Installed Warp 4.52 off the IBM MCP2 disks;
M/board is an Asus A7V333-X which has 4 USB-2 outlets;
There are no other USB devices in the system (yet).
The Award BIOS indicates the USB circuitry is powered, etc.
The USB parts of my CONFIG.SYS are probably gibberish by now:
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBD.SYS /REQ:USBUHCD$
BASEDEV=USBHID.SYS
BASEDEV=USBMSD.ADD
REM BASEDEV=USBCDROM.ADD
REM DEVICE=F:\OS2\BOOT\USBKBD.SYS
REM DEVICE=F:\OS2\BOOT\USBMOUSE.SYS
REM DEVICE=F:\OS2\BOOT\USBCOM.SYS
TIA.
--
Andrew Stephenson
Peter Brown
Apologies if this turns up more than once: I seem to be having some
problems posting to my regular news servers (news.ntlworld.com and
text.news.ntlworld.com) - looks like someone has deleted their password
lists as my posts seem to have been rejected by both servers.
Anyway, I am using the recently released USB updates (from either IBM or
eCS) to access a Digital Camera as a Removable Drive without any
problems. My m/board is a Jetway V333U which is, I think, the same VIA
chipset that your board uses. Which drivers are you using?
Silly question: Are you doing the "Refresh Removable Media" bit? - in
the Drives folder.
Regards
Pete
Andrew Stephenson
lose...@ntlworld.com "Peter Brown" writes:
> Anyway, I am using the recently released USB updates (from
> either IBM or eCS) to access a Digital Camera as a Removable
> Drive without any problems. My m/board is a Jetway V333U which
> is, I think, the same VIA chipset that your board uses. Which
> drivers are you using?
I'm using the newest "basic" set, from IBM. As a side note, IBM
has to be complimented on making them extremely easy to install.
That said, sadly they don't seem to have cut it. Do I need any
others for a HDD? David Johnson, who reminded me of them (credit
where it's due), suggested IBM may be getting close to making USB
work with actual HDDs. So far, however, no banana.
According to the m/b Book Of Words, Northbridge is VIA KT333 and
Southbridge is VIA VT8235. The IBM sniffer program happily found
all four USB ports and seemed quite sure about them. The install
program then set up my CONFIG.SYS with these lines:
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
BASEDEV=USBHID.SYS
BASEDEV=USBMSD.ADD
> Silly question: Are you doing the "Refresh Removable Media"
> bit? - in the Drives folder.
Oh, it's a perfectly reasonable question. Yes thanks. Not that
it makes a sneeze of difference. Looks like HDDs-on-USB are one
of those El Dorado OS/2 objectives: something for eCS to get the
jump on IBM over, perhaps.
--
Andrew Stephenson
Michael Potthoff
http://hobbes.nmsu.edu/pub/os2/system/drivers/storage/cw-usbmsd-v1_2b.zip
Michael
rj friedman
(Andrew Stephenson) wrote:
»The IBM sniffer program happily found
»all four USB ports and seemed quite sure about them. The install
»program then set up my CONFIG.SYS with these lines:
»
»BASEDEV=USBUHCD.SYS
»BASEDEV=USBUHCD.SYS
»BASEDEV=USBUHCD.SYS
»BASEDEV=USBEHCD.SYS
»BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
»BASEDEV=USBHID.SYS
»BASEDEV=USBMSD.ADD
You might try putting some extra info into the
BASEDEV=USBMSD.ADD line to see if that helps.
Try this:
BASEDEV=USBMSD.ADD /V /FLOPPIES:0 /REMOVABLES:0
/FIXED_DISKS:1
(assuming you don't have any floppy or removable drives
attached, of course).
--
________________________________________________________
[RJ] OS/2 - Live it, or live with it.
rj friedman Team ABW
Taipei, Taiwan r...@yyyindoserv.com
To send email - remove the `yyy'
________________________________________________________
Andrew Stephenson
am...@deltrak.demon.co.uk "Andrew Stephenson" writes:
> [...]
Ladies && Gentlemen, we have a winner! One USB LaCie 20GB Pocket
Drive working on Warp 4.52 as a normal HDD... Details later: it
is now 03:48; getting here has been hairy; and I need some zizz.
--
Andrew Stephenson
Andrew Stephenson
am...@deltrak.demon.co.uk "Andrew Stephenson" writes:
FWIW here's how I got it to work. Keep in mind that this is the
result of several people, some ordinarily at each others' throats
for reasons I cannot fathom, cooperating in various ways. Those
of you who recognise your contribution to this effort may indulge
in some quietly smug satisfaction.
HARDWARE: Asus m/board A7V333-X, bought in early March 2003. (It
has the Realtek 6-channel codec.) Southbridge is the VIA VT8235,
providing 6 x USB 2.0 ports -- but I don't know how to select the
two not catered to by m/b default hardware. (Extra USB card?)
UNDERLYING SOFTWARE: Warp 4.52, as installed from MCP2 disks.
NEW SOFTWARE: IBM's recent "basic" USB drivers. I had to use my
SWC ID and password. Lacking these, I cannot say what people do.
Hobbes seems not to have the drivers. Maybe eCS users are served
separately.
The drivers have a simple installation procedure (RTFM) which can
update the USB lines in CONFIG.SYS for you.
NEW SOFTWARE: Once the new IBM drivers are in place, obtain Chris
Wohlgemuth's improved USBMSD.ADD (God bless you, squire), part of
his freeware package on Hobbes (ignore line-wrap):
http://hobbes.nmsu.edu/pub/os2/system/drivers/storage/
cw-usbmsd-v1_2b.zip
Chris' documentation explains the other components are not quite
as versatile as IBM's, so I only replaced IBM's USBMSD.ADD with
his CWUSBMSD.ADD and fiddled with arguments. My USB lines read
(NB, the mix of USB?HCD.SYS lines was caused by hardware, which
the IBM sniffer/installer will recognise and handle for you):
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
BASEDEV=USBHID.SYS
BASEDEV=CWUSBMSD.ADD /V /FLOPPIES:0 /REMOVABLES:1 /FIXED_DISKS:0 /FORCE_TO_REMOVABLE
USB HDD: LaCie USB 2.0 Pocket Drive, 20 GB. Once the previous
changes have been made, plugging the drive in elicits a short
computer beep when it has been detected.
This, however, was not the end of my fun, but the start of still
more, because LaCie (gotta love 'em) helpfully preformatted it as
FAT32-EXT (eh?) which my system did not like, not one little bit.
An attempt to apply LVM to the problem failed (details lost in a
fog of Wee Small Hours blood-sweat-'n'-swearing).
So DFSee 5.15 was wheeled out. (Go to www.mensys.nl and persuade
them to take 30 euros for Jan van Wijk's scary powerful monster.)
This let me stomp the existing rubbish, after which LVM managed
to set the drive up as a logical drive with one partition. Note
that 7 MB of free space seem to be inaccessible and wasted.
The HDD was formatted using standard Warp tools. This can take a
longish time with nothing obvious happening at first; be patient.
Now I simply have to:
* plug in the USB drive;
* wait for the beep (if the drive is already plugged in at boot
time, the beep happens then);
* click on "Refresh Removable Media" in Drives (sometimes twice
for some obscure reason), after which an empty window appears
for a few seconds;
* the drive's icon appears, lettered to follow my existing HDD
partitions (because it's a logical partition, I assume);
and
* use it.
Before unplugging the drive, one is advised to click on "Eject
disk" in its menu, to ensure everything is saved to disk. This
also removes the icon from the Drives folder.
BTW, if you then click on "Refresh..." without touching the plug,
there is no beep but the USB HDD reappears in Drives.
USB 2.0 speed is satisfactory for my purposes, as I plan to use
it for backup. A quick test showed, however, that moving files
onto and off it in normal use happens at very acceptable rates.
Standard HDD actions seem to be available and to work correctly.
HTH somebody. Thanks to you all, gang.
--
Andrew Stephenson
William L. Hartzell
Andrew Stephenson wrote:
>
> So DFSee 5.15 was wheeled out. (Go to www.mensys.nl and persuade
> them to take 30 euros for Jan van Wijk's scary powerful monster.)
> This let me stomp the existing rubbish, after which LVM managed
> to set the drive up as a logical drive with one partition. Note
> that 7 MB of free space seem to be inaccessible and wasted.
>
If you only have one fixed disk, then this disk will have seven MB
reserved for Boot Manager. Fdisk and LVM reserve seven MB (one cylinder
worth of space) for Boot Manager on both the first fixed disk and the
second.
--
Bill
Thanks a Million!
Jack Troughton
>In article <104804...@deltrak.demon.co.uk>
> am...@deltrak.demon.co.uk "Andrew Stephenson" writes:
>
>> In article <104802...@deltrak.demon.co.uk>
>> am...@deltrak.demon.co.uk "Andrew Stephenson" writes:
>>
>> > [...]
>>
>> Ladies && Gentlemen, we have a winner! One USB LaCie 20GB Pocket
>> Drive working on Warp 4.52 as a normal HDD... Details later: it
>> is now 03:48; getting here has been hairy; and I need some zizz.
>
>FWIW here's how I got it to work. Keep in mind that this is the
>result of several people, some ordinarily at each others' throats
>for reasons I cannot fathom, cooperating in various ways. Those
>of you who recognise your contribution to this effort may indulge
>in some quietly smug satisfaction.
<snip>
>Before unplugging the drive, one is advised to click on "Eject
>disk" in its menu, to ensure everything is saved to disk. This
>also removes the icon from the Drives folder.
>
>BTW, if you then click on "Refresh..." without touching the plug,
>there is no beep but the USB HDD reappears in Drives.
>
>USB 2.0 speed is satisfactory for my purposes, as I plan to use
>it for backup. A quick test showed, however, that moving files
>onto and off it in normal use happens at very acceptable rates.
>Standard HDD actions seem to be available and to work correctly.
>
>HTH somebody. Thanks to you all, gang.
Wow, cool. How much was it?
--
-------------------------------------------------------------------
* Jack Troughton jake at consultron.ca *
* http://consultron.ca irc.ecomstation.ca *
* Kingston Ontario Canada news://news.consultron.ca *
-------------------------------------------------------------------
Will Honea
Stephenson) wrote:
> Chris' documentation explains the other components are not quite
> as versatile as IBM's, so I only replaced IBM's USBMSD.ADD with
> his CWUSBMSD.ADD and fiddled with arguments. My USB lines read
> (NB, the mix of USB?HCD.SYS lines was caused by hardware, which
> the IBM sniffer/installer will recognise and handle for you):
>
> BASEDEV=USBUHCD.SYS
> BASEDEV=USBUHCD.SYS
> BASEDEV=USBUHCD.SYS
> BASEDEV=USBEHCD.SYS
> BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
> BASEDEV=USBHID.SYS
> BASEDEV=CWUSBMSD.ADD /V /FLOPPIES:0 /REMOVABLES:1 /FIXED_DISKS:0 /FORCE_TO_REMOVABLE
I've seen these lines a couple of times and finally figured out what
bothered me about them. You have 3 USBUHCD.SYS instances and one
USBEHCD.SYS instance but the USBD /REQ paramters also reference
USBOHCD$ for which you have no driver installed. I've had some grief
trying to get a system stable when binding USBD.SYS to both the
USBDUHCD$ and USBOHCD$ devices when only one was installed (usually
USBOHCD.SYS, in my case). What happens if you remove USBOHCD$ from
the USBD.SYS parameters?
--
Will Honea <who...@codenet.net>
Andrew Stephenson
wlhar...@attbi.com "William L. Hartzell" writes:
> Andrew Stephenson wrote:
> >
> > [...]
>
> If you only have one fixed disk, then this disk will have seven MB
> reserved for Boot Manager. Fdisk and LVM reserve seven MB (one cylinder
> worth of space) for Boot Manager on both the first fixed disk and the
> second.
Ah. Daft idea or what? Anyhow, thanks for the clarification. I
can probably afford to lose 7 MB in some 19,000 MB, especially in
the real world, where greater inefficiencies are certain.
--
Andrew Stephenson
Andrew Stephenson
jake!sp...@consultron.ca "Jack Troughton" writes:
> On Wed, 19 Mar 2003 16:04:24 UTC, am...@deltrak.demon.co.uk
> (Andrew Stephenson) wrote:
>
> [about getting LaCie USB Pocket Drive to work]
>
> Wow, cool. How much was it?
Varies. The going rate in the UK is currently around GBP 130 but
I found a place (Dabs.com) selling it for GBP 107. Both figures
plus Value Added Tax of 17.5%, of course, and handling. Liable
to fall dramatically soon, without doubt. :-(
--
Andrew Stephenson
Andrew Stephenson
who...@codenet.net "Will Honea" writes:
I haven't tried removing USBOHCD$. If it ain't broke... ;-)
My understanding is, the line
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
means "load USBD.SYS if at least one of these items is in use".
I assume they put in all three because it doesn't hurt to do so.
Maybe you had the grief with an earlier USBD.SYS version?
I'd like to know what the difference is between the three kinds
of driver. What clever stuff can the EHCD do, or vice versa?
--
Andrew Stephenson
Jack Troughton
This is actually not true. If you'd made the partition a primary
partition, you wouldn't have ended up with the reserved cylinder.
The second HD in the system I'm typing on is set up that way.
Logical Volume Type Status File System Size (MB)
C: eComStation Compatibility Bootable HPFS 1027
Disk Partition Size (MB) Disk Name
eComStation 1027 35GB SCSI Fujitsu
D: Applications LVM JFS 4100
Disk Partition Size (MB) Disk Name
Applications 4100 35GB SCSI Fujitsu
E: Data LVM JFS 28817
Disk Partition Size (MB) Disk Name
Data 28817 35GB SCSI Fujitsu
J: Windows Compatibility Bootable FAT32 1027
Disk Partition Size (MB) Disk Name
Windows 1027 35GB SCSI Fujitsu
K: Wotzit? Compatibility FAT32 17492
Disk Partition Size (MB) Disk Name
Wotzit? 17492 Disk 1
L: Stv Compatibility FAT32 4102
Disk Partition Size (MB) Disk Name
Windows 4102 Disk 1
M: Maintenance Compatibility Bootable HPFS 54
Disk Partition Size (MB) Disk Name
Maintenance 54 35GB SCSI Fujitsu
O: eCS Test Boot Compatibility Bootable HPFS 5718
Disk Partition Size (MB) Disk Name
eCS Test Boot 5718 Disk 1
*: [ CDROM 1 ] Compatibility CDFS 527
*: [ CDROM 2 ] Compatibility CDFS 582
U: [ LAN 1 ] Compatibility LAN 0
V: [ LAN 2 ] Compatibility LAN 0
W: [ LAN 3 ] Compatibility LAN 0
X: [ LAN 4 ] Compatibility LAN 0
Y: [ LAN 5 ] Compatibility LAN 0
Z: [ LAN 6 ] Compatibility LAN 0
Disk Size (MB) Free Space: Total Largest
35GB SCSI Fujitsu 35040 0 0
Disk Partition Size (MB) Type Status Logical Volume
[ BOOT MANAGER ] 7 Primary In use
eComStation 1027 Primary In use eComStation
Windows 1027 Primary In use Windows
Maintenance 54 Logical In use Maintenance
Applications 4100 Logical In use Applications
Data 28817 Logical In use Data
Disk 1 39079 0 0
Disk Partition Size (MB) Type Status Logical Volume
Windows 4102 Primary In use Stv
Wotzit? 17492 Logical In use Wotzit?
eCS Test Boot 5718 Logical In use eCS Test Boot
[ A1 ] 1953 Logical Available
[ A2 ] 243 Logical Available
[ A3 ] 15 Logical Available
[ A4 ] 972 Logical Available
[ A5 ] 3780 Logical Available
[ A6 ] 4800 Logical Available
As you can see, my Disk 1 has a 4GB primary partition at the
beginning, and does not have a reserved cylinder. The reserved
cylinder is not for BM; it's for a primary partition.
Regards,
Jack
William L. Hartzell
Andrew Stephenson wrote:
> I'd like to know what the difference is between the three kinds
> of driver. What clever stuff can the EHCD do, or vice versa?
The EHCD is the new USB 2.0 driver. The others are two variations on
the USB 1.1 drivers spec.
William L. Hartzell
That there to cover the case where BIOS allows switching primary and
secondary IDE channels, allowing either of two drives to be master on
the first IDE channel. I have a main board with a Cyrix M2 266 that can
do this. This assumes that you place your two drives as master on each
their own channel.
Will Honea
Stephenson) wrote:
Ah, a kindred soul ;-)
What I got into - the TP R30 has an OHCI controller - was that if both
were specified I would lose the mouse fairly regularly. I need to
check the web site since I'm not real sure how current I am on those
drivers as they only show up on the TP and whenever I take it I'm
halfway to where I'm going before I even think about it.
--
Will Honea <who...@codenet.net>
Andrew Stephenson
jake!sp...@consultron.ca "Jack Troughton" writes:
> On Thu, 20 Mar 2003 00:36:27 UTC, am...@deltrak.demon.co.uk (Andrew Stephenson)
> wrote:
>
> >In article <3E7899E1...@attbi.com>
> > wlhar...@attbi.com "William L. Hartzell" writes:
> >
> >> Andrew Stephenson wrote:
> >> >
> >> > [...]
> >>
> >> If you only have one fixed disk, then this disk will have seven MB
> >> reserved for Boot Manager. Fdisk and LVM reserve seven MB (one cylinder
> >> worth of space) for Boot Manager on both the first fixed disk and the
> >> second.
> >
> >Ah. Daft idea or what? Anyhow, thanks for the clarification. I
> >can probably afford to lose 7 MB in some 19,000 MB, especially in
> >the real world, where greater inefficiencies are certain.
>
> This is actually not true. If you'd made the partition a primary
> partition, you wouldn't have ended up with the reserved cylinder.
>
> The second HD in the system I'm typing on is set up that way.
>
> [biggish list of drive configuration info]
>
> As you can see, my Disk 1 has a 4GB primary partition at the
> beginning, and does not have a reserved cylinder. The reserved
> cylinder is not for BM; it's for a primary partition.
Must admit I was unaware of that gotcha. My reasoning had more
to do with what people have said often, that primary partitions
get lettered ahead of secondaries (am I mangling terminology?).
And yes, I realise LVM has brought us a New Age, wherein none of
that nasty stuff matters any more; but I'm wary. The USB HDD had
to be unpluggable without upsetting drive sequencing, so I made
it a secondary. (It drops into a RESERVEDRIVELETTER gap created
ahead of the CD drives.)
I suppose I could have played other RESERVEDRIVELETTER games but
by then my new main HDD had been configured and I wasn't tempted
by the many hours of fun changing it would have entailed. <g>
On balance, I can live with the lost 7 MB.
--
Andrew Stephenson
Andrew Stephenson
wlhar...@attbi.com "William L. Hartzell" writes:
> Andrew Stephenson wrote:
> > I'd like to know what the difference is between the three kinds
> > of driver. What clever stuff can the EHCD do, or vice versa?
>
> The EHCD is the new USB 2.0 driver. The others are two variations on
> the USB 1.1 drivers spec.
(BTW, thanks for the other response, on the "lost" HDD 7MB.)
Now I am confused. (Not a pretty sight.) The m/board is meant
to have six (6) USB 2.0 ports (a hardware thing, of course). Yet
the IBM sniffer identified my four (4) fully equipped USB ports
as 3xUHCI and 1xEHCI. Have I been diddled? Should I change the
three (3) USBUHCD.SYS entries to USBEHCD.SYS? (I could go ahead
and try it; but a scientific/enquiring approach seems indicated.)
--
Andrew Stephenson
Andrew Stephenson
am...@deltrak.demon.co.uk "Andrew Stephenson" writes:
> FWIW here's how I got it to work. [...]
>
> HARDWARE: Asus m/board A7V333-X, [...]
>
> USB HDD: LaCie USB 2.0 Pocket Drive, 20 GB. [...]
>
> Now I simply have to:
> * plug in the USB drive;
> * wait for the beep (if the drive is already plugged in at boot
> time, the beep happens then);
> * click on "Refresh Removable Media" in Drives (sometimes twice
> for some obscure reason), after which an empty window appears
> for a few seconds;
> [...]
Some additional information, after using the setup for a while...
* One need only double-click on the "Refresh..." icon once. It
just takes rather a long time (30 sec or so) to update Drives.
* By accident, I found the LaCie can be powered from the USB port
in the proper way. (I forgot to switch on its PSU.) However,
when "ejecting" the disk, one is apt to get an error message,
saying an error occurred but the message was unavailable (so I
haven't the foggiest idea what the error was); but things seem
to carry on happily afterwards.
--
Andrew Stephenson
USBGuy
> Now I am confused. (Not a pretty sight.) The m/board is meant
> to have six (6) USB 2.0 ports (a hardware thing, of course). Yet
> the IBM sniffer identified my four (4) fully equipped USB ports
> as 3xUHCI and 1xEHCI. Have I been diddled? Should I change the
> three (3) USBUHCD.SYS entries to USBEHCD.SYS? (I could go ahead
> and try it; but a scientific/enquiring approach seems indicated.)
Nope. All is fine Ports != Controlers. You have 2 UHCI controlers in the
chipset each having 2 ports and 1 UHCI as companion controler on the
USB 2.0 (EHCI) Those 2 Controlers share their 2 ports. So you end up
with a total of 6 ports. USB 1.x is a subset od 2.0 Speedwise and any
USB 2.0 device (should) work(s) if connected to an 1.1.
So any USB 1.1 Port is a 2.0 which only implements Fast speed.
Also many Devices are branded as USB 2.0 with "Fast Speed". which
actually means it's a 1.1 device. Read 2.0 devices show a "High Speed"
logo. Thats called marketing ...
USBGuy
> My understanding is, the line
> BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
> means "load USBD.SYS if at least one of these items is in use".
> I assume they put in all three because it doesn't hurt to do so.
> Maybe you had the grief with an earlier USBD.SYS version?
>
True for later releases eariler once where load if ALL listed drivers
are present. Best advice which'll work no matter which version you have
is simply drop the /REQ parm it's not needed.
While USBD.SYS will load then even without an HC driver thats easier
to diagnose then a wrong entry in the REQ parm depending on the version
level of USBD.SYS
Jack Troughton
Well, the thing you have to realise is that os2dasd.dmd in warp 4
AND in MCP+ will always put removable media after fixed disks; that
is, if the drive is a removable drive, it will always get a drive
letter after all fixed disks, regardless of their primary/logical
status.
>I suppose I could have played other RESERVEDRIVELETTER games but
>by then my new main HDD had been configured and I wasn't tempted
>by the many hours of fun changing it would have entailed. <g>
>On balance, I can live with the lost 7 MB.
Yes, we are talking about fine nitpicks here, that's for sure:)
Andrew Stephenson
Okay, I'll try deleting the surplus argument and report back if
it throws a wobbly during the next few days.
--
Andrew Stephenson
Andrew Stephenson
Now the sight of me is even less pretty. Ie, more confused. All
right, I'll swallow that and digest it later. Meanwhile, how can
I be sure my USB plug is in the "real" USB 2.0 socket? There are
four to choose from, identical except one socket-pair's locating
tabs are black plastic, the other white.
On top of that, I've just reviewed the Asus m/b's Book Of Words
and see that it states: "VT8235 built-in USB 2.0 / 6 x USB 2.0
ports"; and elsewhere all references to the connectors say they
are USB 2.0... *meep* Sounds like there's some misdescription
going on. Okay, you call it marketing. Me, I say this spade is
a spade. A strangely bent one.
--
Andrew Stephenson
USBGuy
has 3 UHCI companion controlers so all 6 ports are real 2.0. But that
whould be a realy strange setup. What could also be the case is that you
have 3 UHCI and 3 EHCI and that the IBM tool simply maxes out when it
found 4 controlers as thats the max the current IBM USB stack supports.
William L. Hartzell
Would not if he listed three EHCI drivers in config.sys and no UHCI
drivers, that if they loaded, then this would prove your hypothesis?
Andrew Stephenson
wlhar...@attbi.com "William L. Hartzell" writes:
> Sir:
>
> USBGuy wrote:
> > Andrew Stephenson wrote:
> >
> > > [puzzling over how many USB 2.0 ports]
> >
> > Well the other possibility is that you realy have 1 EHI controler which
> > has 3 UHCI companion controlers so all 6 ports are real 2.0. But that
> > whould be a realy strange setup. What could also be the case is that you
> > have 3 UHCI and 3 EHCI and that the IBM tool simply maxes out when it
> > found 4 controlers as thats the max the current IBM USB stack supports.
>
> Would not if he listed three EHCI drivers in config.sys and no UHCI
> drivers, that if they loaded, then this would prove your hypothesis?
C'mon, Bill -- y'all turnin' methodical on us, boy? <g>
Okay, I shall tinker creatively with CONFIG.SYS, to keep us (you,
USBGuy and myself) collectively happy.
Later...
That was interesting. Changing the three USBUHCI.SYS drivers to
USBEHCI.SYS resulted in (according to Hardware Manager) just the
one "EHCI compliant USN host controller" instead of that and the
three UHCIs which were there before. So now we know. The spade
is a (bent) spade, after all. ;-)
Even more interesting, from my USB-novice POV, was that the USB
HDD plugged in and worked properly, with just the one controller
available. If I tried to plug in additional USB devices, would
they simply fail to connect?
--
Andrew Stephenson
William L. Hartzell
Andrew Stephenson wrote:
> In article <3E7C51B0...@attbi.com>
> wlhar...@attbi.com "William L. Hartzell" writes:
>
>
>>Sir:
>>
>>USBGuy wrote:
>>
>>>Andrew Stephenson wrote:
>>>
>>>
>>>>[puzzling over how many USB 2.0 ports]
>>>
>>>Well the other possibility is that you really have 1 EHI controller which
>>>has 3 UHCI companion controllers so all 6 ports are real 2.0. But that
>>>would be a really strange setup. What could also be the case is that you
>>>have 3 UHCI and 3 EHCI and that the IBM tool simply maxes out when it
>>>found 4 controllers as that's the max the current IBM USB stack supports.
>>
>>Would not if he listed three EHCI drivers in config.sys and no UHCI
>>drivers, that if they loaded, then this would prove your hypothesis?
>
>
> C'mon, Bill -- y'all turnin' methodical on us, boy? <g>
>
> Okay, I shall tinker creatively with CONFIG.SYS, to keep us (you,
> USBGuy and myself) collectively happy.
>
> Later...
>
> That was interesting. Changing the three USBUHCI.SYS drivers to
> USBEHCI.SYS resulted in (according to Hardware Manager) just the
> one "EHCI compliant USN host controller" instead of that and the
> three UHCIs which were there before. So now we know. The spade
> is a (bent) spade, after all. ;-)
>
> Even more interesting, from my USB-novice POV, was that the USB
> HDD plugged in and worked properly, with just the one controller
> available. If I tried to plug in additional USB devices, would
> they simply fail to connect?
The remanding question since you've proved that it is one EHCI
controller with three UHCI satellite controllers, then is how many lines
of controller drivers are really needed in config.sys. I'm betting on
one EHCI driver. Your question triggers this query.
The answer to your question would logically be that when there is no
driver, then they would fail to connect. You can move the one USB
device that you have to all ports to test this hypothesis. It should
work on some and not others if three EHCI drivers are needed and you
have two or less (and I would use EHCI and not UHCI drivers to get the
benefit of what you paid).