[THIN] Re: How to use Windows Server 2003 printer drivers on Windows 2000 Server
- From: "Steve Parr" <sparr@xxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 11 Mar 2005 12:57:41 +0000 GMT
Thanks for all your effort in putting this together Rick - I will test out this
procedure next week in test lab.
Editing the ntprint.inf I recall was problematic on Win2k - suggestion that
there was a digital seal that once edited could be broken and thus not working
anymore(atleast I think it was ntprint.inf) so you would end up with situation
were new drivers previously not added would either not auto-create anymore or
just could not work at all even if manually added at server. I assume that if
any of this is true that it is not the case for Win2k 3 ntprint.inf?? I believe
the solution with win2k if that happened was to just copy the ntprint.inf from
the win2k CD Rom.
-----Original Message-----
From: "Rick Mack" <Rick.Mack@xxxxxxxxxxxxxx>
Date: Fri, 11 Mar 2005 21:54:46
To:<thin@xxxxxxxxxxxxx>
Subject: [THIN] How to use Windows Server 2003 printer drivers on Windows 2000
Server
Hi,
Found a couple of typos right after I sent it. This should now work as typed.
How to use Windows Server 2003 drivers on a Windows 2000 system.
1. stop the spooler, eg "net stop spooler"
2. cd %systemroot%\inf
3. rename ntprint.inf to ntprint.inf.old
and delete ntprint.pnf
3. Make a directory, (it can be anywhere) but for this exercise:
md c:\w2k3_drv
md c:\w2k3_drv\i386
4. Copy driver.cab from \i386 on the Windows Server 2003 CD to
c:\w2k3_drv\i386\pdriver.cab.
Make sure it isn't called driver.cab otherwise it could potentially be used
as a source for other system drivers.
5. Copy ntprint.inf from \i386 on the Windows Server 2003 CD to c:\winnt\inf
6. edit c:\winnt\inf\ntprint.inf.
Look for the following section:
[SourceDisksNames.x86]
1 = %WinNET2003%,driver.cab,,"I386"
[SourceDisksNames.amd64]
1 = %WinNET2003%,driver.cab,,"Amd64"
[SourceDisksNames.ia64]
1 = %WinNET2003%,driver.cab,,"Ia64"
replace these lines with (alter drive lettering to suit):
[SourceDisksNames.x86]
1 = c:\w2k3_drv,pdriver.cab,,"I386"
7. restart the spooler, "net start spooler"
When you add a printer now the Server 2003 drivers will be used.
Sometimes a resource dll isn't found and you'll have to manually select
c:\w2k3_drv\i386\pdriver.cab.
Aside from that this will let you use all the native unidriver and postscript
Windows server 2003 drivers on Windows 2000.
regards,
Rick
Ulrich Mack
Volante Systems
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it in
error please notify the sender immediately by reply e-mail and destroy all
copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby disclaimed
to the extent permitted by law.
********************************************************
This Weeks Sponsor: RTO Software TScale
TScale provides a cost-effective way to improve performance, capacity and
stability for thin-client servers like Citrix MetaFrame or Microsoft Terminal
Services running Windows NT, 2000 or 2003.
http://www.rtosoft.com/enter.asp?id)6
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Excellent SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
