| Updates for Global 360 Imaging for Windows |
|
HotFixes for Imaging for Windows 4.0 HotFixes for Imaging for Windows 2.8 HotFixes for Imaging for Windows 2.7 HotFixes for Imaging Professional 2.6 HotFixes for Imaging Professional 2.5 Patch 2.00.02A for Imaging Professional 2.0 |
| HotFixes for Imaging for Windows 4.0 |
| HotFix 8 completely replaces and supersedes all preceding Imaging 4.0
HotFixes. HotFix8 contains updates for Imaging for Windows(R) 4.0 and
Imaging for Windows(R) 4.0 Developer Resources. |
| HotFix 8: Corrects a file association issue reported on Japanese operating systems. Corrects issue with saving files to a path that includes multi-byte characters. |
| HotFix 7: Corrects problem introduced in HF6 where printing was not working when using the /p command line option Corrects child windows position and maximized/restored state that was not being recalled Corrects toolbar positions that were not being retained Corrects issue with Japanese characters being processed and displayed in registration dialog. |
| Hotfix 6: Corrects a problem with the Image Edit ActiveX Control that caused 'False' to be returned from the ExecuteTextEditCommand(wiIsModifiedEditText) method when a new text mark had been created. |
HotFix 5: |
| HotFix 4: Provides a new Help button to the Phase II registration dialog. Provides a Reset button to the Phase II registration dialog so the user can restart the registration process. Corrects a problem with spontaneous de-registration caused when two instances of Imaging applications attempted to check license data at the same time. Corrects a problem introduced in earlier hotfixes that prevents a Page=>Rotate All. Corrects a problem with restoring the Imaging application window as maximized if it was that way the last time the application ran. Corrects problems that prevented Imaging from running correctly on a Citrix XenApp server in some circumstances. Development Resource Kit: Provides a function that auto rotates black & white documents when they are opened or scanned. Provides a function that auto deskews all document types when they are opened or scanned. Provides .NET interop assemblies for all ActiveX controls. Note: If an earlier HotFix has been installed on a Vista workstation, you may see one of the following messages when attempting to apply HotFix4 or uninstall the product. "This action is only valid for products that are currently installed" "The system administrator has set policies to prevent this installation" "This setup will perform an upgrade of 'Imaging for Windows R 4.0'. Do you want to continue?" This is due to corruption of the MSI database caused by a flaw (since corrected) in the installer development system. To correct this, take the following steps logged on as an administrator_ -Download the 'Windows Installer CleanUp Utility' from 'http://support.microsoft.com/kb/290301'. Choose to Save. -Run the downloaded utility installer by right clicking the downloaded file and choosing 'Run as administrator'. -Choose 'Windows Install Clean Up' from the 'All Programs' menu and 'Allow' to trust the program. -Select 'Imaging for Windows' from the list of MSI installs, click 'Remove' and then 'OK' to proceed. When control returns, exit the utility. -Launch Windows Explorer and navigate to 'C:\Program Files\Common Files\Global 360'. Select the 'Imaging' subfolder and delete. -Run regedit.exe and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs. If the Run command is unavailable on the Start Menu, right click the Start button and choose Properties; On the Start Menu tab, choose Customize, find the 'Run command' entry in the list and check to enable. Exit with OK, OK. -Delete every Value in the 'SharedDLLs' key that begins 'C:\Program Files\Common Files\Global 360\Imaging'. Exit Regedit. -You should now be able to reinstall Imaging and go on to apply HotFix4. You may see a dialog entitled "Evaluation Period" while re-installing Imaging on a machine where it was properly registered. Leave the Serial Number field blank and click Install to continue. The registration will remain valid. |
| HotFix 3: Upgraded third party PDF toolset in order to resolve specific issues with viewing Japanese PDF files. |
| HotFix 2: Resolved an issue when attempting to change the compression type of a TIFF image page displayed from a file caused Internal Error and the application would become nonresponsive. Also, a new, detailed error message for clipboard open failures was added to replace the "Out of memory" error message. |
| HotFix 1: Resolved an issue relating to a memory leak and an error when using File=>New TIFF, Black & White. In addition, PostQuitMessage is now used to exit the application when the license expires. The license expiry dialog was also modified so that it is displayed for a known application and not when the ocx control is loaded via OLE embed. Includes the changes made in version 2.8 for the ClearDisplayEx function. |
| HotFixes for Imaging for Windows 2.8 |
| Note: Hotfix 51 has been recalled, please see Knowledge Base Item
73728-115 for more details. |
| HotFix 53 completely replaces and supersedes all preceding Imaging 2.8 HotFixes. If a newer version of Internet Explorer is installed after Imaging for Windows, or after an Imaging for Windows Hotfix, there may be a problem running the ActiveX controls in HTML or with Microsoft Office. To resolve this problem, either merge the registry file, activex compatibility - restore.reg (included in this Hotfix package), into the system registry by double-clicking on the file or re-install this HotFix. Issues Resolved:
HotFix 53:
|
| HotFix 52: This hotfix corrects a problem in which mark attributes cannot be modified successfully for marks beyond the 256th selected mark on a page. |
| HotFix 51: This hotfix corrects a problem in which temporary files are not deleted following a call to the ImgEdit control's SaveAnnotations() method |
| HotFix 50: Due to potential backward compatibility problems, the ClearDisplay() extension added to HotFix48 has been modified: Instead of the optional "ClearCacheFile" argument added to ClearDisplay(), a new method, ClearDisplayEx(), has been added to include the optional argument, and ClearDisplay() has been restored to its original (no-argument) syntax. Customers requiring the new "ClearCacheFile" option should change their calls to use the new ClearDisplayEx() method instead. |
| HotFix 49: This hotfix corrects several internal memory leaks that may be contributing to problems encountered with a customer application doing repeated ImgEdit ClipboardCopy/Paste and Save operations, a problem partially addressed via the ClearDisplay() workaround in HotFix48. |
| HotFix 48: This hotfix corrects an inability to do auto-size scanning in Memory Mode, such as can be done with the Canon DR-2580C. It also re-fixes a problem with certain badly-formatted JPG files (HotFix 48) to eliminate errors that were occurring in the WorkDesk program. In addition, this hotfix provides a workaround for a problem, currently under investigation, with memory leaks occurring during multiple ClipboardCopy/Paste operations between ImgEdit windows of multipage (25-300 pages) image files. The workaround consists of an optional argument added to the ImgEdit.ClearDisplay() method, as described below: ClearDisplay([optional] boolean ClearCacheFile) If set to True (default is False), the cache will be cleared for the current file, as indicated in the ImgEdit.Image property. The workaround for the aforementioned problem requires that this call, with ClearCacheFile=True, be issued after processing each page of the multipage file. Note that the ImgEdit.Image property itself should not be cleared (i.e., set to "" by the user application) until after the ClearDisplay() call is made, since it is used to determine which cache information is to be removed. Note: Although this enhancement was added specifically as a workaround for the memory leak problem, it is (and will continue to be) a generally-supported feature for use by applications wishing to optimize cache usage or for any other reason. |
| HotFix 47: This hotfix modifies the AutoDeskew algorithm to improve processing after some observations of some specific images experiencing deteriorating deskew quality. This hotfix also corrects a problem with Imaging for Windows crashing when attempting to display a certain (badly-formatted) JPG file. |
| HotFix 46: This hotfix introduces a new "averaging" algorithm for scaling of 24-bit (color) images, which eliminates problems with certain types of images being badly displayed due to use of the "decimation" algorithm which had been in use for image scaling prior to this hotfix. |
| HotFix 45: This hotfix corrects a problem with using Imaging for Windows with scanners having non-ANSI characters in their names, which caused unexpected error messages when attempting to scan. It also corrects a problem which was causing certain marks to not be resizable. |
| HotFix 44: This hotfix corrects (finally, we hope) the various problems with Kofax Group 4 2D images created by their "Kofax standard Multi-Page TIFF Storage Filter v3.03.000". All displayable files containing Pass Mode coding inconsistencies should now be displayed correctly, and other Kofax errors continue to be handled by displaying as much of the image as possible. Other problems corrected in this hotfix include: (1) Correct error message displayed for clipboard-full error; (2) Elimination of excess Mark Select events; (3) Support for long (>256 character) strings for the AnnotationText property, as well as correct processing of Width/Height arguments for TextFromFile marks. |
| HotFix 43: This hotfix corrects the sorting of the third indexed variable of the Flow User Input process. The sorted order of the third index now matches what is defined by the design-time dialog interface matching the functionality of the other index variables. This hotfix also corrects a problem with program crashes following use of the ImgEdit DeleteAnnotationGroup() method. |
| HotFix 42: This hotfix corrects a scanning problem which results in oversized pages when the resolution unit is set to anything other than inches in the TWAIN UI. |
| HotFix 41: This hotfix installs and registers the Interop Assembly (dll) file for the Server Access Object (SAO - Imgsvacc.dll), which allows this control to be used in the Microsoft(R) Visual Studio 2005 environment. It will be installed only if Imaging 1.x support is already present. See HotFix 35 for additional information. |
| HotFix 40: This hotfix includes a new facility for logging TWAIN requests. It also includes miscellaneous fixes for a recent problem with saving certain types of TIFF JPEG image pages and with performing scaling (Zoom) when using Fit To Selection. |
| HotFix 39: This hotfix corrects an engine-level memory overrun problem with AutoDeskew (used in Flow) which caused a program error when processing certain difficult-to-deskew image files. Note that this fix does NOT address deskewing issues with such images, which continue to be badly deskewed (or not deskewed at all) due to their difficult-to-process content. |
| HotFix 38: This hotfix includes an enhancement to the Flow "review" dialog box to allow selection of "Stop Processing" in addition to the existing "Add & Continue" and "Reject/Delete" options. Also, there is no longer a Cancel ("X") menu item on that dialog, in order to avoid confusion due to its original implementation having been to accept the document rather than reject it. Other problems corrected by theis hotfix: (1) A problem with the magnifier window being (re)positioned incorrectly after having already been created; (2) Incorrect processing of the SetScanCapability(Image Layout) call, which was checking for an incorrect argument count; (3) A fix to mouse-related event processing, which in certain cases of right mouse clicks was firing a double set of Up/Down events, possibly causing application confusion. |
| HotFix 37: This hotfix includes a change to the ImgEdit control's persistent-data processing, which corrects a problem with the Flow/UserInput/Insert dialog (it would sometimes not appear). Secondly, processing of Group 4 FAX images has been changed to allow additional improperly formatted (Kofax) scanned images to display (partially addressed in HotFixes 29 and 31). Finally, the error logging facility has been corrected to always locate the default log file (ImagingLog.log) in the Imaging directory; earlier hotfixes were using the directory of whatever executable was running, so multiple log files were being generated if the Imaging controls were being used in programs other than the Imaging (or ImgView) application. |
| HotFix 36: This hotfix includes a change to allow PCX/DCX files with incorrect image sizes (actual rows < header-indicated rows) to be displayed. These were formerly triggering an error message and were not displayed. This hotfix also includes support for writing PackBits compressed TIFF images for all image types (formerly only black&white supported), consistent with TIFF 6.0 baseline requirements. An updated ImagingNET.pdf documentation file for .NET installation/usage is also included in this hotfix. This update addresses the issue of optional arguments in Visual Basic .NET, which are handled differently from Visual Basic 6.0. |
| HotFix 35: This hotfix installs and registers Interop Assembly (dll) files for the five Imaging controls (ImgAdmin, ImgEdit, ImgOCR, ImgScan and ImgThumb), which allows these controls to be used in the .NET 2.0 (Visual Studio 2005) environment. Interop assembly installation is enabled/disabled via either an explicit user prompt or via command line option (+n, -n). |
| HotFix 34: Includes correction of problems with the Draw() method that could result in incorrect bounding rectangle parameters being passed to the MarkEnd event handler. Also includes logging to additional engine-level error events and a more condensed log format. |
| HotFix 33: Includes a fix to the ImgEdit::DeleteAnnotationGroup() method that could cause memory degradation and accesss violations, particularly when used with long (>8) group names. |
| HotFix 32: Includes support for logging of errors occurring in ImgEdit, ImgAdmin, ImgScan, ImgOCR and ImgThumb controls. The default (primary) error log file is ImagingLog.log in the Imaging installation directory, with corresponding secondary log ImagingLog-save.log. Enabling/disabling of the error logging feature, as well as non-default primary log file name and non-default maximum log size, are found in the registry, and can be set via the supplied EnableErrorLogging.reg and DisableErrorLogging.reg files. |
| HotFix 31: Contains a workaround for additional errors encountered in certain Kofax CCITT Group 4 2D FAX TIFF images generated by Scan Manager (extends the HotFix 29 changes). |
| HotFix 30: Contains new Server Access Object (SAO) method CreateDirectory(), which allows users of the SAO the ability to create a file directory or document cabinet, drawer or folder. |
| HotFix 29: Contains a workaround for compression errors encountered in certain CCITT Group 4 2D FAX TIFF images generated by Scan Manager (via Kofax TIFF filter 3.03.000). |
| HotFix 28: Corrects a error occurring when attempting to run Imaging software/controls on the desktop when already running Imaging components in a (background) Windows service. |
| HotFix 27: Corrects a problem in which a stack overflow was occurring in certain CCITT decompression and image scaling functions when run in a Windows Service environment. Also corrects a problem with incorrect sizing when doing copy/paste from one image to another image having different resolution. Also corrects a problem with doing SaveAnnotations when an overlay file is present. |
| HotFix 26: A problem introduced in HotFix 19 caused a program failure when setting any of the "FitTo" options before performing the scan operation. This has been corrected. |
| HotFix 25: Some LZW files created by other companies have illegal JpegInterchangeFormat and JpegInterchangeFormatLength tags which cause Imaging for Windows to crash. This hotfix ignores these illegal tags. |
| HotFix 24: Corrects a memory leak that shows up with repeated calls to the Admin OCX Append function. Also corrects a "hang" problem when displaying an image containing a targeted mark and certain other annotation combinations. |
| HotFix 23: RESERVED FOR INTERNAL USE. HOTFIX NOT RELEASED. |
| HotFix 22: RESERVED FOR INTERNAL USE. HOTFIX NOT RELEASED. |
| HotFix 21: Added the ability to set the fill style and fill color via the AnnotationFillStyle/Color Properties and the SetSelectedAnnotationFillStyle/Color methods for Attach-a-Note marks. |
| HotFix 20: Added ability to disable new-mark selection in ImgEdit and ImgAnno Draw() methods. An additional argument has been added to the Draw() methods in both the ImgEdit and ImgAnno controls. The default action is to select the new mark, which is consistent with past behavior. This additional argument may be set to FALSE/TRUE or it may be omitted. FALSE - leaves the new mark unselected and the selection state of existing marks unchanged TRUE - select the new mark omitted - select the new mark Corrected a "Cannot Save" problem with saving certain types of multipage TIFF images. Corrected an intermittent GPF problem with OLE Automation. |
| HotFix 19: Corrected the inability to zoom certain images to 2% zoom factor. |
| HotFix 18: Corrected a printing problem where items were not printing properly. |
| HotFix 17: Corrected a reported problem with the IMGEDIT SaveAnnotations method not saving the displayed page when the REMOVE_ANNOTATIONS option was specified. Also corrected a similar (unreported) problem with the LoadAnnotations method. |
| HotFix 16: When repeatedly drawing annotations a reduction in available resource handles became apparent. This hotfix resolves this handle leak. The rubber-banding of the selection rectangle is corrected.
top-left -> bottom-right |
| HotFix 15: Added the script label and dropdown box on the font dialog box. This allows users to select the desired script to match their font. For example, select a eJapanesef script to coordinate with the a selected Japanese font. |
| HotFix 14: Between Jan. 20th, 2005 at around 2:54 PM and Jan. 21st, 2005 9:20 PM, if a user tries to create a JPEG image file, the create fails with an access violation. A similar problem would occur at regular intervals for approximately 7 minutes every 228 days. The fix for this problem is in oieng400.dll. |
| HotFix 13: This HotFix contains new functionality. It offers the ability to programmatically specify the text string content to be used when calling the Draw method of the Image Edit OCX for Text and Attach-a-Note annotations. AnnotationText is a new property of the Image Edit OCX,. If this property contains a string, then this string is used to specify the content of a Text or Attach-a-Note annotation created by the Draw method of the Image Edit OCX. During invocation for a Text or Attach-a-Note annotation, the Draw method of the Image Edit OCX assesses the AnnotationText property. If the property value is not an empty string, then the property value is used to set the content of the Text or Attach-a-Note annotation. After using the property value, the Draw method clears the AnnotationText Property, as users are likely to remember to set the AnnotationText property before calling Draw, but not to clear it after use. This provides backward compatible behavior of the Draw method.
AnnotationText property
Applies To
Syntax
Data Type
Remarks |
| HotFix 12: If a newer version of Internet Explorer is installed after Imaging for Windows, or after the Imaging for Windows Hotfix, there may be a problem running the ActiveX controls in HTML or with Microsoft Office. To resolve this problem, either merge the registry file, activex compatibility - restore.reg, into the system registry by double-clicking on the file or re-install Hotfix 08 or later. This file, activex compatibility restore.reg, is included in this Hotfix package. Right-mouse clicking and selecting a menu item from within a selection rectangle drawn other than upper-left to lower-right, resulted in either a no-op operation or the message: "An internal error has occurred." Imaging for Windows with HotFix 12 now accepts the selection rectangle drawn in any direction:
top-left -> bottom-right
|
| HotFix 11: On Windows XP, when running Imaging.exe maximized on the desktop, a Windows Desktop lock no longer yields the error: "No memory is available. The zoom operation cannot be performed." Also, the displayed image remains intact. |
| HotFix 10: Undo memory leak: After clearing part of image on multiple files or multiple pages within a file, undo memory is not released. Memory used by Imaging can become very large. When using the Flow output to 1x with MBCS, the generated document names are now correct. |
| HotFix 09: When using the Clear function to clear a selected image area, the entire area is now cleared without leaving a row of pixels on the right and bottom edges. |
| HotFix 08: When using Internet Explorer releases (v5.00.2919.6307 or later), the ActiveX controls do not work properly in HTML and with Microsoft Office 2003. |
| HotFix 07: While viewing the page properties of a 1.x document, the alt+m functionality revealing the currently displayed page mapping now works. |
| HotFix 06: Displaying and using the Magnifier with images with a mixed x and y resolution i.e. 200 x 98, the magnifier does not scroll correctly. When the magnifier is mid-way down the image on the page the magnifier data is at the bottom of the image. |
| HotFix 05: Attempting to display TIFF-JPEG compressed files written with the optional Technical Note 2 (7.0) JPEGTables TIFF tag failed with "Invalid File Format". Pressing the delete-key in ImageEdit control, 2 KeyDown-events are launched, then 2 KeyUp events. Attempting to display a specific EXIF *.jpg file causes Imaging for Windows to hang. Thumbnail_Click event fails to fire under reproducible circumstances.
Access to a 1.x repository residing on a Windows operating system via various means, such as a call to the DoesObjectExist method does not work correctly and might result in an error, e.g: |
| HotFix 04: In some cases, the Flow Output To WMS driver can generate the error: "Invalid page type for requested function." |
| HotFix 03: After scanning a true color image, saving the image results in the error message:
"Unable to write to this location. Possible causes are low disk space, write |
| HotFix 02: The Flow Output to WMS Driver now applies FormViews to the FormFields dialog and only enforces the required fields that are in the applied user's FormView(s). If a required field is not in the applied user's FormView(s), then it is not required for Flow Output to WMS Driver processing. |
| HotFixes for Imaging for Windows 2.7 |
| HotFix 31 completely replaces and supersedes all preceding Imaging 2.7 HotFixes. If a newer version of Internet Explorer is installed after Imaging for Windows, or after an Imaging for Windows Hotfix, there may be a problem running the ActiveX controls in HTML or with Microsoft Office. To resolve this problem, either merge the registry file, activex compatibility - restore.reg (included in this Hotfix package), into the system registry by double-clicking on the file or re-install this HotFix. Issues Resolved:
HotFix 31:
|
| HotFix 30: This hotfix corrects an intermittent problem with displaying an image embedded in Internet Explorer version 7 or above. |
| HotFix 29: This hotfix corrects a problem in which temporary files are not deleted following a call to the ImgEdit control's SaveAnnotations() method |
| HotFix 28: This hotfix corrects an additional problem encountered in the WorkDesk application when processing the badly-formatted JPG file addressed by hotfix 27. |
| HotFix 27: This hotfix corrects a problem in JPG file processing in which certain badly-formed JPG files were causing a crash in the Imaging code. |
| HotFix 26: This hotfix introduces a new "averaging" algorithm for scaling of 24-bit (color) images, which eliminates problems with certain types of images being badly displayed due to use of the "decimation" algorithm which had been in use for image scaling prior to this hotfix. . |
| HotFix 25: This hotfix corrects a problem in the Imaging engine encountered when performing a Save operation (from the ImgEdit control) on TIFF files containing certain types of JPEG version 6 pages. Specifically, any unmodified page(s) would end up unprocessable due to invalid page format. . |
| HotFix 24: This hotfix corrects (finally, we hope) the various problems with Kofax Group 4 2D images created by their "Kofax standard Multi-Page TIFF Storage Filter v3.03.000". All displayable files containing Pass Mode coding inconsistencies should now be displayed correctly, and other Kofax errors continue to be handled by displaying as much of the image as possible. . |
| HotFix 23: This hotfix corrects a deficiency of the text annotation processor that allowed a maximum of only 256 characters in the string passed to (Set)AnnotationText. That limitation has now been removed, and an AnnotationText string of any length may now be set. This release also includes support for the installation and registration of the Interop Assembly (dll) file for the 1.x Server Access object (ImgSvAcc), which allows this control to be used in the Microsoft(R) Visual Studio 2005 environment, as is already the case for the ImgAdmin, ImgEdit, ImgScan and ImgThumb controls. . |
| HotFix 22: This hotfix corrects a problem in the Imaging engine encountered when performing a Save operation (from the ImgEdit control) on TIFF files containing certain types of JPEG version 6 pages. Specifically, any unmodified page(s) would end up unprocessable due to invalid page format. |
| HotFix 21: This hotfix corrects a problem with the ChkExDt dll which resulted in registry key handle leaks in various situations, including during loading/unloading of the ImgEdit control and when using the OCR facility or creating TIFF LZW images. It also corrects additional problems encountered when attempting to display certain Kofax CCITT Group 4 FAX image files. |
| HotFix 20: This hotfix installs and registers Interop Assembly (dll) files for the four Imaging controls (ImgAdmin, ImgEdit, ImgScan and ImgThumb), which allows these controls to be used in the .NET 2.0 (Visual Studio 2005) environment. Interop assembly installation is enabled/disabled via either an explicit user prompt or via command line option (+n, -n). |
| HotFix 19: Contains a workaround for additional errors encountered in certain Kofax CCITT Group 4 2D FAX TIFF images generated by Scan Manager (extends the HotFix 18 changes). |
| HotFix 18: Contains a workaround for compression errors encountered in certain CCITT Group 4 2D FAX TIFF images generated by Scan Manager (via Kofax TIFF filter 3.03.000). |
| HotFix 17: Corrects a error occurring when attempting to run Imaging software/controls on the desktop when already running Imaging components in a (background) Windows service. |
| HotFix 16: Corrects a problem in which a stack overflow was occurring in certain CCITT decompression and image scaling functions when run in a Windows Service environment. |
| HotFix 15: Corrects a problem where the Image Edit control function SaveAnnotations fails when the image has an Overlay File. |
| HotFix 14: Corrects a problem with not updating the default printer if the user changes it after the print dialog box has already been displayed. |
| HotFix 13: Corrects a memory leak that shows up with repeated calls to the Admin OCX Append function. |
| HotFix 12: Intermittent GPF using Imaging Automation in VB 6.0 on Windows XP. |
| HotFix 11: Corrected a printing problem, where items were not printing properly. |
| HotFix 10: Corrected a reported problem with the IMGEDIT SaveAnnotations method not saving the displayed page when the REMOVE_ANNOTATIONS option was specified. Also corrected a similar (unreported) problem with the LoadAnnotations method. |
| HotFix 09: ROC014565: Between Jan. 20th, 2005 at around 2:54 PM and Jan. 21st, 2005 9:20 PM, if a user tries to create a JPEG image file, the create fails with an access violation. A similar problem would occur at regular intervals for approximately 7 minutes every 228 days. The fix for this problem is in oieng400.dll. ROC015094: From WebDesk, using Internet Explorer, it is impossible to open an image with Imaging 2.7 running as a stand-alone application. Imaging 2.7 always starts embedded within the IE window. Modifying file type options in Windows (disable the "browse in the same window" option) does not change this behaviour. Note: to disable embedded display of images, you must run the "DisableEmbedding.cmd" command file. If kodakimg.exe is installed in a folder other than "C:\Program Files\Imaging", you will need to modify the path in the command file. |
| HotFix 08: Internal, not released. |
| HotFix 07: If a newer version of Internet Explorer is installed after Imaging for Windows, or after the Imaging for Windows Hotfix, there may be a problem running the ActiveX controls in HTML or with Microsoft Office. To resolve this problem, either merge the registry file, activex compatibility - restore.reg, into the system registry by double-clicking on the file or re-install Hotfix 06 or later. This file, activex compatibility restore.reg,is included in this Hotfix package.
|
| HotFix 06: When using Internet Explorer releases (v5.00.2919.6307 or later), the ActiveX controls do not work properly in HTML and with Microsoft Office 2003. |
| HotFix 05: Displaying and using the Magnifier with images with a mixed x and y resolution, i.e.: 200 x 98, the magnifier does not scroll correctly. When the magnifier is mid-way down the image on the page the magnifier data is at the bottom of the image. |
| HotFix 04: Access to a 1.x repository residing on a Windows operating system via various means, such as a call to the DoesObjectExist method does not work correctly and might result in an error, e.g: "75 - Path/File access error. Unable to read or write the specified file." Access to a 1.x repository residing on a Windows operating system now connects properly. This modification does not affect the functionality for accessing a 1.x repository residing on a UNIX operating system. |
| HotFix 03: Memory leak when making repeated calls to BurnInAnnotations. IMPORTANT NOTE REGARDING CODE USAGE: As a workaround to the very large memory leak (400 KB per image), a work around suggestion was made to use code such as: Set frmMyImagingForm = Nothing This alleviated the very large memory leak, and resulted in a much smaller memory leak (10 KB per image). For this HotFix to work correctly, and to correct all memory leaks, the work around suggestion code must be removed. Instead, the proper code usage is: frmMyImagingForm.UnloadForm. |
| HotFix 02: After deleting all of the annotations on a page, calling AddAnnotationGroup and then either ShowAnnotationGroup or HideAnnotationGroup yields an error. |
| HotFix 01: RESERVED FOR INTERNAL USE. HOTFIX NOT RELEASED. |
| HotFixes for Imaging for Windows 2.6 |
| HotFix 17 completely replaces and supercedes all preceding Imaging 2.6 HotFixes Issues Resolved: After calling SavePage to append a page, the final TIFF only contains a single page (the page to be appended) all other pages are gone. |
| HotFix 15: Flow: EIW field validation does not work / exist for date fields or fields with a high/low value range. The EIW server (as designed) will allow a client application to stick anything in one of these fields. Validation is left for client level implementation. The EIW client application should only accept dates in YYYY-MM-DD format for entry into a date field. Copy as Text" context menu function works incorrectly, carriage returns are added to text. Note: This is only an issue with Imaging Professional. Attempting to display a bad image created by Lead Tools Technologies crashes the application. This image is TIFF with JPEG compression. When the TIFF header is stripped from the file, Imaging displays the JIFF data properly. The problem is that the PhotometricInterpretation value is not consistent with the BitsPerSample and SamplesPerPixel values. SetSelectedAnnotationFontColor does not change the text color. When the Pro application runs inline in Internet Explorer 5.x, toolbar settings are not preserved between sessions. They are reset to default when Internet Explorer exits. Pro-File/Flow for EIW document results in the error "The disk is full. Free up some disk space". WorkDesk-Rubberstamp annotation does not update appropriately (every other time). Calling ClearDisplay after ShowMagnifier disables the OCX-DblClick event of the ImgEdit control. The DblClick event of the ImgEdit control fails to fire if the ClearDisplay method is called at any time after the ShowMagnifier method (whether or not the magnifier is still being displayed). Sample code is provided. The ImgQuery method of the ImgAdmin control for FindIFS query against the optical file system volume only returns directories and not files. Sample code is provided. |
| HotFix 13: Use of Imaging Professional's File / Flow menu choice for EIW document results in the error "The disk is full. Free up some disk space". When the Pro app runs inline in IE 5.x, toolbar settings are not preserved between sessions, they are reset to default when IE exits.
Attempting to display an image that contains certain inconsistent internal values causes the
Imaging application to crash. |
| HotFix 10: On Windows 98 the ImgThumbnail control generates a GPF in a custom application that makes repeated use of the DeleteThumbs method. The thumbnail control leaked one handle for each image file opened. When using recent Internet Explorer releases (v. 5.00.2919.6307 or later), Pro 2.6 ActiveX controls do not work properly in HTML. Occasionally, a call to the DisplayPageViewer method of the CALPage object ExportPages method of the CALDocument object on an EIW workitem generates an error such as 1000, 1180, or 1407. The flow output to EIW driver always creates a single page legacy mode image document, even if the document captured by Flow has more than one page. This results in a loss of data. Additionally, this driver should be able to create Professional mode image documents as well as Legacy mode documents. In several circumstances, WorkDesk generates the error "Automation error - The object invoked has disconnected from its client". After applying HotFix 03 and/or HotFix 06, Imaging Professional, Imaging Standard, or WorkDesk generate the error "Property or method is not supported in this version". |
| HotFix 09: After deleting pages in a 1.x document, the following error message is displayed: "An internal error has occurred." The document is closed. When trying to reopen the document, the following error message is displayed: "The document cannot be opened. Invalid page number." This defect may also be reproduced in thumbnail mode. Select the pages and then edit/delete the pages. An 'internal error' message is displayed. The document and its referenced files are in tact and accessible via non-Imaging Professional software, i.e. Cabinet. To Imaging Professional, it appears that the 1.x document is corrupt. However, it actually is not. |
| HotFix 08: Note: HotFix 8 implements strict functional security. It is only useful in very specific circumstances and is not intended for most installations. This HotFix can only be obtained by request from a technical support representative. |
| HotFix 07:
After applying HotFix 03 and/or HotFix 06, Imaging Professional, Imaging Standard, or WorkDesk generate the error: "Property or method is not supported in this version. |
| HotFix 06: In several circumstances, WorkDesk generates the error: "Automation error: The object invoked has disconnected from its client." |
| HotFix 05: The flow output to EIW driver always creates a single page legacy mode image document, even if the document captured by Flow has more than one page. This results in a loss of data. Additionally, this driver should be able to create Professional mode image documents as well as Legacy mode documents. The main driver dialog has been modified to include two new fields: a page name (that defaults to "Page" and allows the use of Flow variables), and a checkbox to select Legacy mode or Professional mode documents. (Note that these used to be in a disabled "Advanced" dialog that has been removed from the project). The driver has been modified to honor the Legacy/Professional mode option. This driver can create two types of documents: Legacy mode documents have one document page per image page in the source image file. The page name specified in the UI is used as a prefix and has the page number appended to the end of the string. These documents are created using the CAL ImportPages method. Professional mode documents have a single document page that contains the entire source image file. These continue to be created using the SetPage method. |
| HotFix 04: Occasionally, a call to the DisplayPageViewer method of the CALPage object ExportPages method of the CALDocument object on an EIW workitem generates an error such as 1000, 1180, or 1407. |
| HotFix 03: When using recent Internet Explorer releases (v. 5.00.2919.6307 or later), Pro 2.6 ActiveX controls do not work properly in HTML. Printing from Pro on Win 2K does not always work correctly. |
| HotFix 02: When the Pro app runs inline in IE 5.x, toolbar settings are not preserved between sessions, they are reset to default when IE exits. This HotFix also implements a number of new security features: 1) Menu settings set in the Toolbars... Dialog (reached from View / Toolbars... or right-click on a toolbar and choose Toolbars...) are now persistent. 2) Several new registry settings have been added. These are located in the
registry section: "HKEY_CURRENT_USER\Software\Kodak\Imaging\Etc\". Note 1) These entries are added to the registry by running the registry file:
ImgProNoEdit.reg. After merging this file, the standard and imaging toolbars are
enabled in the registry. Also, the annotation, scanning and web toolbars are disabled
in the registry. |
| HotFix 01: The thumbnail control leaked one handle for each image file opened. An application containing the thumbnail control would generate a GPF error when the scroll bar was used after setting the Image property to a multipage file containing an LZW-compressed page. The message "Internal Control error" was generated when starting the application, if the thumbnail control was not able to create a ‘required window’. This would occur when attempting moves in thumbnail mode, if the images being moved contain LZW pages. |
| HotFixes for Imaging Professional 2.5 |
| HotFix 11: When using the ImgEdit control, annotation attributes cannot be changed and then used by the Draw method if the SelectTool method had previously been called. Even specifying a ToolID of zero in the call to SelectTool does not correct the problem. The ImgEdit control will now allow the annotation attributes to be changed after the SelectTool method is called with a ToolID parameter of zero. When using the Imaging Professional standalone application or WorkDesk with Imaging Professional as the viewer, there is a problem with creating certain rubber stamps. Custom image rubber stamps, created via Annotation / Rubber Stamps / Create Image, do not work correctly. When applied to an image, no stamp appears on the image and no error is generated. This HotFix allows custom image rubber stamps to be applied to the image in the Imaging Professional standalone application and WorkDesk with Imaging Professional as the viewer.
|
| HotFix 10: Problems accessing 1.x servers after installing Imaging Professional 2.5 over Imaging Professional 2.0 The silent installation of Imaging Professional fails with a result code -12 "there is no silent install response file for the 1.x client install". The installation of the 1.x Server Access Component can be done silently, if the server address and port number are accounted for prior to performing the installation.
|
| HotFix 9: The Imaging Professional application loads slowly if the default printer is off-line.
|
| HotFix 8: This HotFix corrects a bug in the in FindFirstFile and FindNextFile methods of the Server Access Object (SAO) where these two functions would miss the first file out of every 20 returned. Also, the SAO has been enhanced by adding two new methods. The GetKeywords method of the SAO can be used to get the keywords stored in the specified 1.x document. The SetKeywords method of the SAO can be used to set the keywords stored in the specified 1.x document. The Server Access Object (SAO) has been enhanced by adding two new methods. The CopyDocument method of the SAO allows the source document to be copied to a specified destination document, optionally overwriting the specified destination document. The GetDocumentDates method of the SAO can be used to obtain the creation and modification dates of the current document.
|
| HotFix 7: After many repetitions, either the ClipboardCopy or ClipboardPaste method of the ImgEdit control will fail.
|
| HotFix 5: If the NameServer property value is modified since the previous LoginToServer call, the new/updated NameServer value is not used the next time LoginToServer is called. Therefore, the client still connects to the previous server.
|
| HotFix 4: Certain very large image files can cause the application to crash when it tries to save the file.
|
| HotFix 3: Superceded and replaced by HotFix 11 |
| HotFix 2: Superceded and replaced by HotFix 8 |
| HotFix 1: Any Flow that used user input variables of type "Number" or "Date/Time" was saved incorrectly. This caused errors the next time the Flow was opened. This fix prevents this problem, but does not enable already damaged Flows to be opened. Every time you modified a variable definition, the zone was moved slightly to the upper left and got slightly smaller. If you selected an input zone while you were zoomed into the image, the zone placement information was messed up, resulting in the wrong portion of the image being displayed when the flow ran. The image displayed in the data entry dialog was not always updated when the next document was processed.
|
| Note: for language localized versions of Imaging
Professional 2.5 (Dutch, French, German, Italian, and Swedish) Due to the manufacturing process of language localized software, HotFixes 1 through 5 are already included with the localized versions of Pro 2.5. Subsequent HotFixes are not included and localized versions of all HotFixes are required, before they can be applied to the localized versions of Pro 2.5. If you should need a localized version of a HotFix, please contact support@opentext.com with your request. |
| Patch Version 2.00.02A Fixes various issues listed in the readme.
- Included in this patch is support for Visual Basic and Visual C++ 6.0. NOTE: if this patch was previously installed on a system on or before February 18, 1999, uninstall it and then install this copy of the patch. More Info |