Jump to content

Recommended Posts

Posted

That was the thing I was stuck on - I had exactly the same version drivers for both 32 and 64 bit - I just hadn't noticed at the server end that there was a space in the name. I knew the 64 drivers worked locally but not on the server.

 

I might try and edit the .inf file to remove the space - only problem with that is the 64 bit drivers provided by HP are the UPD, yet Windows 7 seems to have its own 64 bit drivers for them, hence the confusion!

 

Plus I just couldn't get the PCL 6 UPD drivers to install on the server, I had to do that at the Win7 client and use the RSAT tools to install onto the server.

Posted
Am sure there was a work around somewhere - not sure if it was the same thing or related but before installing the driver that did not include the space, you can go into the inf file and insert a space and save the inf file and then install it so both had a space ?

 

You can try but that generally messes up the checksum for the driver signing at which point it won't install.

  • Thanks 1
Posted
You can try but that generally messes up the checksum for the driver signing at which point it won't install.

 

Wouldn't it just give you a message box stating that the driver is not digitally signed, yada yada, do you want to continue, click continue and should work ?

 

I cant recall if it was a case of putting the space in for both of them or removing the space between the PCL and the 6 ??

 

Hopefully it works

Posted
I'm stuck with the UPD for these printers I think - I can only get the specific 64 bit driver on a Win7 machine so I don't know where the relevant inf files are.
Posted
Wouldn't it just give you a message box stating that the driver is not digitally signed, yada yada, do you want to continue, click continue and should work ?

 

I cant recall if it was a case of putting the space in for both of them or removing the space between the PCL and the 6 ??

 

Hopefully it works

 

May work on 2003 but its not that it is unsigned but rather corrupted/modified/insecure and so even if it does work on the 2003 server the W7 machines will tell you to get jumped. I would just use the UPD, its better as you only end up with one driver on the machine if you have all hp printers so pushing printer out takes way less time.

  • Thanks 1
Posted
May work on 2003 but its not that it is unsigned but rather corrupted/modified/insecure and so even if it does work on the 2003 server the W7 machines will tell you to get jumped. I would just use the UPD, its better as you only end up with one driver on the machine if you have all hp printers so pushing printer out takes way less time.

 

Can't argue with that :) Fair play....

 

In the words of Duncan Banatyne "I'm ooout" *trys to do scottish accent but fails*

Posted

Argh I should have known it wouldn't last!

 

After trying the UPD drivers for PCL5 and PCL6 I've now found that the 32 bit (ie XP) clients crash every time the printer is accessed if those drivers are specified. Everything crashes when you try to print, Office, open office, IE, explorer - if you try to click print you get an applicaton error!

 

Roll back to the 32 bit only 'proper' HP drivers and we're ok. Use the UPD ones (so that the 64 bit clients work) and all the 32 bit clients fail.

 

Looks like the Win7 64bit clients will just have to do without printers then!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...