>>>>>>I have a .exe that is installed into two different Windows 95 machines. The exact .exe.
>>>>>>
>>>>>>One machine works fine.
>>>>>>The other one I get error 1691 "Library File c:\program files\winmason98\ver1\foxtools.fll is Invalid"
>>>>>>
>>>>>>I have code in a form init that calls the library to display the version number.
>>>>>>Why would it work in one and not the other - both are installed from the same diskettes. I copied foxtools.fll from the one working to the one not working. I made sure it was the one exact one found in my c:\vfp5 directory. There is nothing wrong with the .fll file?
>>>>>>
>>>>>>Help!
>>>>>
>>>>>Try renaming the file in c:\program files\winmason98\ver1\ and then re-copy the file from your machine. It could be that there's a bad cluster on the disk, and when you copy over the file, you haven't really solved the problem. If this fixes it, be sure to run scandisk.
>>>>>
>>>>>hth,
>>>>
>>>>
>>>>hth,
>>>>
>>>>No go - this still isn't working. I'm using InstallShield Express2 for my distribution. I just built a small .exe with only a single form and the foxtools.fll trying to duplicate the problem. I'm getting the same problem. I just built a install set using Microsofts Setup Wizard and am about to try that. I will let you know the results in a moment. I don't want to use the Setup Wizard unless I have to.
>>>>
>>>>Robert.
>>>
>>>I've used foxtools, installing it with the setup wizard, and haven't had a problem. However, I would doubt that the problem would be connected with the setup creation program.
>>
>>
>>hth,
>>I got it working in Windows 95 now. Foxpro Install wizard creates a registry entry as follows:
>>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\foxtools
>>Default
>>Path "C:\WINDOWS\SYSTEM\FOXTOOLS.FLL"
>>Installshield lets me use named expressions \FOXTOOLS.FLL so I was able to get it to go to the right directory in 95 and NT. NT is another issue, I get "Library File is Invalid error" and am calling Microsoft Tech on this one. The VFP setup wizard install disks give me the same error. I hunted KB at MS with no results.
>>
>>Thanks for your time, its appreciated...
>>Robert
>
>Just a passing thought on this. I wonder if the decompressing program on NT is different, and that it might be causing the problem.


hth,

Finally figured it out. When I installed the SP3 to Visual Studio the installation does not update the .dll's in the \vfp\distrib subdirectory. I found a article in KB at MS that says to delete this directory and the setup wizard would recreate it. Luckily I renamed it instead, the wizard appeared to build it, installed the updated .dll's compressed in the distribution directories but failed to recreate the distrib directory. No problem if it will always do this, maybe I'll always get the latest files.
Thanks for your help and taking the time to answer my questions. I'm sure I will have many more.

Robert