#2 ZDT executable launcher unable to locate its companion shared library

[Michael van den Berg]

After installing ZDT v1.0.2, the following error appears:
ZDT executable launcher unable to locate its companion shared library.JPG (see attachment for screenshot)
After clicking OK, the window closes. The splash screen with ZDT logo hasn't even appeared yet and doesn't appear at all.

• It's an upgrade from ZDTv1.0.1
• It's on Windows 7, where administrator must install all software. When the user wants to install the software, Windows asks for the password of the administrator. The software is installed under the name of that admin. This also means, that if only the person who installs (=admin) can see certain files the user (=the user of ZDT who wanted to install ZDT in the first place) will not be able to see these files and perhaps not be able to launch ZDT successfully.

Kaya: would you know a solution?

[Michael van den Berg]

Trouble shooting:
1. Logged in as Admin - was able to run ZDT properly (=the error message didn't appear; ZDT opened properly)
2. Created a new user - new user was able to run ZDT
3. Tried to use old user's profile (=all in C:\Users\<username>, except ntuser*.dat and document, picture, video files )and copy to new user - new user was still able to run ZDT
4a. Removed c:\Users\<user>\zdt for old user - CANNOT run ZDT
4b. Removed c:\Users\<user>\Appdata for old user - old user is able to run ZDT
5. Put back c:\Users\<user>\Appdata for old user - old user is NOT able to run ZDT
6. Continue to drill down bit by bit. Finally: If "C:\Users\Michael\AppData\Local\VirtualStore\Program Files (x86)\zdt\zdt.ini" is removed (renamed or deleted), ZDT will start.
7. Strangely, this file IS present in the new user's Appdata directory, because Appdata from old user was copied to new user. But new user IS able to run ZDT, WITH the zdt.ini. Why, we are not able to figure out.

A difference between old and new user: the old user had used ZDT v1.0.1, and v1.0.0, v0.9.x. Did this leave some setting somewhere else (for example in the registry) that pointed to zdt.ini in the "AppData\Local\VirtualStore\Program Files (x86)\zdt"?

Anyway, the ZDT installer should:
be able to remove old settings as sofar these are conflicting with the new ZDT version
identify previous config files of ZDT (and java?)

zdt.ini contents was as follows:

-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-nl

[Michael van den Berg]

Note:
The problem is NOT as suggested earlier, that the admin installed ZDT and that the user wouldn't have access to some admin-only files.

It is problem where there is an old file from a previous ZDT installation in the user's Appdata directory.