I get the message ‘Error: Object version in file younger than in program version!’. What does this mean?
You are trying to open a configuration which has been generated with a higher version of the software. The program refuses to load the file because this will contain objects which are not supported by your version.
There are 2 solutions: Update your program to the latest version so that you are able to read the file, or ask the producer of the file to generate a version for you which uses the object generation that you have in your software. You can find out about your program version in the ‘About box’ (menu item ?/about).
When I try to start the software I get the message ‘No valid software protection key (dongle) found!’. Why?
Our software packages are protected by so-called dongles. A dongle is a small USB device (looks like a memory stick) which must be present in one of the USB ports of the PC in order to run the software. If you get this message the dongle has not been detected – very likely it is really not there.
When I try to start the software I get the message: ‘This program can be used as OLE server only!’. What does that mean?
The program has been installed with a passport file which allows to run the program as OLE server only. It cannot be started as a normal desktop application.
Very likely you have downloaded the software from our website and installed it on your system. The download packages do not contain valid passport files, i.e. valid user licences. After the installation, you have to copy a valid passport file into the program directory.
In the case of SCOUT, the passport file is called scout_passport.wtp. If you installed CODE the name is code_passport.wtp.
In the case of a software purchase you should have received a passport file from us either by e-mail or with the setup CD. If you are evaluating the software you should have received a passport file with a demo licence by e-mail.
The HASP software protection key (dongle) does not seem to work properly when I install the software on a Windows 7 system. What should I do?
The dongle drivers that used to be delivered with our software products are not compatible with Windows 7. The supplier has provided new drivers which we re-distribute on our website.
Please open the section ‘Support’ and select the page ‘Current driver of the HASP software protection key’. Here you can download a setup program which will install the latest driver version. This should work under Windows 7.
At start-up I get the message ‘Class not registered’. What does that mean?
Very likely this is due to a built-in ActiveX component which needs to be registered by Windows but isn’t. The registration is usually done by the setup routine of the software – in your case this obviously did not work-out all right.
The way to fix this problem is to manually register the component. On most computers you have to have administrator rights to do this. Start a Windows command line as administrator. The Start menu has a command line in the section ‘All programs’ and there in ‘Accessories’. With a right click on the menu item you get the option to run it as administrator.
In the command line, type in the command
regsvr32 “c:\program files\scout\vcf132.ocx”
which should be followed by a message of successful registration of the component. Please note that the path used in the command must be adapted to the location of your software.
In very rare cases it may happen that 2 or more software products register the file vcf132.ocx in different versions. In this case you should unregister all older versions of the component and work with the latest version only. You unregister an ActiveX component with a command like
regsvr32 “c:\program files\scout\vcf132.ocx” /U
where the specified path should be the installation path of your software.
When I start the software, a strange dialog box named ‘Configure Hardware’ pops up. What’s wrong?
The dialog ‘Configure hardware’ is raised by a hardware driver (OceanOptics spectrometers) which cannot find its initialization file ooidrv.ini in the Windows directory.
The easiest way to avoid this is to set the second item of the dialog, the ‘A/D converter type) to ‘NONE’ and then quit the dialog with OK.
The setup routine should have copied a file named ooidrv.ini with proper settings to the Windows directory which obviously did not happen in your case.