VB application - installer problem

[mayurvb]

I have developed a VB application and installer in InstallShield. When i try to install the application, on reboot it screws my PC.

First i get this error:

The procedure entry point SHRegGetValueW could not be located in the dynamic link library SHLWAPI.dll

Basically, simple solution, shlwapi.dll needed to be replaced. I did that, error went away.


Now laptop hangs for several minutes while trying to bring up the login screen and then pops up the message: "The Login User Interface msgina.dll failed to load."

Tried to replace msgina.dll, does nothing.

The laptop is Windows 2000. NO Service Paks installed

[Static]

http://www.microsoft.com/windows2000...ity/msgina.asp

[mayurvb]

I think the document is about how to recover from such failure. I want to know how to aviod reaching a stage where i get this error.
I forgot to mention that my installer do use some MS ocx\dll which depends on SHLWAPI.dll and i am not including SHLWAPI.dll in my setup

[Static]

I found this that mentions it as well

http://www.techimo.com/forum/t76550.html
but your best bet is to google them:

http://www.google.com/search?q=%22shlwapi.dll%22
http://www.google.com/search?hl=en&lr=&q=msgina.dll

[randem]

mayurvb,

Look in my signature for Installer Problems.

[mayurvb]

no use, just an advertisement. Is there any VB\Installer guru around. Most of the links in found on Google.com were about what to do when you come across problem, no information about how to avoid it.

[randem]

mayurvb,

That so call "advertisement" gives you info on how to avoid the problem in the first place.

[mayurvb]

randem,

i have not included those files (shlwapi.dll, msgina.dll etc) which are causing the problems. Moreover i dont have any OS dependent files as well.

[randem]

mayurvb,

How did you determine that you do not have any OS dependent files? If you did not include those files... How are they causing a problem unless some file that they are dependent on was replaced.

What files did you include?

[mayurvb]

I have included just the VB runtimes. Nothing else.

[randem]

mayurvb,

Then that is most unlikely that caused the problem. If this problem occurred when you installed your app you are including something else and do not know it. Do you have a script or list of files that are included?

[mayurvb]

I have some custom VC++ dll which i copy in my target dir.
Earlier i used to include:
comdlg32.ocx
scrrun.dll
psapi.dll

Both these files are already present with XP and 2000, so i have removed those.

Plus these VB files:
mscomct2.ocx
mscomctl.ocx
msstdfmt.dll

[randem]

mayurvb,

I see that shlwapi.dll uses OLEAUT32.DLL and this dll if wrong one used (vbruntime file) will definitely cause problems. You could download the correct vbruntime files from here

What are the dates on your vbruntime files?

[mayurvb]

Actually i use the VB runtime object provided with Installshield. the version is 2.40.4277.1
Let me know if this is the one!

Randem, i am really thankful to you for the efforts you are putting to resolve my problem.

[randem]

mayurvb,

If this is the one what? I asked what your dates are on the vbruntime files you included. Is that the version of OLEAUT32.DLL? What are the versions of the other files?

[randem]

mayurvb,

On what OS did you make your install on?

[mayurvb]

I prepare my installer on XP SP2 and the one i mentioned is the version # of OLEAUT32.dll

Here are the other runtime files and their versions:
Msvbvm60.dll
6.0.89.64

Oleaut32.dll
2.40.4277.1

Olepro32.dll
5.0.4277.1

Stdole2.tlb
2.40.4277.1

Asycfilt.dll
2.40.4277.1

Comcat.dll
4.71.1460.1

Vb5db.dll
6.0.81.69

Vb6de.dll
6.0.89.88

Vb6jp.dll
6.0.89.88

[randem]

mayurvb,

You can't use those vbruntime files. they are not universal to all OS's. Those are XP specific and is probably the reason your 2000 system crashed. Here are the correct versions:

6.0.97.82 - MSVBVM60.DLL
2.40.4275.1 - OLEAUT32.DLL
5.0.4275.1 - OLEPRO32.DLL
2.40.4275.1 - ASYCFILT.DLL
2.40.4275.1 - STDOLE2.TLB
4.71.1460.1 - COMCAT.DLL

Now, if you took the "advertisement" serious...

[mayurvb]

Actually, it crashes on XP as well. Particularly on the systems with NO SP and windows updates!
The VB runtimes are provided by Installshield VB runtime object and not collected from my PC.

[randem]

mayurvb,

OK, then that should tell you something...

[randem]

mayurvb,

Since XP comes with vb Runtime files, create your installation without then and try to install on XP. If it does not crash the system then you have your answer.

XP's version of OLEAUT32.DLL is 5.1.2600.2180

[mayurvb]

actually, we are coming to square one. The problem is with both XP and 2000 and not just XP!

[dglienna]

It seems like Installashield is the problem. Time to try Inno Setup and Inno Script.

[randem]

mayurvb,

You must read the lines not between them. If installshield is replacing the files then that's where the problem lies. That is the purpose of checking the vb runtime file versions.

I would also suggest you try a different installer. Check my signature for more info. This time read the info...

[mayurvb]

InstallShield will not replace the newer files over older one, so if XP oleaut.dll is 5.1.2600.2180 then InstallShield will not replace it.
My XP PRO SP2 shows version 5.1.2600.2180 even when i install my software many time.

[randem]

mayurvb,

Then it has to be something you are doing, some file you are replacing (including in your setup). It won't just crash by itself. You will have to re-check what you are putting into the setup.

[mayurvb]

I think i have mentioned what i am including:

comdlg32.ocx
scrrun.dll
psapi.dll

Both these files are already present with XP and 2000, so i have removed those.

Plus these VB files:
mscomct2.ocx
mscomctl.ocx
msstdfmt.dll

And some VC++ DLL, which i copy into the application path. ( these are not COM)

[randem]

mayurvb,

Some system file is being replaced or installshield would not ask you to restart.

[randem]

mayurvb,

If you send me the vbp file I will take a look.

[mayurvb]

here is the vbp file

Type=Exe
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#..\..\..\WINNT\system32\STDOLE2.TLB#OLE Automation
Reference=*\G{6B263850-900B-11D0-9484-00A0C91110ED}#1.0#0#..\..\..\WINNT\system32\MSSTDFMT.DLL#Microsoft Data Formatting Object Library 6.0 (SP4)
Reference=*\G{F5078F18-C551-11D3-89B9-0000F81FE221}#3.0#0#..\..\..\WINNT\system32\msxml3.dll#Microsoft XML, v3.0
Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.0#0; mscomctl.ocx
Object={BDC217C8-ED16-11CD-956C-0000C04E4C0A}#1.1#0; tabctl32.ocx
Object={86CF1D34-0C5F-11D2-A9FC-0000F8754DA1}#2.0#0; mscomct2.ocx
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; Comdlg32.ocx
Object={3B7C8863-D78F-101B-B9B5-04021C009402}#1.2#0; RICHTX32.OCX
Object={4413781C-C3FE-46C6-A95C-6EEF755A400F}#2.0#0; ciplImageList.ocx
Object={DA03C784-D04D-4E5A-B63C-BF6B02F07590}#2.0#0; ciplListBar.ocx
Form=frmMail.frm
Form=frmAbout.frm
Form=frmAdvReplayOptions.frm
Form=frmAlert.frm
Form=frmBeaware.frm
Form=frmCha****ch.frm
Form=frmEnterPassword.frm
Form=frmErrors.frm
Form=frmGettingStarted.frm
Form=frmHelp.frm
Form=frmLaunchedApplications.frm
Form=frmLogin.frm
Form=frmMessageBox.frm
Form=frmOptions.frm
Form=frmPicture.frm
Form=frmReplay.frm
Form=frmSlideShow.frm
Form=frmSplash.frm
Form=frmUploadInfo.frm
Form=frmURLHistory.frm
Form=frmWelcome.frm
Module=CIPLGeneral; CIPLGeneral.bas
Module=Crypto; Crypto.bas
Module=DiskSpaceRoutines; DiskSpace.bas
Module=General; General.bas
Module=Globals; Globals.bas
Module=gzip; gzip.bas
Module=Hook; Hook.bas
Module=HTML2RTF; HTML2RTF.bas
Module=ModDIBSection; ModDIBSection.bas
Module=modERRORS; modErrors.bas
Module=modToolTip; modToolTip.bas
Module=MSocketSupport; MSocketSupport.bas
Module=PictureStuff; PictureStuff.bas
Module=ProcKill; ProcKill.bas
Module=Registry; Registry.bas
Module=serial; serial.bas
Class=CApplicationPaths; CApplicationPaths.cls
Class=cDIBSection; cDIBSection.cls
Class=clsError; clsError.cls
Class=clsTooltip; clsTooltip.cls
Class=cReadWriteEasyReg; cReadWriteEasyReg.cls
Class=CSocket; CSocket.cls
Class=INIService; INIFile.cls
Class=Region; Region.cls
Form=frmWaitProcessing.frm
Form=frmMDIForm.frm
Form=frmPrivateTime.frm
IconForm="frmMDIForm"
Startup="Sub Main"
HelpFile=""
Title="BeAware"
ExeName32="BeAware.exe"
Command32=""
Name="BEAWARE"
HelpContextID="0"
CompatibleMode="0"
MajorVer=6
MinorVer=0
RevisionVer=72
AutoIncrementVer=0
ServerSupportFiles=0
CompilationType=-1
OptimizationType=2
FavorPentiumPro(tm)=0
CodeViewDebugInfo=-1
NoAliasing=0
BoundsCheck=0
OverflowCheck=0
FlPointCheck=0
FDIVCheck=0
UnroundedFP=0
StartMode=0
Unattended=0
Retained=0
ThreadPerObject=0
MaxNumberOfThreads=1
DebugStartupOption=0

[MS Transaction Server]
AutoRefresh=1

[CodeSMART]
Task_UID=12_01_04_12_53_21

[randem]

mayurvb,

I meant zip and upload it. Could you include the vbp and the exe also.

[mayurvb]

what do you want exactly? the installer?

[randem]

mayurvb,

No, Just the vbp file and the exe file you created from the vbp file.

[mayurvb]

Well, the installer is located at:
http://download.ascentive.com/BeAware.setup.exe

[randem]

mayurvb,

OK, let me put this in english... My spanish must be rusty.

The vbp and the exe you created when you compiled your code. You know the one you compiled in VB.

[mayurvb]

when i try to upload it says it is too large!

[mayurvb]

So you can use the exe from the installer and the VBP file, i have attached here!
I know winzip could not have reduced the size of the exe so you can get it from the installer.
(no problem with english! just patching up for upload limitations)

[randem]

mayurvb,

Is BeAware your program that you wrote and are trying to install?

[mayurvb]

yes, BeAware program is my program.I am working as a Project Lead for the product.
I have created the installer as well.

[randem]

mayurvb,

Then I need the BeAware.vbp and the BeAware.exe.