Read your analysis with interest.
If I provide my e-mail can you send the following files as attachments:
So, for the future, I've now got stored away all four of the needed x86 driver folders for the x86 environment, in case I have to reinstall in the future: NTPRINT, PRNCA00T, PRNCA00X and PRNCA00Y.
Thanks
Hi there
If you had followed THIS advice -- I'm sure the printer would have installed without problem.
This little method allows sharing of printers between X-86 and X-64 machines -- no probs including XP ==>W7 and the other way around too.
Read my post -- it's Nr 3 in this thread.
Networking from Printer attached to Win XP PC to Win 7
Cheers
jimbo
I have a question on that final step 6 of your "recipe":
My question is how does "now Windows7 will load a driver" actually occur? And what if it is the 64-bit Win7 machine that is the host of the printer and 32-bit WinXP which is the client trying to connect and share the printer... where does 32-bit WinXP "get its driver"?assume the computers are call XPMACHINE and W7MACHINE.
1) Ensure Printer on XP machine is shared - assume it's called SHAREDPRINTER.
2) On the Network Browsing on your Windows 7 machine ensure you can "See" the Printer share.
Now on the Windows 7 machine do the following (doesn't matter if it's X-86 or x-64).
3) Control Panel==> add LOCAL (Yes LOCAL) printer. I know it's on a Network but hold your horses -- what we are actually doing is "Poodlefaking" the Windows 7 machine into thinking it's running the printer.
4) Create NEW port==>Local port
5) Portname is \\XPMACHINE\SHAREDPRINTER
6) Now Windows 7 will load a driver and you'll be able to print on the XP machine.
Normally, if the printer-host machine is a 64-bit Win7 where the printer is already installed locally to run in a 64-bit environment (when the USB cable was first plugged in, or using the manufacturer's software CD or downloaded driver/app installer), there is no 32-bit "second additional driver" also installed as only the 64-bit driver is needed for local printing on the 64-bit machine..
So if a 32-bit client machine then tries to "connect" (via the standard "Add printer" dialog process) to the shared printer hosted by the 64-bit machine, the 64-bit machine will actually want to deliver the 32-bit "second additional driver" over to the 32-bit client, and that completes the process. But this can only happen if the 32-bit driver is actually installed as a "second additional driver" on the 64-bit host machine.
If both 32-bit and 64-bit drivers are installed on the host machine, then any 32-bit client or 64-bit client can have the appropriate driver delivered from the 64-bit Win7 host machine to be installed on the 32-bit or 64-bit client machine, and the shared printer hosted by the 64-bit host machine can be used for printing by any 32-bit or 64-bit client. So it's the 64-bit host machine that has BOTH drivers installed, and delivers whichever one is needed to the requesting client machine at "connect" time in its "Add printer" dialog.
In your step 6 above, if that "second additional driver" for 32-bit clients is not present on the 64-bit Win7 host machine, where/how does the 32-bit WinXP client get its 32-bit driver from? Is it downloaded automatically from the Microsoft Updates Catalog site at that moment in the "connect" process from its own "Add printer" dialog?
The approach of my alternative method is for installing the 32-bit "second additional driver" on the host 64-bit machine, by simply pointing to the 32-bit drivers for the S800 which would either (a) be present on the 32-bit Win7 installation DVD, or (b) be downloaded from the Microsoft Updates Catalog site automatically if the drivers were not on the Win7 installation DVD.... when the S800 printer was plugged in on a 32-bit Win7 system.
This is the same 32-bit driver that then suffices to feed over to 32-bit WinXP during the "connect" step of the "Add printer" dialog on that 32-bit WinXP system.
Sounds like your method centers on the client machine apparently retrieving the needed driver... from Microsoft Updates Catalog??..., rather than with my method where the host 64-bit machine actually has BOTH 32-bit and 64-bit drivers installed and delivers whichever one is appropriate to any client machine that is trying to "connect" to the shared printer with its own "Add printer" dialog.
I have used the jimbo45 method successfully with a second printer. It did not work with the S800. The S800 appeared to install but the Print Test Page hung in the queue.
Thanks to dsperber for sending drivers. Using your method I got a successful install on the XP client. You should be commended for staying on the trail as long as you did and providing a complete explanation for what was going on.
Glad I could help.
Excellent!!!Using your method I got a successful install on the XP client. You should be commended for staying on the trail as long as you did and providing a complete explanation for what was going on.
I'm super-pleased that you were able to duplicate my own successful results for your situation.
I honestly hadn't seen Jimbo45's recipe when I began my own effort with my brother-in-law's S800, but if I had I probably would have certainly tried it first. If it works at least for some other printers (as he and you and others will confirm) it certainly seems like a VERY SIMPLE approach, and probably SHOULD have also worked for Canon printers in general.
But in the case of the S800, it's clear that Canon really complicated this whole driver install process, breaking it up into three separate driver components and sub-components... and this seems to have made it unusable as implied by the Jimbo45 method, based on your own story.
Anyway, though a bit more nuts-and-bolts in its approach, my method of simply using the Windows "add additional driver" method on the host machine (when it's a 64-bit Win7 machine with its own 3-part 64-bit S800 driver already installed) to install the 32-bit version of the same 3-part driver, so that the Win7 host can then deliver the 32-bit driver over to 32-bit Win7 and WinXP clients at "connection" time... well this seems to be exactly what Microsoft intended when they invented "add additional driver" and the ability to retain BOTH versions on the host machine.
Nevertheless, I'm glad your own situation was resolved period... using my provided driver files and method, as it turns out, to "add additional 32-bit driver" on the 64-bit Win7 host machine.
Terrific.
And boos to Canon and its crazy Win7 driver design for causing this headache.
Quote