Wine and Cedega problem

[reb]

Somewhere and somehow, something got messed up with my gaming.  I find myself faced with a strange conundrun.  I never did get Cedega working on my other HD, so when I installed Vl 5.9 Delux on this HD, I didn't install Cedega; I installed Wine only.   

After installing Call of Duty, using the loki installer, and use the command to start the single person game, which is: "codsp*" I get this mesg back: "Wine(X)/Cedega not in your path". In the quote below, I show you the sub-dir where the start command is located, the start command, and the strange answer I get.

rebel:$ cd /home/rebel/cod
rebel:/~/cod
rebel:$ ls
CoDMP.exe*  Docs/       Main/   cgamex86.dll  codmp*  gamex86.dll       miles/     pb/        uninstall*       version.inf
CoDSP.exe   EaxMan.dll  README  cod.xpm       codsp*  localization.txt  mss32.dll  uix86.dll  validatekey.dll
rebel:/~/cod
rebel:$ ./codsp*
Wine(X)/Cedega not in your PATH
rebel:/~/cod
rebel:$

Now this makes no sense to me at all.  What has Wine got to do with cedega since I had already installed the game with the loki installer and expected the game to play using Wine?  Hopefully someone can help me out.  Incidentally I posed this very question in the Wine live chat room.  I will share two of the more puzzling answers with you:

1.  ..wine and cedega aren't the same thing..  My thought to this was "like Duuuuuuuh" do they think I'm that stupid?

2.  ..you are trying to start the game with a script.  just start the game normally...

At this point I simply shook my head and dropped out of the chat room.

reb

[uelsk8s]

My guess is try to run it this way

Code:

wine CoDSP.exe

if that doesnt work post the contents of the codsp script

[reb]

OK uelsk8s here is is.  Sorry it took so long but I had other minor issues here at home.

root:# cat ./codsp*
#!/bin/sh

GAME_BINARY="CoDSP.exe"
SUBDIR="."
WINE_NAMES="cedega cvscedega winex3 cvswinex winex wine"

#----------------------------------------
script=$0
count=0

while [ -L "$script" ] 
do
    script=`perl -e "print readlink(\"$script\"), \"\n\""`
    count=`expr $count + 1`

    if [ $count -gt 100 ] 
    then
        echo "Too many symbolic links"
        exit 1
    fi
done

GAME_DIR=`dirname $script`

if [ -z "$WINE_EXEC" ]
then
        WINE_EXEC=`type -p $WINE_NAMES | head -n 1`
fi


if [ -e "$WINE_EXEC" ]
then
        cd $GAME_DIR
        cd $SUBDIR
        $WINE_EXEC $GAME_BINARY "$@" &&
        xgamma -gamma 1.0 &> /dev/null
else
        echo "Wine(X)/Cedega not in your PATH"
        exit 1
fi
rebel://home/rebel/cod

So now I see where it is coming from, but I have no idea what to do about it.    thanks for the help

reb

[uelsk8s]

Reb,

Either wine is not in your path or the script cant find it.

if you run "wine CoDSP.exe" what happens?

you can try and find wine with which or whereis

Code:

whereis wine

if that outputs /usr/bin/wine then you can add that to your script like this

Code:

root:# cat ./codsp*
#!/bin/sh

GAME_BINARY="CoDSP.exe"
SUBDIR="."
WINE_NAMES="cedega cvscedega winex3 cvswinex winex /usr/bin/wine"

#----------------------------------------
script=$0
count=0

while [ -L "$script" ]
do
    script=`perl -e "print readlink(\"$script\"), \"\n\""`
    count=`expr $count + 1`

    if [ $count -gt 100 ]
    then
        echo "Too many symbolic links"
        exit 1
    fi
done

GAME_DIR=`dirname $script`

if [ -z "$WINE_EXEC" ]
then
        WINE_EXEC=`type -p $WINE_NAMES | head -n 1`
fi


if [ -e "$WINE_EXEC" ]
then
        cd $GAME_DIR
        cd $SUBDIR
        $WINE_EXEC $GAME_BINARY "$@" &&
        xgamma -gamma 1.0 &> /dev/null
else
        echo "Wine(X)/Cedega not in your PATH"
        exit 1
fi