Oop! sorry! This command only works once you are in %windir%/system32/
Spent an hour scratching head until I again read the directions!!! LOL!
Duncan
At 08:21 01/19/2009 -0500, dsinc wrote:
Winterlight,
I had a problem similar to this in XP. I had old, busted, printer ports on
two of my upgrade machines. After some searching, I found a cmd-line app
that let me identify and remove the old, busted printer ports. Once gone,
I was able to install my network printer again. Try/google:
cscript prnport.vbs -l (lists printer ports on machine)
cscript prnport.vbs -d (deletes a port)
cscript prnport.vbs /? (many other options/modifiers)
HTH,
Duncan
At 23:48 01/18/2009 -0800, you wrote:
I have a old Latitude that I use as a print server. It runs Win2k SP4 and
makes a great print server. One of the installed printers is a Epson R200
Inkjet. I have no problem installing this printer on another XP PRO
computer using Epson XP drivers. However, Vista 64, which has freaking
NATIVE R200 drivers refuses to use them when I try to install it as a
network device.
I go to add printer, then I browse to the shared printer on the latitude,
then I start the process and when I get to the install drivers Vista64
keeps telling me the shared printer doesn't have the right drivers and
could I point Vista64 to them.
Epson does have a setup program but all the inf files are in encrypted
cabs. So I installed it like a local printer and then tried to change the
port... same problem. Then I installed as a local printer using Vista64s
native R200 driver after which I tried to change the port... same
problem. I don't get why Vista won't use it's own driver with the network
share. Any ideas?
