Messages
Reply
Edit
Delete01:23 pm
3RH0SOSSN
| From: | Rick Strahl |
| To: | Andrew Hall |
I'd think the problem is registry key installation usually. On 64 bit OSs all 32 bit system registry values go into the SysWow64 registry tree. If the install program is really old and doesn't know about the 64 bit key then you end up with missing keys.
If that's the case you need to update your installer or explicitly put in the registry keys.
FWIW, I know it works fine with UAC on - I have several apps running locally here with a UAC on and a lo rights account I use for testing.
+++ Rick ---
Hi Rick
Thanks for your comments. Can I be more specific on this one:
I am using InstallShield Express provided with VFP9 as the installer for my application. The resultant files after installation of my app on a Windows7-64 bit machine in Program Files (x86)\common files\microsoft shared\VFP are (Foxhhelp files,Report??.app files+) VFP9r.dll, VFP9RENU.dll, VFP9t.dll,MSVCR71.dll (the last of which I added within InstallShield and is also present in the Program Files (x86) application directory).
Within Windows7-64 bit the application runs fine if Run from the Administrator account, or from a Standard account installed from that account and Run under the Run as Administrator command. However, the users in question are restricted to UAC and are not able to use Run as Administrator. Consequently the Run command fails with the error "Cannot locate the Microsoft Visual FoxPro support library". Curiously, when the application is installed from the Standard User account the Desktop icon link to the exe file and the All Programs start folders only appear on the Admin account.
Now, if I then install VFP9 on the Windows7-64 bit machine, then uninstall it, the application can be installed from the Standard User account, and Run from it (not elevated as Administrator). Further, under these conditions the Desktop icon and All Programs start folders are on the correct Standard User account. Removal of remaining VFP entries for the VFP9 in the registry reverts behaviour for a newly installed version of my app to that previously experienced with the error. Presumably this is a registration problem, as you suggested.
I wonder if you have any further ideas on this one, and how InstallShield might be modified to sort the problem, i.e. to properly register the necessary files at the time of installation of the app.
Thanks and regards,
Andrew Hall
FoxPro runs fine on 64 bit Windows.
if you're distributing the application either run an installer to put the runtime files in their proper place (in the program files/common files location) or put them into your application folder. If you're not using an installer the latter is a better choice.
Realize though that you need true admin rights (not running under User Account Control) to register the FoxPro runtime files. I think runtime registration fails silently and that's the most likely reason you're seeing this error you're encountering. If you want to manually register make sure you use an Admin Command prompt (Click Run As Administrator on the Command Prompt shortcut).
+++ Rick ---
Hi Rick
I am distributing an application in VFP9 SP2 compiled as an executable on Windows 7 32 bit OS. It runs OK on XP thro Windows 7 (32 bit) but when the application is run on a computer with Windows 7 64 bit OS the user encounters the message "Cannot locate the Microsoft Visual FoxPro support library". The .exe is in a folder under the Program Files (x86) folder and in the same folder are the msvcr71.dll, foxtools and foxuser files. The library appears to have registered correctly. Have you any idea what the issue may be here, and how to overcome it?
Thanks and regards,
Andrew Hall
West Wind Technologies
Making waves on the Web
