WineX is a Windows emulator thingy that has
DirectX support built in. This means you can run those DirectX games that you had to put
a wingdows partitin on for. Max Payne and Diablo II LOD are some of the games it runs after
a few hours (days) of configuration. To get winex, run the following commands as root, and in
roots home directory.
$ cvs -d:pserver:email@example.com:/cvsroot/winex login
Hit Enter when prompted for a password
$ cvs -z3 -d:pserver:firstname.lastname@example.org:/cvsroot/winex co wine
The WineX cvs should now start downloading, it takes a while so go do something
else while its going. Before you install WineX, make sure you dont have ANY wine stuff left
on your machine. Old configs left in home directorys will mess up the installer. Once the
CVS is done downloading go into the top level wine directory. To install WineX type (as root)
There are a TON of errors that you will probably get, here's some of them.
- Gas not found. This happens because you don't have the C++ compiler with the gas package.
Usually downloading gas and rerunning ./configure will solve this problem.
- After the install has compiled, libntdll.so not found aborting. This means you already have
(or had) wine installed, and when you removed it the libraries stayed. To fix this type (as root, in
the wine directory)
$ make uninstall
$ make clean
$ cp lib* /usr/lib
repeat the copy with all the lib directories in your path.
- WineX regapi error, this will happen if you haven't feed the userdefault.reg file into
regapi. The error message you will get is this. Updating winex registries..registry error
dyndata.reg not found. specified file or directory does not exist. Normally this should have
been done by the ./tools/wineinstall, but for you it didn't work. I'm not sure how to do it
manually, but if you know drop me a note at email@example.com
- WineX installer error. Wine will get these errors if you are trying to run a install shield
windows program and you dont have your permissions set up properly. The message will be this:
iKernel could not be initialized. The installshield engine launches it's own kernel, and
this is REALLY unsecure. Wine won't let you launch another kernel because it isn't safe for
your system. My advice would be copy all the files off that game's (or apps) cd onto your
harddrive and run the .exe without installing it.
- Wine error, can't allocate console. This happens when you have another program running
in the backround and you try to start wine. Open a fresh console and run as root and this will
usually go away. Sometimes the windows app can't run correctly in the console so it complains.