I can't for the life of me install Steam, either under WINE or by grabbing some testing libs and trying to use the native (well Ubuntu based) deb. Wheezy it seems lacks the specific version of libc6 (which I can't resolve) for the install of the deb. When I install WINE from the repos which I believe is version 1.4 along with winetricks WINE installs fine, but when I attempt to install steam either by downloading the current exe from the website or running winetricks steam the msi will not extract. I get a checksum error from winetricks. When I try and run msiexec /i steam.msi I get an error. Can anyone help me? I have never had this problem before (and have been through many Linux distros). I have been searching for a solution for days but have come up with nothing
I would prefer to get things running smoothly on WINE because I do have many games that are not yet converted to native Linux ones under Steam.
Last edited by gforce6point0 (2013-09-22 02:05:37)
There's a few threads here on getting Steam running native and I haven't tried it yet but there may be something helpful in one of them. I also haven't used Wine directly in quite a while (for Windows games on Steam), but have had decent luck with the PlayonLinux frontend to it.
Ok thanks...as far as I know all play on Linux does is install and manage a number of wine versions for you. Were you able to get stream running on it using a different wine version?
Yep, looks like Steam is using Wine version 1.3.28 through POL (on mine). I've run Half-Life 1 and Portal (Windows versions) though it.
Last edited by chillicampari (2013-08-24 21:14:40)
Alright, thanks that did it. It installed WINE version 1.5.26 (or something along those lines) and now seems to be doing its thing.
Well, never mind. Steam was working fine but I couldn't get any of the actual games CounterStrike:Source, KillingFloor, Portal, etc. to launch, and since the WINE installed by Play on Linux is different from that of the native system, I'm not quite sure how to get terminal output (because I can't simply run wine Steam.exe). Any more advice/insight on how you are supposed to manage versions and settings of WINE versions that are not really installed on your system?
Whelp... dang, it seems like *something* should be running at this point (even if not running well) and since it's not, either I'm forgetting something important WRT PlayonLinux or something's wonky. I don't want to set you off on a wild goose chase and waste your time so I'm going to ask for additional assistance (whether it's Steam, Wine or POL) from anyone who plays more games than I do and is more familiar with getting it to work. As for your last question, each application install can be managed independently through the PlayonLinux configuration panel (Wine versions, tweaks and libraries) and each application has it's own separate virtual environment. But you do lose the benefit of see what's actually going on by running it through the terminal (as you mentioned).
I just noticed this thread is in Crunchbang Talk and I'm going to request a move to Help and Support (I'm assuming you're on 11, Waldorf?) and that way more people might see it.
I could swear that this was under the help and support stable threads...perhaps I missed a pull-down menu somewhere...
Last edited by gforce6point0 (2013-08-26 03:58:50)
Bump, again... I still have found no solution on the interwebs
edit: I deleted for it was irrelevant.
editNew: if you run wine with steam is not steam trying to run the game windows natively? maybe try the executable with wine>
Last edited by bleach (2013-09-02 05:53:03)
obstacles are only in your mind. how you deal with them is what "matters".
Thanks bleach. I however find your comment irrelevant considering running native windows applications is the function of WINE.
Playonlinux is simply installing a number of different WINE versions (those found to best work with certain games and applications). The problem is that as far as I could tell playonlinux doesn't register these versions system wide, and I could not find a way (I'm sure there must be one?) to configure each individual WINE version separately (because the usual wincfg would default to the installed repo version).
I fixed the problem by:
1) Installing PoL
2) Downloading and installing Steam using PoL (the provided wine version must have a bug in the msi extractor)
3) Removing PoL and installing just the version of WINE currently available in the repos
4) Copying the Steam prefix files into the singular WINE prefix
5) Configuring WINE via winecfg till things worked
Yes, this could have all been avoided if there were a more recent WINE version available on Waldorf, but there is not.