|T O P I C R E V I E W
||Posted - 09/20/2006 : 11:29:20 AM
I'm experimenting with a Win 2003 R2 x64 print server, which of course needs to handle 32-bit clients. I've been able to configure a Dell 5100 printer without any problems because Dell provides both 32 and 64 bit drivers. But I'm not having any luck setting up a Dell 1700; the 1700 does not offer x64 drivers, so I have tried both the Dell 1710 and HP 5000 drivers. In both cases, the server can print without any trouble (so the drivers seem compatible) but I can't install the 32-bit driver on the server for clients to download. I am selecting "Additional Drivers" and then x86 Win 2000, XP and 2003. I am then asked to provide a printer driver. I receive an error message that the specified location does not contain the driver for the requested processor architecture.
This is the first I've needed to work with the Additional Drivers feature, and I'd appreciate any help in getting this to work.
|10 L A T E S T R E P L I E S (Newest First)
||Posted - 03/28/2012 : 06:58:04 AM
It worked for me too.
I did the following:
1. downloaded both x86 and x64 drivers from official HP site.
2. Replaced x64 driver with downloaded one for win2008r2 on advanced tab of printer settings.
3. added x86 driver on Sharing tab of printer settings.
THE DRIVERS HAVE TO BE THE SAME FOR BOTH PLATFORMS. If they are of different versions (older or newer) or different types (pcl5 & pcl6) they may not install. So download both drivers from a single source simultaneously.
||Posted - 08/23/2007 : 12:55:08 PM
ah... more clues. Thanks.
||Posted - 08/16/2007 : 1:17:23 PM
I nearly bumped my own thread with a similar solution just a few days ago. TheDB is pretty much on the money, but I did notice a few oddities.
After installing the printer on the x64 server, connecting to it via a 32-bit client will (apparently) require installing the 32-bit driver (manually) on the local machine. Once (and only once) that's done, can you then access the Additional Drivers and add the 32-bit driver to the server. The net result is it appears you're loading the driver twice. I'm using a clustered print server, so perhaps this is a quirk with clustering; I'm not sure.
Now, all that said, printing support on x64 is still lousy. I ended up using the universal HP driver for a few models, and had to track down similiar/compatible drivers for some non-HP units that didn't have x64 drivers available. I won't know how well all this is working until school starts again in a few weeks; hopefully it all goes well.
There is one thing I could not get to work. We have an old (read: unsupported) HP plotter that does not offer x64 drivers. Windows includes a driver for this plotter that unfortunately doesn't offer the features we need. What I wanted to do was get the server to use the built-in x64 driver for x64 and let me install the proper (HP) driver for x86. No such luck. I couldn't find a way to replace the built-in driver on x86 without being able to do it on x64 as well.
In any event, for now I'd have to say stay with 32-bit Windows for your print servers.
||Posted - 08/09/2007 : 1:06:09 PM
I got it to work. I am using Server 2003 x64 on the print server.
1. The 'Processor Architecture' error happens because the printer names in the .inf files are different.
For example, in the Ricoh Aficio 1060 x64 driver .inf file (RICOHX64.inf), the printer name is "Ricoh Aficio 1060 PCL". In the x86 driver .inf file (OEMSETUP.inf), the printer name is "Ricoh Aficio 1060 PCL 5e". In my case, I installed the x64 driver first, so when you go to add the x86 driver, Windows Server is looking for the same printer name. I went into the OEMSETUP.inf file and edited the printer name so it is the same as the RICOHX64.inf file.
It is a pain in the butt since you have to do it for every printer you want to add/change. But once you do it its easy to do it over and over again. Luckly some newer driver packages use the same name for the x64 an x86 .inf files.
2. Adding x86 drivers... In my Ricoh Aficio 1060 example, I went onto a x86 Windows XP box logged in as a domain server admin account. Downloaded the x86 driver (and edited the .inf file as I said above). And then went to my print server's "Printers and Faxes" share. Right click the printer -> click properties -> sharing -> additional drivers. Check off the proper driver type (in my case "Intel Windows 2000 or XP") and point it to the driver I had downloaded.
I hope this helps anyone out still looking at this thread.
||Posted - 03/22/2007 : 10:16:04 PM
I am having the same issue on an X64 Windows 2003 server. I have installed drivers for a Ricoh. When I try to add print drivers, per the Add Print Fax option on the server> right click the printer> select Share tab> additional drivers. I get the error about the processor architecture. I also get an error when I try to install another driver that says I must install it from a remote x86 machine.
But when I try to install the x86 driver from an X86 machine I get the Processor Architecture error again. Please help?
||Posted - 10/11/2006 : 1:09:23 PM
So, does this work like printer setup on a clustered server? Start| Run \\ServerName | Open Printers and Faxes | Open the properties of the printer in question | Switch to the sharing tab and THEN click Additional drivers?
||Posted - 10/11/2006 : 10:04:43 AM
installed the printer on winxp x86 machine. shared it. "point and print"ed to it from x64 server. then added additional (in this case x64) drivers. worked like charm!
but I'm a bit confused here :). what i want is: a network printer (it has an internal printserver) shared (and listed in AD) by windows server 2003 x64 server so that x86 winxp clients could "point and print" to it.
current situation (the one that worked like charm :) seems to be different.
any help on my "unlimited wishes" ? :)
||Posted - 10/11/2006 : 08:58:56 AM
* EDIT - Fixed up some bad english/description*
I don't have an x64 server but have you tried this:
- Browse to the print server from XP x32 machine with a server admin account.
- Go into the printer and faxes "share".
- Get the properties of the printer
- Click on additional drivers and try adding the x86 driver from there.
* EDIT - Fixed up some bad english/description*
||Posted - 10/11/2006 : 08:13:46 AM
I am experiencing exactly the same problem. No solution yet :( Moreover, I encountered a slightly different problem when trying to add additional drivers for Samsung ML-2251n printer. The printer ships with x86 and x64 drivers. I install x64 printer drivers on the server and then try adding x86 additional drivers. The message I get:
"The selected driver must be installed remotely from an x86 computer running Windows XP, windows 2000 or Windows Server 2003".
I've googled a lot about this error, but found no answer.
||Posted - 09/27/2006 : 5:35:36 PM
I wish i had some 64bit hardware to test this. This sounds like a bummer.