Printer destination - rant

Nancy Palmquist nlp at vss3.com
Fri May 29 08:32:38 PDT 2009


rkreiss wrote:
> Windows filePro
>
> filePro will accept win:lpt1 as a valid destination.
>
> Then why will it not accept IP_192.168.nn.nn(port designation), a network
> printer destination, as a valid destination?
>
> It would seem to me that being able to specify a specific IP address would
> make life much simpler the using a printers name.  This is especially true
> in the Windows environment where each computer needs to have the same
> printer name unless they are are local printer connected to lpt1.  this is
> getting rarer and rarer as parallel ports are being replaced by USB or
> network printers.  Even the most modestly priced printer are network
> enabled; either wired or wireless.
>
> Richard Kreiss
> GCC Consulting
> 		
>
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>   
Richard,

Use the Windows Printer Name.  It needs to use the windows drivers to 
get to the printer properly.

Install the Printer in Windows, then use the name in the 
WIN:WindowsPrinterName

If all the users, attach the printer with the same name, it will work 
for all the users, perfectly.

For example:

WIN:Lexmark T634 PCL

is a printer destination on my system and this is not attached to my 
computer, it is setup as a network printer on our system.

What you are proposing is almost a bypass of the Printer stuff on your 
local machine and a dump directly to the printer.  Wouldn't that be 
dangerous on a network printer?

But that is how I do it, there are a million ways to connect to printers 
anymore, I just find this one simplest for my brain to handle.

Good luck.

Nancy

-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com



More information about the Filepro-list mailing list