READ.ME for the latest Print code:
 
Description:
------------
 
This package provides replacement files for LPD.EXE, LPQ.EXE,
LPR.EXE, LPRM.EXE, LPRMON.EXE, LPRPORTD.EXE, PDRVR.PDR,
and LPR32.DLL.  To date, these are the only files in the PRINT
component that have had apar fixes made to them in OS/2 Warp
v3.0 TCP/IP.
 
Installation instructions:
--------------------------
 
You must have the following installed on your system:
  - OS/2 version 3.0 with TCP/IP v3.0 

TCP/IP Stack Apar IC14052 is a prerequisite for this print code.   

You should put the LPRFILES.EXE file in a temporary subdirectory
and enter:
 
  LPRFILES
  
LPRFILES.EXE file contents:
--------------------------
 
READ.ME 
LPD.EXE         39366   4-23-97   8:24a  
LPQ.EXE         27248   8-07-97   2:01p      
LPR.EXE         44784   8-07-97   2:00p
LPRM.EXE        27840   8-07-97   2:02p
LPRMON.EXE      35009   8-05-97   1:04p 
LPRPORTD.EXE    65946   4-16-97   7:15a
LPRPDRVR.PDR    52241   3-21-97   7:08a 
LPR32.DLL       63694   8-05-97  12:58p 

TNLS16.DLL      47104   4-09-97   7:51a
 
You should back up the current versions of these files on your 
system.  Then replace the *.EXE files in the TCPIP\BIN directory, 
and the LPRPDRVR.PDR, LPR32.DLL, and TNLS16.DLL files
in the TCP\DLL directory. Then SHUTDOWN and REBOOT the
system to make these executables and the corresponding dlls active.

 
Apars included in this group of fixes with a brief description:
(executables and/or dlls fixed)   
--------------------------------------------------

IC13719 - After applying CSD u200067 for warp connect, the LPRMON
          exe does not recognize the set (lpr_server and lpr_printer)
          environment variables. This is because the DHCP support added
          in the module getopts.c only looked at the tcpos2.ini file for 
          the lpr_server and lpr_printer fields and failed to check the
          environment variables.(lprmon.exe)

IC15168 - Module LCLLPR.C in the LPR component does not return a nonzero  
          return code for an error on a DOSOPEN (filename). LPR      
          returns with a zero return code on a failure case.
          (lpr.exe)

IC15573 - When starting LPRPORTD from the command line on a pristine      
          installed system, the error message  "LPR 32.DLL failed to      
          initialize, RC=-20021" is displayed. (lpd.exe, lpq.exe,
          lpr.exe, lprm.exe, lprmon.exe, lprportd.exe, lpr32.dll)

IC15752 - When a customer opens the printer object and then opens the
          PIPE/LPD port settings, the PMSHELL grabs the port driver
          making it impossible for another process to print thereby
          locking the print jobs.  If you do try to print, the spooler
          will either trap or hang the print job. (lprpdrvr.pdr)

IC15763 - The LPRPORTD.EXE process can trap when two jobs are 
          printing at the same time in two different printer queues each 
          configured to output to a different \PIPE\LPDx pipe. It will   
          not trap every print job, but it will trap. In our tests, it  
          traps within 10 minutes of IPL with a nominal load. 
          (lpr32.dll)

IC16508 - SYS3175 with access violation in SETLOC1.DLL when 
          LPRPORTD tries to access a printer that is turned off or 
          unavailable.(lpr32.dll)

IC16807 - When customer attempts to send a very large print job to 
          the server using LPR on the client, the lpd window 
          will fail with a SYS3175 error. The register contents 
          show TNLS16.DLL as the failing module. They are able 
          to LPR small print jobs, but when the jobs get very large, 
          such as 100MB, they get this failure every time. (lpd.exe,
          tnls16.dll)

IC17041 - Provides DHCP (Dynamic Host Configuration Protocol) support
          for the LPR print function. Also, NLS translation problems    
          were fixed that prevented translated messages from being 
          displayed. ( lpd.exe, lpq.exe, lpr.exe, lprm.exe, lprmon.exe,
          lprportd.exe, lpr32.dll, lprpdrvr.pdr)

IC17322 - Printing of files using LPRPORTD.EXE takes excessive
          amounts of time. A 300K file takes between 5.0 to 6.5 
          minutes to print. This is due to the fact that writes 
          to the named pipe are occurring in 1K blocks and at 1.0
          sec cycle increments. (lprportd.exe)

IC17589 - Customer has 14 printers and 14 print queues on print
          server. Customer is limited to accessing only ports   
          (721 - 731) at one time. The customer sees a 3 minute 
          delay on the additional 4 queues after the print jobs
          are complete on the first 10 queues. (lpr32.dll)

IC18394 - Incorrect messages received for lprportd, lpr,lpq,     
          lprm and lprmon commands. This happens on translated  
          messages.