If the scenario is remote PCs accessing the HP3000 server using an
emulator via the web, then why not have the "printed" output
fornatted in HTML(or PDF for that matter).  That way the user(s) can
pick up the reports on their PCs and print to a local printer if they
need to.

I find with my users that most print because they "always have".
Looking at reports on a screen does require some training and
discipline and there is something convenient about having a piece of
paper on which other things can be written....even if it's next
week's shopping list.



> I would suggest an e-mail address and when the job is complete the output is
> posted to a web accessible file which is then sent to the client by e-mail
> and then have HP Instant Delivery pick up the URL and print the page(s) out
> on a HP printer. Thus allieviating the problem of staying logged on, or
> connected, while the job runs. As for input and output, those would be
> predefined, such as asking for information knowing what will happen, i.e.
> forms processing on the web. Output would be as stated above or sent as an
> e-mail to be downloaded and printed by the user.
>
> James
>
> > -----Original Message-----
> > From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> > Behalf Of Wirt Atmar
> > Sent: Wednesday, February 24, 1999 4:06 PM
> > To: [log in to unmask]
> > Subject: Re: OT : Need a bare-bones box to run Linux on
> >
> >
> > John Krussel writes:
> >
> > > Better yet, if you have your firewalls and routers set up
> > correctly there is
> > >  no reason why you can't print to a jet-direct enabled printer
> > anywhere in
> > >  the world.
> >
> > We've thought about that too, but there are several significant
> > problems with
> > the model. Among them are that most small-business, remote-site
> > PCs and LANs
> > (if they exist) are not likely to be set up as a continuous
> > connection to the
> > internet. It's still too expensive. Dialing into a local ISP is
> > considerably
> > cheaper -- and much less fuss for a small business owner.
> >
> > Similarly, most small-business LANs, when they do exist, are likely to be
> > private-address spaced, and that would require some form of NAT (network
> > address translation), whether they were connected continuously or
> > not. Since
> > the advent of Windows 95, every copy of windows now has its own internal
> > router structure. I don't think it's possible to take a
> > real-world IP address
> > and bridge it across to a specified, office-internal private
> > address space IP
> > using only that structure that exists in a PC. If it were, it
> > would seem to
> > break much of the reason behind non-routable addresses.
> >
> > Thirdly, routers are still too expensive and too difficult to
> > program up for
> > extended small business use, in the absence of an on-site data processing
> > staff. But dialing into something like AOL (which now has extremely good
> > bandwidth) isn't difficult at all -- and it too is amazingly inexpensive.
> >
> > The simplest way still seems to be to have the client (in this case, a
> > terminal emulator) absorb the incoming print string and re-direct to any
> > printer to which it has access. What we want is the capability of
> > creating a
> > full-color PostScript series of pages on the HP3000 and transparently pass
> > that output through the terminal emulator to any printer that the PC can
> > reach, just as if that output originated in the PC itself.
> >
> > We also want the infrastructure to be simple enough so that all
> > that a remote
> > user need do it plop a PC down on a desk, plug the power cord
> > into the wall
> > and modem cord into a telephone jack and have an instant office, anywhere.
> >
> > Wirt Atmar
> >
>
Regards,

Ewart North,
Finance Department,
University of Birmingham,
Edgbaston, Birmingham B15  2TT
Tel:    0121 414 7099
Fax:    0121 414 7979
email:  [log in to unmask]