Welcome to ImageMAKERHome Product Information Component Info White Papers Specifications Technical Support Demo Download About ImageMAKER

The Leader in TIFF Imaging Solutions






ImageMAKER Release notes: Windows NT4 Printer Drivers

The following release notes are common to all our Windows NT4 drivers. Not all of them will apply to all driver versions.

  • Release build 250 (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 249 (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.
    • A change in the way forms were handled starting in release build 245 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.
    • Under one particular set of circumstances, the driver could decide it had to allocate an arbitrarily large amount of memory.
    • 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 248 (31 December 04)
    • Some rationalization to resources was carried out.
  • Release build 247 (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 246 (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 245 (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.
    • Custom build for one customer
    • 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 242. 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 242. 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 244 (10 February 04)
    • A minor issue in the build tree change introduced at build 242 was preventing normal users from printing in Windows 2000 and newer systems. The fix was migrated back to NT4 because it will affect clients who have more restrictive printer security settings than the default.
  • Release build 243 (03 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 242 (30 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.
    • 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 241 (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.
  • Release build 240 (16 July 03)
    • Brought up to current standards. This includes some rationalization of the build tree, plus a small correction to one file type.
  • Release build 239 (24 April 03)
    • An earlier fix, Release build 233 "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.
  • Release build 238 (13 March 03)
    • 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.
  • Release build 237 (26 February 03)
    • 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.
    • Somehow a change made a year ago (in build 225) got backed out. It has been re-instated.
  • Release build 236 (4 February 03)
    • One particular build type needed some additional work to support new file types. This should not affect most users of these drivers.
  • Release build 235 (29 January 03)
    • 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.
  • Release build 234 (2 January 03)
    • A timing problem in the FaxBatch driver was resolved. This would only affect printing to file; embedded text strings would get lost on certain combinations of machine speed and hardware.
  • Release build 233 (20 December 02)
    • 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.
  • Release build 232 (17 December 02)
    • The color drivers were returning an incorrect error code if they were unable to create or open their output files.
  • Release build 231 (4 December 02)
    • Additional changes were made to support new file types. This should not affect most users of these drivers.
    • An internal change caused some difficulty with 256-color dither modes.
    • An internal change caused the JPEG quality slider to be disabled.
  • Release build 230 (25 November 02)
    • 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 blue-screen error.
  • Release build 229 (6 November 02)
    • The NT4 driver has been brought up to parity with the Windows 2000 driver version 140. Changes include:
      • The ActivePDF driver does strange things to the registry in order to copy-protect itself. As a result, installation of earlier ImageMAKER drivers will fail after ActivePDF has been installed, even if it is later removed. We now set registry security descriptors to prevent this problem. Note: This requires installer DLL version 1.2.24.0 or later.
      • A number of internal changes were made to support additional output file types. The file types are still in beta and so are not yet in the release drivers, but changes to support them are now fully tested.
      • An advanced feature was added that would allow turning off concatenation of Excel worksheets (Release build 219 and later).
      • A check was made on loading user profile (implemented in build 225) so that we no longer attempt to load a user profile for jobs created in the LocalSystem account.
      • An oversight in the compile switches resulted in one driver version failing to work properly.
      • An uninitialized variable resulted in there being too few grey values in 256-color modes.
      • Additional settings have been exposed on an Advanced section of the Device Settings tab of the device properties.
  • Release build 228 (26 July 02)
    • A problem in handling custom form sizes was corrected.
    • Some irregularities in setting the copy field in the DEVMODE were corrected.
    • The control dialog would not launch if the directory specified for the TIFF file to be output did not exist. This is because the output directory was used as the control dialog's working directory.
  • Release build 227 (22 May 02)
    • One particular build needed a custom string in order to not conflict with our standard drivers. There should be no change to most drivers.
  • Release build 226 (9 April 02)
    • Small client-specific changes for one client. No other effects should be noticeable.
  • Release build 225 (3 April 02)
    • When launching the control dialog in a specific user security context, we had not been setting the users' profile or loading the users' environment block correctly. Code to do this has been implemented and is available in this version for testing.
    • Changes for one client's custom file type were implemented.
    • A long-standing problem with some lesser-used options was found and fixed.
    • An internal optimization would occasionally result in black junk appearing on the right edge of TIFF images. The optimization was rationalized.
  • Release build 224 (23 Jan 02)
    • The port monitor was not able to create a DevMode on installation (install was failing).
    • The print driver was returning an error code at a time when there was no error (user cancelled). Correcting this error caused the special handling for Excel spreadsheets to break.
    • The height of a landscaped page was being calculated incorrectly when journalling was active.
    • The limited FaxBatch version was double-incrementing page numbers.
  • Release build 223 (11 Jan 02)
    • A new version of the driver with limited FaxBatch capabilities that supports journalling (for extremely large pages) has been created.
    • A problem with the exact printing and journalling combination was found that would result in generated pages being totally scrambled. This turned out to be the result of a rounding error in the exact printing handling.
    • The driver would not correctly generate a landscape-mode page if Exact Printing was enabled.
    • A problem was found when printing large pages at high resolution (greater than 16,000 pixels total width, e.g. A-size sheet at 600 DPI).
  • Release build 222 (31 Oct 01)
    • A long-standing error in our color TIFF Packbits (RLE) implementation has been corrected. This will affect color drivers only.
  • Release build 221 (24 Oct 01)
    • A further expansion of the fix to handle Excel workbooks (Release build 219) now allows this to work when printer pooling is enabled.
    • Exact printing and journalling can now be provided in the same driver, though journalling (see Release build 218) is disabled if exact printing (Release build 206) is enabled.
  • Release build 220 (11 Oct 01)
    • A long-standing problem with generating file names when the driver is set to generate a single page per file was found. This would affect file names containing five or more digits. It has been fixed.
  • Release build 219 (5 October 01)
    • Microsoft Excel generates multiple print jobs when printing a single workbook because it stores a DEVMODE with each worksheet; when it finds a new DEVMODE while processing a workbook, it closes the job and opens a new one (instead of using the ResetDC system API). Code to re-combine jobs produced this way while they are being printed has been added to the driver and can be enabled on a per-customer basis.
  • Release build 218 (23 August 01)
    • The first release of our driver that fully supports "journalling" or "banding" in color modes, this driver should be immune to the occasional "Error 0 - Cancelled from spooler" and should be able to handle any form size up to the Windows DEVMODE limit of 3276.7mm / 3-1/4 meters
  • Release build 217 (10 August 01)
    • A longstanding imperfection in handling the right edge of documents printed at 200x200 DPI was finally tracked down and nailed to the wall.
  • Release build 216 (24 July 01)
    • A new registry value has been added that forces the reported resolution in the output TIFF file to square (200x200 or 200x100). Normally the reported resolution is 204x196 or 204x98, because that is what FAX modems expect, but one customer requested this change for their document storage application.
    • Aborting a print job should be much quicker.
  • Release build 215 (25 May 01)
    • It is now possible to set custom values for resolution and unprintable areas in the install process, which are associated with the "custom" printer, and which are sticky.
  • Release build 214 (15 May 01)
    • The addition of 600 dpi resolution to the NearFAX Square Pixel emulation exposed a flaw in the handling of an internal structure. This flaw has been corrected.
    • Near-FAX Square Pixel printer emulation now includes 600x600 DPI resolution.
  • Release build 213 (7 May 01)
    • A small change was made to the UI of combined color / monochrome printers so that the file type choices updated correctly when the printer mode was changed.
    • An error that could cause failed print jobs when multiple printers were defined and simultaneously in use was corrected.
  • Release build 212 (10 April 01)
    • There was one way of setting the new Exact Print options that would cause a blue-screen in NT. This has been fixed: if you select a target resolution finer than the current source resolution, exact printing will be silently turned off by the driver for that one print job.
  • Release build 211 (21 March 01)
    • It was found that a 16-bit MFC application printing to the default DevMode of a non-default printer would result in an incorrect DevMode being associated with the job passed in to the port monitor. We now detect this problem and use the printer's own default DevMode in this case.
  • Release build 210 (31 January 01)
    • Small changes to resource ID numbers in the port monitor were made in the process of setting up the external resource library. No functional change is expected from this set of deltas.
  • Release build 209 (24 January 01)
    • Trivial changes internally; should have no effect on driver operation.
  • Release build 208 (4 January 01)
    • Change to resolutions captured from emulated printer to eliminate a nuisance resolution selection
  • Release build 207 (2 January 01)
    • Change to printer emulation mechanism: now retrieves entire table of available resolutions for a printer when Emulation selected.
  • Release build 206 (21 December 00)
    • Fine-tuning of WYPIWYF for first release:
      • Corrected handling of interaction between gray-scale depth and dither mode
      • Changed UI handling of printer emulation, unprintable areas
      • Updated help file
      • Corrected some bugs
    • Added 196x196 square pixel resolution. This is used for those plain-paper fax machines that choke on pages longer than 2156 (Letter), 2287 (A4), or 2744 (legal) pixels. At least one machine refuses to print faxes rendered at 200 DPI.
    • Version number now available in modules other than UI
  • Release build 205 (30 November 00)
    • One-bit dither / resolution change handling was added to the driver. This will remove the last limitation on exact printing: fast NT dither is now supported when exact printing is enabled. NOTE that exact printing is still beta, albeit late beta.)
    • A problem that would cause install to fail for one customer was found and repaired.
  • Release build 204 (14 July 00)
    • Up until this version, while What You Print Is What You Fax was supported in both portrait and landscape, the associated unprintable areas were only supported in portrait mode.
    • Printer Emulation was modified to read whether the printer selected is set to default to landscape or portrait mode, set the ImageMaker printer the same way, and now sets unprintable areas correctly in the case where the source printer is set to landscape mode.
  • Release build 203 (6 July 00)
    • The blue-screen error fixed in build 202 reappeared and was re-fixed. It would appear when Error Diffusion dithering from 8-bit color was selected with Exact Printing enabled.
  • Release build 202 (29 June 00)
    • A problem with page sizes in landscape mode was created by an optimization at build 196. This has been corrected. This correction also corrected some other outstanding issues with landscape printing, most notably printing from PowerPoint to low-resolution.
    • A change at build 201 added to assist support of What You Print Is What You Fax caused a blue-screen error in a small number of cases. It has been fixed.
    • The UI has been modified to prevent one particular illegal combination of settings for the What You Print Is What You Fax driver versions.
  • Release build 201 (22 June 00)
    • Some internal structures and routines were modified as part of the process of making What You Print Is What You Fax ready for prime time.
    • Additional dither patterns (classical 45-degree screens), and the ability to make the existing dither patterns skewed rather than rectangular, were added to the dithering library and to the driver.
    • A problem with 200x200 resolution was created as part of the What You Print Is What You Fax code, about build 195. This would have created problems in all driver variants. It has been fixed.
    • A problem with page sizes reported by the driver when changing from C-size to D-size sheets and back, or between any two page sizes that share a common dimension (e.g. A-size or letter 8.5"x11" and B-size 11"x17"), was reported and fixed.
  • Release build 200 (2 June 00)
    • An optimization installed with the What You Print Is What You Fax code caused the color drivers to fail to load, causing an NT blue-screen. This has been corrected.
  • Release build 199 (29 May 00)
    • A change in resource ID broke the browse button used to select an output folder.
  • Release build 198 (28 Apr 00)
    • Starting, we believe, with SP4 of NT4, the "Run in separate memory space: Disabled" setting triggers an Illegal Parameter error (log entry: "Spawn from faxmon.dll failed for app: xxx (87)") if you are attempting to launch a 16-bit application in the User security context (which requires a separate memory space). We have changed the UI to prevent this situation from being created by the user, and modified the driver so that selecting "Run in separate memory space: Disabled" silently forces System security context.
    • Further work on the What You Print Is What You Fax code was carried out to lock out a particular device setting that was not yet completed. Additionally an Emulate Printer option was created to automatically set document properties to match another existing printer. Note that this code is still beta and so is enabled only on request; note also that the user interface for this function is not yet in its final state.
  • Release build 197 (11 Apr 00)
    • Further work on the What You Print Is What You Fax code was carried out to add UI support for control of unprintable areas and to resolve one outstanding bug in this area. Note that this code is still beta and so is enabled only on request.
  • Release build 196 (4 Apr 00)
    • Further work on the What You Print Is What You Fax code was carried out to allow control of unprintable areas. UI to support this is still pending. Note that this code is still beta and so is enabled only on request.
  • Release build 195 (22 Mar 00)
    • Further work on the What You Print Is What You Fax code was carried out to alleviate memory cramp problems at 600x600 DPI (24-bit color, a standard letter-size page occupies 90+MB). An additional UI entry was created to allow selection of the source image depth. Note that this code is still beta and so is enabled only on request.
  • Release build 194 (13 Mar 00)
    • High-resolution versions of the driver now include 600dpi resolution
    • Beta-test level support is available for What You Print Is What You Fax, on request from individual customers.
  • Release build 193 (3 Jan 00)
    • A problem was reported when running the driver on systems with dual Pentium Pro CPUs.
  • Release build 192 (21 Oct 99)
    • The printer now correctly reports that it can handle color. Note that this applies both to our monochrome and color printer drivers; when a dither mode is selected in which the printer is expected to do the dithering ("Dither from 256 colors", for instance) it should report color to any application that is trying to print to it.
    • Error diffusion dithering and noise mask dithering have been added. Note that neither error diffusion nor "blue-noise" dithering is particularly good for fax transmission; they produce better-looking images at the expense of image size. Noise mask dithering is a first pass only.
  • Release build 191 (10 Sep 99)
    • A registry value "NumberOfEols" (REG_DWORD) has been added to control how end-of-page is marked in G3 TIFF files. For instructions on using this feature please see the Readme file, the Registry Keys section.
  • Release build 190 (10 Sep 99)
    • A registry value "Overwrite" (REG_DWORD) has been added to control how TIFF files are generated. For instructions on using this feature please see the Readme file, the Registry Keys section.
  • Release build 189 (8 Sep 99)
    • Excel's habit of caching inappropriate DEVMODEs caused a problem when trying to print a worksheet that had been generated on a different computer using a form that was not defined on the printing computer. This problem has been resolved.
  • Release build 188 (1 Sep 99)
    • The change at 186 did not properly handle numbering files if a long file name was specified and multiple pages per file was disabled.
  • Release build 187 (27 Aug 99)
    • In response to a user request, it is now possible to include a registry setting that will prevent the ImageMaker drivers from rotating the image if it is generated in landscape mode. No user interface for this feature has been provided as we felt it was dangerous to allow end users to potentially change settings to make FAXes that looked like they should be valid but which would choke any fax modem. For instructions on using this feature please see the Readme file, the Registry Keys section.
  • Release build 186 (23 Aug 99)
    • The limit of four characters for the default output prefix was removed.
  • Release build 185 (28 Jul 99)
    • Further custom modifications were carried out for one client.
  • Release build 184 (26 Jul 99)
    • Moderately extensive customization was done for one client; three other custom builds were added. This should have no effect on most users.
    • The limit on pages in the DCX file format was raised from 250 to 2000.
    • The driver now sends the name of the pipe up to the control dialog. If your control dialog accepts "-n" on the command line, you will be passed a unique pipe name which will guarantee that the instance of the print driver to which you are attached is the same as the one which generated your command line. The old form of the command line may also be used; the print driver creates and publishes both the unique and the original pipe names.
  • Release build 183 (13 Jul 99)
    • A long-standing bug in DCX-format output was found and fixed.
    • The optimization of the color BMP output routines at build 180 was found to cause a spooler crash under certain circumstances. It has been fixed.
    • CSID generation was found to not work and to cause a spooler crash in the 24-bit color driver. It has been temporarily disabled in the color driver only while we debug this problem. Some resource leaks in the CSID generation code were also corrected.
  • Release build 182 (24 Jun 99)
    • A problem in the BMP output routines, introduced in 180, was found and corrected.
    • The file name passed to the control dialog for output is now enclosed in quotes. This will eliminate any problems with spaces in output file paths, but may require small changes in your control dialog.
  • Release build 181 (18 Jun 99)
    • A problem was found in the case where an older program was hardwired to an old-format DEVMODE; specifically AmiPro would hand us a V3.10 DEVMODE which we would try to interpret as a V4.01 DEVMODE. This has been corrected.
  • Release build 180 (8 Jun 99)
    • The color driver BMP output routines were optimized; we are seeing an approximate 10-fold increase in speed for BMP file output.
  • Release build 179 (21 May 99)
    • The problem repaired at build 178 also caused the color driver to fail to install. This problem has been resolved.
    • Support for 24-bit BMP files has been added to the color print driver. Note that this support is an initial version only; it is extremely slow and resource-intensive. The next revision of the drivers will have a more efficient algorithm.
  • Release build 178 (12 May 99)
    • Internal changes were made to increase commonality of source code. No operational effect should occur as a result of these changes.
    • A problem was introduced at release 175 that would prevent changing settings on the Device Settings page. This release resolves that issue.
  • Release build 177 (16 Apr 99)
    • Internal changes were made to increase commonality of source code. No operational effect should occur.
  • Release build 176 (19 Mar 99)
    • The driver will now support stamping print images with a CSID for FAX related applications without a server. This does not cause any change in the UI; the CSID is set at install time using the new INS_PRINTER3 structure. By default the CSID is disabled.
  • Release build 175 (18 Mar 99)
    • Code changes were made to support common code with the new 24-bit color drivers in NT4. This has resulted in some rationalization (read: change) of the user interface pages.
  • Release build 174 (18 Jan 99)
    • (FaxBatch only) Whited-out text had the co-ordinates in the wrong order if the page was being printed in landscape mode. This would result in a vertical rectangle in the incorrect location being whited out.
    • A new licensing information tab has been added to the printer properties.
  • Release build 173 (9 Nov 98)
    • A conflict was found between the technique we use to communicate with the daemon, and the technique used by RightFax. We have changed our driver to only look for a daemon if a specific value is set in the registry, and have changed the installer to clear that value; if you need the daemon installed, you will need to modify your installer to match ours.
    • A problem was discovered having to do with file names returned from the control dialog communication handler when the control dialog timed out.
  • Release build 172 (21 Oct 98)
    • Some applications force an invalid resolution into a DEVMODE and ask the print driver to match it. In these cases, we would return (e.g.) fine FAX resolution, that being the driver's default resolution. The driver now goes to the default DEVMODE in the registry to resolve an invalid resolution; the result is that we will get the resolution set in the printers folder instead of the driver's default resolution.
  • Release build 171 (20 Oct 98)
    • A new build which supports color has been added. At this point, color support is beta only, 24-bit TIFF packbits. GIF and JPEG support will be added in a later release if demand appears.
    • Internally, modules were reorganized within the port monitor to break up one monolithic module into functional blocks.
  • Release build 170 (8 October 98)
    • A new custom build was added for one client
    • A problem with setting the default DevMode appeared in build 168. It has been fixed.
    • The intensity value 0 was not valid, as it would produce the same output as intensity value 50. The slider has been changed to allow values only between 1 and 100.
  • Release build 169 (5 October 98)
    • One oversight was found in the common code for Windows Terminal Server which would cause a GPF on install.
    • Some small changes to the build process were made to eliminate warnings that appeared while building on Alpha machines.
  • Release build 168 (28 September 1998)
    • A new version of the DLL set supporting Windows NT Terminal Server Edition was created. Internally, in order to create this new DLL, the build tree was reorganized.
    • The TIFF file output was altered: the G3 options tag is now provided only for Group 3 (T.4) compressed files, the G4 options tag is provided only for Group 4 (T.6) compressed files.
  • Release build 167 (6 September 1998)
    • Code to support a variable left margin was implemented for one client. A new registry value was added to support this.
    • Code and a registry value to support a new custom TIFF file format were added for one client.
    • The name of the FaxBatch DLL was added to the user interface for the FaxBatch driver. This required renaming the FaxBatch driver and changing the installer in one location.
    • New registry values were added to support the FaxBatch library name and the timeout between successive mfx_Xxx calls -- previously, both were hard-coded, the former to IMG32MM.DLL, the latter to 300 seconds.
  • Release build 166 (28 August 1998)
    • A small problem with page numbering in the FaxBatch driver was found and resolved.
    • A workaround for a problem in Notepad and WordPad (MS Knowledge Base Q152380) was installed.
  • Release build 165 (11 August 1998)
    • The fix installed at 163 did not quite work and had a hard-to-find side effect: attempting to change the driver settings by editing the registry would not take effect until the system was rebooted.
    • A custom build was created for one client.
  • Release build 164 (6 August 1998)
    • The documented technique for retaining the existing file name in the function mm_NewFileName(), returning the current file name to the caller, would result in a multi-page file with all pages marked "page 1 of 1". This would result in problems with some FAX boards. This change affects FaxBatch drivers only.
  • Release build 163 (4 August 1998)
    • A longstanding bug which prevented changes entered from the File | Print Properties pages in MS Word from being retained was fixed.
  • Release build 162 (4 July 1998)
    • One client reported a problem with the way his control dialog was being spawned. This has been corrected.
  • Release build 161 (26 June 1998)
    • While testing the latest version of the installer, it was discovered that the port monitor was filling in two strings in the PORT_INFO_2 structure incorrectly (the pMonitorName and pDescription fields were switched).
  • Release build 160 (16 June 1998)
    • It was discovered that the sense of the separate VDM switch was reversed: while Default was default, Disabled selected a separate VDM and Enabled selected a common VDM.
  • Release build 159 (02 June 1998)
    • A situation was found in which the FaxBatch version of the driver could hang or crash the spooler when print volumes were very high.
  • Release build 158 (22 April 1998)
    • Some constant names were changed internally to simplify the build process
    • Some applications that did what might be called "minimalist printing" would fail under NT4, because certain fields in the spooler structures would not be set at print time. These conditions have been trapped.
    • New custom builds were created for individual clients
    • Over-aggressive detection of empty print jobs was toned down
  • Release build 157 (3 March 1998)
    • A trivial change for one client. Since it could possibly impact all clients, I have assigned it a new version number.
  • Release build 156 (25 February 1998)
    • A trivial change for one client. Since it could possibly impact all clients who use group 4 fax compression, I have assigned it a new version number.
  • Release build 155 (23 February 1998)
    • On some machines, the change at build 150 which allowed deletion of a stalled print job from the Printers folder would cause print jobs to be deleted before they were completely printed. This has been cured.
    • The change at build 154 that corrected the copy count report caused problems with some applications that actually paid attention to the copy flag returned; this would result in no output being generated and in errors 109 and 232 being reported by the control dialog.
    • Some applications that did what might be called "minimalist printing" would fail under NT4, because certain fields in the spooler structures would not be set at print time. These conditions have been trapped.
  • Release build 154 (13 February 1998)
    • The change at build 153 did not actually cure the problem noted in all cases; in some cases it actually made it worse, so it was backed out.
    • The driver was modified to support spawning control dialogs with embedded spaces in their names
    • Due to problems in Microsoft's documentation, it was not clear how to specify that a printer did not support multiple copies. This was resolved only through experimentation; we now report correctly that we do not support multiple copies.
  • Release build 153 (4 February 1998)
    • A trivial change in the drivers' reported capabilities resulted in TrueType fonts being printed incorrectly from some applications.
  • Release build 152 (3 February 1998)
    • A problem was reported with printing very short pages (<2 inches at low resolution). This has been fixed; however, there is still a limit on the smallest allowable page. Pages smaller than 1.6 inches will not print in Normal resolution; pages smaller than 0.8 inches will not print in Fine or 200DPI resolutions.
  • Release build 151 (29 January 1998)
    • The help file has been updated to reflect the latest UI changes. It has also been broken into two sections: a standard, hyperlinked Help file with a table of contents that can be accessed from the standard Help engine (HELP_SINDEX_xxx), and a set of pop-up topics presented by the print driver UI component (HELP_INDEX_xxx).
    • A problem with pressing the Cancel button on the control dialog's running page count dialog has been fixed.
  • Release build 150 (22 January 1998)
    • Cancelling a print job from the Printers folder now works correctly.
    • Moderately involved changes were made for one customer that involved the UI, driver, and port monitor. This should not affect most customers.
    • The changes at release 146 evidently changed the driver so that it was no longer seeing the default settings when it was creating a default DEVMODE. This has been corrected.
    • Attempting to change the name of the control dialog in the printer properties device settings page would cause an infinite loop and a crash of Explorer. This has been fixed.
    • An obscure problem relating to named pipe state on open was cured. In some circumstances, the initial call to mfx_GetDocInfo() would return -1 due to data not being available instantly upon pipe open. Once this had happened, all communication up and down the pipe would be invalid, because the two ends of the pipe would be out of sync.
  • Release build 149 (16 January 1998)
    • Part of the UI component was rebuilt using TCHARs instead of WCHARs to keep code common with a component in the Win95 driver
    • A new conditional compile directive was added to allow building drivers that only support 200x200 DPI for use with earlier versions of MS Office 97.
  • Release build 148 (14 January 1998)
    • A trivial change in the resource strings was made for the new installer DLL.
    • A section was added to this readme file concerning the use of a server ID and password for use with a server share.
  • Release build 147 (19 November 1997)
    • Two small problems with the FaxBatch version of the driver were found and fixed: the page number returned to the mm_StartPage and mm_EndPage entry points was wrong, and the row and column number returned to the mm_ParseText entry point were reversed.
  • Release build 146
    • The UI has been modified so that unavailable fields are grayed out.
    • We have added a field to the UI under the Control Dialog option that allows you to specify that the control dialog is to be spawned in a separate VDM. This is recommended if you are using a 16 bit control dialog and have an application that may require Print Direct to Printer. See the Print Direct to Printer section below. Please also see the Separate VDM section, below.
    • We have added Fast Dither to our list of dithering options. See the section on Dithering, below.
    • The installer has been modified to include default settings for the separate VDM flag and the fast dither options.
    • A help file is now included in the drop as a compiled .HLP file and as the source RTF, HM, and project files. Note that compiling this help file requires Help Workshop 4.02; the help RTF file was written using Office 97.
  • Release build 145
    • Additional projects were added to the makefile. No effect on end users is expected.
  • Release build 144
    • A change was made to the form determination technique to hide a bug in Office 97. See "Form Selection" below.
    • It was drawn to our attention that the Win95 version of FaxBatch was subtly different from the NT version of FaxBatch. New functionality has been added to the FaxBatch versions of the driver to give the Win95 functionality to the NT4 driver. See the latest version of the MMDLL sample (function mm_ParseText) for details.
  • Release build 143
    • A correction was made to one user-specific file format.
  • Release build 142 (8 September 1997)
    • An optimization caused the blue-screen problem fixed in release build 122 to re-surface. This has been re-fixed.
  • Release Build 141
    • A small change has been made to deal with programs (notably PageMaker) that pass the name of the output port as the name of the destination. We had been interpreting these as output file names; they are now interpreted as the port names. Note that this will have some effect on the behaviour of the -d switch passed to the control dialog; in these cases, the -d switch will be followed by the name of the output port.
  • Release Build 140 (20 August 1997)
    • A3 and B4 paper sizes were adjusted to bring them in line with Japanese FAX standards: A3 is 2432 pixels, B4 [JIS] is 2048.
  • Release Build 139 (25 July 1997)
    • Support for larger paper sizes (A3, B4 [JIS]) was added. The driver now correctly handles B4 (2022 pixels across) and A3 (2338 pixels). If you specify a FAX resolution (204x196, 204x98, or 200x200), paper 8.5 inches and below is forced to 1728 pixels; A3 (and other 297mm +- 10mm width) and B4 (and other 257mm +- 10mm width) page sizes are forced to appropriate pixel counts for those standards; and all other paper sizes and resolutions (if enabled) have pixel sizes calculated from their actual width. NOTE: This does mean that page sizes other than those listed WILL NO LONGER TRANSMIT SUCCESSFULLY.
  • Release Build 138 (18 July 1997)
    • A small memory leak was discovered. This leak would result in the loss of one handle and about 2kb of kernel memory per document printed.
    • A larger memory leak, amounting to 10,000 bytes per document, was also found and corrected.
    • A number of changes to the palette handling were made in an attempt to make printing from Office 97 less problematic.
  • Release build 137 (17 July 1997)
    • A timing problem surfaced on fast machines under Acrobat Reader. This would occasionally result in the TIFF tags for the last page of the printout not being updated, which would make the last page appear to be a copy of the first page.
  • Release build 136
    • Some small changes to the dithering code were made. Note that this does not fix difficulties with pictures imported into Office 97 documents; these documents may still appear washed out on printing.
  • Release build 135 (3 July 1997)
    • Programs that use the DMRES_xxx constants were not being properly handled by our driver. (Excel for Office 97 does this; this is the first program we have found that does.) This has been corrected.
  • Release build 134 (26 June 1997)
    • Complete FaxBatch functionality is now provided in the printer driver.
  • Release build 133 (20 June 1997)
    • One small oversight in the creation of the 200x200 bit pad code caused creation of small black artifacts on the screen if you specified Dither from 256 Colors.
  • Release build 132 (19 June 1997)
    • Yet another fix for the 200x200 dpi code; fix 131 broke the code that was padding the output to 1728 pixels.
  • Release build 131 (17 June 1997)
    • A problem was found with the multi-threading which would result in strange dither patterns appearing if multiple users try to print using Dither From 256 Colors at the same time.
    • Aspect ratios for pixels were being calculated incorrectly for landscape mode. This would particularly affect low-resolution printing in landscape mode.
    • An error in the 200x200 dpi code was resulting in occasional blue-screen errors while printing.
    • Errors in the dithering code and in the BMP-format file dump routines were exposed by the change to 200x200 dpi.
  • Release build 130 (13 June 1997)
    • Microsoft Office 97, as released, does not support pixels that are not square. As we report true Fax resolution (204x196), Office 97 will not fill in tables correctly. As a workaround, we have provided a true 200x200 resolution in this version of the driver; the output, if this resolution is set, will be subtly distorted (pages will be 2% longer, and the printed area will be 2% narrower), but the tables will be correctly filled in.
  • Release build 129 (13 June 1997)
    • Additional FaxBatch functionality has been added to the printer. Text strings are now passed to the FaxBatch library for processing. We do not yet support blanking out a string. NOTE that printing to file will no longer produce a valid (if inverted) Windows BMP file; the text strings will be embedded in the image.
  • Release build 128 (6 June 1997)
    • Custom work for one client required addition of a new file type to the FAXAPI library
    • Co-incident with this work, the last separate version of the ImageMaker FAXAPI library was merged into the main stream. As a result, starting with this build, it is possible now to define multiple output ports and have the printer driver handle output to all ports at once. For server applications, this alleviates one bottleneck in the drivers; previously, a 2-page job would have to wait until a 100-page job cleared the queue before it could begin printing.
    • To support this, a new version of the installer is provided that can create and install multiple printer ports.
  • Release build 127 (4 June 1997)
    • One client's custom version, and the demo version, were not allowing printing in standard FAX mode.
  • Release build 126 (23 May 1997)
    • The changes in release 124 were discovered to be not quite adequate to the task they had been set; the code was reworked to completely eliminate that particular timeout.
  • Release build 125 (21 May 1997)
    • We now include an INF file as a backup installation method, for those rare cases that INSTFAX4 doesn't work. To get the port monitor INF file to work, some small changes had to be made to the driver.
  • Release build 124 (21 May 1997)
    • Particularly complex images, ones that took longer than 30 seconds to realize, would hang in the printer queue if there was no control dialog specified. Typically this would only be a problem on slower machines or machines with limited memory.
  • Release build 123 (28 April 1997)
    • The code that was retrieving the output file path name from the registry somehow got removed from the port monitor. It has been restored.
  • Release build 122
    • A flaw was discovered in the dithering code such that selecting Dither From 256 Colors and setting the intensity slider to 1 would result in an NT blue-screen error.
  • Release build 121 (22 April 1997)
    • An option has been added to allow control of whether the control dialog is spawned in system or user security context. We have found that often 16-bit control dialogs work better if they are spawned in the system security context; they then run in the default 16-bit WOW process rather than in a separate VDM.
    • An option has been added to allow specification of a user name and password to access a share on a server for loading the control dialog. Note that the password is not particularly well encoded.
    • Several problems with the user interface component have been corrected, specifically involving contention between the Document Defaults and Printer Properties pages.
    • The debug logging functions have been re-enabled for the port monitor and the fax UI components. NOTE that changing debug status does not take effect instantly; the port monitor does not see the change of status until the next document is started. The print driver will be significantly slower with logging enabled.
  • Release build 120 (16 April 1997)
    • A deadlock condition in the driver could occur when attempting to print an empty text file from Notepad, or any other condition where a zero-byte print job is created.
  • Release build 119 (16 April 1997)
    • Some applications that cached DEVMODEs would have difficulty switching to the Imagemaker driver. The classic example is Excel 95; if you print to a 600 DPI printer, and save your file; then restart Excel on that file, attach to our printer, and try to print, it would attempt to print at 600 dpi.
  • Release build 118 (8 April 1997)
    • A problem with creating large images (D-size and E-size) in landscape mode was corrected.
    • The fill order tag was being set to an invalid value (0) if the PackBits compression option was used. It is now set to Normal fill order (1).
    • The count of total pages printed was not being reset at the start of the print job. This bug first appeared in build 114.
  • Release build 117 (4 March 1997)
    • A problem with the strip byte count in multi-page TIF files was corrected.
  • Release build 116 (4 March 1997)
    • Small, client-specific custom file format changes.
  • Release build 115 (4 March 1997)
    • Preliminary work towards FaxBatch NT revealed some problems with the TIFF strip byte count tag. This has been repaired.
  • Release build 114 (28 February 1997)
    • One client had some problems with a custom file format.
    • On occasion TIFF files were being generated with incorrect tags, most notably single page TIFF files were being generated with "page 1 of 2" page-number tags.
  • Release build 113
    • One client was reporting generation of 0-length files. This has been corrected.
  • Release build 112 (27 February 1997)
    • An occasional problem with applications such as NotePad which would result in stalled printing (if spooled) or an access violation (C0000005) at 0x6AA022C4 has been cured.
  • Release build 111 (17 January 1997)
    • Some customers installing the printer using .INF files reported difficulty setting the printer driver registry values. Since the name of the printer is never returned to the code in the .INF file, there is no way to determine the true registry key to use to set the PrinterDriverData fields. We now default these values. Note that it is not possible to associate the printer with our port monitor from inside an INF file; you must rely on the end user to make that association.
  • Release build 110 (16 January 1997)
    • A problem with NT4 SP1 was corrected. This problem would result in the error "Error sending cancel status: #232" and a stalled print job on some machines with NT4 service pack 1 installed.
    • The port monitor now uses a registry entry rather than the WIN.INI file to store its port information. The registry key is
      "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Print/Monitors/%s"
      where %s is the name of the fax monitor selected at install time.
    • Support for multiple languages is now available as an option. All non-debug-message strings are in resources in the driver and UI, and provision has also been made for an external resources-only DLL.
    • The About dialog is now entirely in the FaxUI resources, as mentioned in release build 107, below. Among other things, this means that by selecting the About button in the printer properties dialog, you can view the driver build number and version info.
  • Release build 109 (8 January 1997)
    • The control dialog is now spawned in the security context of the user who created the print job. Note that the user's drive mappings are still not available at the time the control dialog is started, so the control dialog must be located on the user's physical hard disk.
    • Occasionally a 10-minute pause in the queue would occur on cancelling a print job. This delay has been removed.
  • Release build 108 (31 December 1996)
    • The code introduced to support the daemon process or service has been revised to make it easier to install and use. Specifically, the driver now checks first to see if the daemon is available; if the daemon is available, information is passed to it to allow the daemon to create the control dialog; if not, the driver (or, more accurately, the port monitor) spawns the executable as before. The daemon uses the same set of registry keys as the printer does. NOTE that this requires a revision to the daemon; you must use daemon version 1.1 or later.
  • Release build 107 (10 December 1996)
    • The code for handling ResetDC has been brought in from the NT 3.51 version of the driver. This should correct any lingering issues with programs which use multiple DCs in a single document.
    • The About dialog is being moved to the driver UI resources. If you open the file IMGFAXUI.DLL with MS Developer Studio (under Windows NT only) you can modify the resources that make up the About dialog. Earlier releases were using the MS supplied routine ShellAbout() which included "Microsoft (R)" in the About text. The ComPStUI interface defaults to using the ShellAbout routine; we are researching ways of overriding this default.
    • We have added support for launching the control dialog from a user-supplied service or daemon program, rather than from the driver or spooler service. Services and daemon programs can run in user security context; this will mean that the control dialog will have access to the users drive mappings and (e.g.) MAPI profiles. For details, see the provided spec.doc (Word 6 format) or spec.txt in the service directory.
  • Release build 106
    • The driver would not generate correct names when the multiple pages per file switch was turned off. This has been traced to a Microsoft function that changed behaviour between the versions shipped with MSVC 2.0 and MSVC 4.0.
    • The driver would sometimes generate a TIFF file which indicated its resolution was 203 by 197 instead of 204 by 196.
  • Release Build 105
    • Some versions of this driver managed to get shipped with a requirement that you have MSVCRT40.DLL in your SYSTEM32 directory. The offending driver component is IMGFAXMN.DLL dated 6 November; the fixed version is dated 7 November.
    • The port monitor was not correctly handling EnumPort calls for PORT_INFO_2 structures. This resulted in a crash of Explorer when trying to install new local printer drivers, and in an alert box or Dr. Watson event when trying to select the Ports tab of the Printer Properties pages.
    • Handling the cancel return code from the control dialog has been considerably improved.
  • Release Build 104 (28 October 1996)
    • An earlier fix resulted in some programs presenting the printer driver with an invalid file name for output (along the lines of "C:\TEMP\NE00:"). This would result in a crash of SPOOLSS if not corrected from the control dialog.
    • We have added the -D"filename" functionality from our NT 3.51 printer driver. We now provide the file name passed to the driver for output by the operating system as a command line parameter to the control dialog. This file name may be used to determine whether the user is printing to a file. The new command line item uses the -D switch, so the command line for your control dialog will look like this:
      img16dlg.exe -FAAAA.TIF -C"Microsoft Word - CALLRISK.DOC" -D"FILBERT.TIF"
      where "FILBERT.TIF" is the name of the file entered using the Print to File mechanism. Note that, in fact, if you are printing to a file, the file name following the -F switch will be the same as the file name following the -D switch, except that the -F filename will also have the full path name to your selected temporary directory.
    NOTE: As features are added to the control dialog, we may have to use other command line switches. At present, -P/-p and -R/-r are used by one of our clients; as such, we will not use them for our own purposes. If your control dialog uses command switches, please contact us to ensure that we don't have conflicts.
  • Release Build 103 (21 October 1996)
    • A problem with having the named pipe span user security contexts has been corrected.
    • With this release drop, the user interface module is now essentially complete.
line

Sales: (866) 525-2170 Toll Free in North America
Sales: +1 (604) 525-2170  
Support: +1 (604) 525-2108  
Fax: +1 (604) 520-0029
Local (Pacific) time: GMT-8

ImageMAKER Development Inc.
#102 - 416 Sixth Street
New Westminster, B.C.
Canada V3L 3B2

Copyright 2000 - 2008, ImageMAKER Development Inc. All rights reserved.
Legal information | Privacy policy | Contact information