cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
DmitryV
Level 3

Vista built setup vs XP \winhttp.dll

Hi All!

I have built the setup for my application on Vista PC. My application requirements are NET Framework 3, Jet 4., MDAC.In the Installation Designer of IS2008 I selected the NT,XP,W2000,MS2003 and Vista as target Operation Systems.

After installation of my application on XP PCs (all-XP SP2), for part PCs several other applications (i.e. MS Messenger) put following error messages "The procedure entry point strncpy_s could not be located in the dynamic link library msvcrt.dll". (Not for all XP PC, some XP PC only).Vista PCs do not issue this error (or I have a little statistic sample).
The same application setup package which was built on XP PC (IS 11.5) did not lead to erros/warnings from other applications.

First impression is what Vista built setup damages some XP dll-s(i.e winhttp.dll).
(Or I confused:confused: )

Empirical solution: overwrite system32\winhttp.dll , reverte to the old version of 'winhttp.dll" in system32 folder and it seems to have solved the problem.

Any ideas?

Thanks in Advance

Dmitry
Labels (1)
0 Kudos
(2) Replies
MichaelU
Level 12 Flexeran
Level 12 Flexeran

Are you explicitly including winhttp.dll in your installation, or is it being pulled in by a dependency scan at build? If the former, this should be trivial to fix, and if the latter it's still easy but also might represent a bug on our end. For the latter case, please see the file Filters.xml in the help, stored in the support folder of the IS2008 installation.

My copy of Filters.xml includes a block for winhttp.dll, so I suspect your installation is explicitly including this file (as the filtering only applies for files added due to depenendency scans and the like).
0 Kudos
DmitryV
Level 3

Thanks!
My setup does not explicity include winhttp.dll.

I 'll check the content of Filters.xml
0 Kudos