Getting drivers from MS Update site

[Howard Woodard]

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

 

[Paul]

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

Propertiesriver_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

 

[Howard Woodard]

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
==============================================================

 

[JS]

The heart of the problem:
If you connected the multi-function printer/scanner to your PC and then
installed the printer drivers/software, the chances are very high
that the printer may work but scanner function will not.

Most scanners or multi purpose printers require
that you install the software before connecting the scanner or
printer/scanner.

Step By Step Instructions:
1) Disconnect the multi-function printer or scanner.
2) Uninstall the printer/scanner software and twain drivers using
the Add/Remove programs option.
3) Look/search for folders associated with your printer/scanner model that
contain 'Twain' files, if the folder(s) still exist after the uninstall,
then delete these files and the associated folders.

Note: In the list of files that Search has found you can ignore any
files listed in:
C:\Windows
C:\Windows\system32\....
C:\Windows\ServicePackFiles\.....

NOTE: In the C:\WINDOWS\twain_32 folder you may have
one or more files. The one "not to delete" is named: wiatwain.ds
(wiatwain.ds is installed by Windows XP)
Any additional files in this folder were most likely created when you
installed the printer/scanner. Check each files 'Properties' and if has the
brand of your scanner (Epson, Cannon, HP, Etc) identified as the
company/brand, those files can be safely deleted.

On my PC I have my HP scanner's twain file located in:
C:\Program Files\Hewlett-Packard\Precisionscan Pro 3.1\TwainCtrl.ocx
There should be something similar on your PC, so in my case at least
I would uninstall the HP Scanner software and if that 'TwainCtrl.ocx file
is still there after uninstalling the scanner software I would delete it.
I also have a second twain file named 'Twain_32.dll' located in:
C:\Program Files\Adaptec\Easy CD Creator 5\PhotoRelay

4) Check Device Manager and remove any entries if necessary.
5) Create a Restore Point
6) Scan registry using the brand name/make of the scanner as key word for
search. (Delete any entries found, but be certain it's a scanner related
entry)
7) Reboot the PC and once again check Device Manager,
it should not show any listings for the printer/scanner.
8) Now reinstall the software and twain drivers.
9) Shutdown the PC.
10) With the PC power off, connect the printer/scanner and then
restart/boot to Windows.

Note: Sometimes it's might help if you try a different USB port if you
printer/scanner is a USB device.

One easy way to test your software installation's twain driver are working,
is to use a graphics editor named IrfanView.
http://www.irfanview.com/

If you download, install and run this software,
located in the menu bar is an option named 'File'.
On selecting the 'File' option you should find an
option (near the bottom of the list) to named:
'Select TWAIN Source', click on this option
and a popup should then display valid Twain sources
for you scanner. If you see your scanner listed,
select it, and then try to scan an object (Photo).

By selecting Twain Source from the file menu IrfanView should load
your scanner's software and then scan.

If you choose the 'Copy Shop' option also in the file menu you have the
ability to bypass your scanner's software and directly scan a photo into
IrfanView. Try the 'Copy Shop' option and let me know what happens.
Note that 'Copy Shop' will list both your scanner's Photo editing/scanning
software and the hardware name (make & model) of your scanner when
you click on Copy Shop's 'Select Twain Source' button.
You should choose the scanner's hardware option.

For instance on my PC the Photo editing/scanner software is named:
'HP Precisionscan Pro 3.1'
The second entry in Copy Shop's 'Select Twain Source' list is my scanner
make and model which shows as:
'WIA-Hewlett-Packard Scanjet 5470C 1.0'

So for me when using Copy Shop I select the second entry when
asked to select a Twain Source.
I then check the 'Show Twain Preview' box.
(I check this option so the scanned image does not go directly
to the printer, but instead is displayed in IrfanView).
Next I click the 'Start' button located a the bottom of the Copy Shop
window to start the scan.

--
JS
http://www.pagestart.com

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
==============================================================

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

Propertiesriver_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

 

[DL]

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

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
==============================================================

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

Propertiesriver_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

 

[Howard Woodard]

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
===================================================

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

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
==============================================================

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

Propertiesriver_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

 

[Paul]

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

I cannot promise anything, but have a look in the setupapi.log file.
It is in C:\WINDOWS. I also have a setupapi.log.0.old file, which
presumably is from the system starting a new one at some point.

"Troubleshooting Device Installation with the SetupAPI.Log File"
http://www.microsoft.com/whdc/driver/install/setupapilog.mspx

At the device level, I see by googling, that the printer would be
a "USB Composite" Device. So it is possible a copy of UVCView would
show the config space information, if the printer/scanner was plugged
directly into the computer. You should see a couple sections to
the config information, each covering a function of the device.

*******
ftp://ftp.efo.ru/pub/ftdichip/Utilities/UVCView.x86.exe
http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe

File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e

This is a picture of what the UVCView info looks like.

http://www.die.de/blog/content/binary/usbview.png

Some information on the parameters seen in UVCView.

http://www.beyondlogic.org/usbnutshell/usb5.htm
*******

And if you thought the problem was purely related to the VIA USB
interface, and this was a desktop computer, you could use a separate
USB2 PCI card with a different brand of chip on it. You can find
ones with NEC chips for example. The only negative on NEC chips,
is occasionally a port will blow out due to ESD (at least, that
is what the symptoms suggest). Otherwise, the NEC chips seem to
work. Microsoft delivered the first USB2 driver, using a NEC
USB2 chip to test it.

Four external USB2 ports, NEC chip onboard.
http://www.newegg.com/Product/Product.aspx?Item=N82E16815104216

The thing is, if you can print but not scan, it suggests that
the existing interface works at the physical level. Something
a little higher up might be involved.

Paul

 

[Howard Woodard]

Thanks for spending so much time on this Paul. I'll try this and let you
know the outcome.

Best regards,

Howard
Redmond, WA
========================================================

 

[DL]

You might also check hardware devices, hidden devices

If you installed the cannon using the correct method, no drivers should have
been updated when you connected it

 

[smlunatick]

You might also check hardware devices, hidden devices

If you installed the cannon using the correct method, no drivers should have
been updated when you connected it

Save the following to a batch file:
------------------------------------------------------------------------------
set devmgr_show_nonpresent_devices=1
cd %SystemRoot%\System32
start devmgmt.msc
------------------------------------------------------------------------------

Once the Device Manager is started, select "Show hidden devices' from
the View menu.

As for install most USB based printers, the install instruction would
normally state to run the included CD first or download the "revised"
printer drivers before ever connecting the printer to the PC. I
personally encountered huge problems when a USB printer was first
connected to the PC before installing the drivers. I had to go back
with a System Restore first since no drivers would correct the
access / set up to the printer.

 

[Howard Woodard]

I guess I need to give more consideration to the "incorrect install"
possibility. I can assure you that I have installed it correctly each and
every time. However, I think that my son did, in fact, connect the printer
the very first time before running the CD installation which would have
installed an XP USB [probably printer] driver.

If that's the case, wouldn't my subsequent uninstall of the printer and its
drivers have removed whatever got installed the first time?

Thanks all for continuing to help me with this.

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

 

[smlunatick]

I guess I need to give more consideration to the "incorrect install"
possibility.  I can assure you that I have installed it correctly each and
every time.  However, I think that my son did, in fact, connect the printer
the very first time before running the CD installation which would have
installed an XP USB [probably printer] driver.

If that's the case, wouldn't my subsequent uninstall of the printer and its
drivers have removed whatever got installed the first time?

Thanks all for continuing to help me with this.

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

Save the following to a batch file:
------------------------------------------------------------------------------
set devmgr_show_nonpresent_devices=1
cd %SystemRoot%\System32
start devmgmt.msc
------------------------------------------------------------------------------

Once the Device Manager is started, select "Show hidden devices' from
the View menu.

As for install most USB based printers, the install instruction would
normally state to run the included CD first or download the "revised"
printer drivers before ever connecting the printer to the PC.  I
personally encountered huge problems when a USB printer was first
connected to the PC before installing the drivers.  I had to go back
with a System Restore first since no drivers would correct the
access / set up to the printer.

No. Windows XP will detect a "driver" for this printer. If the
driver is incorrect, then XP will constantly load that incorrect
driver before check the correct driver. You now have a "long" jobs
ahead in order to clear out that incorrect selected driver setting.
Once this incorrect driver is "removed" from "Device Manager" you
could re-install the correct drivers before re-connecting the printer.

Please save my "recommended" settings (previous post) and try running
the 'batch' file. Then, in the USB, printer, Ports, Imaging and "DOT"
section, uninstall the "ghosted" hidden devices. (BE CAREFUL.)

 

[Howard Woodard]

Ok, I have done everything everybody has suggested, including installing a
new Koutech PCI to USB2.0 Card Model IO-PU520, and I still have the exact
same problem. At the end of the install step that occurs right after
plugging in the printer's USB cable I get a message saying that the driver
failed to install properly and then, though every other printer function
works properly, Device Manager has an error icon "Driver failed to load
(code 39)" and when I try to use the scanner function I get an error saying
that the PC can't connect to the scanner.

I have extracted the scanner installation section from the C:\setupapi.log
file and I don't see any errors. I'm gonna attach it just in case any of
you are able to read anything more into it. This is driving me absolutely
nuts.

Thanks in advance for continuing to help me.

Howard

SetUpAPI.log (Canon scanner section)
[2009/05/05 23:52:49 3260.8 Driver Install]
#-019 Searching for hardware ID(s): canon_bjnp&mx700_series
#-198 Command line processed: "C:\Program Files\CanonBJ\IJPrinter\Canon
MX700 series\nwiainst.ex_" /I:"CANON_BJNP&MX700_SERIES"
#I022 Found "CANON_BJNP&MX700_series" in c:\windows\inf\oem9.inf; Device:
"Canon MX700 ser Network"; Driver: "Canon MX700 ser Network"; Provider:
"Canon"; Mfg: "Canon"; Section name: "CNCInstallNet_XP".
#I023 Actual install section: [CNCInstallNet_XP.NT]. Rank: 0x00000000.
Effective driver date: 05/18/2007.
#I063 Selected driver installs from section [CNCInstallNet_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains: {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\CANON_IJ_NETWORK\0000".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [CNCInstallNet_XP.NT.Interfaces] from
"c:\windows\inf\oem9.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\CANON_IJ_NETWORK\0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "ROOT\CANON_IJ_NETWORK\0000" finished successfully.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\CANON_IJ_NETWORK\0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/05/05 23:52:48 3260.5 Driver Install]
#-019 Searching for hardware ID(s): canon_bjnp&mx700_series
#-198 Command line processed: "C:\Program Files\CanonBJ\IJPrinter\Canon
MX700 series\nwiainst.ex_" /I:"CANON_BJNP&MX700_SERIES"
#I022 Found "CANON_BJNP&MX700_series" in C:\WINDOWS\inf\oem9.inf; Device:
"Canon MX700 ser Network"; Driver: "Canon MX700 ser Network"; Provider:
"Canon"; Mfg: "Canon"; Section name: "CNCInstallNet_XP".
#I023 Actual install section: [CNCInstallNet_XP.NT]. Rank: 0x00000000.
Effective driver date: 05/18/2007.
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#I063 Selected driver installs from section [CNCInstallNet_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains: {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\CANON_IJ_NETWORK\0000".
#I298 DICS_DISABLE DICS_FLAG_GLOBAL: Disabling device globally.

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

I guess I need to give more consideration to the "incorrect install"
possibility. I can assure you that I have installed it correctly each
and
every time. However, I think that my son did, in fact, connect the
printer
the very first time before running the CD installation which would have
installed an XP USB [probably printer] driver.

If that's the case, wouldn't my subsequent uninstall of the printer and
its
drivers have removed whatever got installed the first time?

Thanks all for continuing to help me with this.

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

You might also check hardware devices, hidden devices

If you installed the cannon using the correct method, no drivers
should
have
been updated when you connected it

Thanks for spending so much time on this Paul. I'll try this and
let
you
know the outcome.

Best regards,

Howard
Redmond, WA
========================================================

Howard Woodard wrote:
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,

I cannot promise anything, but have a look in the setupapi.log
file.
It is in C:\WINDOWS. I also have a setupapi.log.0.old file, which
presumably is from the system starting a new one at some point.

"Troubleshooting Device Installation with the SetupAPI.Log File"
http://www.microsoft.com/whdc/driver/install/setupapilog.mspx

At the device level, I see by googling, that the printer would be
a "USB Composite" Device. So it is possible a copy of UVCView would
show the config space information, if the printer/scanner was
plugged
directly into the computer. You should see a couple sections to
the config information, each covering a function of the device.

File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e

This is a picture of what the UVCView info looks like.

Some information on the parameters seen in UVCView.

And if you thought the problem was purely related to the VIA USB
interface, and this was a desktop computer, you could use a
separate
USB2 PCI card with a different brand of chip on it. You can find
ones with NEC chips for example. The only negative on NEC chips,
is occasionally a port will blow out due to ESD (at least, that
is what the symptoms suggest). Otherwise, the NEC chips seem to
work. Microsoft delivered the first USB2 driver, using a NEC
USB2 chip to test it.

Four external USB2 ports, NEC chip onboard.
http://www.newegg.com/Product/Product.aspx?Item=N82E16815104216

The thing is, if you can print but not scan, it suggests that
the existing interface works at the physical level. Something
a little higher up might be involved.

Save the following to a batch file:
------------------------------------------------------------------------------
set devmgr_show_nonpresent_devices=1
cd %SystemRoot%\System32
start devmgmt.msc
------------------------------------------------------------------------------

Once the Device Manager is started, select "Show hidden devices' from
the View menu.

As for install most USB based printers, the install instruction would
normally state to run the included CD first or download the "revised"
printer drivers before ever connecting the printer to the PC. I
personally encountered huge problems when a USB printer was first
connected to the PC before installing the drivers. I had to go back
with a System Restore first since no drivers would correct the
access / set up to the printer.

No. Windows XP will detect a "driver" for this printer. If the
driver is incorrect, then XP will constantly load that incorrect
driver before check the correct driver. You now have a "long" jobs
ahead in order to clear out that incorrect selected driver setting.
Once this incorrect driver is "removed" from "Device Manager" you
could re-install the correct drivers before re-connecting the printer.

Please save my "recommended" settings (previous post) and try running
the 'batch' file. Then, in the USB, printer, Ports, Imaging and "DOT"
section, uninstall the "ghosted" hidden devices. (BE CAREFUL.)

 

[Howard Woodard]

Btw, I have the complete SetUpAPI log file if anyone wants to take a further
look at it.

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

Ok, I have done everything everybody has suggested, including installing a
new Koutech PCI to USB2.0 Card Model IO-PU520, and I still have the exact
same problem. At the end of the install step that occurs right after
plugging in the printer's USB cable I get a message saying that the driver
failed to install properly and then, though every other printer function
works properly, Device Manager has an error icon "Driver failed to load
(code 39)" and when I try to use the scanner function I get an error
saying that the PC can't connect to the scanner.

I have extracted the scanner installation section from the C:\setupapi.log
file and I don't see any errors. I'm gonna attach it just in case any of
you are able to read anything more into it. This is driving me absolutely
nuts.

Thanks in advance for continuing to help me.

Howard

SetUpAPI.log (Canon scanner section)
[2009/05/05 23:52:49 3260.8 Driver Install]
#-019 Searching for hardware ID(s): canon_bjnp&mx700_series
#-198 Command line processed: "C:\Program Files\CanonBJ\IJPrinter\Canon
MX700 series\nwiainst.ex_" /I:"CANON_BJNP&MX700_SERIES"
#I022 Found "CANON_BJNP&MX700_series" in c:\windows\inf\oem9.inf; Device:
"Canon MX700 ser Network"; Driver: "Canon MX700 ser Network"; Provider:
"Canon"; Mfg: "Canon"; Section name: "CNCInstallNet_XP".
#I023 Actual install section: [CNCInstallNet_XP.NT]. Rank: 0x00000000.
Effective driver date: 05/18/2007.
#I063 Selected driver installs from section [CNCInstallNet_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains:
{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\CANON_IJ_NETWORK\0000".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [CNCInstallNet_XP.NT.Interfaces] from
"c:\windows\inf\oem9.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\CANON_IJ_NETWORK\0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "ROOT\CANON_IJ_NETWORK\0000" finished
successfully.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\CANON_IJ_NETWORK\0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/05/05 23:52:48 3260.5 Driver Install]
#-019 Searching for hardware ID(s): canon_bjnp&mx700_series
#-198 Command line processed: "C:\Program Files\CanonBJ\IJPrinter\Canon
MX700 series\nwiainst.ex_" /I:"CANON_BJNP&MX700_SERIES"
#I022 Found "CANON_BJNP&MX700_series" in C:\WINDOWS\inf\oem9.inf; Device:
"Canon MX700 ser Network"; Driver: "Canon MX700 ser Network"; Provider:
"Canon"; Mfg: "Canon"; Section name: "CNCInstallNet_XP".
#I023 Actual install section: [CNCInstallNet_XP.NT]. Rank: 0x00000000.
Effective driver date: 05/18/2007.
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#I063 Selected driver installs from section [CNCInstallNet_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains:
{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\CANON_IJ_NETWORK\0000".
#I298 DICS_DISABLE DICS_FLAG_GLOBAL: Disabling device globally.

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

I guess I need to give more consideration to the "incorrect install"
possibility. I can assure you that I have installed it correctly each
and
every time. However, I think that my son did, in fact, connect the
printer
the very first time before running the CD installation which would have
installed an XP USB [probably printer] driver.

If that's the case, wouldn't my subsequent uninstall of the printer and
its
drivers have removed whatever got installed the first time?

Thanks all for continuing to help me with this.

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



You might also check hardware devices, hidden devices

If you installed the cannon using the correct method, no drivers
should
have
been updated when you connected it



Thanks for spending so much time on this Paul. I'll try this and
let
you
know the outcome.

Best regards,

Howard
Redmond, WA
========================================================

Howard Woodard wrote:
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

I cannot promise anything, but have a look in the setupapi.log
file.
It is in C:\WINDOWS. I also have a setupapi.log.0.old file, which
presumably is from the system starting a new one at some point.

"Troubleshooting Device Installation with the SetupAPI.Log File"
http://www.microsoft.com/whdc/driver/install/setupapilog.mspx

At the device level, I see by googling, that the printer would be
a "USB Composite" Device. So it is possible a copy of UVCView
would
show the config space information, if the printer/scanner was
plugged
directly into the computer. You should see a couple sections to
the config information, each covering a function of the device.

*******
ftp://ftp.efo.ru/pub/ftdichip/Utilities/UVCView.x86.exe
http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe

File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e

This is a picture of what the UVCView info looks like.

http://www.die.de/blog/content/binary/usbview.png

Some information on the parameters seen in UVCView.

http://www.beyondlogic.org/usbnutshell/usb5.htm
*******

And if you thought the problem was purely related to the VIA USB
interface, and this was a desktop computer, you could use a
separate
USB2 PCI card with a different brand of chip on it. You can find
ones with NEC chips for example. The only negative on NEC chips,
is occasionally a port will blow out due to ESD (at least, that
is what the symptoms suggest). Otherwise, the NEC chips seem to
work. Microsoft delivered the first USB2 driver, using a NEC
USB2 chip to test it.

Four external USB2 ports, NEC chip onboard.
http://www.newegg.com/Product/Product.aspx?Item=N82E16815104216

The thing is, if you can print but not scan, it suggests that
the existing interface works at the physical level. Something
a little higher up might be involved.

Paul

Save the following to a batch file:
------------------------------------------------------------------------------
set devmgr_show_nonpresent_devices=1
cd %SystemRoot%\System32
start devmgmt.msc
------------------------------------------------------------------------------

Once the Device Manager is started, select "Show hidden devices' from
the View menu.

As for install most USB based printers, the install instruction would
normally state to run the included CD first or download the "revised"
printer drivers before ever connecting the printer to the PC. I
personally encountered huge problems when a USB printer was first
connected to the PC before installing the drivers. I had to go back
with a System Restore first since no drivers would correct the
access / set up to the printer.

No. Windows XP will detect a "driver" for this printer. If the
driver is incorrect, then XP will constantly load that incorrect
driver before check the correct driver. You now have a "long" jobs
ahead in order to clear out that incorrect selected driver setting.
Once this incorrect driver is "removed" from "Device Manager" you
could re-install the correct drivers before re-connecting the printer.

Please save my "recommended" settings (previous post) and try running
the 'batch' file. Then, in the USB, printer, Ports, Imaging and "DOT"
section, uninstall the "ghosted" hidden devices. (BE CAREFUL.)

 

[Howard Woodard]

Sorry 'bout that last post. It was the wrong section of the log file. I'm
installing a direct USB connect so the network install is supposed to fail.
Here's the scanner install and you can see that it fails to load the driver
after installing it. However, it doesn't tell me why.

[2009/05/05 23:56:10 684.7 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_04a9&pid_1729&rev_0108&mi_00,usb\vid_04a9&pid_1729&mi_00
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_ff,usb\class_ff&subclass_00,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\VID_04A9&PID_1729&MI_00" in C:\WINDOWS\inf\oem9.inf;
Device: "Canon MX700 ser"; Driver: "Canon MX700 ser"; Provider: "Canon";
Mfg: "Canon"; Section name: "CNCInstall_XP".
#I023 Actual install section: [CNCInstall_XP.NT]. Rank: 0x00000001.
Effective driver date: 05/18/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [CNCInstall_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains: {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [CNCInstall_XP.NT.Interfaces] from
"c:\windows\inf\oem9.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000"
finished successfully.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.

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

 

[Howard Woodard]

Hi Paul and thanks for hanging in there with me. If I said that I had tried
to install it as a network connected device then I mis-spoke. The printer
connects directly to the desktop via USB.

I redid everything with the log file set for verbose and it provides a
little more info:

#-166 Device install function: DIF_INSTALLDEVICE.
@ 13:58:35.515 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:35.562 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
#I123 Doing full install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
@ 13:58:35.656 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:35.703 #V005 Opened the PNF file of "c:\windows\inf\sti.inf"
(Language = 0409).
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000"
finished successfully.
@ 13:58:36.359 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:38.609 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.

Is it any more helpful? Does it help?

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

Sorry 'bout that last post. It was the wrong section of the log file.
I'm installing a direct USB connect so the network install is supposed to
fail. Here's the scanner install and you can see that it fails to load
the driver after installing it. However, it doesn't tell me why.

[2009/05/05 23:56:10 684.7 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_04a9&pid_1729&rev_0108&mi_00,usb\vid_04a9&pid_1729&mi_00
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_ff,usb\class_ff&subclass_00,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\VID_04A9&PID_1729&MI_00" in C:\WINDOWS\inf\oem9.inf;
Device: "Canon MX700 ser"; Driver: "Canon MX700 ser"; Provider: "Canon";
Mfg: "Canon"; Section name: "CNCInstall_XP".
#I023 Actual install section: [CNCInstall_XP.NT]. Rank: 0x00000001.
Effective driver date: 05/18/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [CNCInstall_XP] in
"c:\windows\inf\oem9.inf".
#I320 Class GUID of device remains:
{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [CNCInstall_XP.NT.Interfaces] from
"c:\windows\inf\oem9.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000"
finished successfully.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.

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

Ok, I have done everything everybody has suggested, including installing
a new Koutech PCI to USB2.0 Card Model IO-PU520, and I still have the
exact same problem. At the end of the install step that occurs right
after plugging in the printer's USB cable I get a message saying that
the driver failed to install properly and then, though every other
printer function works properly, Device Manager has an error icon
"Driver failed to load (code 39)" and when I try to use the scanner
function I get an error saying that the PC can't connect to the scanner.

I have extracted the scanner installation section from the
C:\setupapi.log file and I don't see any errors. I'm gonna attach it
just in case any of you are able to read anything more into it. This is
driving me absolutely nuts.

Thanks in advance for continuing to help me.

Howard

SetUpAPI.log (Canon scanner section)...

So what does the log tell you ? Not much really.

This line tells you what INF file is being consulted right now. The
USB\VID_04A9&PID_1729 was found to match in there. That is why
that particular INF was picked. Looking in the file, would
give you some idea what the printer needs, what registry stuff
it might play with, and so on.

Installing section [CNCInstall_XP.NT.Interfaces] from
"c:\windows\inf\oem9.inf"

Looking at the printer characteristics, it is moderately complicated.

Pixma MX700
http://www.usa.canon.com/consumer/c...ategoryid=123&modelid=15651#ModelTechSpecsAct

It has USB printing, USB scanning, and also supports memory cards
via a memory card slot. The memory card slot feature will invoke
some kind of driver in Windows, and you may see some bogus drive
letters show up when that installs. It could even be, that the
driver installation is failing on the memory card interface, and
not the rest of the printer.

But you also claim to have tried to install with the network interface
connected. And it failed the same way ? When trying the network interface,
was the USB disconnected ?

Paul

 

[Paul]

Hi Paul and thanks for hanging in there with me. If I said that I had
tried to install it as a network connected device then I mis-spoke. The
printer connects directly to the desktop via USB.

I redid everything with the log file set for verbose and it provides a
little more info:

#-166 Device install function: DIF_INSTALLDEVICE.
@ 13:58:35.515 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:35.562 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
#I123 Doing full install of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
@ 13:58:35.656 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:35.703 #V005 Opened the PNF file of "c:\windows\inf\sti.inf"
(Language = 0409).
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000"
finished successfully.
@ 13:58:36.359 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
@ 13:58:38.609 #V005 Opened the PNF file of "c:\windows\inf\oem9.inf"
(Language = 0409).
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of
"USB\VID_04A9&PID_1729&MI_00\6&3401984A&1&0000".
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I304 DICS_PROPCHANGE: Device could not be restarted.

Is it any more helpful? Does it help?

I have an "sti.inf" on my computer, and it says

STI.INF -- Windows Still Image Setup File

So maybe that has something to do with scanning ?

If I open a command window, and do

tasklist /svc

I can see one svchost which has "stisvc" running in it.

Is there some other piece of hardware that was installed,
that has changed something related to STI.INF ? I noticed
plugging in my webcam, it doesn't go near STI.INF, and
instead uses usbvideo.inf for video and wdma_usb.inf
for audio. So I don't immediately see the reason why
stisvc is running on my machine - unless it is always
running on everyone's machine.

Some of the related software is mentioned here.

http://en.wikipedia.org/wiki/Windows_Image_Acquisition

Paul