cc: chrisridd at mac.com
Subject: Re: Re: [ksh93-integration-discuss] [Bug 585] New: Old libtools think
OpenSolaris uses EBCDIC
--------
> Greetings, I am a Linux and Win32 developer getting interested in
> developing and porting projects using the AT&T UWin POSIX layer.
>
> I've had an hard time, though, when I tried to launch the installer of
> the uwin-base binary.
> On my development (not part of a domain) XP system, without VS,
> running as a local admin, even just running instgui.exe would cause an
> OS-generated error, stating "unable to run this application", with
> very vague directions ("reinstalling the application might solve this
> problem" - oh, really? that's what I'm trying to do...).
> I borrowed from another old XP box (with VS200x and many many other
> programs) the Dependency Walker, which reported a problem with the SxS
> (side by side assemblies) configuration specified in the manifest file
> of the program.
>
> A quick search with Google showed that binaries built using VS2008 are
> tied to the VC80 runtime (msvcr80.dll), which is quite obvious.
> What is apparently not so obvious is that said DLL cannot be
> redistributed as-is, but requires to be installed in the
> %SystemRoot%\WinSxS directory, with its catalog and other manifest
> stuff, and this is taken care of by the official way of redistributing
> the VC80 runtime (vcredist_x86.exe), publicly available for download
> at
> <http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-
> 8a4d-074b9f2bc1bf>.
>
> After installing the runtime as a SxS assembly, eventually even
> deleting the msvcr80.dll distributed in the uwin-base package, which
> is apparently completely disregarded because of the manifest embedded
> in each binary, I did get instgui.exe to run.
>
> So, I personally solved the problem (actually copying the necessary
> files from the older XP box, rather than installing and polluting the
> whole system), but you will probably want to ease that to future
> non-VS-users developers.
>
> Feel free to ask for more info if needed, as Win32 is my homeland (and
> I do know quite a lot about its quirks), and I only recently started
> using Linux.
>
> --
> CS
>
Thanks for the feedback.
I don't know very much about windows since I work primarily on
UNIX and Linux.
Currently we put a copy of msvcr80.dll in the directory where
instgui.exe gets extracted to and that seems to work for most
users.
If I understand you e-mail, mvvcr80.dll is not enough since it
neess its catalog and it manifest. Is this correct?
Do these need to be installed int the systems directory or
can they be anywhere on the PATH or in the directory where
instgui.exe is located?
Hopefully, the answer is that it can be in the instgui.exe
directory since then we can fix this by adding these
to the self extracting archive.
David Korn
dgk at research.att.com
