How to install Printer Driver

[Cameron Shaw]

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?

[John John - MVP]

Post by Cameron Shaw
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
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

[Cameron Shaw]

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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[John John - MVP]

You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true

John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[Cameron Shaw]

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

Post by John John - MVP
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true
John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[Cameron Shaw]

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?

Post by Cameron Shaw
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

Post by John John - MVP
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true
John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[John John - MVP]

If the drivers are unsigned prndrvr.vbs will not be able to install them.

John

Post by Cameron Shaw
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?

Post by Cameron Shaw
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

Post by John John - MVP
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true
John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[Alan Morris [MSFT]]

this should be signed but Xerox universal driver has 'global' in the name

the driver name is located in the inf file


C:\Test\x2UNIVP.inf
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by John John - MVP
If the drivers are unsigned prndrvr.vbs will not be able to install them.
John

Post by Cameron Shaw
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?

Post by Cameron Shaw
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

Post by John John - MVP
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true
John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[Cameron Shaw]

I resolved the issue. It turned to be an issue that you have the ability to
save configuration settings changed in the xerox printer properties but if
you copy that file into the driver despite being instructed to then I found
the install wouldn't work. Once I went back to black config file everything
worked fine.

Post by Alan Morris [MSFT]
this should be signed but Xerox universal driver has 'global' in the name
the driver name is located in the inf file
C:\Test\x2UNIVP.inf
--
Alan Morris
Windows Printing Team
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no rights.

Post by John John - MVP
If the drivers are unsigned prndrvr.vbs will not be able to install them.
John

Post by Cameron Shaw
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?

Post by Cameron Shaw
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

Post by John John - MVP
You could add the driver with Prndrvr.vbs, but you still need to use a
valid driver name (-m).
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true
John

Post by Cameron Shaw
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?

Post by John John - MVP

Post by Cameron Shaw
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
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

[Cameron Shaw]

Where is the prindvr.vbs script located? I ran the command but it oculdn't
find the vbs

Post by Cameron Shaw
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
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?