Running XP programs in wine

Dotan Cohen · Post by **Dotan Cohen** » Sat Feb 23, 2008 4:26 pm

On 21/02/2008, Alan McKinnon <[email protected]> wrote:

On Thursday 21 February 2008, Dotan Cohen wrote:
Thank you Tres. I'll start googling the topic, as until now I was
unaware of the technical details of dlls and such. If I have a legal
Windows license, then I should be able to use the dlls, no?
Not necessarily. Sometimes there are unusual conditions in the Microsoft
license for the product, and the do tend to vary a lot.

For the general case, the older the dll, the more likely it is to have a
license that simply says something like "you can use this stuff if you
paid" whereas more recent products are more likely to include bizarre
conditions like "this dll may only be used on a Microsoft platform" -
which makes usage on Wine technically violate the license.

And some dll's are freely redistributable, like the vb runtime.

In any event, you always have to read the license for the product that
supplied the dll to see what the exact license says. Assumptions can be
dangerous.

Interestingly enough, I do not have access to the EULA of my version
of Windows! I was force-sold the OS through Dell when I bought my
Inspiron laptop. There is no paper EULA, and I cannot read the version
on the disk without installing it from scratch! I wonder if this
inability to read the EULA invalidates it.

As there is no technical reason not to use the MS dll's, which may or
may not be licensed for such but MS provides no way of reading the
license, I dare to use them. Note that _all_ the software and media on
my computer are properly licensed and this is the first time in about
three years that I walk on potentially ill-licensed software. I'm no
pirate, and I expect that if a company wishes me to respect their
license, they should make the license available.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

FatButtLarry · Post by **FatButtLarry** » Sun Feb 24, 2008 12:22 am

That is a solid argument as long as you can afford to pay an attorney to say
it.

Just kidding. You'll be fine for now. I've never heard of a single person
being audited by M$ in the "dll" fashion. As long as you understand the
consequences in redistributing them to others, its a safe move.

-Tres

On Sat, Feb 23, 2008 at 4:25 PM, Dotan Cohen <[email protected]> wrote:

On 21/02/2008, Alan McKinnon <[email protected]> wrote:
On Thursday 21 February 2008, Dotan Cohen wrote:
Thank you Tres. I'll start googling the topic, as until now I was
unaware of the technical details of dlls and such. If I have a legal
Windows license, then I should be able to use the dlls, no?
Not necessarily. Sometimes there are unusual conditions in the Microsoft
license for the product, and the do tend to vary a lot.

For the general case, the older the dll, the more likely it is to have
a
license that simply says something like "you can use this stuff if you
paid" whereas more recent products are more likely to include bizarre
conditions like "this dll may only be used on a Microsoft platform" -
which makes usage on Wine technically violate the license.

And some dll's are freely redistributable, like the vb runtime.

In any event, you always have to read the license for the product that
supplied the dll to see what the exact license says. Assumptions can be
dangerous.

Interestingly enough, I do not have access to the EULA of my version
of Windows! I was force-sold the OS through Dell when I bought my
Inspiron laptop. There is no paper EULA, and I cannot read the version
on the disk without installing it from scratch! I wonder if this
inability to read the EULA invalidates it.

As there is no technical reason not to use the MS dll's, which may or
may not be licensed for such but MS provides no way of reading the
license, I dare to use them. Note that _all_ the software and media on
my computer are properly licensed and this is the first time in about
three years that I walk on potentially ill-licensed software. I'm no
pirate, and I expect that if a company wishes me to respect their
license, they should make the license available.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

Dotan Cohen · Post by **Dotan Cohen** » Sun Feb 24, 2008 4:31 pm

It turns out that my Windows installation doesn't have MSVCR80.dll
either. And this is on a system that has Vegas Movie Studio installed.
So why should the program work on Windows without the dll and not in
wine?

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

vitamin · Post by **vitamin** » Sun Feb 24, 2008 4:57 pm

Dotan Cohen wrote:It turns out that my Windows installation doesn't have MSVCR80.dll

You didn't look good enough. It won't be in system32. But either in c:\windows\winsxs (system wide install) or somewhere under c:\Program Files\...

Dotan Cohen wrote:So why should the program work on Windows without the dll and not in wine?

In most cases it won't work on windows as well.

Can you repeat again what the exact problem you have? I haven't seen one yet, except some remarks about legality of using some dlls. How did you installed your program? And how exactly you running it (exact command line from what exact directory)?

FatButtLarry · Post by **FatButtLarry** » Tue Feb 26, 2008 8:10 pm

Did you look in folders other than "system32", its most likely on that
system somewhere.

-Tres

2008/2/24 Dotan Cohen <[email protected]>:

[quote]It turns out that my Windows installation doesn't have MSVCR80.dll
either. And this is on a system that has Vegas Movie Studio installed.
So why should the program work on Windows without the dll and not in
wine?

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

Dotan Cohen · Post by **Dotan Cohen** » Wed Feb 27, 2008 4:45 am

On 27/02/2008, A. Tres Finocchiaro <[email protected]> wrote:

Did you look in folders other than "system32", its most likely on that
system somewhere.

Thanks. I found that I needed 4 dll's, and each one was in a different
place on that system. I used the Windows Search function to find them.
I put them all in ~/.wine/drive_c/windows/system32System32 and at
least I get a bit further.

feisty@feisty-laptop:~/.wine/drive_c/Program Files/Sony/Vegas Movie
Studio Platinum 8.0$ wine ./VegasMovieStudioPE80.exe
Xlib: extension "XFree86-DRI" missing on display ":1.0".
fixme:actctx:FindActCtxSectionStringW 00000000 (null) 2 L"msvcr80.dll" 0x347b6c
Xlib: extension "XFree86-DRI" missing on display ":1.0".
err:module:LdrInitializeThunk "MSVCR80.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for
L"C:\\Program Files\\Sony\\Vegas Movie Studio Platinum
8.0\\VegasMovieStudioPE80.exe" failed, status c0000142
feisty@feisty-laptop:~/.wine/drive_c/Program Files/Sony/Vegas Movie
Studio Platinum 8.0$

I also get this popup:
http://dotancohen.com/images/examples/wine_error.png

So I copied msvcr80.dll to an identical file MSVCR80.dll, and then
copied both those files to the ~/.wine/drive_c/Program
Files/Sony/Vegas Movie Studio Platinum 8.0 directory. I still get the
same error.

Any ideas on where to proceed from here? Thanks for the patience with this.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

vitamin · Post by **vitamin** » Wed Feb 27, 2008 9:19 am

Dotan Cohen wrote:Thanks. I found that I needed 4 dll's, and each one was in a different
place on that system. I used the Windows Search function to find them.
I put them all in ~/.wine/drive_c/windows/system32 and at
least I get a bit further.

You can't do that with MSVCR80.dll. Remove it from system32.

billstei · Post by **billstei** » Wed Feb 27, 2008 4:00 pm

Would it be right to assume that msvcr80.dll is properly installed by vcrun2005 via winetricks?

Bill

John Drescher · Post by **John Drescher** » Wed Feb 27, 2008 4:05 pm

On Wed, Feb 27, 2008 at 4:00 PM, billstei <[email protected]> wrote:

Would it be right to assume that msvcr80.dll is properly installed by vcrun2005 via winetricks?

That worked for me but for some unknown reason failed for the OP.

John

Dotan Cohen · Post by **Dotan Cohen** » Wed Feb 27, 2008 5:11 pm

On 27/02/2008, John Drescher <[email protected]> wrote:

On Wed, Feb 27, 2008 at 4:00 PM, billstei <[email protected]> wrote:
Would it be right to assume that msvcr80.dll is properly installed by vcrun2005 via winetricks?

That worked for me but for some unknown reason failed for the OP.

John

Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work. Not even in
a fresh ~/.wine directory. Any ideas?

I've already tried giving the user Kino, but he does not like Kino, so
this app is a must for this user.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

John Drescher · Post by **John Drescher** » Wed Feb 27, 2008 5:16 pm

Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work. Not even in
a fresh ~/.wine directory. Any ideas?

I assume you meant ~/.wine/drive_c/windows/system32 and not
~/.wine/drive_c/windows/system32System32

I've already tried giving the user Kino, but he does not like Kino, so
this app is a must for this user.

I believe the problem is the .NET2 requirement.

John

Dan Kegel · Post by **Dan Kegel** » Wed Feb 27, 2008 5:19 pm

On Wed, Feb 27, 2008 at 2:11 PM, Dotan Cohen <[email protected]> wrote:

Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work.

It's designed not to. You simply cannot copy msvcr80.dll
into plain old windows/system32. It aborts if you do.
You have to use the installer, which is what winetricks does.

Mark Knecht · Post by **Mark Knecht** » Wed Feb 27, 2008 6:41 pm

On Wed, Feb 27, 2008 at 2:19 PM, Dan Kegel <[email protected]> wrote:

On Wed, Feb 27, 2008 at 2:11 PM, Dotan Cohen <[email protected]> wrote:
Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work.
It's designed not to. You simply cannot copy msvcr80.dll
into plain old windows/system32. It aborts if you do.
You have to use the installer, which is what winetricks does.

Just as a general question, if all of this winetricks stuff is
required to run so many programs, and I think it is as almost nothing
I've ever wanted to run ran fine just installing it, then why isn't
whatever winetricks does part of the Wine install process?

If it's a matter of Wine not shipping M$ dll's and such, which I can
understand, then why doesn't the Wine installer tell us to go get a
certain set of dll's, put them in some location, and then use them?

I continue to feel that Wine handcuffs itself with all of these
problems. Just curious and ONLY my view as an end-user type.

Thanks,
Mark

Dan Kegel · Post by **Dan Kegel** » Wed Feb 27, 2008 6:53 pm

On Wed, Feb 27, 2008 at 3:41 PM, Mark Knecht <[email protected]> wrote:

Just as a general question, if all of this winetricks stuff is
required to run so many programs, and I think it is as almost nothing
I've ever wanted to run ran fine just installing it, then why isn't
whatever winetricks does part of the Wine install process?
...
I continue to feel that Wine handcuffs itself with all of these
problems. Just curious and ONLY my view as an end-user type.

winetricks is needed for two kinds of things:

1) to work around bugs in Wine (e.g. gdiplus or msxml3 not good
enough, missing wsh, etc.)

2) to work around bugs in Windows installers (e.g. app forgot to bundle vcrun6)

For #1, the right thing for Wine to do is simply fix the bugs in Wine,
rather than apply a band-aid fix. This might take a while.

For #2, the right thing to do is probably for Wine to automatically
install a few standard apps that come bundled with the needed runtime libraries.

Feel free to contribute to either effort.
- Dan

vitamin · Post by **vitamin** » Wed Feb 27, 2008 7:04 pm

Mark Knecht wrote:Just as a general question, if all of this winetricks stuff is
required to run so many programs, and I think it is as almost nothing
I've ever wanted to run ran fine just installing it, then why isn't
whatever winetricks does part of the Wine install process?

Because it's responsibility of the application installer to install all that. If it does not - in many cases it won't work on Windows. Also winetricks created so you can be told "just run this command" instead of standard windows way of 10 pages manual with 100s images showing how to move mouse and click buttons.

However the biggest problem is legal problem - you have to have valid windows license to install all those components. It's wrong to require this for every Wine installation.

James McKenzie · Post by **James McKenzie** » Wed Feb 27, 2008 9:55 pm

Dotan Cohen wrote:

On 27/02/2008, A. Tres Finocchiaro <[email protected]> wrote:

Did you look in folders other than "system32", its most likely on that
system somewhere.

Thanks. I found that I needed 4 dll's, and each one was in a different
place on that system. I used the Windows Search function to find them.
I put them all in ~/.wine/drive_c/windows/system32System32 and at
least I get a bit further.

feisty@feisty-laptop:~/.wine/drive_c/Program Files/Sony/Vegas Movie
Studio Platinum 8.0$ wine ./VegasMovieStudioPE80.exe
Xlib: extension "XFree86-DRI" missing on display ":1.0".

This was explained elsewhere, but it appears to be a faulty driver
installation. Are you absolutely sure you are using screen 1, subscreen
0? For my MacIntosh system, it is screen 0, subscreen 0. UNIX/Linux
usually starts with screen zero and counts up for each screen. Are you
using a second screen to run this program in?

fixme:actctx:FindActCtxSectionStringW 00000000 (null) 2 L"msvcr80.dll" 0x347b6c
Xlib: extension "XFree86-DRI" missing on display ":1.0".
err:module:LdrInitializeThunk "MSVCR80.dll" failed to initialize, aborting

This needs to be in the proper location.

I looked at a couple of the test .NET 2.0 installations and this is what
I came up with:

./.wine.backup.0.9.54.NET/drive_c/windows/system32/msvcr80.dll
./.wine.backup.0.9.54.NET/drive_c/windows/winsxs/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/msvcr80.dll

I think you will have to install .NET 2.0 completely in order for this
.dll to function properly. There are several things you must do in
order to make it install properly and I highly recommend visiting the
Applications Database entry for .NET 2.0 and read through the how-to on
installing.

James McKenzie

Dotan Cohen · Post by **Dotan Cohen** » Thu Feb 28, 2008 5:03 am

On 28/02/2008, John Drescher <[email protected]> wrote:

Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work. Not even in
a fresh ~/.wine directory. Any ideas?

I assume you meant ~/.wine/drive_c/windows/system32 and not

~/.wine/drive_c/windows/system32System32

Yes, that's what I meant.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

Dotan Cohen · Post by **Dotan Cohen** » Thu Feb 28, 2008 5:17 am

On 28/02/2008, Dan Kegel <[email protected]> wrote:

On Wed, Feb 27, 2008 at 2:11 PM, Dotan Cohen <[email protected]> wrote:
Even when I install MSVCR80.dll from a Windows machine into
~/.wine/drive_c/windows/system32System32 it does not work.
It's designed not to. You simply cannot copy msvcr80.dll
into plain old windows/system32. It aborts if you do.
You have to use the installer, which is what winetricks does.

Oh? I didn't realize that it could not be simply copied over to system32.

I just downloaded the latest winetricks from
http://www.kegel.com/wine/winetricks and it does _not_ have an
installed for MSVCR80.dll, and grepping the source code does not find
the string "msvcr80" in it at all.

Can I 'install' msvcr80.dll another way? If I put the file in
system32, is there a registry entry that I can add so that it will be
'installed'?

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

Dotan Cohen · Post by **Dotan Cohen** » Thu Feb 28, 2008 5:19 am

On 28/02/2008, James McKenzie <[email protected]> wrote:

feisty@feisty-laptop:~/.wine/drive_c/Program Files/Sony/Vegas Movie
Studio Platinum 8.0$ wine ./VegasMovieStudioPE80.exe
Xlib: extension "XFree86-DRI" missing on display ":1.0".
This was explained elsewhere, but it appears to be a faulty driver
installation. Are you absolutely sure you are using screen 1, subscreen
0? For my MacIntosh system, it is screen 0, subscreen 0. UNIX/Linux
usually starts with screen zero and counts up for each screen. Are you
using a second screen to run this program in?

No, I'm not sure. I simply opened Konsole and worked in there. I have
not CTRL-ALT-F'ed into any other screens (what is the correct term for
that, anyway?).

How do I check what screen I'm on?

fixme:actctx:FindActCtxSectionStringW 00000000 (null) 2 L"msvcr80.dll" 0x347b6c
Xlib: extension "XFree86-DRI" missing on display ":1.0".
err:module:LdrInitializeThunk "MSVCR80.dll" failed to initialize, aborting
This needs to be in the proper location.

I looked at a couple of the test .NET 2.0 installations and this is what
I came up with:

./.wine.backup.0.9.54.NET/drive_c/windows/system32/msvcr80.dll

I have one in there.

./.wine.backup.0.9.54.NET/drive_c/windows/winsxs/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/msvcr80.dll

I have these, none with the appropriate dll:

feisty@feisty-laptop:~/.wine/drive_c/windows/winsxs$ cd
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.100_x-ww_6818287e/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.93_x-ww_0de56c09/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.101_x-ww_6818287f/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.94_x-ww_0de56c0a/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.103_x-ww_68182881/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.95_x-ww_0de56c0b/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.104_x-ww_68182882/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.96_x-ww_0de56c0c/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.193_x-ww_68212ab8/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.97_x-ww_0de56c0d/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.98_x-ww_0de56c0e/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.99_x-ww_0de56c0f/
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.89_x-ww_0de46bd0/

I think you will have to install .NET 2.0 completely in order for this
.dll to function properly. There are several things you must do in
order to make it install properly and I highly recommend visiting the
Applications Database entry for .NET 2.0 and read through the how-to on
installing.

Thanks, I'll start googling .NET 2.0 for wine.

If I install .NET 2.0 will that install msvcr80.dll? Is there a
whatprovides service for Windows dlls?

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
×

Timeout · Post by **Timeout** » Thu Feb 28, 2008 5:42 am

Dotan Cohen wrote: No, I'm not sure. I simply opened Konsole and worked in there. I have
not CTRL-ALT-F'ed into any other screens (what is the correct term for
that, anyway?).

How do I check what screen I'm on?

The driver will be used as soon as you log on into your user access. The driver will be used as soon as you open a window under wine. This will not work unless you get an update of your video card driver (the card on which your [physical] screen is normally attached to).

Dotan Cohen wrote:
Thanks, I'll start googling .NET 2.0 for wine.

you don't need to google, the info is on the application description page of Wine. Searching for the .NET on Wine on Google, you will probably get mostly error log messages.

msvcr80.dll is already properly installed on Wine
If the net is installing something out of it, at the most in its own directory but not in sxs, but it's my own untested opinion.

John Drescher · Post by **John Drescher** » Thu Feb 28, 2008 8:31 am

I just downloaded the latest winetricks from
http://www.kegel.com/wine/winetricks and it does _not_ have an
installed for MSVCR80.dll, and grepping the source code does not find
the string "msvcr80" in it at all.

It is installed via vcrun2005
I started out with a clean .wine folder and used winetricks to install
.wine/drive_c/windows/system32/msvcr80.dll

# rm -rf .wine
localhost ~ # wineprefixcreate
libGL warning: 3D driver claims to not support visual 0x66
libGL warning: 3D driver claims to not support visual 0x66
libGL warning: 3D driver claims to not support visual 0x66
fixme:system:SetProcessDPIAware stub!
fixme:iphlpapi:NotifyAddrChange (Handle 0x789e69e8, overlapped 0x789e69cc): stub
libGL warning: 3D driver claims to not support visual 0x66
fixme

DllCanUnloadNow stub
/root/.wine updated successfully.
localhost ~ # ls .wine/drive_c/windows/system32/msvcr* -al
-rw-r--r-- 1 root root 2456 Feb 28 08:09
.wine/drive_c/windows/system32/msvcrt.dll
localhost ~ # ./winetricks vcrun2005
libGL warning: 3D driver claims to not support visual 0x66
Executing sha1sum --status -c
/root/.winetrickscache/vcrun2005/vcredist_x86.exe.sha1sum
Executing wine /root/.winetrickscache/vcrun2005/vcredist_x86.exe
libGL warning: 3D driver claims to not support visual 0x66
libGL warning: 3D driver claims to not support visual 0x66
fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP000.TMP\\" 00000000
libGL warning: 3D driver claims to not support visual 0x66
fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP001.TMP\\" 00000000
libGL warning: 3D driver claims to not support visual 0x66
fixme:advapi:LookupAccountNameW (null) L"root" (nil) 0x34f7fc (nil)
0x34f800 0x34f7f4 - stub
fixme:advapi:LookupAccountNameW (null) L"root" 0x128320 0x34f7fc
0x1245a8 0x34f800 0x34f7f4 - stub
fixme:msi:ACTION_HandleStandardAction unhandled standard action
L"SetODBCFolders"
fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10
ignored L"MsiAssembly" table values
fixme:msi:msi_unimplemented_action_stub MsiPublishAssemblies -> 10
ignored L"MsiAssembly" table values
Install of vcrun2005 done
winetricks done.
localhost ~ # ls .wine/drive_c/windows/system32/msvcr* -al
-rw-r--r-- 1 root root 626688 Sep 23 2005
.wine/drive_c/windows/system32/msvcr80.dll
-rw-r--r-- 1 root root 2456 Feb 28 08:09
.wine/drive_c/windows/system32/msvcrt.dll
localhost ~ #

John

Dan Kegel · Post by **Dan Kegel** » Thu Feb 28, 2008 8:52 am

On Thu, Feb 28, 2008 at 5:30 AM, John Drescher <[email protected]> wrote:

I just downloaded the latest winetricks from
http://www.kegel.com/wine/winetricks and it does _not_ have an
installed for MSVCR80.dll, and grepping the source code does not find
the string "msvcr80" in it at all.

It is installed via vcrun2005

Right!

I started out with a clean .wine folder and used winetricks to install
.wine/drive_c/windows/system32/msvcr80.dll

A copy does end up in there, but it's just a decoy. (Ask microsoft why,
they did it.) The real copy is buried in the winsxs directory.

# rm -rf .wine

Ack! NEVER run wine as root! It voids your warranty and stunts your growth!
- Dan

John Drescher · Post by **John Drescher** » Thu Feb 28, 2008 10:40 am

Ack! NEVER run wine as root! It voids your warranty and stunts your growth!
- Dan

I know. Its just a testing box and nothing important is installed. At
the moment it only has 2 valid logins and the other one uses kde which
is not fully installed.

John

Dan Kegel · Post by **Dan Kegel** » Thu Feb 28, 2008 10:44 am

On Thu, Feb 28, 2008 at 7:40 AM, John Drescher <[email protected]> wrote:

Ack! NEVER run wine as root! It voids your warranty and stunts your growth!
I know. Its just a testing box and nothing important is installed. At
the moment it only has 2 valid logins and the other one uses kde which
is not fully installed.

Not an excuse. Never run wine as root. It's a direct invitation to
getting rooted.

John Drescher · Post by **John Drescher** » Thu Feb 28, 2008 11:01 am

I started out with a clean .wine folder and used winetricks to install
.wine/drive_c/windows/system32/msvcr80.dll
A copy does end up in there, but it's just a decoy. (Ask microsoft why,
they did it.) The real copy is buried in the winsxs directory.

There is quite a lot installed there.

localhost winsxs # ls -alR
.:
total 2
drwxr-xr-x 9 root root 544 Feb 28 08:10 .
drwxr-xr-x 12 root root 568 Feb 28 08:10 ..
drwxr-xr-x 7 root root 464 Feb 28 08:10 Policies
drwxr-xr-x 2 root root 1096 Feb 28 08:10 manifests
drwxr-xr-x 2 root root 80 Feb 28 08:10
x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_6e805841
drwxr-xr-x 2 root root 144 Feb 28 08:10
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd
drwxr-xr-x 2 root root 336 Feb 28 08:10
x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3415f6d0
drwxr-xr-x 2 root root 176 Feb 28 08:10
x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2
drwxr-xr-x 2 root root 80 Feb 28 08:10
x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0ee63867

./Policies:
total 1
drwxr-xr-x 7 root root 464 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
drwxr-xr-x 2 root root 120 Feb 28 08:10
x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff
drwxr-xr-x 2 root root 120 Feb 28 08:10
x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773
drwxr-xr-x 2 root root 120 Feb 28 08:10
x86_policy.8.0.Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_x-ww_caeee150
drwxr-xr-x 2 root root 120 Feb 28 08:10
x86_policy.8.0.Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_x-ww_0f75c32e
drwxr-xr-x 2 root root 120 Feb 28 08:10
x86_policy.8.0.Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_x-ww_7d81c9f9

./Policies/x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff:
total 12
drwxr-xr-x 2 root root 120 Feb 28 08:10 .
drwxr-xr-x 7 root root 464 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7441 Sep 23 2005 8.0.50727.42.cat
-rw-r--r-- 1 root root 712 Sep 23 2005 8.0.50727.42.policy

./Policies/x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773:
total 12
drwxr-xr-x 2 root root 120 Feb 28 08:10 .
drwxr-xr-x 7 root root 464 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7441 Sep 23 2005 8.0.50727.42.cat
-rw-r--r-- 1 root root 712 Sep 23 2005 8.0.50727.42.policy

./Policies/x86_policy.8.0.Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_x-ww_caeee150:
total 12
drwxr-xr-x 2 root root 120 Feb 28 08:10 .
drwxr-xr-x 7 root root 464 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7447 Sep 23 2005 8.0.50727.42.cat
-rw-r--r-- 1 root root 718 Sep 23 2005 8.0.50727.42.policy

./Policies/x86_policy.8.0.Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_x-ww_0f75c32e:
total 12
drwxr-xr-x 2 root root 120 Feb 28 08:10 .
drwxr-xr-x 7 root root 464 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7441 Sep 23 2005 8.0.50727.42.cat
-rw-r--r-- 1 root root 712 Sep 23 2005 8.0.50727.42.policy

./Policies/x86_policy.8.0.Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_x-ww_7d81c9f9:
total 12
drwxr-xr-x 2 root root 120 Feb 28 08:10 .
drwxr-xr-x 7 root root 464 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7447 Sep 23 2005 8.0.50727.42.cat
-rw-r--r-- 1 root root 718 Sep 23 2005 8.0.50727.42.policy

./manifests:
total 66
drwxr-xr-x 2 root root 1096 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 7423 Sep 23 2005
x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_6e805841.cat
-rw-r--r-- 1 root root 464 Sep 23 2005
x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_6e805841.manifest
-rw-r--r-- 1 root root 7423 Sep 23 2005
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.cat
-rw-r--r-- 1 root root 1868 Sep 23 2005
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.manifest
-rw-r--r-- 1 root root 7436 Sep 23 2005
x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3415f6d0.cat
-rw-r--r-- 1 root root 1238 Sep 23 2005
x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3415f6d0.manifest
-rw-r--r-- 1 root root 7423 Sep 23 2005
x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2.cat
-rw-r--r-- 1 root root 2370 Sep 23 2005
x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2.manifest
-rw-r--r-- 1 root root 7436 Sep 23 2005
x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0ee63867.cat
-rw-r--r-- 1 root root 467 Sep 23 2005
x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0ee63867.manifest
-rw-r--r-- 1 root root 1575 Feb 28 08:09
x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.2600.2982_none_deadbeef.manifest

./x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_6e805841:
total 97
drwxr-xr-x 2 root root 80 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 95744 Sep 23 2005 ATL80.dll

./x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd:
total 1618
drwxr-xr-x 2 root root 144 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 479232 Sep 23 2005 msvcm80.dll
-rw-r--r-- 1 root root 548864 Sep 23 2005 msvcp80.dll
-rw-r--r-- 1 root root 626688 Sep 23 2005 msvcr80.dll

./x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3415f6d0:
total 481
drwxr-xr-x 2 root root 336 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 40960 Sep 23 2005 mfc80CHS.dll
-rw-r--r-- 1 root root 45056 Sep 23 2005 mfc80CHT.dll
-rw-r--r-- 1 root root 65536 Sep 23 2005 mfc80DEU.dll
-rw-r--r-- 1 root root 57344 Sep 23 2005 mfc80ENU.dll
-rw-r--r-- 1 root root 61440 Sep 23 2005 mfc80ESP.dll
-rw-r--r-- 1 root root 61440 Sep 23 2005 mfc80FRA.dll
-rw-r--r-- 1 root root 61440 Sep 23 2005 mfc80ITA.dll
-rw-r--r-- 1 root root 49152 Sep 23 2005 mfc80JPN.dll
-rw-r--r-- 1 root root 49152 Sep 23 2005 mfc80KOR.dll

./x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2:
total 2251
drwxr-xr-x 2 root root 176 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 1093632 Sep 23 2005 mfc80.dll
-rw-r--r-- 1 root root 1079808 Sep 23 2005 mfc80u.dll
-rw-r--r-- 1 root root 69632 Sep 23 2005 mfcm80.dll
-rw-r--r-- 1 root root 57344 Sep 23 2005 mfcm80u.dll

./x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0ee63867:
total 65
drwxr-xr-x 2 root root 80 Feb 28 08:10 .
drwxr-xr-x 9 root root 544 Feb 28 08:10 ..
-rw-r--r-- 1 root root 65536 Sep 23 2005 vcomp.dll

John