| Global 360 Imaging for Windows ® Knowledge Base Items |
| (Click on "Edit" in your browser menu to use the "Find" feature.) |
| KB 1588 - When trying to add an Imaging ActiveX control, e.g. ImgAdmin or ImgEdit to a VBA user form, VB form, or HTML page, the following error message is generated: The subject is not trusted for the specified action. |
| This problem also manifests by generating no error, but when a form or HTML page containing an Imaging OCX is displayed, the OCX is not visible or does not work correctly. This occurs especially after installing Microsoft Office 2003, Internet Explorer, or an update or service pack for one of these. |
| To work around this problem, it is necessary to unset a kill bit that is set in the Windows registry for the Imaging OCXs by Microsoft products. The kill bit fix was originally released as a reg file included with ImagePro 2.6 Hotfix 03. Currently, the kill bit fix is still a reg file included with the Imaging Hotfix versions listed below. The removing of the killbit is included in the executable of 2.7 Hotfix 06 and 2.8 Hotfix 08 and later Hotfixes. The reg file may be run by itself to remove the killbits, however it is run automatically by the Hotfix executable as of 2.7 Hotfix 06 and 2.8 Hotfix 08. The latest release of Imaging for Windows, 4.0, also clears these bits. A reg file is also copied to the install directory. After applying this fix, updating any Microsoft product, especially Office or Internet Explorer, may reset the kill bit and require a reapplication of the Hotfix. |
| KB 1841 - Default viewer in Windows XP is not Imaging for Windows. |
| If you are looking for a way to make Imaging for Windows to be the default application for TIFF files on Windows XP, here is what you can do to replace the Windows XP Picture and Fax Viewer Application:
- Click 'Start' and then click 'My Computer'. - On the 'Tools' menu, click 'Folder Options'. - Click 'File Types' and then in the 'Registered file types' list, click on '.TIF TIF Image Document' - Then click on 'Advanced'. -If the 'Advanced' dialog box is not present, click on the 'Restore' button. Then the 'Advanced' button reappears. - In the 'Edit File Type' dialog box, in the 'Actions' list, click 'Preview' and then click 'Edit...' - In the 'Editing action for type: TIFF Image Document' dialog box, click 'Browse...' - In the 'Open With' dialog box, locate the Imaging Preview application, imgprv.exe. If the default location was used for installation, the file will be located in c:\Program Files\Imaging. - Select 'imgprv.exe' and click 'OK' or 'Open'. - 'Click 'OK' to close the 'Editing action for type: TIFF Image Document' dialog box. - Now back in the 'Edit File Type' dialog box, select 'Preview' again and click on 'Set Default'. - Click 'OK' to close the 'Edit File Type' dialog box. - If the 'Advanced' dialog box is not present, click on the 'Restore' button. Then the 'Advanced' button reappears. Do the same for the .TIFF and .JFX file extensions. Please note: this all needs to be set by a user with administrator rights. |
| KB 1958 - Unsupported CITRIX / Terminal Server configuration. |
| Can I use Imaging for Windows in a Terminal Services environment? In the past years we have had some issues between Imaging Pro and Terminal Server products (as well as the MS Terminal Server and CITRIX products) The official position of R&D was that our Imaging Pro product was not certified nor supported with Terminal Server products. That was mainly due to the network transfer load and speed, and the fact that these products are using a lot of virtual device drivers. The support position is to ask the customer to reproduce the problem in a standard configuration. |
| KB 4918 - Imaging for Windows 2.7 / 2.8 and .NET compatibility. |
| Will Imaging for Windows 2.7 and 2.8 ever be .NET compatible? Imaging 2.7 Hotfix 20 and Imaging 2.8 Hotfix 35 are now available. These hotfixes contain support for Microsoft .NET Framework 2.0 / Visual Studio 2005. The hotfix packages include the required Interop dlls (see the readme file for more info), as well as ImagingNET.pdf, which describes use of Imaging in the .NET environment. Imaging for Windows Developer Resources 4.0 also installs the Interop assemblies. |
| KB 4909 - Finding out installed hotfix number for version 2.7. |
| How do I find out what hotfix I have installed on Imaging for Windows Standard Edition, version 2.7 or Imaging for Windows, version 2.7? To Determine what Hotfix has already been installed by checking the version number of the oieng400.dll file.
- In Windows Explorer, navigate to the Imaging program directory (typically located in "C:\Program Files\Imaging" or "C:\Program Files\Imaging Standard"). |
| KB 4910 - Finding out installed hotfix number for version 2.8. |
| How do I find out what hotfix I have installed on Imaging for Imaging for Windows, version 2.8? To Determine what Hotfix has already been installed by checking the version number of the oieng400.dll file.
- In Windows Explorer, navigate to the Imaging program directory (typically located in "C:\Program Files\Imaging" or "C:\Program Files\Imaging Standard"). |
| KB 73728-115 - Hotfix 51 Recall |
| Imaging for Windows 2.8 Hotfix 51 has been recalled. You will receive an internal error when creating a tiff image after you install Hotfix 51. If you installed Hotfix 51, please download Hotfix 50. Extract the files in Hotfix 50 to a temporary location. Replace the following files in your c:\program files\imaging\ directory with the ones from the newly extracted Hotfix 50 directory: IMGEDIT.OCX IMGEDIT.INTEROP.DLL OIENG400.DLL |