Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP 9 SP2 Hotfix 3
- Thread starter mstrcmtr
- Start date
Olaf Doschke
Programmer
You are aware you first need to apply SP2, then the Hotfix?
You can install VFP from CD (no SP aka SP0), then install SP2 (no need to go through SP1), then the Hotfix3 (no need to go through Hotfix 1 and 2). But you cannot skip installing SP2, you cannot apply the Hotfix on VFP SP0 or SP1, that'll result in that error. When sites say you can apply the Hotfix without going through earlier Hotfixes, that doesn't say SP2 is included, it just says the fixes of Hotfix1 and 2 are included. The SP2 changes are by far bigger changes and that setup also is modifying your VFP installation without your manual intervention of copying and replacing files, so you can't expect that to be included all in just the Hotfix3. And lastly, Hotfixes then are never incorporated into SPs, so that upgrade has the manual steps and no programmatic file fixing. Notice UAC may have redirected some of your replacements into the VirtualStore folder. Applying the hotfix is far easier, if you don't install into %ProgramFiles% but into eg Users\Public\VFP9, you can use the installation interview of the CD to install into such destination folders.
Bye, Olaf.
You can install VFP from CD (no SP aka SP0), then install SP2 (no need to go through SP1), then the Hotfix3 (no need to go through Hotfix 1 and 2). But you cannot skip installing SP2, you cannot apply the Hotfix on VFP SP0 or SP1, that'll result in that error. When sites say you can apply the Hotfix without going through earlier Hotfixes, that doesn't say SP2 is included, it just says the fixes of Hotfix1 and 2 are included. The SP2 changes are by far bigger changes and that setup also is modifying your VFP installation without your manual intervention of copying and replacing files, so you can't expect that to be included all in just the Hotfix3. And lastly, Hotfixes then are never incorporated into SPs, so that upgrade has the manual steps and no programmatic file fixing. Notice UAC may have redirected some of your replacements into the VirtualStore folder. Applying the hotfix is far easier, if you don't install into %ProgramFiles% but into eg Users\Public\VFP9, you can use the installation interview of the CD to install into such destination folders.
Bye, Olaf.
- Thread starter
- #3
Olaf Doschke
Programmer
I would say this proves you haven't followed instructions of the Hotfix replacements fully or UAC redirected (some of) your replacements.
Did you once copy runtimes elsewhere, into system32 or syswow64? Then remove those. Your runtimes of the IDE installation should always be in \Program Files\Common Files\Microsoft Shared\VFP only and there you do some of the replacements of the Hotfix3 files.
And the major resource file the IDE useses and only the IDE uses, the VFP9ENU.DLL is in Home() and not in Microsoft Shared\VFP. All this and more is mentioned in the readme you read. There are no optional replacements, you obvioulsy left out something and thought you get away with it.
Bye, Olaf.
Did you once copy runtimes elsewhere, into system32 or syswow64? Then remove those. Your runtimes of the IDE installation should always be in \Program Files\Common Files\Microsoft Shared\VFP only and there you do some of the replacements of the Hotfix3 files.
And the major resource file the IDE useses and only the IDE uses, the VFP9ENU.DLL is in Home() and not in Microsoft Shared\VFP. All this and more is mentioned in the readme you read. There are no optional replacements, you obvioulsy left out something and thought you get away with it.
Bye, Olaf.
- Thread starter
- #5
Olaf Doschke
Programmer
You just proof you can't read. I talked about that folder, yes, but you highlighted the VFP9RENU.DLL while I also talked about the HOME() folder and talked about the VFP9ENU.DLL in there. The similar DLL without the R for the IDE.
The IDE does not use runtime resource DLLs, it uses the IDE resource DLLs, which are separate and since VFP8 are not available in all languages.
You have to take the readme literally. literally literally.
Bye, Olaf.
The IDE does not use runtime resource DLLs, it uses the IDE resource DLLs, which are separate and since VFP8 are not available in all languages.
You have to take the readme literally. literally literally.
Bye, Olaf.
Olaf Doschke
Programmer
And to make one more thing clear: You can't retrofit the Hotfix 3 runtimes to an already eloyed VFP application compiled in VFP9 without the hotfix.
The hotfix only is for the IDE and the deployment of fixed application has to go through the whole build and deploy process again, you have to redo a setup with the new MSM files or new runtime DLLs, but also have to recompile an EXE with the upgraded VFP9.EXE and all other upgraded files. You can't skip anything and you should also think about removing any further occurrrances of runtimes you may have put into system32 or syswow4 or anywhere at some installation, especially files, which were even registered. Also see
If all else fails, try to do all the steps on a new VM, inside there in the guest system any compromised configuration or other file of the host system will not play any role. And if you don't get it going in the VM you finally know you have misread or skipped something. And if you do the same things and it works, you at least know you are still able to read and follow instructions, but then find out what you did to compromise your host system. Removing all files of wrong versions will surely help and maybe even go with one of those often more harming than helping registry cleaners, preferrably a tool just listing deprecated entries and be able to pick only VFP related, to also remove wrong registrations of older VFP DLLs.
Bye, Olaf.
The hotfix only is for the IDE and the deployment of fixed application has to go through the whole build and deploy process again, you have to redo a setup with the new MSM files or new runtime DLLs, but also have to recompile an EXE with the upgraded VFP9.EXE and all other upgraded files. You can't skip anything and you should also think about removing any further occurrrances of runtimes you may have put into system32 or syswow4 or anywhere at some installation, especially files, which were even registered. Also see
If all else fails, try to do all the steps on a new VM, inside there in the guest system any compromised configuration or other file of the host system will not play any role. And if you don't get it going in the VM you finally know you have misread or skipped something. And if you do the same things and it works, you at least know you are still able to read and follow instructions, but then find out what you did to compromise your host system. Removing all files of wrong versions will surely help and maybe even go with one of those often more harming than helping registry cleaners, preferrably a tool just listing deprecated entries and be able to pick only VFP related, to also remove wrong registrations of older VFP DLLs.
Bye, Olaf.
- Status
Similar threads
