Regarding the possibility of one vcredist installation overwriting another.
Roland Knall wrote;
"[i]After installing Dragon Age into the same Steam bottle, Torchlight had been installed, Torchlight crashed immediatly after clicking on the icon. What resolved this issue was, that I went to the torchlight folder in the bottle: /home/<username>/.cxgames/default/drive_c/Program\ Files/Steam/SteamApps/common/torchlight/ and executed the vcredist_x86.exe
I installed the executable into the bottle again, just as you would install a game (not listed) into the same bottle
The reason for this is, that other games might overwrite the Visual C Runtime library upon installation. Torchlight does not seem to like that very much.[/i]"
citing: http://www.codeweavers.com/compatibility/browse/name/?app_id=6534;tips=1
One of our Indomitable Ninjas encouraged me to chase the what of this
down - by the sounds of it, something's going awry here (at install
time) and/or something else might be at play. Even though here we're
specifically touching on the Steam release, with the advent of the c4p
system and so on, and in the interests of making CXG get things like
'right' the first time, we need a bit more testing done to properly
conclude the position here....
The above may be happening, but obviously it's hard for me to conclude
either way without the game myself to test. The filename 'vcredist_x86.exe'
is really indescript - this name could refer to vcrun2005, vcrun2005SP1,
vcrun2008, the SP1 for the 2008 redist...or even vcrun6...it's kind of
like saying "I have a car" without saying which make and model it is...
Afaik, the registry uninstall tag is used to identify whether or not a
certain support dependency package is present or not. With this in mind,
let's just hypothesize the vcredist_x86.exe (the one that's distributed
with the Steam version of the game) is in fact vcrun2008. Now, the install
target in CXG for Microsoft Visual C++ 2008 Redist is actually vcrun2008SP1.
As a service pack upgrade typically supercedes/replaces the previous version,
if you already had vcrun2008SP1 installed, the installer is unlikely to install
the earlier version, as it's already detected the newer SP1 version installed.
On the other hand....if you didn't have vcrun2008 installed, you would have to
install it (or the installer might do it for you in the background), as no
installed version exists. If this were the case, and another program went to
install the vcrun2008SP1 package, that will probably proceed and replace the
previously installed version with the SP1 updated package....
..in a perfect world, everything done to a service pack upgrade should have it
remain backwards compatible with the previous version, so the SP release(s) don't
go on to break every program based on the previous runtime version(s)...
There is no perfect world here - if Torchlight absolutely needs the version
of vcrun that it ships with, that will be something of an issue in the cases
where Torchlight is part of a Steam bottle installation and/or part of a single
bottle containing more than one game. If you have Torchlight installed into it's
own bottle, you won't have problems with one vcrun overwriting another - just
remember this situation exists and don't install another vcrun into this bottle B)
For Steam and multigame bottle installs, if Torchlight really needs the vcrun it
ships with, probably the easiest away around any possible issues here, would be to
install the vcrun redist shipped with the game into a fresh clean new bottle, and
copy the dll files required into Torchlight's base $installdir -- by doing this, the
search path for required dll's will hit these copies first and load them, regardless
of what may be installed in the bottle's ../../windows/system32/ location. In this
way, you can avoid any possible conflicts/troubles regarding dll versions being used..
@Mr. M -- seeing as you offered..."Your mission, should you decide to accept it.."
-
Create a new bottle, give it a name , winxp profile, install other software,
install the vcredist_x86.exe package that ships with the Steam installation.
-
Then run the following command;
~/cxgames/bin/wine --bottle <bottle-name> uninstaller.exe --list
You should see something like;
bash-3.2$ ~/cxgames/bin/wine --bottle NewBottle uninstaller.exe --list
CXHTML|||CrossOver HTML engine
{7299052b-02a4-4627-81f2-1818da5d550d}|||Microsoft Visual C++ 2005 Redistributable
{9A25302D-30C0-39D9-BD6F-21E6EC160475}|||Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
-
Post that output back here to properly identify the 'vcredist_x86.exe' package
-
Try to ascertain whether Torchlight requires that specific version of
vcrun or not, or if the nearest available vcrun install target in CXG
works or not with this title without issues.
Oh, btw, there's a bit of reading on Torchlight over at WineHQ...see;
http://appdb.winehq.org/objectManager.php?sClass=version&iId=18314
Cheers!