Page 1 of 2

MP 0.2 on Windows relied on VS2005 runtime?

Posted: Fri Sep 25, 2009 2:10 pm
by Killua
I get this error on win 7....

Error: The Side-by-Side configuration information for "xnview.exe" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).

Does Windows version complied on VS2005 without using static link library (to eliminate the dependence of VS2005 Redistributable Package)?
And Would there be x64 version for better system integration?

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Fri Sep 25, 2009 2:57 pm
by xnview
Killua wrote:I get this error on win 7....
A crash?
Does Windows version complied on VS2005 without using static link library (to eliminate the dependence of VS2005 Redistributable Package)?
All needed library are in the package (i hope)
And Would there be x64 version for better system integration?
Yes, i'll make a x64 bits version later

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Fri Sep 25, 2009 7:08 pm
by helmut
I also experience problems on Windows (XP SP3). When starting, an error message is displayed:

C:\Programme\XnViewMP\xnview.exe
Diese Anwendung konnte nicht gestartet werden, weil die Anwendungskonfiguration nicht korrekt ist. Zur Problembehebung sollten Sie die Anwendung neu installieren.


Rough translation:
C:\Program Files\XnViewMP\xnview.exe
This application could not be executed because the application configuration is not correct. For solving this problem please reinstall the application."

Manifest version numbers don't match

Posted: Fri Sep 25, 2009 8:12 pm
by marsh
Manifest version numbers don't match. Just for curiousity's sake, here is what 'wine' said:
$ wine xnview.exe
fixme:actctx:parse_assembly_elem wrong version for assembly manifest: 8.0.50727.762 / 8.0.50727.42
fixme:actctx:parse_manifest_buffer failed to parse manifest L"D:\\xnviewqt\\Microsoft.VC80.OpenMP.manifest"
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.OpenMP" (8.0.50727.762)
err:module:attach_process_dlls "vcomp.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"D:\\xnviewqt\\xnview.exe" failed, status c0000142

Re: XnViewMP beta 0.20

Posted: Fri Sep 25, 2009 8:46 pm
by Clo
:arrow: Pierre

:) Hello !

• Sorry, I can't start this 20 MP version at all, I get only the message below :

ImageImage

• Same mess from a button of Total Commander,
except that I get only the internal T.C. error message “Error executing program!

- Installed from the ZIP archive downloaded @ 22:30 … :(

Win XP-Pro SP1 (FR) - 1 Gio RAM - Intel Celeron 2.4 GHz…

:mrgreen: KR
Claude
Clo

Re: XnViewMP beta 0.20

Posted: Fri Sep 25, 2009 9:03 pm
by ouistiti
3 lancements défectueux : xnview.exe a rencontré un problème et doit fermer. Nous vous prions de nous excuser pour le désagrément encouru.

Au 4ème : idem mais :
Signature de l'erreur
AppName: xnview.exe AppVer: 0.0.0.0 ModName: ntdll.dll
ModVer: 5.1.2600.5512 Offset: 00011669


Au 5ème : Je parviens à changer de répertoire et enfin cela fonctionne.
Mais replantage quand je vais sur le répertoire de départ (C'est le répertoire avec mes images de test, il fonctionne parfaitement avec la version 1.96.5) Le plantage semble être dû à un fichier, mais lequel ? et ma mémoire utilisée passe de 51% à 99%)

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Fri Sep 25, 2009 9:13 pm
by Clo
:arrow: helmut

• Hi !

SAME PROBLEM HERE, the message from Win (thus, in French) is exactly the same… Impossible to start the programme.

:mrgreen: G.
Claude
Clo
Note : Sorry for the wrong location of the linked posts, please move them.

Re: XnViewMP beta 0.20

Posted: Fri Sep 25, 2009 9:48 pm
by Clo
:arrow: XnTriq

:) Hello W. !

• Below, the Paul's message in English …
3 start failures : «Xnview.exe has encountered a problem and must be closed… blah blah…»

At the 4th. start attempt : Same but with
Error signature
AppName: xnview.exe AppVer: 0.0.0.0 ModName: ntdll.dll
ModVer: 5.1.2600.5512 Offset: 00011669


At the 5th. try : I succeed in changing the directory and finally it works.
But it crashes again when I come back into my start folder (It's the folder which contains my test images, all work perfectly with 1.96.5). It seems that the crash is due to some image file, but which one ? When crashing, the 51% normal used memory grows up to 99%)
:mrgreen: KR
Claude
Clo

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sat Sep 26, 2009 8:06 am
by jgutierrez
Same problem here under Win 7 x64.
Image
Image

Re: Manifest version numbers don't match

Posted: Sat Sep 26, 2009 9:57 am
by oops66
marsh wrote:Manifest version numbers don't match. Just for curiousity's sake, here is what 'wine' said:
$ wine xnview.exe
fixme:actctx:parse_assembly_elem wrong version for assembly manifest: 8.0.50727.762 / 8.0.50727.42
fixme:actctx:parse_manifest_buffer failed to parse manifest L"D:\\xnviewqt\\Microsoft.VC80.OpenMP.manifest"
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.OpenMP" (8.0.50727.762)
err:module:attach_process_dlls "vcomp.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"D:\\xnviewqt\\xnview.exe" failed, status c0000142
Hello,
For Information ( under wine too, v1.1.29) I have almost the same errors messages plus the ALSA_MixerInit message:
$ wine xnview.exe
fixme:actctx:parse_assembly_elem wrong version for assembly manifest: 8.0.50727.762 / 8.0.50727.42
fixme:actctx:parse_manifest_buffer failed to parse manifest L"Z:\\XnViewMP-0.20\\Microsoft.VC80.OpenMP.manifest"
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.OpenMP" (8.0.50727.762)
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer
err:module:attach_process_dlls "vcomp.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"Z:\\XnViewMP-0.20\\xnview.exe" failed, status c0000142

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sat Sep 26, 2009 10:57 am
by jgutierrez
After some investigations it seems the problem is a mismatch between the OpenMP manifest, and the libray (vcomp.dll).
Also, why not compiling with VC++ 2008 instead of 2005 Pierre? Maybe a performance increase could be achieved by the upgrade.

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sat Sep 26, 2009 1:45 pm
by Killua
jgutierrez wrote:Same problem here under Win 7 x64.
Yes, MP could start after install VS2005 SP1 Redistributable Package (x86).

However, It could be avoided when using static linking (/MT or /MTd) instead of dynamic linking (/MD or /MDd)
http://msdn.microsoft.com/en-us/library ... 80%29.aspx

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sat Sep 26, 2009 4:44 pm
by jgutierrez
That only applies to the C/C++ Runtime Library, and unfortunatelly is not valid to OpenMP (even in 9.0 it is not possible to statically link it to my knowledge), but at least would be a good choice for MSVCRT (I believe it will overall decrease the size of the distribution).

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sun Sep 27, 2009 10:24 am
by jgutierrez
Meanwhile Pierre fixes the OpenMP deployment problem, I have uploaded to my personal site the propper OpenMP manifest file from Visaul C++ 2005 SP1, that works fine with the supplied DLL.

You only need to download the file, replace your existing one, and it will work fine.

Reach it at http://guti.bitacoras.com/_temp/upload/ ... P.manifest

Re: MP 0.2 on Windows relied on VS2005 runtime?

Posted: Sun Sep 27, 2009 7:24 pm
by Clo
:arrow: jgutierrez

:) Hello !

• Thanks, I updated the file, unfortunately that doesn't work either, still the same error message than above… :(

:mrgreen: KR
Claude
Clo