playonlinux - FARCRY2 glitch
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
playonlinux - FARCRY2 glitch
Hello. I installed Far Cry 2 + the patch. I have suse 11.4 + KDE.
The run button doesn't do anything. Right after I installed it, I use the autorun feature to get far cry running. After I reboot, I can't get the feature to work again. The start menu has far cry references, but they give file not found. The correct location: media\FARCRY2, it's set at media\cdrom.
I have to attemped a reinstall and correct the media name. Then run it from menu that pops up. I have to eject the cd rom and reinsert it to get it to see the dvd rom.
install->dvd version->insert far cry disk->cd rom mounted->other->FARCRY2 then cancel then try autorun again and follow the prompts.
This takes about 5-25 times to get the game to run. All menus say file not found even when it's fully installed. :p
After using play in linux APP. How do manually run it in wine?
Need help. Thanks.
The run button doesn't do anything. Right after I installed it, I use the autorun feature to get far cry running. After I reboot, I can't get the feature to work again. The start menu has far cry references, but they give file not found. The correct location: media\FARCRY2, it's set at media\cdrom.
I have to attemped a reinstall and correct the media name. Then run it from menu that pops up. I have to eject the cd rom and reinsert it to get it to see the dvd rom.
install->dvd version->insert far cry disk->cd rom mounted->other->FARCRY2 then cancel then try autorun again and follow the prompts.
This takes about 5-25 times to get the game to run. All menus say file not found even when it's fully installed. :p
After using play in linux APP. How do manually run it in wine?
Need help. Thanks.
- SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
What about this?
If the problem is simply the mount point, just change it.
I'd go to terminal and do:
mount
//This gets a list of what's mounted where. Find what's mounted at /media/cdrom or whatever instead of /media/FARCRY2. It's probably /dev/sr0 or /dev/sr1 or /dev/cdrom or something like that.
//Then do:
sudo umount [/dev/sr0 or whatever it is]
//That just unmounted it.
sudo mkdir /media/FARCRY2
//That makes that folder. We're going to mount it to that folder.
sudo mount /dev/sr0 /media/FARCRY2
//That just made the contents of the disc be displayed in that folder.
Ok, now it's mounted where it wants it!
As far as how to run the game manually with WINE, you can navigate to /media/FARCRY2, right click the game launcher and tell it to run with the WINE program launcher. If that option isn't there, open terminal, type "wine" with a space after it and drag what you want to run in wine after it. The hit enter.
There are folders that contain a drive_c folder that WINE uses as a virtual C:\ drives. Also in the folder are registry keys. These folders are WINE prefixes. Each prefix is a separate "WINE world".
When you run something through wine in terminal, you can specify the prefix. For example: WINEPREFIX=$HOME/farcry2 wine [path to executable].
The default prefix is $HOME/.wine, a hidden folder. Whenever you don't specify the wine prefix, the default it used. I should say that that is the default default. If you compile WINE from source, you can pick the default WINE prefix.
So if PlayOnLinx put the game in a prefix other than the default, and you don't specify the prefix to run the launcher, it wil go to the default prefix and not find the game.
Also know that you are running the launcher off the disc which further runs the game executable in the program files folder. You aren't directly running the game executable.
Also know that it is possible that simply typing "wine" in terminal won't do it. It's actully looking in /usr/bin for a shortcut or actual executable named "wine". If the wine executable is named something else, or if the shortcut to it is named something else, you'll need to use that. For example, when I have more than one version of WINE I have a shorcut named wine1.3.22 or whatever. So I have to say "WINEPREFIX=[prefix path] wine1.3.22 [path to executable]" or something like that.
I don't think PlayOnLinux would make life hard on you like in the above to you. If they really wanted to mess with you, they could put the wine executable off in some folder somewhere with no shortcut in /usr/bin, and you'd have to write the full path to it (or you could get ahead and make a shortcut their named "wine").
Cheers,
Jake
I'd go to terminal and do:
mount
//This gets a list of what's mounted where. Find what's mounted at /media/cdrom or whatever instead of /media/FARCRY2. It's probably /dev/sr0 or /dev/sr1 or /dev/cdrom or something like that.
//Then do:
sudo umount [/dev/sr0 or whatever it is]
//That just unmounted it.
sudo mkdir /media/FARCRY2
//That makes that folder. We're going to mount it to that folder.
sudo mount /dev/sr0 /media/FARCRY2
//That just made the contents of the disc be displayed in that folder.
Ok, now it's mounted where it wants it!
As far as how to run the game manually with WINE, you can navigate to /media/FARCRY2, right click the game launcher and tell it to run with the WINE program launcher. If that option isn't there, open terminal, type "wine" with a space after it and drag what you want to run in wine after it. The hit enter.
There are folders that contain a drive_c folder that WINE uses as a virtual C:\ drives. Also in the folder are registry keys. These folders are WINE prefixes. Each prefix is a separate "WINE world".
When you run something through wine in terminal, you can specify the prefix. For example: WINEPREFIX=$HOME/farcry2 wine [path to executable].
The default prefix is $HOME/.wine, a hidden folder. Whenever you don't specify the wine prefix, the default it used. I should say that that is the default default. If you compile WINE from source, you can pick the default WINE prefix.
So if PlayOnLinx put the game in a prefix other than the default, and you don't specify the prefix to run the launcher, it wil go to the default prefix and not find the game.
Also know that you are running the launcher off the disc which further runs the game executable in the program files folder. You aren't directly running the game executable.
Also know that it is possible that simply typing "wine" in terminal won't do it. It's actully looking in /usr/bin for a shortcut or actual executable named "wine". If the wine executable is named something else, or if the shortcut to it is named something else, you'll need to use that. For example, when I have more than one version of WINE I have a shorcut named wine1.3.22 or whatever. So I have to say "WINEPREFIX=[prefix path] wine1.3.22 [path to executable]" or something like that.
I don't think PlayOnLinux would make life hard on you like in the above to you. If they really wanted to mess with you, they could put the wine executable off in some folder somewhere with no shortcut in /usr/bin, and you'd have to write the full path to it (or you could get ahead and make a shortcut their named "wine").
Cheers,
Jake
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
Re: What about this?
SpawnHappyJake wrote:If the problem is simply the mount point, just change it.
I'd go to terminal and do:
mount
//This gets a list of what's mounted where. Find what's mounted at /media/cdrom or whatever instead of /media/FARCRY2. It's probably /dev/sr0 or /dev/sr1 or /dev/cdrom or something like that.
//Then do:
sudo umount [/dev/sr0 or whatever it is]
//That just unmounted it.
sudo mkdir /media/FARCRY2
//That makes that folder. We're going to mount it to that folder.
sudo mount /dev/sr0 /media/FARCRY2
//That just made the contents of the disc be displayed in that folder.
Code: Select all
umount /dev/sr1/ (superuser mode)
umount: /media/FARCRY2: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
I get on autorun
Line #1: *
Line #2: other
If scans for autorun and finds it I get: "farcry has been found."
- SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Oh. I'm backwards. I thought it usually mounts at /media/cdrom and you want it to mount at /media/FARCRY2. Apparently it's the other way around.
The other way of fixing this is to go into winecfg and have it look at /media/FARCRY2 as, say, drive D:. And might as well have it look at /media/cdrom as drive E: or whatever in case it gets mounted there.
Go to terminal and type "wine winecfg.exe" and go to the drives tab (a window will pop up). You'll see what I mean. You can throw a prefix in front of that to set the settings for a certain prefix.
Cheers,
Jake
The other way of fixing this is to go into winecfg and have it look at /media/FARCRY2 as, say, drive D:. And might as well have it look at /media/cdrom as drive E: or whatever in case it gets mounted there.
Go to terminal and type "wine winecfg.exe" and go to the drives tab (a window will pop up). You'll see what I mean. You can throw a prefix in front of that to set the settings for a certain prefix.
Cheers,
Jake
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
playonlinux - FARCRY2 glitch
This is what I see when I do autorun:
playonlinux->tools->autorun->forward->
"a cd rom has been found on your drive.
media/FARCRY2/autorun.exe
name:unknown"->
"no setup location was found in autorun.inf
[In an existing prefix(add-on)] *selected
[in a new prefix]->
Choose the prefix:
[FarCry22]
[wine]
If I pick wine, I get a menu. Play is greyed out. Install is not.
If I select FarCry2, the game will run as normal.
Usually nothing happens, I get "* or other".
If I right click on farcry2 in media/FARCRY2/, I get a game menu with play greyed out and install black.
playonlinux->tools->autorun->forward->
"a cd rom has been found on your drive.
media/FARCRY2/autorun.exe
name:unknown"->
"no setup location was found in autorun.inf
[In an existing prefix(add-on)] *selected
[in a new prefix]->
Choose the prefix:
[FarCry22]
[wine]
If I pick wine, I get a menu. Play is greyed out. Install is not.
If I select FarCry2, the game will run as normal.
Usually nothing happens, I get "* or other".
If I right click on farcry2 in media/FARCRY2/, I get a game menu with play greyed out and install black.
-
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
playonlinux - FARCRY2 glitch
On 7/4/11 12:28 PM, Lord_Valarian wrote:
James
This appears to be a POL issue and needs to be addressed to them.This is what I see when I do autorun:
playonlinux->tools->autorun->forward->
"a cd rom has been found on your drive.
media/FARCRY2/autorun.exe
name:unknown"->
"no setup location was found in autorun.inf
[In an existing prefix(add-on)] *selected
[in a new prefix]->
Choose the prefix:
[FarCry22]
[wine]
If I pick wine, I get a menu. Play is greyed out. Install is not.
If I select FarCry2, the game will run as normal.
Usually nothing happens, I get "* or other".
If I right click on farcry2 in media/FARCRY2/, I get a game menu with play greyed out and install black.
James
- SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Making It Easy
Let's make this easy. Forget about PlayOnLinx. Make sure your WINE is either the latest or one behind by going to terminal and doing "wine --version" and update it if necessary.
Just make a launcher or a bash script on your desktop to run the game executable located within the program files folder in the prefix rather than relying on autorun.
Cheers,
Jake
Just make a launcher or a bash script on your desktop to run the game executable located within the program files folder in the prefix rather than relying on autorun.
Cheers,
Jake
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
Re: Making It Easy
OK, so I think I found the right place play on linux put them. The saved files are in media/farcry2/SpawnHappyJake wrote:Let's make this easy. Forget about PlayOnLinx. Make sure your WINE is either the latest or one behind by going to terminal and doing "wine --version" and update it if necessary.
Just make a launcher or a bash script on your desktop to run the game executable located within the program files folder in the prefix rather than relying on autorun.
Cheers,
Jake
version: wine-1.3.12
/.PlayOnLinux/wineprefix/FarCry2/drive_c/Program Files/Ubisoft/Far Cry 2/bin>
What line to use? Play on linux never created a shortcut.
WINEPREFIX=[prefix path] wine1.3.22 [path to executable]
-
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
playonlinux - FARCRY2 glitch
On Tue, Jul 12, 2011 at 1:14 PM, Lord_Valarian
<[email protected]> wrote:
Should return /usr/bin/wine
Should return that the file is an executable
-rwxr-xr-x root <something> <file size> wine
That should start Far Cry 2.
James
<[email protected]> wrote:
Try this:SpawnHappyJake wrote:OK, so I think I found the right place play on linux put them. The saved files are in media/farcry2/Let's make this easy. Forget about PlayOnLinx. Make sure your WINE is either the latest or one behind by going to
terminal and doing "wine --version" and update it if necessary.
Just make a launcher or a bash script on your desktop to run the game executable located within the program files folder
in the prefix rather than relying on autorun.
Cheers,
Jake
version: wine-1.3.12
/.PlayOnLinux/wineprefix/FarCry2/drive_c/Program Files/Ubisoft/Far Cry 2/bin>
What line to use? Play on linux never created a shortcut.
WINEPREFIX=[prefix path] wine1.3.22 [path to executable]
Code: Select all
which wine
Code: Select all
cd /usr/bin
ls -l wine
-rwxr-xr-x root <something> <file size> wine
Code: Select all
cd '/.PlayOnLinux/wineprefix/FarCry2/drive_c/Program Files/Ubisoft/Far
Cry 2/bin'
wine <name of Far Cry 2 executable>
James
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
farcry2 in wine
That is a distribution problem. Not all distributions use /home for where they locate user files. What Linux/UNIX distribution are you using, again?If I change to '/home/[username]]', it still says directory not found..
Code: Select all
cd '/.PlayOnLinux/wineprefix/FarCry2/drive_c/Program Files/Ubisoft/Far
Cry 2/bin'
And it should not. You'll have to use the UNIX list (ls) command with the all (-a) option like this>dir
doesn't list the hidden files.
Code: Select all
ls -a
-
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
playonlinux - FARCRY2 glitch
On 7/12/11 2:51 PM, Lord_Valarian wrote:
releases place user files in a specific directory under the /home directory.
this. You will need to use the UNIX ls (list) command with the -a (all)
option to see hidden (.<something>) files. As a warning this also lists
the current (.) and parent (..) directory information as well if you use
the -al (all long) option.
The program executable should be listed just using the dir or ls command
as <something>.exe
James
This appears to be a distribution related problem. Not all Linux/UNIXThat gives directory not found. If I change to '/home/[username]]', it
still says directory not found..
releases place user files in a specific directory under the /home directory.
Does this work?Code:
cd '/.PlayOnLinux/wineprefix/FarCry2/drive_c/Program Files/Ubisoft/Far
Cry 2/bin'
The DOS based dir<ectory> command as it was ported to Linux does not dodoesn't list the hidden files.dir
this. You will need to use the UNIX ls (list) command with the -a (all)
option to see hidden (.<something>) files. As a warning this also lists
the current (.) and parent (..) directory information as well if you use
the -al (all long) option.
The program executable should be listed just using the dir or ls command
as <something>.exe
James
-
- Level 2
- Posts: 34
- Joined: Sat Apr 16, 2011 3:00 pm
farcry2
Code: Select all
/home/username/> cd /.PlayOnLinux/
Do I need to be in superuser mode to run it? No, right?
playonlinux - FARCRY2 glitch
On Tue, 2011-07-12 at 20:49 -0700, James McKenzie wrote:
dir -a
does more or less the same as ls -a. In fact it accepts most (all?) of
the same options as ls, though some of the defaults may differ, e.g. on
my Fedora system 'dir' doesn't colour directory entries while 'ls' does,
but 'dir --color' gives identical output to 'ls'.
Martin
Yes it does.The DOS based dir<ectory> command as it was ported to Linux does not do
this.
dir -a
does more or less the same as ls -a. In fact it accepts most (all?) of
the same options as ls, though some of the defaults may differ, e.g. on
my Fedora system 'dir' doesn't colour directory entries while 'ls' does,
but 'dir --color' gives identical output to 'ls'.
Martin