Debugging a Win32 installer
To view or capture the debug output from a Win32 installer, hold down
the <CTRL> key immediately after launching the installer and until a
console window appears. Before exiting the installer, copy the console
output to a text file for later review.
On some Windows NT systems, run the installer once with the <CTRL> key
down, resetting the scroll back buffer for the console window, then quit
and run the installation again.
If there are problems capturing the console output, try a slightly more
convoluted method (this will often be the case on Win9x because of the
limited ability of the console to capture output). First launch the
installer and allow it to extract the necessary files. Once it reaches
the "Preparing to Install..." window, when given the opportunity to
choose a language or to go to the Windows "temp" directory, look for a
temp folder which starts with an 'I" followed by many numeric digits
(ex. I1063988642). Be sure it is the most recent directory, by sorting
the directories by their "modified" date. Open the directory, there
should be a file called "sea_loc". Delete this file. Now go back to the
installer, click OK, and at the first opportunity, cancel the
installation.
Now go back to the directory inside the temp directory, where the file
"sea_loc" was deleted. There should be another directory called
"Windows"; open it. There should be an .exe file (most likely
"install.exe"). There should also be another file with the same name
except it will have a .lax extension. Open it with a plain text editor
and edit the lines:
lax.stderr.redirect= AND lax.stdout.redirect= to be:
lax.stderr.redirect=output.txt AND lax.stdout.redirect=output.txt
After these changes have been made, save the file and launch the .exe.
When the installation is complete there should be an output.txt file in
the same directory as the .lax file. The output.txt file will contain
the same information as that generated to the console.
On Mon, 2004-02-23 at 15:34, Andrew Scott wrote:
> No total fresh install, the first thing I would like to install is
> coldfsuion but no luck on that.
>
> Regards
> Andrew Scott
> Technical Consultant
>
> NuSphere Pty Ltd
> Level 2/33 Bank Street
> South Melbourne, Victoria, 3205
>
> Phone: 03 9686 0485 - Fax: 03 9699 7976
>
>
> _____
>
> From: Rob Rohan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 24 February 2004 10:31 AM
> To: CF-Talk
> Subject: Re: CF MX 6.1 install problem with installanywhere
>
>
> Do you have virus scanning software on that server and active during
> install? I've had installs barf on me because of that.
>
> On Mon, 2004-02-23 at 15:25, Andrew Scott wrote:
> > Hoping that someone might be able to shed some light on a problem I am
> > having, have installed coldfusion a number of times in the last 8 years,
> but
> > have never come across this. When trying to install CF MX 6.1 on a Windows
> > 2000 server, it is trying to extract the files after it gets to 100% on
> this
> > server it stops no error nothing. I can't even find a file to tell me why
> it
> > hasn't gone any further.
> >
> > This is a new install of Windows 2000 server, has been patched to server
> > pack 4 and has all the security updates/patches from Microsoft installed.
> I
> > must be missing something, I can run the same file on a Windows 2000
> Server
> > elsewhere and it will try to install, I can even run the install on
> Windows
> > XP Professional and it will try to install. Just not on this server!
> >
> > Has anyone got any clues, ideas what might be wrong. I thought about
> > permissions, but this is a total fresh install formatted hard drive on
> > install of windows 2000 server. I am totally stumped for ideas and
> solutions
> > to this.
> >
> >
> >
> > Regards
> > Andrew Scott
> > Technical Consultant
> >
> > NuSphere Pty Ltd
> > Level 2/33 Bank Street
> > South Melbourne, Victoria, 3205
> >
> > Phone: 03 9686 0485 - Fax: 03 9699 7976
> >
> >
> >
> >
> _____
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
