dvips output - Network printing

[ALAN A DUNWELL]

Many thanks Eli, you win the cookie! The DVIPSRC= worked when pointed 
to my network printer. Thanks also for the gentle reminder to look at 
the documentation. I had of course done that first, but it was a case 
for me of the "man page syndrome". I needed to know what I was 
actually looking for before I could find it and it made sense. Sorry 
for taking bandwidth on this. 

I did some further experimentation and my final procedure for 
network printing is

- edit texmf.cnf to include the variable statement
   DVIPSRC = C:\TeX\dvips\config\config.ps
- on the local machine create the above path and copy the default 
config.ps file to that location.
- edit the local config.ps file so that the "o" line is
   o lpt3
NOTE: if you only use one printer it can just be hardwired 
here with something like   o \\netserver\printername This still 
leaves the option open to others for alternatives since this is a 
local file. If you do this ignore the next step.

- Then edit one of your Windows postscript printer definitions and 
add a captured port LPT3: and direct it to the desired printer. In my 
case I used
   LPT3:  \\jilant\publichp
which is an HP 4SiMx postscript device. You can verify this 
connection from a DOS window with the NET USE command which will echo 
back the ports in use.

WinEdit also picks up this capture when it runs dvips.


Thanks to all,
Alan

--------------- previous ------
> Date:          Wed, 29 Sep 1999 16:06:16 +0200 (IST)
> From:          Eli Zaretskii <eliz@is.elta.co.il>
> Subject:       Re: dvips output error revisited...
> To:            DUNWELL@jila.colorado.edu
> Cc:            fptex@tug.org

> 
> On Wed, 29 Sep 1999, ALAN A DUNWELL wrote:
> 
> > files are shared by all win/95/98/2000/whatever workstations. They
> > just modify their path to see the bin area. So they all end up using
> > the same config.ps. Some may want to print to local printers, mostly
> > HP laserjet types, or more often to network printer queues, all
> > postscript printers. However different folks may want to go to 
> > different printers or queues, so I can't hardwire that in config.ps.
> 
> In that case, the right thing is for each user to have their own printer 
> configuration file, in addition to the global config.ps.  The default 
> printer is just a tip of the iceberg: before long, you will hear 
> complaints that other config.ps settings, like amount of memory installed 
> in the printer, its resolution, etc. are also wrong.
> 
> The easiest way to have customized startup file is to set the DVIPSRC 
> variable in the environment whose value is the full path of a file.  That 
> file has the same format as config.ps, but it is read by dvips *after* 
> config.ps, and so can override the defaults.
> 
> Finally, if the users change their default printer often, or if they use 
> several different ones, there's the appropriate command-line option.
> 
> This is all in the docs, btw.
> 

!--------------------------------------------------------
!Reply to:                                               
! Alan A. Dunwell, JILA Software Manager,               
! JILA - CB440, Univ. of Colorado, Boulder,Co. 80309   
! E-Mail - dunwell@jila.colorado.edu                                            
! Voice  - (303) 492-5308   FAX - (303) 492-5235         
!--------------------------------------------------------