Technical Issues - Installation Problems

Windows 7-11 Compatibility

FilmStar runs under Win XP/Vista/7-11, but adjustments may be required, especially if installing old versions. MEASURE versions work with 64-bit Windows with the exception that Mpe19AX requires 32-bit Windows.

Please contact FTG Software about any issues and solutions not discussed below.

1. PASSWORDS DON'T WORK or NEW VERSION  NOT INSTALLED...If setup32.exe is already in your Downloads directory your new download will be renamed setup32(1).exe. This has stumped several users.

2. SUDDEN QUIT...If you get the Unexpected error; quitting error message or if the program quits without error message, right click the program's icon and select 'Run as administrator'. The next time the program should run normally. Repeat for each FilmStar/Scantraq program. You may need to contact IT to Run as adminstrator.

3. NEW PROBLEM (18 Jan 2023)...The GdiPlus.dll error at the right, followed by installer crash, was reported in setup32.exe. Another user reported the same error referring to MSVBVM60.DLL; in this case the 'Plan B' installer was utilized instead see Another solution #2 below.

The error seems related to Windows 11 security settings or anti-virus software requiring whitelisting.

A user with Norton anti-virus reported the same error along with a Threats blocked pop-up. Upon re-installing without Data Protector, installation proceeded normally.

To disable Data Protector, click and search for "Data Protector" in your My Norton screen. Users may require the assistance of IT personnel.

Another user reported that installing with XP (SP2) compatibility and Administrator Privilege Level (see ¶4 below) worked.

Should you require assistance or be able to report a new solution, contact FTG Software.




Another solution #1: An IT engineer resolved the issue but the explanation (whitelisting) is rather uncertain:

"I reloaded the System and then redownloaded ..setup32.. and it just worked without hesitation so not sure if when they White listed the product it authorized the installation. I am guessing that modifications was caused before the Whitelisting and it made changes to some of the DLL's and it messed up the installation."

The 'compatibility mode' setting given in the next section (¶4) might apply. Please let us know! You can also update DESIGN/INDEX and MEASURE with Updaters which do not write to Windows directories.
 
Another solution #2: (21 May 2023, updated 18 Dec 2024): Installation errors occur when writing to Windows directories. Windows 11 appears to be especially troublesome.  As an alternative, setup32b.exe ('Plan B') does not copy files to Windows.

The following procedure was required (11/2024) when updating a previous Windows 11 installation:

1. Rename c:\Winfilm to c:\WinfilmOld.
   FilmStar should then install as if it is a new installation and not give an error message.

2. Reinstall with setup32b.exe ('Plan B')
   Our experience is that Windows 11 does not allow the installer to write to c:\Windows.
   setup32b puts Windows support files in c:\Winfilm\System

3. Later, copy previous data files from
   c:\WinfilmOld\Designs to c:\Winfilm\Designs
   c:\WinfilmOld\Data to c:\Winfilm\Data
   c:\WinfilmOld\Index to c:\Winfilm\Index
   c:\WinfilmOld\Basic32 to c:\Winfilm\Basic32
   etc.

Scantraq users should substitute "Scantraq" for "Winfilm" in the above.

4. XP COMPATIBILITY...Should installation still fail, try Setup32.exe with XP compatibility. Right-click setup32.exe and adjust as shown.


Note the Digital Signatures tab. If its missing you have
an older unsigned version which may be problematic.

Click here if you get Error: You do not have access to make the required system configuration modifications. Google any other error messages.

5. SECURITY...Worried about viruses hidden in bogus FTG Software EXE files or an Attention required notice when installing software? You might want to verify that downloaded files are genuine.

In Explorer, right click File Name...Properties...Digital Signatures...FTG Software... Details...Certificate...Details...View Certificate. ('Valid from' refers to Certificate signing and does not mean that older software expires.) Please advise FTG about any issues.

      
Current Certificate                                                  A Previous Certificate

6. USB LICENSE KEY DOESN'T WORK...Setup32.exe and Setup32B.exe include a built-in HASP USB License Key driver, but it occasionally fails. Should it get stuck at installing the driver, re-run the installer, select NO in the Install USB License Key dialog and follow the instructions below. It is also possible that there is no error message but the driver failed to install (LED unlit when key inserted).

Note added 09 Feb 2022: We had reports of new USB License Key failures wherein the LED is lit but not recognized. The issue has been addressed and Setup32.exe updated, but if you already installed the failed HASP driver you might need to remove and re-install. Download haspdinst.exe and copy to C:\. Open Command Prompt as Administrator and do as follows:

There is no need for the first command line (-purge) if the key was never installed.

 Unfamiliar with Command Prompt? Download and run LicenseKey.exe.

Contact your IT department or FTG Software if you require assistance. Please keep us informed about any further USB License Key issues. A previous link to a standalone HASP installer has been deleted because it does not install a required component.

7. INDEPENDENT LICENSE KEY TEST...http://localhost:1947/_int_/devices.html.

If the key seems OK (blink test) but the error message at the right pops-up, click <Retry> followed by <License Information>. This displays and copies license settings to the Windows Clipboard. Paste into an e-mail to FTG Software.

Note: Key ID is the decimal value of hex Module ID displayed in the License Information window. Click here for an online converter.

8. FilmStar/Scantraq MIX-UP... You want to install FilmStar but, after mistakenly specifying Scantraq can only install Scantraq (or vice-versa). The fix: run RegEdit (Registry Editor) and delete the FTG Software key as follows...

32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\FTG Software
64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FTG Software

Now reinstall the version you require. Reluctant or can't run RegEdit? Contact IT.

9. MEASURE Test Mode... MEASURE is initially configured with Test Mode ON. Turn OFF in File.. Configuration.. Preferences. Test Mode makes it possible to develop and test BASIC macros without having to perform actual scans.

10. OLE32.DLL ERROR resulting from INVALID PATH...We obtained a misleading message when attempting to install to Winfilm rather than C:\Winfilm. Since the path was invalid nothing was actually installed.

11. POSSIBLE MESSAGE... In reponse to This program might not have installed correctly we found no problem after clicking This program installed correctly.

12. UNUSUAL PROBLEM...Contact your IT department

13. FONT INSTALLATION PROBLEM...Lucida Sans Typewriter is the default fixed font for editors, numeric grids, etc. If not found in ..\Windows\Fonts it will be added. If the Fonts directory is not writable contact IT to enable writing and re-run setup32.exe. Alternatively, fonts can be downloaded here.

14. UNIMPORTANT PROBLEM...Vista/Win 7 omit the WinHlp32.exe viewer for *.hlp help files. This is no problem because FilmStar uses HTML help. There is one place, however, where WinHlp32 is accessed: pressing the '?' icon in the BASIC UserDialog editor. You will probably never do this, but just in case here is what happens: On accessing WinHlp32 for the first time you arrive at a Microsoft site informing you that the help is obsolete, but they'll let you view it anyway. We've uploaded Microsoft's help installers for your convenience: 32-bit help installer, 64-bit help installer for newer computers. If you download from the Microsoft site, note that '64' indicates the 64-bit installer and '86' the 32-bit installer.

15. SOFTWARE BASED LICENSE KEY...A license intended for temporary users or situations where the USB License Key has failed, USB keys are not permitted, etc.

The license is implemented by replacing License=USB in c:\Winfilm\Config\Common.ini ([Install] section). We recommend Notepad++ (free) as an alternative to Windows Notepad.

Example: License=VgCAAEt;JtkBBgA5NzE1MjABHwf9NQ7L86T5NU1gKDsl7206AlfredENeuman

In order to generate your license code we require the Machine ID given in File..Configuration..Security..<License Information>. Excel users can obtain the Machine ID before installing FilmStar in GetFTG_Code.xlsm.

16. REMOTE ACCESS...The HASP security key is not recognized when FilmStar is accessed remotely via Windows Remote Desktop (WRD). This relates to security features and is not considered to be a bug.

FTG has verified that GoToMyPC , LogMeIn and Chrome Remote Desktop (free) work.

Should IT insist on WRD, another possibility (not tested by FTG) is Donglify.


GoToMyPC

 

DLS 'ActiveX component can't create object' error

If you get the above error during DLS optimization, it's because math library matrix30.dll was not registered during installation. Although we don't know why this (rarely) occurs on some computers, it is easily fixed. Close DESIGN and click the Windows Start button followed by Run; then type

regsvr32 c:\Winfilm\Matrix30.dll

and click OK. You should get the following message

DLLRegisterServer in c:\Winfilm\Matrix30.dll succeeded

Vista/Windows 7 users need to deactivate UAC (User Account Control) or run regsvr32 as Administrator. Click Start.. All Programs.. Accessories and right-click Command Prompt followed by 'Run as administrator'. Then type the regsvr32 command given above followed by <Enter>.

If FilmStar is installed in a different directory, adjust the statement accordingly. Please let us know if this does not fix the problem.

Click here for information about restoring the Run command in Vista/Win 7. You can also use shortcut key <Windows +R>. Remember, however, that UAC must be disabled in order to execute regsvr32 from the Run command.

 

'OLE2.DLL is not a valid Windows image' error

The following message appears at the end of the installation routine:

The application or DLL C:\Windows\System32\OLE2.DLL is not a valid
Windows image. Please check this against your installation diskette.

This is a known anomaly that rarely occurs during the dynamic link library (DLL) self-registration process at the end of the install routine. The message does not necessarily indicate that an actual installation error has occurred.

If an actual error happens during DLL self-registration, you will see much more specific error messages during program operation. In that case, please contact FTG Software and include the exact error message.

 

Cary WinUV 5 issues when installing Mcary5.exe

1. This note applies to MEASURE Mcary5.exe which utilizes WinUV 5 drivers. It does not apply to MCary5U.exe which utilizes WinUV 6 drivers.

2. 32-bit WinUV 5 installs in Program Files on 64-bit machines instead of Program Files (x86) where 32-bit programs are typically installed. It does not seem to matter, however.

3. The WinUV 5 installer copies Fcary.dll 2.3 to C:\Windows\System32 (32-bit Windows) or C:\Windows\SysWOW64 (64-bit Windows). It also copies newer Fcary.dll 6.4 to C:\Program Files\Agilent\Cary WinUV.

Fcary.dll 2.3 must be deleted or renamed (e.g. Fcary.dllBAK) before installing FilmStar MEASURE. If you don't remove the file, you get a cryptic Following are not exported... error message when installing FilmStar.

4. After installing FilmStar MEASURE, Cary32.ocx should already be registered. If not you can run

regsvr32 "C:\Program Files\Agilent\Cary WinUV\Cary32.ocx"

 

Copyright © 2024 FTG Software Associates
Last updated on December 18, 2024