Changes since 2.33

-----
2.33A
-----
PCOUNTER EXE     60135 02-19-94   4:04p

Fixed job filename errors.
Fixed plain text page counting on Mac text files.
Added 30 second automatic reboot on critical/network errors.
Shows correct account balance when QAccounting=No.
Fixed an obscure PCL page counting problem.
Fixed communication w/LJ4 (without PostScript).
Improved error handling.

-----
2.33B
-----
PCOUNTER EXE     60772 03-15-94   6:20p

Fixed recognition of graphics-only PCL files which caused counting errors.
PCL counting fix for PFS.
Added remote rebooting feature (see below).
If job has unknown user, uses banner name field in PCOUNTER.LOG.
Tweaked serial port code.
Fixed critical error reboot if unknown user and no PCOUNTER.MAP.

P-REBOOT EXE      9873 03-15-94   5:40p

Usage: P-REBOOT [FileServerName/]PrintServerName
Remotely reboots a PCOUNTER server from another station.
User must be supervisor equivalent or a print server operator.

-----
2.33C
-----
PCOUNTER EXE     60788 03-21-94   9:14p

Another fix for recognition of PCL files which caused counting errors.
Another serial port fix - i/o stable now - use DTR/DSR if you have a choice.

-----
2.33D
-----
PCOUNTER EXE     60790 04-29-94   1:31p

PCL count fix for Lotus 123 WYSIWYG.

-----
2.33E
-----
PCOUNTER EXE     62237 05-23-94   9:04p

Fixed Ctrl-Break Handler.
Added manual PS counting support for Windows ADOBEPS Level 2 driver.
Fixed LJ4 spooling problem for Windows ADOBEPS Level 2 driver.
Fixed problem with not reading large PCOUNTER.MAP file.
Reduced waiting time for LPT hardware port errors.

-----
2.33F
-----
PCOUNTER EXE     62239 06-14-94   8:37p

Fixed Text->PS ignoring %* commands.
Fixed PCL counting if the job is only HPGL/2 commands.
P-REBOOT reboots only the specified Pcounter server (instead of all!).

-----
2.33G
-----
PCOUNTER EXE     62222 06-20-94   9:24p

Fixed (COMx) sending repeat character on a long handshake (pause).


Latest News:
------------
Using PS bi-directional printing on the LJ4M+ in Powersaver mode WILL result 
in a zero page count if the printer is in a power saving state and has to
warm up.

If a user edits PCOUNTER.LOG, and the editor places a lock on the file, and
PCOUNTER tries to write to it, a critical error will result and the PCOUNTER
server will reboot.  This has been observed when the user is on a Macintosh.
It is unlikely (but who knows?) that an MSDOS editor would use file locks.
In Windows, Write uses file locks, but Notepad does not.  Anyway, a version
of GREP has been uploaded to the ftp site, and it is useful for getting
individual users' print activity information from the PCOUNTER.LOG file.
