Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Installation Where Windows .DLL May Need Updating
Message
De
14/07/2000 09:55:10
 
 
À
14/07/2000 06:12:35
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Divers
Thread ID:
00392294
Message ID:
00392357
Vues:
8
>I have an application which is distributed in an InstallShield setup. It has become apparent that for one part of it to work, the file WSOCK32.DLL in the Windows System directory needs to be at least a certain version.
>
>I can get to that version by manually installing DUN 1.3, but that is really an overkill, and not suitable for silently doing as part of a user driven installation.
>
>So my question is; can I copy a good version of WSOCK32.DLL into the install, and let IS install and register it, or are other files related to it and need doing at the same time? Also what are any MS License implications to doing this?
>

I think that you can just copy that dll, but I would try it on a test machine first, to make sure you don't hose anything else. You should also be aware that trying this on a Windows 2000 machine, you will have to go to considerably more trouble to overwrite a system file, because Win2K repairs itself from backup files. To copy over a system file, you fiest must replace that file in Windows' backup directory (don't ask me the exact path, I don't remember- you'll have to do some research :-)), delete the file you are trying to overwrite, and then reboot or somesuch. Windows then tries to repair itself by copying your file back over it's missing file. At least this is how I remember that the procedure goes- you'll want to verify all this. But I thought you should know it's not such a simple process.
Erik Moore
Clientelligence
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform