PDA

View Full Version : Error when finishing InstallShield.



NewsArchive
04-05-1997, 01:00 AM
I have some problems with InstallShield. It caused a GPF in KERNEL32.DLL
while it's finishing, and the main window has been closed. It caused by a
module _in0432.???. Please help me. That's nothing wrong with the IS custom
version but ISX Pro. Thanks.

Daniel Leung

E-Mail : superb@poboxes.com

NewsArchive
04-05-1997, 01:00 AM
Hi,

Follow the suggestions of the following knowledge base article to narrow
down the cause.

Sincerely,
Wen-Ting
InstallShield Tech Support

=====================================================================
Troubleshooting: Fatal Errors During Installation
=====================================================================

This document relates to the following InstallShield Express product(s):
All Express Editions
Target Platform(s): All Platforms

----------------------------------------------------------------------------
---------------------------------------------
ISSUE:
----------------------------------------------------------------------------
---------------------------------------------
My installation hangs or causes a GPF. What should I do?

----------------------------------------------------------------------------
---------------------------------------------
DISCUSSION:
----------------------------------------------------------------------------
---------------------------------------------
Below are possible reasons for the error and suggestions for eliminating
the problem:

A. A conflict with a concurrently running program such as a screen saver
or virus scanning program.

Shut down any concurrently running programs and attempt to run the
installation again. This includes any virus checking software which may be
running in the background.


B. TEMP directory related problems.


o Make sure that there is a least 500 KB of free space in the TEMP
directory. (You can find out which directory the TEMP environment variable
points to by typing "set" in a DOS window. ) If not, free up some space
and attempt to run the installation again.
o If the TEMP directory is set to a RAM drive, make sure that at least 2
MB of space is available.
o Make sure that the user has write privileges to this directory.
o Delete any InstallShield files left in this directory. If a file
cannot be deleted because it is in use, the system should immediately be
restarted, then the files deleted and the installation attempt re-tried.

The TEMP directory should be checked and cleared after every further
installation attempt until the problem is solved.


C. User does not have write privileges to the Windows or Windows\System
directory.

Make sure that the installer has write privileges to the Windows directory
and Windows\System directory. The installation program must have write
access to these directories. If necessary, a system administrator who has
the appropriate privileges may need to perform the installation.


D. Uninst.exe is read-only.

Make sure that Uninst.exe is not marked as read-only if it already exists
on the user's system. If Uninst.exe exists on the user's system, it can be
found in the Windows directory.

(Note: Some virus checking programs automatically mark all .exe files as
read-only. If Uninst.exe is found to be read-only, all virus checking
programs should be terminated before running the installation again.


E. Problem with 32-bit disk/file accessing (16-bit Windows only).

Try turning 32-bit disk or file accessing on and off. (Not all systems
have a 32-bit file accessing option.) To do this, go to the Control Panel
under 386Enh/Virtual Memory/Change and click 32-bit disk and/or file
accessing on or off. If this solves the problem, please report the problem
to InstallShield Technical Support.


F. Problem with installing Ctl3dxx.dll.

Create a dummy file with the name Noctl3d.txt in the directory with
Setup.exe and then run the installation again. If this solves the problem
contact InstallShield Technical Support.


G. A corrupt Setup.ins, Setup.exe or other installation file caused by a
media-related problem such as a corrupt diskette or hard disk.

Try using a different set of disks for the installation. If the problem
is occurring at a remote site, send the customer a set of replacement disks
and ask the customer to return the disks. If possible test the customer's
disks at the development site.


H. A corrupt Setup.ins, Setup.exe, or other installation file caused by a
non-media-related problem, such as a compiler failure.

Run ScanDisk, if available, on the system's hard drive to see if there are
any bad sectors. If necessary, fix any problems.

Copy an uncorrupted Setup.exe, _Instxx.ex_, _Setup.dll, or _Setup.lib to
the installation directory and attempt to run the installation again.

Recompile the script and try the installation with a new Setup.ins.


I. Problem with a network drive or CD-ROM drive.

If the installation is being run from a network drive or CD-ROM drive, try
the installation from a local drive.


J. A conflict with an installed driver.

Modify the Autoexec.bat and Config.sys files to load as few drivers as
possible and attempt to run the installation again.


K. A conflict with the system's hardware.

Attempt the installation on as many systems as possible. See if it runs on
any other systems. If it does, try to determine what drivers are installed
on the problem system(s).

Remove as many peripherals as possible and attempt to re-run the
installation.


L. Contact InstallShield Technical Support for further information.

----------------------------------------------------------------------------
---------------------------------------------
Article Number: X1092
Date Published: 01/31/97
Date Last Modified: 03/27/97
The information provided in the InstallShield Express Knowledge Base is
subject to change without notice and is provided "as is," without warranty
of any kind. InstallShield Corporation disclaims all warranties, either
express or implied, including the warranties of merchantability and fitness
for a particular purpose. In no event shall InstallShield or its suppliers
be liable for any damages whatsoever, including direct, indirect,
incidental, consequential, loss of business profits or special damages,
even if InstallShield Corp. or its suppliers have been advised of the
possibility of such damages.


Daniel Leung <superb@poboxes.com> wrote in article
<01bc41c8$4c72fc40$2804afca@dcpleung>...
> I have some problems with InstallShield. It caused a GPF in KERNEL32.DLL
> while it's finishing, and the main window has been closed. It caused by a
> module _in0432.???. Please help me. That's nothing wrong with the IS
custom
> version but ISX Pro. Thanks.
>
> Daniel Leung
>
> E-Mail : superb@poboxes.com
>

NewsArchive
04-06-1997, 01:00 AM
Thanks first. But the GPF caused is not during the installation. It's after
the installation. I've seen and tried the things in the article but didn't
work. Can you help me?

Daniel Leung

E-Mail : superb@poboxes.com
HomePage URL : http://superb.home.ml.org/

---

<01bc41e1$24bdd940$2fc7c5d0@WenTingTsai.installshield.com>...
> Hi,
>
> Follow the suggestions of the following knowledge base article to narrow
> down the cause.
>
> Sincerely,
> Wen-Ting
> InstallShield Tech Support

NewsArchive
04-15-1997, 12:00 AM
Hi Daniel,

Are you using a self-extracting executable? If you are,
can you check for the date of your setup.exe? Also
what is your OS? There was a problem with using
self-extracting exe with an older version of setup.exe.

Sincerely,
Wen-Ting
InstallShield Tech Support

Daniel Leung <superb@poboxes.com> wrote in article
<01bc4294$9233e9c0$6203afca@dcpleung>...
> Thanks first. But the GPF caused is not during the installation. It's
after
> the installation. I've seen and tried the things in the article but
didn't
> work. Can you help me?
>
> Daniel Leung
>
> E-Mail : superb@poboxes.com
> HomePage URL : http://superb.home.ml.org/
>
> ---
>
> <01bc41e1$24bdd940$2fc7c5d0@WenTingTsai.installshield.com>...
> > Hi,
> >
> > Follow the suggestions of the following knowledge base article to
narrow
> > down the cause.
> >
> > Sincerely,
> > Wen-Ting
> > InstallShield Tech Support
>
>

NewsArchive
05-11-1997, 12:00 AM
Wen-Ting Tsai wrote:
>
> Hi Daniel,
>
> Are you using a self-extracting executable? If you are,
> can you check for the date of your setup.exe? Also
> what is your OS? There was a problem with using
> self-extracting exe with an older version of setup.exe.
>
> Sincerely,
> Wen-Ting
> InstallShield Tech Support
>
> Daniel Leung <superb@poboxes.com> wrote in article
> <01bc4294$9233e9c0$6203afca@dcpleung>...
> > Thanks first. But the GPF caused is not during the installation. It's
> after
> > the installation. I've seen and tried the things in the article but
> didn't
> > work. Can you help me?
> >
> > Daniel Leung
> >
> > E-Mail : superb@poboxes.com
> > HomePage URL : http://superb.home.ml.org/
> >
> > ---
> >
> > <01bc41e1$24bdd940$2fc7c5d0@WenTingTsai.installshield.com>...
> > > Hi,
> > >
> > > Follow the suggestions of the following knowledge base article to
> narrow
> > > down the cause.
> > >
> > > Sincerely,
> > > Wen-Ting
> > > InstallShield Tech Support
> >
> >

Wen-Ting:

Please specify what the problems were. I am having a similar problem.
During an install I am getting the following:

Runtime Error!
Program: C:\TEMP\_INS0432._MP
abnormal program termination

Please Help. Thanks.

NewsArchive
05-13-1997, 12:00 AM
Lorne Brinkman wrote:
>
> Wen-Ting Tsai wrote:
> >
> > Hi Daniel,
> >
> > Are you using a self-extracting executable? If you are,
> > can you check for the date of your setup.exe? Also
> > what is your OS? There was a problem with using
> > self-extracting exe with an older version of setup.exe.
> >
> > Sincerely,
> > Wen-Ting
> > InstallShield Tech Support
> >
> > Daniel Leung <superb@poboxes.com> wrote in article
> > <01bc4294$9233e9c0$6203afca@dcpleung>...
> > > Thanks first. But the GPF caused is not during the installation. It's
> > after
> > > the installation. I've seen and tried the things in the article but
> > didn't
> > > work. Can you help me?
> > >
> > > Daniel Leung
> > >
> > > E-Mail : superb@poboxes.com
> > > HomePage URL : http://superb.home.ml.org/
> > >
> > > ---
> > >
> > > <01bc41e1$24bdd940$2fc7c5d0@WenTingTsai.installshield.com>...
> > > > Hi,
> > > >
> > > > Follow the suggestions of the following knowledge base article to
> > narrow
> > > > down the cause.
> > > >
> > > > Sincerely,
> > > > Wen-Ting
> > > > InstallShield Tech Support
> > >
> > >
>
> Wen-Ting:
>
> Please specify what the problems were. I am having a similar problem.
> During an install I am getting the following:
>
> Runtime Error!
> Program: C:\TEMP\_INS0432._MP
> abnormal program termination
>
> Please Help. Thanks.

Wen-Ting, are you there?

NewsArchive
05-21-1997, 12:00 AM
Lorne Brinkman <LBrinkman@aol.com> wrote in article
<3378DDDD.1415@aol.com>...
> Lorne Brinkman wrote:
> >
> > Wen-Ting Tsai wrote:
> > >
> > > Hi Daniel,
> > >
> > > Are you using a self-extracting executable? If you are,
> > > can you check for the date of your setup.exe? Also
> > > what is your OS? There was a problem with using
> > > self-extracting exe with an older version of setup.exe.
> > >
> > > Sincerely,
> > > Wen-Ting
> > > InstallShield Tech Support
> > >
> > > Daniel Leung <superb@poboxes.com> wrote in article
> > > <01bc4294$9233e9c0$6203afca@dcpleung>...
> > > > Thanks first. But the GPF caused is not during the installation.
It's
> > > after
> > > > the installation. I've seen and tried the things in the article but
> > > didn't
> > > > work. Can you help me?
> > > >
> > > > Daniel Leung
> > > >
> > > > E-Mail : superb@poboxes.com
> > > > HomePage URL : http://superb.home.ml.org/
> > > >
> > > > ---
> > > >
> > > > <01bc41e1$24bdd940$2fc7c5d0@WenTingTsai.installshield.com>...
> > > > > Hi,
> > > > >
> > > > > Follow the suggestions of the following knowledge base article to
> > > narrow
> > > > > down the cause.
> > > > >
> > > > > Sincerely,
> > > > > Wen-Ting
> > > > > InstallShield Tech Support
> > > >
> > > >
> >
> > Wen-Ting:
> >
> > Please specify what the problems were. I am having a similar problem.
> > During an install I am getting the following:
> >
> > Runtime Error!
> > Program: C:\TEMP\_INS0432._MP
> > abnormal program termination
> >
> > Please Help. Thanks.
>
> Wen-Ting, are you there?
>

Well, I guess not.