| Page 1 of 2 | 1 | 2 |
|
|
|
How to install Printer Driver
I've got a universal driver that is not included in Windows. My plan is to
pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? |
How to install Printer Driver
Cameron Shaw wrote:
I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
I realized I maybe approxing this wrong. The whole idea here is that I
install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
I realized I maybe approxing this wrong. The whole idea here is that I
install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
I'll try that, but to make things more complicated the driver is a universal
driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
I'll try that, but to make things more complicated the driver is a universal driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
Where is the prindvr.vbs script located? I ran the command but it oculdn't
find the vbs "Cameron Shaw" wrote in message ... I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? |
How to install Printer Driver
Where is the prindvr.vbs script located? I ran the command but it oculdn't
find the vbs "Cameron Shaw" wrote in message ... I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? |
How to install Printer Driver
I think I got the syntax right
csript prndrvr.vbs -a -m "XeroxMultiFunction" -e "Windows NT x86" -v 3 -h C:\Test -i C:\Test\x2UNIVP.inf except I just a message saying "Unable to add printer driver XeroxMultifunction Win32 error code 87 Any idea what that means? "Cameron Shaw" wrote in message ... I'll try that, but to make things more complicated the driver is a universal driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
I think I got the syntax right
csript prndrvr.vbs -a -m "XeroxMultiFunction" -e "Windows NT x86" -v 3 -h C:\Test -i C:\Test\x2UNIVP.inf except I just a message saying "Unable to add printer driver XeroxMultifunction Win32 error code 87 Any idea what that means? "Cameron Shaw" wrote in message ... I'll try that, but to make things more complicated the driver is a universal driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
If the drivers are unsigned prndrvr.vbs will not be able to install them.
John Cameron Shaw wrote: I think I got the syntax right csript prndrvr.vbs -a -m "XeroxMultiFunction" -e "Windows NT x86" -v 3 -h C:\Test -i C:\Test\x2UNIVP.inf except I just a message saying "Unable to add printer driver XeroxMultifunction Win32 error code 87 Any idea what that means? "Cameron Shaw" wrote in message ... I'll try that, but to make things more complicated the driver is a universal driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
How to install Printer Driver
If the drivers are unsigned prndrvr.vbs will not be able to install them.
John Cameron Shaw wrote: I think I got the syntax right csript prndrvr.vbs -a -m "XeroxMultiFunction" -e "Windows NT x86" -v 3 -h C:\Test -i C:\Test\x2UNIVP.inf except I just a message saying "Unable to add printer driver XeroxMultifunction Win32 error code 87 Any idea what that means? "Cameron Shaw" wrote in message ... I'll try that, but to make things more complicated the driver is a universal driver support multi brand printers so it doesn't really have a fixed name "John John - MVP" wrote in message ... You could add the driver with Prndrvr.vbs, but you still need to use a valid driver name (-m). http://www.microsoft.com/resources/d....mspx?mfr=true John Cameron Shaw wrote: I realized I maybe approxing this wrong. The whole idea here is that I install this universal driver once and then any printer I add I can assign this driver. So would the add inf even be the correct method? "John John - MVP" wrote in message ... Cameron Shaw wrote: I've got a universal driver that is not included in Windows. My plan is to pre-deploy this driver onto the O/S and then as we add the various printer just point to that driver. I'd prefer to do it this way rather then having to isntall the driver everytime we add a printer I've been various commands: rundll32 printui.dll,PrintUIEntry /ia /m "Test Printer" /h "Intel" /v "Windows 2000 or XP" /f c:\test\x2UNIVP.inf but everytime I just get the popup "the arguments are invalid" Any suggestions? Maybe choking on the /m switch, it's the driver name, look in the .inf file. John |
| All times are GMT +1. The time now is 10:20 AM. |
|
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters