In article <3FABAC48.EB665B17@att.net>, Steve Fabac <smfabac@att.net> wrote:
>Bob Meyers wrote:

>> "Steve Fabac" <smfabac@att.net> wrote in message


>Your opinion. My opinion is XP is bloat ware and only necessary to keep
>pulling money from installed base of pre-XP users via forced upgrade.
>Win 98 in an office environment providing browsing, word processing,
>spread sheet, and Termlite access to UNIX is satisfactory for 98% of
>small business clients.

And Win98 support and bug fixes and security patches goes away in
the coming year. :-(. They [MS] are going to eventually force
all old variants to upgrade, or be vulnerable [may be it should be
more vulnerable] than current versions because of no security
upgrades, just as 95 is today.


--
Bill Vermillion - bv @ wjv . com

"Steve Fabac" <smfabac@att.net> wrote in message
news:3FABAC48.EB665B17@att.net...
>
> Yes. And from command line: cat /etc/somefile | lp -dwinprinter.
>
> But what difference does that make? The application essentially pipes
> to lp -dwinprinter -s. So what is the reason for your question?

I apologize for my munged replies, I have printed to XP both ways. I logged
in on remotes and checked. The best way is to simply add the 'visionfs
print' line to the spooler script, and share the printer on the XP box.

This method sometimes did not work, it may be that XP boxes with Windows
Domain authentication won't allow it. In those cases, I used Windows XP TCP
Print services (LPD) with good success.

If I can help more, like XP config, email me.