![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Printing, Faxing and Scanning with Vista A forum for using printers, scanners and fx with Windows Vista. (microsoft.public.windows.vista.print_fax_scan) |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hank - Unless you have the original disk from the printer - and I'm guess it doesn't have drivers for Vista - you're best bet is going to be to switch to the universal print driver on the 1300. It seems that the only 64-bit driver that HP is making available is the UPD - you can determine if PCL5, PCL6, or PS is the best for you. If the driver names don't match, you can't install the 64-bit driver on the 32-bit system - it won't regonize it as a valid driver. I know, I'm having the same problem with every one of my printers on my 32-bit Server 2003 systems (about 150 print servers, with an average of 6 printers per server!). All drivers installed are the original drivers from HP, and the only thing they offer for Vista and 64-bit systems is the UPD. I now have to remove and upgrade to the UPD for all of my systems......for about 3 dozen Vista and 64-bit users! -- HaywoodJ |
|
|||
|
Hank - Unless you have the original disk from the printer - and I'm guess it doesn't have drivers for Vista - you're best bet is going to be to switch to the universal print driver on the 1300. It seems that the only 64-bit driver that HP is making available is the UPD - you can determine if PCL5, PCL6, or PS is the best for you. If the driver names don't match, you can't install the 64-bit driver on the 32-bit system - it won't regonize it as a valid driver. I know, I'm having the same problem with every one of my printers on my 32-bit Server 2003 systems (about 150 print servers, with an average of 6 printers per server!). All drivers installed are the original drivers from HP, and the only thing they offer for Vista and 64-bit systems is the UPD. I now have to remove and upgrade to the UPD for all of my systems......for about 3 dozen Vista and 64-bit users! -- HaywoodJ |
|
|||
|
Thanks, I don't have the disk and I'm trying the UPD with no luck either. We have other Vista machines (32 bit) and they seem to be able to point and install. Not so with 64 bit! -- Hank Taylor |
|
|||
|
Thanks, I don't have the disk and I'm trying the UPD with no luck either. We have other Vista machines (32 bit) and they seem to be able to point and install. Not so with 64 bit! -- Hank Taylor |
|
|||
|
A Remote Procedure Call connection (RPC) is not going to work in this case
since the driver names do not match. You have a couple quick options. 1) Install the x86 Vista driver for this device onto the print server and install a new (or change the current queue to use the Vista driver but HP does not recommend this) queue for the device. When the driver name matches, the x64 Vista machine will install the local driver for the connection. 2) Create a Local Port in the form \\printserver\printer where printer is the share name (avoid using spaces in the share name ) on the x64 machine and use this port for a Local Printer that uses the Vista x64 driver. This basically just copies the formatted for printer data to the share as if you had printed to file and copied the file to the print share. -- Alan Morris Windows Printing Team Search the Microsoft Knowledge Base he http://support.microsoft.com/search/?adv=1 This posting is provided "AS IS" with no warranties, and confers no rights. "Hank Taylor" wrote in message ... Hi Alan, Local Drivers.. Driver Name Environment Driver Version Provider Server Name Microsoft XPS Document Writer Windows x64 0.0.0.0 Microsoft ANGEL-HANK (local) Microsoft Shared Fax Driver Windows x64 6.0.6001.18000 Microsoft ANGEL-HANK (local) HP Universal Printing PS Windows x64 61.91.12.106 HP ANGEL-HANK (local) HP Universal Printing PCL 5 (v5.0) Windows x64 61.91.12.106 HP ANGEL-HANK (local) HP Universal Printing PCL 5 Windows x64 61.91.12.106 HP ANGEL-HANK (local) hp LaserJet 1300 PCL 5 Windows x64 6.0.6001.18000 Microsoft ANGEL-HANK (local) HP Color LaserJet CP3525 PCL 6 Windows x64 61.82.61.41 HP ANGEL-HANK (local) Amyuni Document Converter 300 Windows x64 0.0.0.0 ANGEL-HANK (local) Amyuni Document Converter 2.51 Windows x64 0.0.0.0 ANGEL-HANK (local) HP Universal Printing PCL 5 (v5.0) Windows NT x86 61.91.12.106 HP ANGEL-HANK (local) Server Drivers... river Name Environment Driver Version Provider Server Name hp LaserJet 1300 PCL 5 Windows x64 6.0.6001.18000 Microsoft ANGELSERVER HP Universal Printing PCL 5 (v5.0) Windows x64 61.91.12.106 HP ANGELSERVER HP Universal Printing PCL 5 (v5.0) Windows NT x86 61.91.12.106 HP ANGELSERVER Microsoft XPS Document Writer Windows NT x86 0.0.0.0 ANGELSERVER hp LaserJet 3030 PCL 6 Windows NT x86 60.5.36.2 HP ANGELSERVER hp LaserJet 1300 PCL 5e Windows NT x86 60.5.17.2 Hewlett-Packard ANGELSERVER HP Color LaserJet 3600 Windows NT x86 60.52.41.0 HP ANGELSERVER I don't have the same names and have been having a difficult time loading what I need. I've even tried hubbing the USB for a direct connect, no luck. -- Hank Taylor |
|
|||
|
A Remote Procedure Call connection (RPC) is not going to work in this case
since the driver names do not match. You have a couple quick options. 1) Install the x86 Vista driver for this device onto the print server and install a new (or change the current queue to use the Vista driver but HP does not recommend this) queue for the device. When the driver name matches, the x64 Vista machine will install the local driver for the connection. 2) Create a Local Port in the form \\printserver\printer where printer is the share name (avoid using spaces in the share name ) on the x64 machine and use this port for a Local Printer that uses the Vista x64 driver. This basically just copies the formatted for printer data to the share as if you had printed to file and copied the file to the print share. -- Alan Morris Windows Printing Team Search the Microsoft Knowledge Base he http://support.microsoft.com/search/?adv=1 This posting is provided "AS IS" with no warranties, and confers no rights. "Hank Taylor" wrote in message ... Hi Alan, Local Drivers.. Driver Name Environment Driver Version Provider Server Name Microsoft XPS Document Writer Windows x64 0.0.0.0 Microsoft ANGEL-HANK (local) Microsoft Shared Fax Driver Windows x64 6.0.6001.18000 Microsoft ANGEL-HANK (local) HP Universal Printing PS Windows x64 61.91.12.106 HP ANGEL-HANK (local) HP Universal Printing PCL 5 (v5.0) Windows x64 61.91.12.106 HP ANGEL-HANK (local) HP Universal Printing PCL 5 Windows x64 61.91.12.106 HP ANGEL-HANK (local) hp LaserJet 1300 PCL 5 Windows x64 6.0.6001.18000 Microsoft ANGEL-HANK (local) HP Color LaserJet CP3525 PCL 6 Windows x64 61.82.61.41 HP ANGEL-HANK (local) Amyuni Document Converter 300 Windows x64 0.0.0.0 ANGEL-HANK (local) Amyuni Document Converter 2.51 Windows x64 0.0.0.0 ANGEL-HANK (local) HP Universal Printing PCL 5 (v5.0) Windows NT x86 61.91.12.106 HP ANGEL-HANK (local) Server Drivers... river Name Environment Driver Version Provider Server Name hp LaserJet 1300 PCL 5 Windows x64 6.0.6001.18000 Microsoft ANGELSERVER HP Universal Printing PCL 5 (v5.0) Windows x64 61.91.12.106 HP ANGELSERVER HP Universal Printing PCL 5 (v5.0) Windows NT x86 61.91.12.106 HP ANGELSERVER Microsoft XPS Document Writer Windows NT x86 0.0.0.0 ANGELSERVER hp LaserJet 3030 PCL 6 Windows NT x86 60.5.36.2 HP ANGELSERVER hp LaserJet 1300 PCL 5e Windows NT x86 60.5.17.2 Hewlett-Packard ANGELSERVER HP Color LaserJet 3600 Windows NT x86 60.52.41.0 HP ANGELSERVER I don't have the same names and have been having a difficult time loading what I need. I've even tried hubbing the USB for a direct connect, no luck. -- Hank Taylor |
|
|||
|
The local port option worked. I just had to rename the share and take out the spaces. Thanks Guys! Hank -- Hank Taylor |
|
|||
|
The local port option worked. I just had to rename the share and take out the spaces. Thanks Guys! Hank -- Hank Taylor |
|
| Thread Tools | |
| Display Modes | |
|
|