Everhart, Glenn
From:	mathog@seqaxp.bio.caltech.edu
Sent:	Thursday, February 18, 1999 5:56 PM
To:	Info-VAX@Mvb.Saic.Com
Subject:	Re: print queues to Win95/98/NT connected printers
In article <7ahfal$t31@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu writes:
>
>$ sss  "\\wnt_machine_name\SAF LPS17" -
>  "-P" 
>  "-U" wnt_user_name -
>  "-password" wnt_users_password
>  "-file" somefile.ps
>
>What would I then need to do to make this into a print queue?

Thanks to Brian Reed for suggesting CTLSMB (http://www.dls.net/~reed/)
and to Wolfgang J. Moeller for offering up EXECSYMB.  I'm not sure
which I'll go with, but in the meantime, I wrote a couple of little
scripts to hide SMBCLIENT and make printing through it moderately
transparent for end users.  You may pick these up at 

  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/PRINT_TO_WINDOWS.ZIP

you'll also need SMBCLIENT and some configuration files from the Samba
for VMS distribution.  The SMBCLIENT from that distribution may require
a few tweaks to work with these scripts. The version I use 
is a port of Samba 1.9.19, a binary (Alpha only) is availabe at:

  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/SMBCLIENT.ZIP

The scripts in the first ZIP are used this way:

$! in login.com or sylogin.com
$!
$ define prtowin disk:[directory]
$ findwin*printers :== @PRTOWIN:FINDWINPRINTERS.COM
$ printwin*dows    :== @PRTOWIN:PRINTWINDOWS.COM

The information for various printers are stored on a per user basis in
SYS$LOGIN:WINPRINT.DAT.  For once this lets the users target their own
printers, something that they could not do with Pathworks/Mac and LPR print
queues. 

To fill this file, use:

$ findwin machinename username [password]

and answer as appropriate to add printers which are located to the file.
Since the WINPRINT.DAT file may hold passwords, it is protected so that
there is neither group nor world access. 

To print a file use

$ printwin filename [printer]

Where filename points to a postscript file (recognized via .ps, otherwise
assumed to be text and converted on the fly to postscript before printing.)
The second parameter is a short printer name, which you can set at the time
you add printers using findwinprinters.

I've found a couple of Windows machines which refuse to talk to SMBCLIENT
(even the Unix versions). There's no obvious pattern to it - I think it
indicates misconfiguration on the Windows end. 

Hopefully somebody will find these procedures useful.  

Regards,

David Mathog
mathog@seqaxp.bio.caltech.edu
Manager, sequence analysis facility, biology division, Caltech