Script Causes IE8 Problems

Started by Randem, August 18, 2011, 01:59:05 AM

Previous topic - Next topic

Randem

Here's an idea, your system could be infected so check this:
 
Open IE go to Manage Add-ons, Note all the add-ons that you have listed. Install your app then check the add-ons again to see if anything has changed. It is possible that you have a browser hi-jack going on...
 
More info and Help https://randemsystems.support/expert-computer-repair/virus-problems/

Randem

Not a clue. Hopefully you are not using your development system to test on...

Tom Buggy

Thanks - that's good to know from an isolation standpoint.  Any ideas about possible problems on my system?

Randem

Installed the application on clean Windows XP (32 bit) and Windows 7 (64bit) and neither had a problem with IE8. So I suspect that the system you are installing this on has a problem, it is certainly not the installation.

Tom Buggy

I realize that you didn't say that removing the MDAC folder would solve the IE8 problem, but I thought I'd see if it did.
 
The installation file has been uploaded via FTP.  Thanks for your support (and patience!).

Randem

I did not say that removing the MDAC folder would change the IE problem, just that the folder was not needed and made the installation greatly over-sized.
 
You cannot upload exe files here, you need to zip it first.

Tom Buggy

I removed the MDAC folder from the script, recompiled, and did a new installation.  The IE8 problem remained.
 
The attached file is the installation.  Note that after installation you will not be able to run the program.  It's an update version and does not contain the skeleton database files included in versions sent to new users.

Randem

That MDAC folder has no need to be deployed...

Tom Buggy

The IE8 problem occurs after installation and before running the app.  After reinstalling IE8 there are no problems running IE8 or the app.
 
Contents of the MDAC folder:
MDAC.typ (Version 27.0.77134)
VB_DCOM_MDAC_JET_AutoSetup
VB_DCOM_MDAC_JET_AutoSetup_XP
WindowsXP_Windows2000_Script56_KB917344_x86_enu (Version 5.50.4134.600)

Randem

Also does IE have problems immediately after installation or after running the application for the first time? Have you tried to run IE after installation and before running the application?
 
I could install your installation to see what I can detect if you like...

Randem

I have provided two lines from your script that show that yo are deploying the same file and overwriting itself... not the IE problem but should be a concern if you have two different version of the exe...
 
It does not look as if the line you showed could be a factor, One is I have no idea of what files you are coping to the destination and secondly unless you are using a file in that location that conflicts with IE I have no way of telling. What is in the MDAC folder you are coping?

Tom Buggy

Dymolbl.exe is deployed only once.  The files deployed from Program FilesDYMO Label are labels.def and labels.dll.
 
Back to the original problem, I have verified that installing the app definitely causes the IE8 problem.  Could the following in the script be a factor?
 
C:MDAC*.*; DestDir: {cf}SportsWare Ltd.ReleaseMDAC; Flags: ignoreversion recursesubdirs

Randem

You are correct, perhaps it was something else...
Are you aware you are deploying a file twice to the same location from two different locations? Otherwise I do not see anything that would be causing any issues with Internet Explorer.
 
Source: C:Program FilesMicrosoft Visual Studiovb98Package (6)GHMXPSupportDymolbl.exe; DestDir: {app}; Flags:  ignoreversion;
 
Source: C:Program FilesDYMO LabelDymolbl.exe; DestDir: {app}; Flags:  restartreplace sharedfile;

Tom Buggy

I don't see a labels.exe file in the script.  The Dymolbl.exe file is targeted to {app}.  The label.def and label.dll files are targeted to {sys}.

Randem

Oh, I remember now. You can't put the label.exe file in the {sys} folder. You are overwriting the Windows lable.exe file and that will certainly cause you issues down the road.
 
Also, on what machine are you testing on? hopefully not your development machine. You should be using a Virtual Machine to test on - Microsoft Virtual PC 2007