On starting "DirectSOFT 5 Programming" from DSLaunch in a new installation we get
"Error 1003 Invalid API version in module c:\DirectSOFT32\Program\Bin\Prgrm50.DLL.".
I found the FAQ
http://www.hosteng.com/faqfiles/Directsoft.htm#FAQ0185 which describes a number of possible causes, none of which appear applicable.
Thus far I first installed on a Windows 7 64-bit system, then on Windows Server 2008 64-bit. These are all virgin installations for DirectSOFT5 version 5.3 software, therefore no chance of incompatibilities with older versions of the same. DSLaunch version is 5.3.194.
Actions taken on Windows 7 system (installed 3 times):
- Had selected "Skip" when prompted regarding locked DLLs MSVCP71.dll and MSVCR71.dll. These DLLs are associated with the Microsoft C++ runtime package. Manual verification showed file version 7.10.3077.0, therefore "Skip" was chosen after determining that file to be installed and file already installed (found on-line reference for DirectSOFT5 to identical version number). Rebooted. No change, therefore uninstalled.
- Initially installed in non-default directory, Re-install in default directory.
For the installation on Windows Server 2008 we did a default install. The DirectSOFT5 started without error as administrator, but produced E1003 when using regular user privileges. As a test I changed the privileges for non-administrator users on the C:\DirectSOFT5 folder to full control, after which DirectSOFT5 starts without error 1003.
Based on my experience there is still an issue with the DirectSOFT5 software installation related to the UAC (User Account Controls) settings. Perhaps the program is dependent on write permission to one of the sub-directories below C:\DirectSOFT5 which are not granted by default on Windows 7. I am therefore able to use the program, but only after manually changing the directory permissions in the default installation. I have not had time to isolate the problem further.
As a new user of the software I only found the FAQ0185 as relevant description of the ERROR1003 problem and in my experience this FAQ is out of date for Windows 7 and UAC issues.