Install LabSim Client (from testout.com) in WINE

kasl33 · 09-01-2011, 01:00 PM

Has anybody here successfully been able to install the LabSim client? This one program is the one and only reason that I need Windows - which I am currently running in a VMware virtual machine.

It would be so much better if I could just run it in WINE and not have to worry about it.

Here's the only output I get when trying to install LabSim:

Code:

 wine LabSimOnlineSetup.exe 
fixme:storage:create_storagefile Storage share mode not implemented.
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
wine: Install Mono for Windows to run .NET 2.0 applications.
err:msi:ITERATE_Actions Execution halted, action L"KillApps" returned 1627
err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1627

I have checked all of my log files and there is nothing displayed anywhere that I can fine.

The main problem I can see is if I try to install the prerequisites via winetricks, they fail. DotNet 3.5 is one example - it says it is too new for the OS (WINE) and reverts to an older version 2.0 which complains that it won't work on a 64-bit OS.

business_kid · 09-02-2011, 12:53 PM

Quote:

The main problem I can see is if I try to install the prerequisites via winetricks, they fail. DotNet 3.5 is one example - it says it is too new for the OS (WINE) and reverts to an older version 2.0 which complains that it won't work on a 64-bit OS.

Wine is normally 32 bit, and runs as such on my 64 bit box. If you want a 64 bit only program, you need a 64 bit version of wine which you may have to build yourself.

The winetricks script is very well maintained, so if you hit problems report them to the maintainer, and they get fixed. BTW, the sort of stupidity you mention above is actually a windows problem, because m$ install programs are barfing.

I did give some of the electronic software some time with wine, and found issue after issue after issue. If you are running already in a VM, why try to fix it?

kasl33 · 09-08-2011, 07:10 PM

Quote:

Originally Posted by business_kid

Wine is normally 32 bit, and runs as such on my 64 bit box. If you want a 64 bit only program, you need a 64 bit version of wine which you may have to build yourself.

The winetricks script is very well maintained, so if you hit problems report them to the maintainer, and they get fixed. BTW, the sort of stupidity you mention above is actually a windows problem, because m$ install programs are barfing.

I did give some of the electronic software some time with wine, and found issue after issue after issue. If you are running already in a VM, why try to fix it?

The LabSim program is a 32-bit program. But the progs I am trying to install (dotnet 3.5, etc) via winetricks are the ones that are barfing because it wants a 32-bit host as well. If there was a way to get winetricks to think of my host as a 32-bit machine, then there is a possibility of potential success here.

Any ideas for forcing architecture?

business_kid · 09-09-2011, 02:46 AM

I have a 64 bit box, with a 32 bit wine. I have compiled from git and still end up with a 32 bit wine.

Quote:

The main problem I can see is if I try to install the prerequisites via winetricks, they fail. DotNet 3.5 is one example - it says it is too new for the OS (WINE) and reverts to an older version 2.0 which complains that it won't work on a 64-bit OS.

I would certainly get in there with winecfg and see if you can choose a newer version of windows to aim at. Get the 32 bit version of the wine package for your distro, or update from git and build it. I use slackware; I make as normal, run make DESTDIT=/tmp/emptydir install and it all ends up in /tmp/emptydir. Then cd to /tmp/emptydir and ruin makepkg, which gives me an installable & removable package.

To run wine, you need a filly multilib system. Just in case, also try
ldd /usr/bin/wine |grep found
There should be no output.

kasl33 · 09-09-2011, 03:55 PM

Quote:

Originally Posted by business_kid

I have a 64 bit box, with a 32 bit wine. I have compiled from git and still end up with a 32 bit wine.

I would certainly get in there with winecfg and see if you can choose a newer version of windows to aim at. Get the 32 bit version of the wine package for your distro, or update from git and build it. I use slackware; I make as normal, run make DESTDIT=/tmp/emptydir install and it all ends up in /tmp/emptydir. Then cd to /tmp/emptydir and ruin makepkg, which gives me an installable & removable package.

To run wine, you need a filly multilib system. Just in case, also try
ldd /usr/bin/wine |grep found
There should be no output.

Well, I made a small amount of progress. I renamed my ~/.wine directory to .wine.bak (after realizing I need to change my WINEARCH variable. After that, I ran

Code:

WINEARCH=win32 winecfg
# Found this at https://wiki.archlinux.org/index.php/Wine#Using_WINEARCH

At least dotnet30 is installing at this point. It isn't the 35 version required, but maybe i'll find a way around it somehow.

Thanks for the tips and I'll post the result if I get LabSim working or not. At least until then, I have VMware with Unity mode.