Dmitry wrote:
> Error Dialog Box contain "Application not run, because not correct tuning.
> Reinstal application ..."
Yes, I think one essentially gets that error when not
the Manifest/SxS stuff comes up.
Other messages I've seen:
The system cannot execute the specified program.
C Runtime Error R6034
I ran into these back in October 2006 with one of my customers
trying to help the compile a (non-FLTK) CLI tool that used
ILM's EXR image library. It unfortunately /had/ to be compiled
under VS Express, due to EXR's use of template features the older
VS .NET compiler did not support.
Here's what I wrote to the customer after they sent me some
of the above error messages (links shown here still work):
---------------------------------------------------------------------------------------
> > Greg wrote:
> > Ya, it sounds like the problem we encountered is exactly what
> > this Microsoft page describes:
> > http://msdn2.microsoft.com/en-us/library/ms235560.aspx
> >
> > ..and that this page describes as the solution:
> > http://msdn2.microsoft.com/en-us/library/ms235624.aspx
> >
> > Sounds like 2005 compiler needs to generate 'manifests' ..
> > [I'll read all this and get back to you.]
As the "Family Guy" would say.. oh my freaking god.
That little Microsoft document fans out into about a hundred little
sub-documents on this whole 'manifest' subject, replete with XML
examples and the usual Microsoft meaningless hex codes. I love it
when they actually /document/ stuff like this:
"The dependent side-by-side assembly can be installed as either
a shared assembly or as a private assembly. For example, Visual
Studio 2005 installs the CRT assembly as a shared side-by-side assembly
which can be found in the directory
%WINDIR%\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50608.0_x-ww_b7acac55.
..riiight. And it goes on:
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.42"
processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<file name="msvcr80.dll" hash="3ca5156e8212449db6c622c3d10f37d9adb12c66"
hashalg="SHA1"/>
<file name="msvcp80.dll" hash="92cf8a9bb066aea821d324ca4695c69e55b27cff"
hashalg="SHA1"/>
<file name="msvcm80.dll" hash="7daa93e1195940502491c987ff372190bf199395"
hashalg="SHA1"/>
yeesh. I'm printing this all out now for reading. Jesus, wotta mess.
* * *
> Hi Greg,
> >
> > So I just found some time to run the test below.
> > All three attempts fail. See the message below.
Three other things to try, in this order:
1) In the C:\temp\ directory, create a subdir
called "WinSxS", copy the dll's in there,
then try running the app again.
2) Copy the DLLs to the c:\windows\system32\
*and* to the c:\windows\WinSxS\ directory (if it exists)
and retry the test (rename away any existing dlls)
then try running the app again.
3) If neither 1 or 2 work, I hesitate to suggest you download
and run this executable from microsoft [which will update
the OS to support the SxS stuff]:
http://go.microsoft.com/fwlink/?linkid=65127&clcid=0x409
..then try running the original app again.
What XP service pack are you on? I'm on SP2.
---------------------------------------------------------------------------------------
As I recall, with some kanoodling, it was made to work.
But because they were deploying the executable in question
to a render farm of 400 machines, installing that little Microsoft MSI file
that tweaked the OS proved maddening, since it had a GUI that apparently
could not be automated, and thus had to be run by hand on each machine.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
