|
ImageMAKER Release notes:
Windows 2003 Server Printer Drivers
The following release notes are common to all our Windows Server 2003 drivers. Not all of them
will apply to all driver versions.
- Release build 127 (22 June 05)
- A small memory leak (on the order of 100 bytes per print job) was found
in the port monitor. This would result in the memory used by the spooler
to slowly increase over time.
- A little-used function (file type -1, do not produce any image output at
all) was found to cause a spooler crash.
- Release build 126 (14 June 05)
- The license support code failed to detect when no image output was
desired.
- Licensing support was added to several builds.
- Release build 125 (9 June 05)
- A long-standing obscure bug in Group 4 compression would very
occasionally result in output files expanding to fill all free space
on the disk.
- Release build 124 (1 June 05)
- A change in the way forms were handled starting in release build
115 caused a problem in the display of the form size in the document
properties sheets.
- Optionally we now create a flag file (filename.flg) on completion
of the processing of the output image file. This is used by one
client who wants to keep file processing completey separate from
the spooler.
- Release build 123 (20 April 05)
- As applications have discovered new forms available by default in
Windows 2000, we have added support specifically for Rotated Letter
and Rotated A4.
- Release build 122 (9 March 05)
- Under one particular set of circumstances, the driver could decide it
had to allocate an arbitrarily large amount of memory.
- Release build 121 (21 February 05)
- Corrections were made in the handling of the DeviceCapabilities call.
- Some changes to the handling of the DEVMODE were made, notably in
reporting of supported fields and value verification, and in handling
our private DEVMODE.
- Some additional error reporting was added.
- Release build 120
- Some rationalization was done in the resources.
- Release build 119 (29 December 04)
- A test used to detect when a very short file is being printed was
implemented in the wrong direction. This would only affect files
less than about 1/2" in length.
- Some rationalization of files was performed
- A new technique for logging error messages is being implemented.
- A registry setting was added for one client to allow selection of
non-Fax pixel widths when generating monochrome images at 200DPI.
Normally the driver forces images near Fax resolution to be the
correct widths for fax machines.
- Release build 118 (6 August 04)
- A registry setting was added for one client to allow forcing 24-bit
colour output to grey-scale
- In those builds with a removable demo stamp, one demo stamp was not
being removed. This has been corrected.
- Release build 117 (22 June 04)
- A problem with TIFF JPEG output handling mixed page sizes was found
and corrected.
- Negative or over-large copy counts caused problems; we now restrict the
driver to a range of 1 to 99 copies.
- One client build had a problem handling ResetDC.
- A problem was found when the output resolution was set to 196x196 in
one particular client build.
- Release build 116 (26 May 04)
- Small changes to one build type
- Custom build for one customer
- Release build 115 (20 April 04)
- One new feature was added to one build.
- There was one particular set of circumstances which would result in an
invalid handle being used and closed. While probably benign, this was
corrected.
- A bug that would cause a major failure occasionally was found in the
additional client added at build 111. Some additional work was done to
that client build as well.
- A very old fix, for MS Word and mixed legal and letter sized pages, was
lost with Release build 111. It has been reinstated.
- A problem with multiple simultaneous conversions to 24-bit JPG-based file
types (JPEG, TIFF, PDF) was corrected.
- A small change was made to one build, and to one build technology.
- Release build 114 (10 February 04)
- A minor issue in the build tree change introduced at build 111 was
preventing normal users from printing in Windows 2000 and newer systems.
- Release build 113 (3 February 04)
- A new output file type was added. Color driver versions now include
support for TIFF compression mode 6 (JPEG within TIFF).
- Release build 112 (21 January 04)
- A long-standing bug in the FaxBatch drivers was dealt with -- when
printing in landscape mode, the printer would white-out the incorrect
area, the area corresponding to the text location before the page was
rotated into landscape.
- An issue with down-sampling from 24-bit color to monochrome output types
was found in one particular driver version. This was only a problem when
printing to a resolution > 210 dpi, in the '1/8/24 formats' PDF driver.
- Further enhancements to the new client build
- Release build 111 (27 November 03)
- It is now possible to define and use form sizes as large as 2000x2000
metres (over a mile on a side). Previously we were limited to forms no
larger than 3.25 metres (10 feet).
- A new client build caused a change in the build tree. This first check-
in of the client build is a test of the overall build stability.
- Release build 110 (01 October 03)
- A longstanding bug with mixed portrait and landscape pages in documents
was found and fixed.
- Release build 109 (1 August 03)
- Changing exact printing output resolution settings from an application's
printer settings box would cause a failure.
- The first time a driver is installed, the default resolution reported to
Windows when you first switch to Exact Printing is set to an
unrealistically low value (100x100 typically). We now default to a more
reasonable value.
- The name stored in the port monitor that specified the port monitor UI
component was incorrect for some custom builds and for FaxBatch.
- Release build 108 (16 May 03)
- Trivial changes related to the build process, plus some rationalization
of included system libraries.
- Release build 107 (24 April 2003)
- An earlier fix, Release build 104 "The right-edge unprintable area was
not getting cleared properly if error diffusion dithering was selected."
caused a problem in some cases when landscape printing was selected.
- RC2 build 106 (13 March 2003)
- At the request of one client, the drivers can now check for free disk
space before going to the next page. This is controlled by a new registry
setting: "Free Space Minimum" REG_DWORD, measured in bytes, default
125000. This is the minimum amount of space that must be present for the
printing to continue. Note that this number is multiplied by 8 if you
select an 8-bit output type, 24 for a 24-bit filetype. Setting this
registry value to 0 disables drive space checking.
- Error reporting from the JPEG library was improved. Note that this
improvement depends on an enhancement to the JPEG library. These drivers
will work with the older JPEG library, but the error code reporting will
fall back to the older behaviour unless the JPEG library is version
1.0.0.3 or later.
- One additional build type was created. This should not affect most
users of the drivers.
- A small issue in the version of the drivers that ships with the ODC
Server and Carrier-Grade Servers was corrected.
- Additional driver debug debug information is now available.
- An internal change caused a problem with page numbering in TIFF files
being generated by the printer. This has been fixed.
- Cancelling a JPEG print job, from the Printing Page x status box or
from the spooler, would result in a locked file. This has been fixed.
- RC1 build 105 (29 January 2003)
- One particular build type needed some additional work to support new
file types. This should not affect most users of these drivers.
- A user interface problem was found in the "browse for directory for
output file" code; this would result in "Unexpected error 123" when
selecting an output directory from the directory tree. This has been
fixed.
- RC1 build 104 (20 December 2002)
- One particular page size caused a problem in the landscape page rotation
code. This has been fixed.
- The right-edge unprintable area was not getting cleared properly if error
diffusion dithering was selected. This has been corrected.
- Additional changes were made to support new file types. This should not
affect most users of these drivers.
- RC1 build 103 (17 December 2002)
- The color drivers were returning an incorrect error code if they were
unable to create or open their output files.
- An internal change caused some problems with 256-color dithering.
- Additional changes were added to support new file types. This should not
affect most users of these drivers.
- RC1 build 102 (28 November 2002)
- An internal change caused some problems with 256-color dithering.
- Additional changes were added to support new file types. This should not
affect most users of these drivers.
- An internal change made it impossible to change the JPEG quality setting
in the color drivers. This has been corrected.
- RC1 build 101 (25 November 2002)
- Additional changes were made to support new file types. This should not
affect most users of these drivers.
- A potential buffer overrun was found in code that handled unprintable
areas in the driver. For certain very specific settings of resolution,
color mode, and left and right unprintable areas, this could result in a
protection-fault error.
- RC1 build 100 (14 November 2002)
- First generally available version, this has the same functionality as
Windows 2000 build 140.
|
