yes, this is correct. It must be the exact same driver or it will fail. So,
if your printer is natviely supported by ntprint.inf, you need to either
edit the ntprint.inf file (tricky, and not recommended), or make a decision
about what workaround printer you will use that IS supported, and then
create a printer on the server that uses that same (but 32-bit version)
driver, and then add the x64 version.
--
Please, all replies to the newsgroup.
======================
Charlie.
http://www.msmvps.com/xperts64/
Alex Griffin wrote:
> "Alex Griffin" wrote:
>> Ok, more fiddling and it does work. I created a fresh printer pointing at
>> the same printing device, and when I tried to add the 64 bit driver on
>> that system, it worked. I guess my earlier fiddling has left the original
>> printer instanced in a befuddled state and it is not playing. Nothing a
>> reboot probably will not fix. *grumble*
>
> Ok, last update, I hope... but I felt it only fair to share my last
> discovery. This may be obvious to the printer gurus out there, but it was
> not to me. You have to use the same driver across the board, and that's
> where the problem was occurring when I was trying to add the 64 bit driver
> to the orginal "printer". When I installed the second "printer" I choose
> the 32 bit Windows 2003 Server provided Optra 1200 driver called "Lexmark
> Optra Color 1200 (MS)", and consequently the 64 bit driver was able to
> install because that is the same driver "series" that is also on the 64
> bit OS . The original Lexmark driver I had on my original "printers" must
> be a Lexmark version since it is literally called "Lexmark Optra Color
> 1200" (Not the MS or PS one), and as a result there was indeed no 64 Bit
> version which is what the installer kept on telling me, and it was right
> there was none.
> I am not too sure my explanation is very clear, if you want me to clarify
> futher then please say so and I will try.