Anyone know if/how you can use the new wisotool with the games it supports through Steam? I have several of the titles it "supports" and would love to give it a try if it works through Steam.
Regards,
~Jeff
Using wisotool with Steam
wisotool's primary function is to ease installation of games from ISOs so make sure to load the iso for the particular game before installing. wisotool currently doesn't support installing via steam download.
set your wine user name and password in the shell environment with STEAMUSER="YourUserName" STEAMPW="YourPassword" before running the script.
ie:
STEAMUSER="GregR" STEAMPW="foo" ./wisotool codmw2
The installs for the steam games are still a work in progress so open up the wisotool script with your editor and take a look at the comments to see if there are any special instructions for a particular game.
-eg
set your wine user name and password in the shell environment with STEAMUSER="YourUserName" STEAMPW="YourPassword" before running the script.
ie:
STEAMUSER="GregR" STEAMPW="foo" ./wisotool codmw2
The installs for the steam games are still a work in progress so open up the wisotool script with your editor and take a look at the comments to see if there are any special instructions for a particular game.
-eg
Using wisotool with Steam
On Tue, Jun 8, 2010 at 3:59 PM, DanKegel <[email protected]> wrote:
of the steamapps folder to some where out side of your wine prefix.
They also provide a great game backup solution that works well.
The real value would be in modifying the installscript.vdf 'first time
run' scripts that ship with games that Steam downloads. This script
is the cause of a lot of pain for playing games we know work in Steam.
If we could replace the modules Steam tries to install with install
scripts that run faster using alternative methods that we know work
reliably and quickly. For example VCRedist takes ages while
winetricks does it almost instantly. Another example is games that
don't rely on GFWL but still require it to install could have that
issue by passed.
These vdf scripts are very plainly written and simple to follow.
Extensive editing does not cause any issues and is already used with a
couple of games. Windows users have been changing them for awhile now
without any comment from Valve.
Might be a good idea to look into?
The Steam game cache can be easily preserved by just making a symlinkwisotool's value in that situation would be to cache the
downloaded games for quick re-installation later. I think
Steam's download system makes that possible.
of the steamapps folder to some where out side of your wine prefix.
They also provide a great game backup solution that works well.
The real value would be in modifying the installscript.vdf 'first time
run' scripts that ship with games that Steam downloads. This script
is the cause of a lot of pain for playing games we know work in Steam.
If we could replace the modules Steam tries to install with install
scripts that run faster using alternative methods that we know work
reliably and quickly. For example VCRedist takes ages while
winetricks does it almost instantly. Another example is games that
don't rely on GFWL but still require it to install could have that
issue by passed.
These vdf scripts are very plainly written and simple to follow.
Extensive editing does not cause any issues and is already used with a
couple of games. Windows users have been changing them for awhile now
without any comment from Valve.
Might be a good idea to look into?
Go ahead and try it. We've added Steam support to wisotool,
and I could imagine the wisotool verb for a game could edit
the .vdf file when replaying the cached install,
but it's not something I'll have time to play with myself.
Current wine should execute the directx runtime installer a lot
faster, which ought to help.
and I could imagine the wisotool verb for a game could edit
the .vdf file when replaying the cached install,
but it's not something I'll have time to play with myself.
Current wine should execute the directx runtime installer a lot
faster, which ought to help.
