W-ELP needs for each print job the CPU power of about copying the print file 4 times. When you archive the print file there is one more copy time on top. But for the MyPrintArchive function also 1 less because you don't read the print data back. So the processor is used as like the print data is copied 4 times into another file.
So it is very few CPU power needed. But we even can reduce it by 50%, so it is possible to limit it to 2 copies, but then the archived files need to be stored under the user logon name or any other name ELP gets from the print processor.
For getting the archived files back, it is like copy them 2 times. Plus 0.2 seconds.
So in general if the server has less power, the only thing that can happen is that the user waits instead of one additional second maybe 2 or 3 additional seconds, but I think he needs more time to walk to the printer than that.
Based on our experience we can tell that the Windows overhead of controlling queues needs more time...
For Unix and other operating systems, you may subtract 2 to 3 copy times, if you work with STDIN and STDOUT piped commands
Conclusion: As conditions for the W-ELP server, please follow the recommendations of the operating system vendor for a server, which holds the print server role (incl. the consideration of the number queues).
The product ELP does have a lot of features. They are grouped into modules. The BAS module is obligatory for all licenses.
Any module license needs to be purchased for all needed licenses. Unless it is not a big installation, the modules can´t be splitted, e.g. 5 bar code (BAR) and 4 Forms-Management (FOR) licenses. In that case you need to purchase 9 licenses with BAS, BAR and FOR modules.
The modules BAS, BAR, FOR, EMU, UNI, PLU, UNF and SND are per licensed per output device / Queue.
The modules RAW-IN, PDF, TIF and/or DS are licensed per server, respectively per cluster node, if the code isn't used shared by the nodes.
The amount of needed licenses "Z" is calculated according those rules:
X = Amount of printing devices which will be driven by the ELP/W-ELP software.
Y = Amount of the printer queues driven by ELP for those X devices and or for the archive etc.
Z = MAX (X,Y) - note that "Z" is the higher value in the comparison of the Values X and Y
Note: If ELP serves a FollowMeTM kind of system, then you need licenses for all devices, the data stream might be printed on.
PCL5: This is our default printer language. ELP was originally designed for PCL5, therefore all features are available for this printer language.
PostScript: Bar codes are possible. The data stream can be converted to PCL for applying the full ELP functionality
TIFF: If turned on, Tiff data streams are automatically converted to PostScript.
PCL6: Only conversion to PDF is possible and banner pages.
PDF: If the function is not disabled, the data stream is automatically converted to PostScript
Kyocera Prescribe, Epson, Printronix PGL, Printronix VGL, Proprinter DS, Cobrabox, PSi bar codes and Cals:
Such data streams are converted to PCL5, and then all features can be used.
|W-ELP||Client OS: Windows Vista and above. Server OS: Windows 2008 and above (incl. Cluster- and Terminal-Server).||Enhanced features available (like e-mail support, creation of PDFs etc.)
NT and 2000 are no longer officially supported since 2011, 2003 and XP are no longer officially supported since 2016
|X-ELP||Linux, Solaris, HP-UX, AIX, True64, VMS||Other Unix platforms can be support upon request (Linux / Unix / AIX / Solaris etc )|
|B-ELP||IBM iSeries and AS/400||Not all W-ELP functions are supported|
|AP-ELP||Networked Ethernet appliance which works in a TCP/IP printing environment||Optional output methods like USB or Parallel port possible, 1 device per appliance|
|I-ELP*||Internal printer/MFP based (product is shipped on a memory flash card, existing hard disk of MFP's can be used as well)||Sold as IBS in the "Ricoh World"
Installation and configuration of ELP for Ricoh devices.
|OEM-ELP*||Depends on the 3rd party vendor||Always bundled with a 3rd party vendor application|
|S-ELP*||ANSI-C Compiler needed||Source code is supplied to the customer, various Terms and Conditions of usage are possible|
* These names are internal codenames used by stethos only
Printing from a Windows application: My print device supports PCL5 but the manufacturer does not supply a PCL5 print driver:
The differences between the devices or manufacturer is, if there is one at all, the handling of the device options. So stapling or punching commands, or sometimes with which numbers the input and output paper trays are selected.
But the good news is, that exact those commands are set by ELP using the key ELP_Command. Even in mixed environment, ELP offers methods to set the correct command for each printer model.
So if the manufactirer offers no PCL5 print driver, then select simply another one:
- Use an older PCL5 driver from the manufacturer, if available
- Use a PCL5 driver from MS Windows for the printer, if available
- or one of the drivers named in the tips below,.
Printing from Linux or another host based system (like SAP):
It is recommended to install a PCL5, 5e or 5c driver for your oldest used printer. And add also two queues named "ELP FORM B/W" and "ELP FORM color" which are used for printing the forms to file.
However there are huge differences between the drivers and the print job sizes they produce.
Data stream printing
stethos tries to do everything to support any PCL5 windows driver. In very rare cases however, searching and maybe reading values in the data stream or printing colored documents with colored forms may fail.
Hints if you have problems:
Avoid using a color driver for printing black and white only data streams to a color enabled printer, using colored ELP forms.
Using anyway ELP_Commands for forms and printer management, you are able to use any driver you like, from any manufacturer, as ELP does handle the manufacturer specific [tray] settings.
A 32Bit and a 64Bot color driver for all Windows operating systems can be downloaded from here.
Read here more about how ELP works under MS Windows.
Does W-ELP work together with Novell? I want to add here Banyan VINES as well.
Preamble: I assume, that ELP should trace data streams within a certain queue.
Answer is YES and NO!
The problem: Both network systems take the print data stream before the Windows spooler (Print Processor) which makes sense, because why to spool it twice. Unfortunately then, the data stream will never reach the ELP process.
The current solution: Do not connect the PC directly to the Novell Server, just let the Windows print queue, where ELP is installed, print to lpt1, 2 or 3. Then use the Novell capture command to reroute lpt1 to your Novell Server Queue.
A) If the ELP is installed on a client PC, then you have no problems.
B) Direct on a server is unfortunately not possible.
We may have some expertise to look even behind the curtain on a Novell server, but then we need first to know which release the client uses.
If you know a way how to call within a Novell server queue an external software, please let us know.
1st case: The DOS application runs in a DOS Box under MS Windows using a network printer:
Redirect the data stream from LPT1 to any MS Windows queue, like NET USE LPT1 \\server\Sharename
The queue can be on the same PC or any other PC/Server. Of course it needs to be an ELP supported Windows system on it (See above). Then install ELP and activate ELP in this queue. The queue itself will be connected to the printer.
2nd case: The DOS application runs in a DOS Box under MS Windows, the printer is connected via LPT1.
If the DOS application is able to print to LPT2, then set it to LPT2, redirect LPT2 using the same method as above to the queue, which prints to LPT1.
3rd case: The DOS application runs in a DOS Box under MS Windows, and it could not print to lpt2.
Add a second Centronix card to the PC and connect the printer via LPT2. Redirect as mentioned above lpt1 to the queue which is printing to lpt1.
4th case: It is a pure DOS PC, and the printer is connected to LPT1
4.1) Use ELP as a DIMM
4.2) Some software can print to a file first, and then the file could be copied copy /b ... to lpt1, or the software uses the DOS print command.
In this case, you are maybe able to generate and a batch file like this:
convert infile outfile -s.... -c.... -p...
Before answering this in detail, please note that there is a way in W-ELP to set it to the DIMM mode, meaning only the DIMM functions will work.
Once PPAdmin is set to the DIMM Mode, it enables the 2 buttons, which loads the forms and generated setup ini file(s) to the printer, like the macro loader from HP or Euroform F&FM.
In DIMM Mode the automatic downloading of Micr and OCR-A and B fonts is disabled, as if needed, fonts can be installed on the FSA Dimm
Some variables are not available in the DIMM, like in and out file names and time functions.
Please check the list of all ELP keys which keys are available in DIMM mode.
My configuration is screwed,
then you may want to reset ELP to its default after installation settings. Please follow these steps:
Maybe save your ini file before overwriting.
Exit PPAdmin Control Center if open
Please copy in the Workpath folder c:\ProgramData\WELP the file convert.ori over the convert.ini file.
You can start with a new configuration by reopening PPAdmin Control Center
When I print from Windows test pages, all is fine, but when I print from my Linux or old DOS application there are copies printed, but no forms are added.
ELP needs form feeds at the end of every page. Without them, there is no form added. There are some possibilities to add forms on a page, here are the two most common ones:
Use a counter and perform tasks based upon counter value Example 2 uses the key Search_RowNo
Use search and add on the first page, overlay a form on all pages:
[When an invoice is found]
; add a command to print form 500 on every page
Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.
Change the Printer Spooler Priority
Normally the printer spooler runs at the same priority as other services on a system. If your system is being mainly used for printing or handles a large number of print jobs you can use this tweak to change the priority class the print spooler.
Open your registry and find this directory: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
Create a new DWORD value, or modify the existing value called 'SpoolerPriority' using one of those settings :
0 = Normal priority,
1 = High priority,
0xFFFFFFFF = Idle priority
Exit your registry, you may need to restart or log out of Windows for the change to take effect.
When printing through a MS Windows driver, make sure a PCL5 driver is installed
When printing from DOS or Unix / Linux etc. make sure the data stream uses form feeds for page breaks. Where are my forms?
Need help, here is the key to success: Need help? How to get support!
then ELP will also parse Postscript for our way of printing bar codes (Having PCL bar code commands in the Postscript file and the output will be automatically in Postscript). As a side effect, the Search_xxx commands are in that configuration also all fully performed!
Solution: Remove unloved FormFeed
ELP is speed. This means there are some limitations, here for example there is no look ahead so after the last form feed the form 500 is again inserted, even there is no data anymore.
Solution us this command instead: ELP_COMMAND=C1:1-#PREPARSEPAGECOUNT#G500; and make sure that the key Preparsing=ON is set in the rule GLOBAL.
Usually this is the same problem as when selecting duplex and the job is still not duplexed. See here for this.
So try to set the page commands all on the first page, or if for example tray changes need to be performed, use them on the specific page, where the change needs to be performed. See here