View Full Version : Merge module for Microsoft C++ Runtime library bug??
02-08-2002, 12:09 PM
My installation contains Merge module for Microsoft C++ Runtime library bug, when I install prodict on NT machine, I felt that mege module is not installed properly.
is there any known bug with merge module with NT platform though it is working fine on 2000 machine.
Help will be really appreciated..
02-08-2002, 03:36 PM
First of all, you shouldn't even be installing msvcrt.dll from the merge module on a Windows 2000 system because it's a protected system file - it's part of the OS.
Second, what makes you think there's a bug in the merge module when you install it on an NT system?
02-08-2002, 03:48 PM
Merge module included in my project has version number 6.0 while after installing I checked the file version n it is 5.0. That's why I am thinking it's not getting installed or it is getting installed in non-system directory which seems wrong as it is system file and should be installed in system directory.
am I right?
N you are saying that this file should not be installed as it is protected system file. But some files in my product is dependent on this file and if I don't install this file, some feature in my application is not working properly if it is installed on fresh machine.
Do you have any suggestion regarding this.
Thanks for yr help.
02-08-2002, 04:11 PM
I'm saying that you don't install msvcrt.dll on Windows 2000. It's part of the operating system. It's always there and is updated by service packs etc, not by you. You do not need to install it on Windows 2000. Like kernel32.dll, it is always there.
On NT, check very carefully that you are in fact installing the merge module and that you're installing to the merge module destination, which should be the Windows system directory. What version are you checking that says 5.0? Could it be the one in Windows System folder but you're installing a copy to your application folder?
02-08-2002, 04:27 PM
Thanks for quick response.
I got you regarding 2000. I have to tell user that update their system to latest 2000 service pack before installing product.
Now about NT, can we do the same thing. That means, does NT latest Sp contains this file or not?
In previous mail, version I checked that was a one of attributes in properties n that is 5.0.
I also checked merge modules default destination using ORCA tool n it is system folder. But due to some reason that is installed in product installation directory.
If anything can be done regarding this?. I am using merge modules provided by Installshield with ISWI 2.03.
02-08-2002, 04:37 PM
>>> I have to tell user that update their system to latest 2000 service pack before installing product.
But only if your product requires the latest and greatest msvcrt.dll. Thjis Dll is fairly stable, I'd be surprised if your app was using brand new functionality in msvcrt.dll.
>>>But due to some reason that is installed in product installation directory.
You must say in InstallShield that the merge module should be installed to the merge module's destination. It's a choice in the IDE somewhere in the merge module properties.
>>>Now about NT, can we do the same thing. That means, does NT latest Sp contains this file or not?
Doesn't matter. You can install this on NT and if your version is newer it will update NT, if NT's version is newer your version won't be installed, which is the right way for it all to work. NT does not have protected files, so it's ok for you to just install it.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.