RE: [LINUX5250] lp5250d as a windows service?

["Ruel, Marc-Antoine" <maruel@xxxxxxxxxxxxxxx>]

I have experience in setting up printing services so here are some hints:

You can use FireDaemon or something like that to run your software as a service 
as a quick fix but you will have a choice to make:
Either your "service" is interactive so you can see the lp5250d window.
Either your "service" runs as a domain user so it has access to the network 
printers but with no UI.

I think the choice is obvious :)

You will have to install the printers manually on the domain user on the 
computer(s) which will run the lp5250d "service".
I did have problems with printer driver installation and did make some kind of 
protocol in my own service to add printers on this domain user account (which 
is used to run the service). I could setup something for this in lp5250d if I 
get some time on this and there is a need.

Someony could add a -nogui to lp5250d-win.c so it is more silent but it is not 
necessary. The window will not be visible anyway since non interactive services 
run on a different "window station".

Marc-Antoine Ruel

-----Message d'origine-----
DeÂ: linux5250-bounces@xxxxxxxxxxxx [mailto:linux5250-bounces@xxxxxxxxxxxx] De 
la part de Paolo Marchiori
EnvoyÃÂ: 22 octobre, 2004 04:16
ÃÂ: Linux 5250 Development Project
ObjetÂ: Re: [LINUX5250] lp5250d as a windows service?

Well, great, it seems I'm getting more than I ever expected! :)

Scott Klement, Thu, Oct 21, 2004 at 03:27:40PM -0500:
> It has a really simple GUI in Windows, basically just a window where it
> tells the last message that it's received from the '400 and a button to
> allow you to shut down the program.

Absolutely. And while this is a great advantage for a workstation user,
it's very annoying if you want to set up a single central printer in a site
where you only have w32.
I am lucky since the '400 is in the same site as the linux machines, so a
print job sent to PRTPDF would only send PDFs over the WAN, but the basic
idea is: if the original program has been conceived as a daemon, why must
the w32 port run as a session-bound application?

> remember that working with pipes in Windows is not a lot of fun...
...like diving in a pool. In winter. In Trondheim. When the pool is empty
for maintenance.

(...)