Re: A7V333 Problems, USB2 is not recognise by XP SP1

In article <44fed42a$0$31420$626a54ce@xxxxxxxxxxxx>, "Roswellbob"
<roswellbob@xxxxxxxxxxx> wrote:

Pour occuper son temps libre "Paul"
nous a gentiment octroyé la missive :
news:nospam-0609060945410001@xxxxxxxxxxxxx
et y developpa le theme de :

Thanks for reply

A7V333 has some USB ports supported by 8233A Southbridge and
some by the VT6202 USB2 chip. The 8233A Southbridge ports are
USB 1.1 . Consult the picture in your user manual, to see
which connectors on the back of the computer, and which
2x5 USB header connectors, are USB 1.1 or USB 2.0.

Ok, i've check this before reading your reply

In the Device Manager, there should be one USB entry with
the word "Enhanced" in it. That is how you can tell whether
a USB2 driver has been loaded for the VT6202. Only the
connectors labelled "USB2" in the manual are connected
to the VT6202.

I've install USB2.0 Via drivers, the USB Enhanced Controller appears in the
hardware, but the four USB Ports recognise not the Key.......

In the fourth message in this thread, they list the Device
Manager entries for A7V333 USB and they seem to match
what you show in your picture. So that isn't the problem.

http://groups.google.ca/group/alt.comp.periphs.mainboard.asus/browse_frm/thread/55c39f6ff048b554/c87b30a52414d342

"In Device Manager you should see 4 "VIA Rev 5 or Later USB Universal
Host Controller", 1 "VIA USB Enanced Host Controller" and 5 "USB Root
Hub". The "Enhanced" Conroller and one of the Root Hubs are the USB 2.x
things, are you missing them? "

So at least the Device Manager appears correct.

I notice that the USB2 entries in Device Manager are in
English and the other entries are in French. This tells
me you probably installed the VIA 2.2.5 USB driver (one
version of that driver is not multilingual, so English
is used).

My advice in general, is to use the USB driver that comes
as part of Service Pack 1 for WinXP. You can create problems
for yourself, by using earlier Microsoft patches, or by using
third party drivers. USB devices are designed according
to standards, so that the Microsoft generic driver can make
them work. Installing a third party driver complicates matters,
and there is no way to know whether the OS will end up using the
correct files.

Things you can try:

1) Unplug all unnecessary USB devices. Remove the VIA USB driver.
(In this case, I am assuming there is an entry in Add/Remove
in Control Panels.) Then use the USB cleanup procedure, to
get Windows to reinstall the Device Manager entries. After
carrying out the procedure, reboot. Then, plug the USB2 device
you were testing into the computer.

http://www.usbman.com/Guides/Cleanup%20Device%20Manager%20Safe%20Mode.htm

OR

2) Try a repair install of WinXP. After the repair install is
finished and the machine has rebooted, plug in your USB2 device
and test it again. You have to install Service Pack 1 and
any security patches, after the repair install is done.
Your user data and programs will not be affected. (If you
upgraded Internet Explorer, you have to do that over again
as well.)

http://www.michaelstevenstech.com/XPrepairinstall.htm

OR

3) Disconnect all hard drives. Label everything so you can put
it all back the same way later. Unplug all unnecessary USB
devices. Find an empty hard drive. Install WinXP on the
empty hard drive. Install WInXP SP1 service pack on that
hard drive. After the reboot, plug in your USB 2.0 device
and test it. The purpose of this test, is to demonstrate
that there is nothing wrong with the hardware. If procedure
(3) works, it means some driver or patch you installed in
an attempt to get it working on your real boot drive, has
screwed up the USB subsystem. If procedure (3) works, then
applying procedure (2) to the original boot disk should
work.

I would test by using the USB2 connector in the I/O area
on the back of the computer. That should be the best
connector. If you have done that, all the rest of your
problems are likely being caused by the use of a driver
or patch, when all you really needed was Service Pack 1
or later for WinXP.

If you wish to save time, another solution is to use a
PCI USB2 add-in card. The card should NOT have a VIA
USB chip on it. Find a USB2 card with a NEC chip. They are
the best in terms of compatibility. The NEC chip will use
the Microsoft generic driver, as provided in Service Pack 1.
Since the VIA driver will not be used by the NEC chip,
it should not get confused by whatever drivers you have
already installed on the system. Then, plug all the
devices you have trouble with, into that PCI add-in card.

HTH,
Paul
.

Relevant Pages

  • Problems with Touchpad,keyboard and USB after Ideacom update (solu
    ... and keyboard .I have made fresh install of XP Home and have all updated ... recomended update from Driver detective,that i use offten. ... allready and when i do this it knocks off my USB mouse leaving me not able to ... 2.Mutil-Access driver HCT driver verify crash fix! ...
    (microsoft.public.windowsxp.general)
  • Re: Problems with Touchpad,keyboard and USB after Ideacom update (solu
    ... touchpad and keyboard .I have made fresh install of XP Home and have all ... recomended update from Driver detective,that i use offten. ... allready and when i do this it knocks off my USB mouse leaving me not able ... 2.Mutil-Access driver HCT driver verify crash fix! ...
    (microsoft.public.windowsxp.general)
  • Re: Cant connect mouse to my laptop, please help
    ... that) and connected it using a PS/2 to USB adapter. ... found new hardware USB human interface device ... I leave it on "Install the ... there may in fact be a driver problem a clean ...
    (microsoft.public.windowsxp.basics)
  • Re: Driver libraries on the Asus web site.
    ... I disabled USB in bios and ran initial test-boots. ... I'm hoping to be able to install chipset etc drivers with the MS Recovery ... driver libraries that I have to deal with. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Cant connect mouse to my laptop, please help
    ... that) and connected it using a PS/2 to USB adapter. ...    USB to PS/2 adapters don't always work. ... and an install will not fix this. ... there may in fact be a driver problem a clean Windows ...
    (microsoft.public.windowsxp.basics)