winex question--should be easy

[urinal cake]

I got the winex source via CVS, and it apparrently compiles OK. make install seemed to be OK, at least I didn't see any errors. I mounted the Windows partition where halflife is installed (win2K-NTFS) and ran:

wine --winver win98 hl.exe

I get back:

bash: wine: command not found

Obviously, I screwed something up. How do I identify the problem and fix it?

Thanks for your help. :-)

[urinal cake]

update: Found I had no .wine directory. Reinstalled, now directory iexists. Still getting

bash: wine: command not found

[bwkaz]

Unmount everything except your Linux partition(s). Then do one of these:

find / -name wine

It will recursively search everything that's mounted, looking for a file named "wine". It'll print out all the matches. My guess at this point is that wine got installed in /usr/local/bin (I believe that's the default), and that /usr/local/bin isn't in your PATH, but I'm not sure.

[Icarus]

Using winex, the command is wrong...try

winex -winver win98 hl.exe

only one '-' in there :D
or better yet...

winex hl.exe :D

and be sure you are using winex not wine

[ 18 January 2002: Message edited by: mahdi ]

[bwkaz]

WineX CVS doesn't create a winex executable. It's still called wine.

The WineX RPM (well, the one from Transgaming at least) installs winex as a shell script that does some fiddling and then invokes wine.

[urinal cake]

Thanks for the help...let me update. Yes, cheapskates like me that don't pay get a wine executable, not winex. I got it running, even installed Halflife, but cant run anything else yet. I've found the binary, and exported it's location to my PATH, but the new addition to PATH is only there in runlevel 3; in runlevel 5 it's gone. Once I figure this out, I'll work on configure it so I can actually use it to run stuff. But it is working. :-)

[bwkaz]

Did you add the path to rc.local? Or, better yet, ~/.bashrc or ~/.profile? I would do one of those, that way no matter how you get into the box, no matter which runlevel you boot to, the PATH would get changed.

rc.local should change it for all users, your ~/.bashrc gets run when you log in (though I'm not sure about Xdm/kdm/gdm), and your ~/.profile gets run when bash isn't a login shell (like when you open a terminal, or su from another account).

Wait, you're not logging in as root, are you? Because I believe that as root, most distros set up a different PATH that discards all the additions made by any one user.