1% is not a valid Win32 application when running the exe.

Got a problem you cannot solve? Try here.
Post Reply
CBelanger
Posts: 15
Joined: Thu Mar 05, 2009 6:19 pm

1% is not a valid Win32 application when running the exe.

Post by CBelanger »

Hello:

Just about finished with my first use of InstallAware 8 and when running the standalone exe, it shows the file extraction progress bar, then the following message comes up:

1% is not a valid Win32 application

I googled this and there was one thread about this and the user thought that maybe his icons were the problem. That thread ended without noting a resolution, so I'm wondering what became of the issue, especially since I am experiencing this, too. Also, I have a custom icon.

I have a BMP splash screen that should pop up at first. This installation works fine when run in the IDE.

Anything else I should look for?

Thanks,

Chuck Belanger
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

We'll need a reproducible project.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
CBelanger
Posts: 15
Joined: Thu Mar 05, 2009 6:19 pm

Post by CBelanger »

Based on the previous discussion about icons, I looked at the Creatives list and there was added "icon.ico". I deleted that and all worked fine.

I'm assuming InstallAware added this default icon.

Thanks and hope that helps.

Chuck
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

That would imply your custom setup icon corrupted the setup file somehow. You can try using another icon or stick to the default InstallAware icon.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
SteveDude
Posts: 253
Joined: Wed Apr 11, 2007 6:07 pm

...

Post by SteveDude »

I have run into this problem as well with BMP's and seems to have something to do with the bit depth. Just haven't figured out which one is actually causing the problem. Sometimes just opening and saving the bitmap again from your preferred editor will solve the problem.

Also when I use an custom icon I make sure there are only two in the file, 1 16x16 and one 32x32 each at 256 colors or True Color. The problem with True color is you get a dithered look on some users machines.
[email protected]
Posts: 1
Joined: Tue Jul 07, 2009 5:51 am

Also got this error right out of the box

Post by [email protected] »

I created a simple setup and all icons working just fine. I even removed the icons. I still get this error: %1 is not a valid Win32 Application.

There is nothing special I am doing. Just set up a simple win32 application.
dunion
Posts: 106
Joined: Tue Oct 14, 2008 10:43 am

Re: 1% is not a valid Win32 application when running the exe

Post by dunion »

Does anyone know if this problem is supposed to be fixed in the (licensed version) of IA9 R2? I just tried it and on Win7 I am seeing this behavior. Is there a very specific Icon format that will mitigate this (such as a color depth, size, etc.)? Thanks.
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Re: 1% is not a valid Win32 application when running the exe

Post by MichaelNesmith »

Can anybody affected by this issue send a minimum setup with just the icon and file it points to, so we can check this issue in house?
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
dunion
Posts: 106
Joined: Tue Oct 14, 2008 10:43 am

Re: 1% is not a valid Win32 application when running the exe

Post by dunion »

This stopped happening for me when I did two things. First I installed R2. Then I started the project over again (new directory). Closed it, copied the dialogs and other 'stuff' from the first project, re-opened it; manually edited the MSI file for the changes I needed and re-selected the project dependencies and merge modules. Then all was well. So it seemed it was some bug in the prior version.

There had been some work-arounds that were no longer needed with R2 so that was a good time to clean those up too.
Post Reply