|
| |
 |
 |
System
Requirements
In order to use KPrint with
an existing Kerridge system, you will need the following:
 | A PC running Windows
XP or 2000 (Server or Workstation, Server recommended), Windows
95, 98, NT4 or a Citrix NT3.51
system. Depending on the amount of printing, the PC should be a
dedicated machine - that is, it shouldn't be one that is used for
Word, Windows, Excel, etc. Most NT servers are not actually used
as workstations, so we recommend NT as the desired environment.
In some cases where only a small amount of printing needed, using
a workstation will be acceptable. If a Windows 95
PC is used as a KClient terminal, for example, then
there is no reason why KPrint cannot be running at the same time,
with very little effect on system performance. |
|
| The PC using KPrint should
have a sensible amount of memory - Windows NT4 should be run on a PC
with a minimum of 32MB. Windows tends to eat up a lot of memory, and the print jobs
tend to be quite large, so please bear this in mind when sourcing a
suitable server.
KPrint uses very little disk space - a typical KPrint form is around
10KB in size. Windows tends to spool print jobs to
disk, so the more printing that will be done the
disk space becomes more of a factor.
|
| A TCP/IP network
connection from the KPrint server PC to the KCML host. The
PC that is acting as the KPrint server should be connected to the
same TCP/IP LAN as the KCML host. KPrint uses a special network
printing protocol called lp in order to receive
print jobs, so a network must be in place. Note that the KCML host can be the other side of a 64KB
bridge/router - the print jobs sent from the KCML host to KPrint are
just ASCII text and tend to be quite small. The
most important network consideration is the link between the KPrint
server PC and the destination printer.
|
| A Windows printer,
preferably connected directly to the TCP/IP network. Please note
that this printer should be the same side of the WAN as the
KPrint server PC. In other words, the destination
printer should NOT be the other side of a low-bandwidth bridge -
Windows print jobs tend to be quite big - printing a typical form
may cause a 100KB print job to be sent to the printer. If the
printer is the other side of a 64KB link, then this could cause
serious degradation of the network. As long as the KPrint server PC
and the printer are on the same side of the WAN, there should
be no problems.
It is imperative that no attempt is made to send a Windows print job
across a low-bandwidth network. If you want to use
a laser printer at a remote branch, this branch will need a
TCP/IP LAN and a separate KPrint server. |
|
| Tests have also shown
that a high quality laser printer plugged directly into the network
performs better than when plugged directly into the KPrint server
PC. Note that having the printer directly on the LAN is only a
recommendation - KPrint can print to any printer that the server can
see - which could also be a printer connected
directly to LPT1, or even a shared Windows
for Workgroups printer. |
| Either suitable UNIX
lp software (for Kerridge UNIX systems) or KCML 6 (for Kerridge NT systems).
Most versions of UNIX include lp software as
standard.
|
|
|
Related Topics
KPrint
Benefits
Overview
System
requirements
Forms
Sample
Forms Kerridge
KPrint Website
|
|
