Please enable JavaScript to view this site.

A-Shell Consolidated Reference

Navigation: AshLPD > Other Topics

Known Limitations

Scroll Prev Top Next More
Server is only single-threaded, and is unable to respond to requests while performing other operations. (This is not true of all operations, since some, such as the View / Reprint dialog, launch an additional instance.)
The ASHLPD.LOG file does not note whether a file was successfully printed or not.
Print requests that are queued for later on the application server (because AshLPD wasn't available) are mixed together in the ASHLPR: holding directory, even if for different printers. Then, when a successful transfer is made, the queued up files will end up being transferred using the current instance of ASHLPR.SBX, which could result in delivery to the wrong AshLPD print server if there were multiple servers and the file in question was submitted to a printer which specified a different server address.
The configuration file and printer definitions are currently edited via NOTEPAD rather than via custom dialogs.