I have installed the IW at Win7 laptop with GeForce 9200M card. After launching the shortcut I can see the movies with logos and intro but right after that when the player closes the picture you can see in screenshot appears.
Anyone also having this issue? I have tried all solutions I could find on this forum, to no avail. Any ideas what I can do more?

Same here.
No luck so far with windows 7.
I'll try again WinXP.

Yeah I have been thinking about dualbooting too lately but its kind of counter productive and undoes the whole idea behind GOG.com.

Are you running the game as administrator? The patch may be doing something low-level to fix the game to work on a modern OS, and it's getting blocked. Try running as administrator.

Tried that too, no luck.

Can you list the things that you've tried?
"All solutions I could find on this forum" is a bit ambiguous.

Sure, I list them below, also please note the problem appears whether I use the iwar_start.exe or IWar.exe. WHen launching Defiance instead of I-War patch I get "Independence War Defiance" error msg, in exactly the same spot, right after Bink movies.
-Running with/without UAC
-running as admin
-WinXP and Win98 compability options
-alternative wrappers
-reinstalling the game, also to different folders
also I noticed I don't have the glide_wrapper.zbag.ini file in Users\[Username]\AppData\Roaming\ folder.
Hope this helps

Thanks. I also forgot to ask: What is that error message in English?
I would suggest trying to run the game in what you might refer to as "safe mode", which would be software rendering (no 3Dfx), windowed, with sound disabled. Create a new shortcut to IWar.exe, and append these command-line arguments to the Target (under file properties), similarly to this: "C:\games\I-War Deluxe\IWar.exe" -nologos -w -xsound
If by some chance that actually works, try again without the -xsound argument. If it crashes, then obviously you have a problem with the sound. If it still works, there's something funky going on when it tries to switch to full-screen mode.

I'm not sure as it is quite a time now since I used Windows in English but I think the error msg would be something along the lines of "I-War Patch caused exception and needed to close" or something along this lines. It's just the most standard Windows error msg when application misbehaves.
Your command line arguments at last got me into menus. The same error msg appears however when I try to start the mission. Last thing I see is "security chech.... please wait" loading screen. Will try those parameters together with a dgVoodoo wrapper, and post results.

Well dgVoodoo won't do anything if you use those parameters (you need -b -16), and -w only works for software rendering, but note that you can also ask dgVoodoo to run in a Window (using its own config tool), which is probably a good idea.
To be honest, if the game won't run with software rendering, I would be incredibly surprised if switching to hardware-accelerated rendering made any difference. At that point I think that all you're doing is adding additional reasons for the application to fall over. Still, do give it a try, just in case.
Read the I-War (1) Resources thread for full descriptions of the command-line options. You should probably also grab a copy of the original readme files while you're in there, and see if any of the old troubleshooting instructions are still applicable!

I finally ended up with reinstalled Win7 together with WinXP in dualboot. Now, I-War works great on both systems.

What patch are you talking about ?

The thread title is certainly a bit confusing. I believe that all it refers to is the 'description' property of the IWar.exe file, which reads "I-War Patch", and this 'description' is appearing as part of the error message when the game crashes.
I haven't installed the original game to compare, so I don't know if this was an original value, or something reflecting that GOG have modified this executable (if they have in fact done so -- that the SHIFT-Q bug fix does not rely upon the iwar_start.exe launcher program suggests that this may be the case, however).