On my P4T533-C USB2 doesn't work

[Jon J Panury]

Bought two years ago.
Never really needed USB2 till now.

Neither the pair of (of two pairs of) on-board USB2's nor the
additional USB2 header does the job.
As far as I can see, all jumper settings are according to USB2
enabling.

The harware manager shows a lot of USB stuff, six "USB Root Hub"
devices, and things (NEC etc.).

Got me an additional combi-card (adaptec AUA-3121 Duo Connect)
more than one year ago, featuring two IEEE 1394 Ports - and
three more USB2.

These function; but not all of them with my USB 2.0 Video
grabber. One does. But video grabbing still fails with every
single program I tried. Yes, it may well be the grabber that
spoils the fun here ...
But then, as I tried the supposed "USB2" connectors that Asus
provides, I found out that they in fact do not work as 2.0:
Warning balloon said that a Hi-speed USB device was being
connected to a non-Highspeed Port ...

It's the drivers, I reckon :-<

Anyone any idea how best to start fixing all of this muddle?

[Win XP(H)]

JJ

 

[JoeK]

Is the USB2 enabled and configured in BIOS?

 

[JohnJeninga]

Run the CD that came with the board. It will give you the option to load
USB 2.0 drivers (NEC). Works fine on my P4T533-C. Check the built in ports
first once the drivers are installed. A lot of the front ports built into
cases will not handle USB 2.0.

--
Remove "john" from the address to reply.

Regards,
John

Is the USB2 enabled and configured in BIOS?

Bought two years ago.
Never really needed USB2 till now.

Neither the pair of (of two pairs of) on-board USB2's nor the
additional USB2 header does the job.
As far as I can see, all jumper settings are according to USB2
enabling.

The harware manager shows a lot of USB stuff, six "USB Root Hub"
devices, and things (NEC etc.).

Got me an additional combi-card (adaptec AUA-3121 Duo Connect)
more than one year ago, featuring two IEEE 1394 Ports - and
three more USB2.

These function; but not all of them with my USB 2.0 Video
grabber. One does. But video grabbing still fails with every
single program I tried. Yes, it may well be the grabber that
spoils the fun here ...
But then, as I tried the supposed "USB2" connectors that Asus
provides, I found out that they in fact do not work as 2.0:
Warning balloon said that a Hi-speed USB device was being
connected to a non-Highspeed Port ...

It's the drivers, I reckon :-<

Anyone any idea how best to start fixing all of this muddle?

[Win XP(H)]

JJ

 

[Jon J Panury]

Run the CD that came with the board.
Done

It will give you the option to load USB 2.0 drivers (NEC). Works fine on my P4T533-C.

With mine, too. Now. Think the bloaks at that Shop simply forgot
that one.

Check the built in ports
first once the drivers are installed. A lot of the front ports built into
cases will not handle USB 2.0.

They all work fine now, thanks. Got no front ports at all.
That keeps me in exercise.

BUT

Getting bluescreen now every time I run a program using that
USB2-Grabber ...
The file named there is "asusehcd.sys" - but I have no idea what
in particular that wants to signify.

Yes I understand that that file is sort of "ASUS enhanced host
controller device" thing. But it *is* there, so this bluescreen
cannot have something to do with a *missing* file.

Device manager clean, i.e. without any question- or exclamation
marks. Asustec device is there. Adaptec Duo-Connect is there.
Image processing device ("Crescentec DC-1100") is recognized and
there.

Had had that sort of bluescreen together with the grabber
before. Installing latest DirectX helped then. But now, that
DirectX *is* installed. And the bluescreen mess comes up so
significantly after having "fixed" the USB2 thing ...

The Video capturing used to die on _stopping_ the actual
capturing. That is to say the data flow DID somehow function.
But everything was unstable, as it were.

Now the bluescreen comes up *immediately* on opening (or
"starting") the Crescentec USB2 device.

Maybe there is a simple solution to this - or that grabber is
just a piece of crap.
Likely, that.

JJ

 

[Paul]

With mine, too. Now. Think the bloaks at that Shop simply forgot
that one.




They all work fine now, thanks. Got no front ports at all.
That keeps me in exercise.

BUT

Getting bluescreen now every time I run a program using that
USB2-Grabber ...
The file named there is "asusehcd.sys" - but I have no idea what
in particular that wants to signify.

Yes I understand that that file is sort of "ASUS enhanced host
controller device" thing. But it *is* there, so this bluescreen
cannot have something to do with a *missing* file.

Device manager clean, i.e. without any question- or exclamation
marks. Asustec device is there. Adaptec Duo-Connect is there.
Image processing device ("Crescentec DC-1100") is recognized and
there.

Had had that sort of bluescreen together with the grabber
before. Installing latest DirectX helped then. But now, that
DirectX *is* installed. And the bluescreen mess comes up so
significantly after having "fixed" the USB2 thing ...

The Video capturing used to die on _stopping_ the actual
capturing. That is to say the data flow DID somehow function.
But everything was unstable, as it were.

Now the bluescreen comes up *immediately* on opening (or
"starting") the Crescentec USB2 device.

Maybe there is a simple solution to this - or that grabber is
just a piece of crap.
Likely, that.

JJ

I just downloaded the 2V21 USB2 driver from the Asus site for
your board, and the Readme.txt file says:

"The following USB 2.0 devices and features are not supported
in this driver release:
- USB 2.0 Isochronous devices (example: USB 2.0 webcams and
USB 2.0 speakers).
- Composite USB 2.0 Devices.
- USB Remote Wake Up."

Is your grabber a streaming device or does it capture a simple
still picture ? If it is a streaming device, that would be
classed as an "Isochronous" device.

Now, I thought generic USB2 support was in SP1 for WinXP. Maybe
if you uninstall the USB2 driver from the CD, and install
Service Pack 1 from Microsoft, you'd have support for an
isochronous device. (The guys at your shop may not have installed
this driver for a reason.)

Have a look here. If you succeed in installing a USB2 driver,
then Device Manager should have an entry with the word "Enhanced"
in it.

http://usbman.com/Guides/checking_for_usb_2.htm

HTH,
Paul

 

[Jon J Panury]

Paul schrieb:

[...]

Now, I thought generic USB2 support was in SP1 for WinXP. Maybe
if you uninstall the USB2 driver from the CD, and install
Service Pack 1 from Microsoft, you'd have support for an
isochronous device.

Done exactly that.
Working!!

The knack, it seems, was that there had to appear an "enhanced"
Controller *of the NEC sort*

As it did not work properly with that "asustec" enhanced
controller, it seems to me that the USB-PCI interface was the
problem here. Even my additional Adaptec Duo-Connect card is a
"PCI" device at the end of the day.

BTW I think it would have been wiser by Microsoft programmers to
show all these "USB Root Hub" entries (in the device manager)
hierarchically assigned to the respective NEC Controllers; I
played around a little, disabling controllers one by one looking
what happened. I found out that disabling any NEC USB Controller
makes one or more "USB Root Hub" entries dissappear and the
connected devices get out of function. This way, I could
allocate the respective Ports to the respective controller
entries.

But it all remains a little bit awkward to me ...

Thanks for advice.

JJ