HP Laserjet 4200 printer driver package issue
I've packaged the HPLJ4200 printer driver using Adminstudio 7.5. All seems to work ok, but although it deploys and you can create a new printer using the driver, when you go to the properties of this printer and click on the "Device Settings" tab, some of the headings for each section are in Arabic, some are in English.
I can't find anything within Adminstudio which controls this and it's something I've never come across before. Anyone seen this or possibly offer a solution?
Thanks
nmi
I can't find anything within Adminstudio which controls this and it's something I've never come across before. Anyone seen this or possibly offer a solution?
Thanks
nmi
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
kkaminsk
18 years ago
Posted by:
nmi
18 years ago
Thanks for the reply. Adminstudio uses DPinst anyway to create the driver so I don't think doing it manually will make any difference.
PrintUI isn't appropriate since all I want to do is make sure the machine "knows" about the existence of the driver and the user isn't prompted to select where the source files are. We are not actually creating a printer on the server, this will be done by another team at another stage.
PrintUI isn't appropriate since all I want to do is make sure the machine "knows" about the existence of the driver and the user isn't prompted to select where the source files are. We are not actually creating a printer on the server, this will be done by another team at another stage.
Posted by:
kkaminsk
18 years ago
Posted by:
nmi
18 years ago
With a bit of fiddling about, I've managed to get it working with DPinst outside of Adminstudio.
I believe that Adminstudio is doing something to the package which is screwing up some part of it (what I don't yet know). For the moment, I have it at a stage where it can be deployed successfully, so will probably leave it there for now.
That one change to dpinst to enable legacy-mode has made the util about 100 times better!
Thanks for the reply.
nmi
I believe that Adminstudio is doing something to the package which is screwing up some part of it (what I don't yet know). For the moment, I have it at a stage where it can be deployed successfully, so will probably leave it there for now.
That one change to dpinst to enable legacy-mode has made the util about 100 times better!
Thanks for the reply.
nmi
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.