On Sun, 22 Dec 2002 18:14:46 -0600 (CST)
Mark <mindfunk@mindfunk.net> wrote:

> > Mark wrote:
> >
> > > I'm trying to set up a windows machine to print to a printer attached to
> > > my netbsd box. I'm not currently running samba, and I believe there is a
> > > way to do this without doing so since I found a posting about OS X
> > > describing this w/o samba.
> >
> > I know nothing about CUPS, but if you can make it listen on "printer"
> > (BSD LPD) then take this sequence in Windows:
> >
> > Printers
> > Add New Printer
> > Local printer
> > Create a new port - select Standard TCP/IP Port
> > Enter IP address and symbolic name
> > Select printer driver
> 
> no, I want to be able to print from a windows machine to a printer
> attached via lpt to a netbsd machine running cupsd. I want to do this
> without using samba.
> 
> I found out that win2k can do this easily... it looks like a problem with
> windows 98.... but I'm not completely sure.
> 
> namaste,
> Mark
> 

This is all based on 4 year old memories of things I didn't want to know tio
begin with, so please bear with me if I am mistaken. :-)

newer versions of windows and OSX can use lpr protocol to connect to the
lpr daemon on your netbsd box. The jobs gets queued and printed in the same
ways as a local job.

win98 [I believe] and win95 or older, all require some kind of additional
software to make them work and play well with lpr [and lots of other
standards]. 

So, as I see it,you have three options. 

1. run samba [which you don't want to do]
2. add a lpr driver to your win98 box [or better yet load something like
solstice and add lots of things like nfs, X, etc..]
3. get a cheap network lpt to ethernet print server and make it into a budget
network printer. Make sure you get one that has a windows lpr driver that will
work with the frob. Also, you'll need to have the right drivers for the
printer on your win98 box. With 1 and 2 above, you can let lpr call
ghostscript, cups, etc... from /etc/printcap, so if you can't get a driver for
win98 for your printer, then this wont work for you. [In the past I used a
DLINK one and my windows and unix boxs all seemed to like it. I've divested
myself of windows, except for virtual PC on one mac]

My experience is that option 3 is easiest, since most printers have at least
some compatibility mode, e.g. HP LJII, so that you can use a generic windows
driver to print to the print server frob. Just as a datapoint, print
server frobs can be found online for around $50. [sometimes less]

I hope that helps more that it hurts.

-- 
Harry Waddell
Caravan Electronic Publishing