Re: Getting drivers from MS Update site

Thanks for your note. I don't think that its an incorrect installation but I do think that it's an incomplete installation. I think that something is wrong that keeps the driver from installing completely at the very end of the process. My problem is that, even though the device shows to be in error -- "Unable to load driver (code 39)" in Device Manager -- there is nowhere for me to find out why it can't load it. There is no Canon installation log. There is no entry in any of the Windows event logs. It simply is not being recorded.

Any ideas how I can get a better handle of this?

Thanks in advance,

Howard
===================================================

"DL" <notvalid@xxxxxxxxxxxxxxxxxx> wrote in message news:e#sjz13wJHA.6068@xxxxxxxxxxxxxxxxxxxxxxx
IMO a very bad idea to take any hardware drivers from MS Update, unless you want reduced functionality or none functioning drivers, in the worst case
Obtain your mobo drivers from MSI direct, modify MSUpdate for critical updates only.

However your problem is probably as Paul states, incorrect installation of your Cannon
============================================================ "Howard Woodard" <woodard@xxxxxxx> wrote in message news:2569541A-9735-4573-AA1E-4B4DAD25512E@xxxxxxxxxxxxxxxx
Hi Paul and thanks so much for your very detailed and helpful response. It sounds like you have the same mobo. Here is the problem that I am working on and thought that the USB drivers might be the problem/solution:

I just bought a new Cannon MX-700 multifunction printer. After installing it on my [XP Home sp3] desktop system everything works great except for...

The scanner won't work. When I try to use/load it I get an error saying that the system can't communicate with the scanner. I have worked with Canon for two weeks and tried every thing they suggested without any change in the issue. I have removed and re-installed the Canon software and drivers so many times that it will do it by itself if it notices that I'm pulling out the Canon CD. They also had me try 3 different USB cables though I have never seen where I could specify a type or "model" for USB cables with the same connector types.

I have tried it with USB 2.0 enabled and disabled. All other USB functions -- the printer, digital cameras, external disk drives and my web camera work perfectly as 2.0 devices.

It installs and operates perfectly on my HP laptop. The only significant difference that I can see between the two systems is that the desktop MSI mobo uses the Via chipset. I decided that I would delete the MSI driver for the integrated USB 2.0 controller and then connect to the Microsoft Update site and get the latest drivers and see if that would cure the problem. Then I found out that I couldn't tell exactly which of the drivers on the MSI support site was the one that included the integrated USB 2.0 controller so I used MSI's online live update and it found and installed a new chipset driver.

Also, while looking for others having this problem -- I found scads of them, I ran across an article describing [what appears to be] the exact same situation -- Via chipset, driver not detecting USB device, etc. -- with the only difference being that it was a Logitech camera. The problem it described had to do with OHCI vs UDCI compatibility and occasionally IRQ sharing under XP.

Do you have you any awareness of this problem and how, assuming that it can, be resolved?

Thanks in advance,

Howard Woodard
Redmond, WA
==============================================================
"Paul" <nospam@xxxxxxxxxx> wrote in message news:gsmkqt$g3e$1@xxxxxxxxxxxxxxxxxxxxxx
Howard Woodard wrote:
When my system detects new hardware it is automatically installing the driver. It is completing so fast that I don't believe that it is going online to check for the latest driver. Is there any way to get the driver dialog box back? IE, be given the chance to cancel, go online, check on hard drive, etc?

Also, when I uninstall a driver for something like the USB host controller, is there a way to tell Windows to remove the driver file as well? I'd delete them myself except I don't know the .inf file names.

I'm trying to force my MSI motherboard with the Via chipset to load its USB drivers from the Microsoft update site.

Does anyone know how to do this?

Thanks in advance,

Howard

I tried an experiment here, by selecting "update driver" in Device
Manager, for my VIA USB2 Enhanced entry, and Windows Update reports
there are no later updates. These are the files listed for my Enhanced
entry, as far as drivers are concerned.

usbehci.sys 5.1.2600.5512 (xpsp.080413-2108)
usbhub.sys 5.1.2600.5512 (xpsp.080413-2108)
usbport.sys 5.1.2600.5512 (xpsp.080413-2108)
hccoin.dll 5.1.2600.5512 (xpsp.080413-2108)
usbui.dll 5.1.2600.5512 (xpsp.080413-2108)

My installer CD, is an OEM WinXP SP3 installer, purchased several
months ago. So the above files correspond to something bundled
with SP3. USB drivers have been bundled since SP1 for things
like USB2, and there would be files provided for USB, since
SP1 was made available. (At that point, hardware manufacturers
lost the licensed ability to offer copies of USB2 drivers on
their own. Microsoft wanted people to download SP1, to get a
USB2 driver for their hardware.)

If I look in C:\WINDOWS\inf , I can see files like

usb.inf
usbport.inf
usbprint.inf
usbstor.inf
usbvideo.inf

I don't even see any of the "OEM.inf" files I used
to see in Win2K. The stuff I see, seems to be named
as you might expect, rather than being obfuscated.

If I look on my installer CD, in the i386 folder, I
can see usbport.in_ , which is a compressed version
of an INF file. If I uncompress that and examine it,
it has plenty of hardware instances listed. And those
hardware instances would be the ones that would
"install instantly", instead of prompting you with
a wizard. For example, these VEN=1106, DEV=3104 would
correspond to my VIA USB2 logic block. My VIA USB2 was
installed without a fuss, when I installed from the
OEM WinXP SP3 CD.

;USB2 controllers
%PCI\VEN_1106&DEV_3104&REV_51.DeviceDesc%=EHCI.Dev,PCI\VEN_1106&DEV_3104&REV_51
%PCI\VEN_1106&DEV_3104&REV_51.DeviceDesc%=EHCI.Dev,PCI\VEN_1106&DEV_3104

WinXP has layers of file caching, which will make "stomping"
on stuff more difficult. I don't know if I could delete
all traces of USB support, such that Windows was completely
unprepared to handle the USB stack. The above files,
have multiple vendor entries, so the files in fact,
support a wide range of hardware (like even a NEC PCI
USB2 card might be supported).

You'll notice, if you go to viaarena.com, that there is
no separate USB installer. Some manufacturers immediately
removed their pre-SP1 downloads, when they were supposed to.
Some download sites, are only now getting around to deleting
files they still had on servers, so it was possible to
still find pre-SP1 versions, even if they weren't supposed
to be available. Using one of those old hotfix drivers, could
mess up a more modern WinXP install.

If you were to update to SP3, then you'd get the Microsoft
built-in capabilities (at least, as shown in the files I've
listed above). A Service Pack offers the opportunity
for MS to clean up the Hotfix situation, so that the
Service Pack contains an up-to-date at the time, version
of the driver. When I tried to update my USB2, using

Properties:Driver_tab:Update Driver:

Can Windows connect... Tick Yes, this time only
Install the software automatically... Tick the box.

and that gives this as a response ==>

"Cannot Continue the Hardware Update Wizard"
The wizard could not find a better match for your
hardware than the software you currently have installed.

I captured some network activity with Wireshark, and the Wizard contacts

update.microsoft.com.nsatc.net

So it did try to contact Microsoft, to check for an updated
driver.

Did you attempt to use a stale hotfix ? If you did, indicate
what you did, and maybe someone knows how to back out.

Maybe Add/Remove has an entry for the hotfix or something, and you
can uninstall it. Drivers also have a "Roll back driver" button,
to undo a mistake, but it is a one-level rollback, only
handling a mistake you detect immediately.

Paul



.