Well I guess I am indeed behind the times. Thanks for the info motub.

typing winesetup didn't work, but winecfg did.

Thank you-- at least now I know the command to run the d**m thing .

Okay... don't know anything at all about 'symlinks'...

I followed the /usr/share/documentation/winex/index.html, and in the installing section it said that I should create folders etc... I made all the folders as per instructions, and set up the .wine/config to reflect the changes etc.

I also found that I should have some .reg files from somewhere, so I copied them from the samples folder...

I have the exact error messages now:

[root@JC-LINUX cdrom]# wine install.exe
A dialog box appears, title ¨ERROR¨, contents ¨No Program Start Menu Found¨.

[root@JC-LINUX cdrom]# cvswinex install.exe
fixme:msvcrt:__CxxFrameHandler (0x4058ca28,0x40761298,0x4058c6c0,0x4058c650):stub?
fixme:msvcrt:__CxxFrameHandler (0x4058c654,0x40761298,0x4058c2ec,0x4058c27c):stub?
fixme:msvcrt:__CxxFrameHandler (0x4058c280,0x40761298,0x4058bf18,0x4058bea8):stub?
fixme:msvcrt:__CxxFrameHandler (0x4058beac,0x40761298,0x4058bb44,0x4058bad4):stub?
... (pages of, etc.)

Oh, and by the way, I did download the binary RPM of WineX... I had that installed before I installed Wine and CVSWineX... I think this could be problematical, but I have no idea how I'm supposed to manage the 3 different programs... Lemme get this straight, the executable file for WineX is still called wine?


Any more ideas?

UPDATE:

I got my wine sorted!
I needed a file called msvcrt.dll in my C:\ as well, to solve my CxxFrameHandler messages... I used a Windows 98 one, and put it in C:\windows\system

The install worked fine!
I updated to The Frozen Throne (expansion) and also updated to the latest patch I had available on short notice (1.15 if youŕe interested)

The game works!
but its terribly, terribly lag. I've tried using the -opengl switch, but I'm not sure on
a) whether is -opengl or --opengl
b) the syntax for wine to pass the switch to the war3.exe
cvswinex war3.exe -- -opengl?

To find out what the switch is, try cvswinex --help. Usually that will give you the syntax and a list of options.

The general rule is, if the switch is just one letter, there's only one - (dash) in front of it, if it's more than one letter (meaning a whole word, like "help"), there are two. So the suggested command above could normally be used as either

cvswinex --help
cvswinex -h

or even

cvswinex -?

But some programs do not follow this protocol, and use a single dash even for multi-character switches, so always try "--help", "-help", or just run the command without arguments, because if it needs arguments, the default behaviour of any program is to print the help screen if none are present.

As for symlinks (for the future, as you will need to know this)-- they are essentially a type of what a Windows user would call a shortcut.

If you look in the ~/.wine/dosdevices folder (for a current version of regular Wine, this does not apply to CVSWineX, as they're still using the old Wine layout), you will see a list of "folders" called things like "c:", and "x:" and "z:', iirc.

If you look at the properties of the "c:" folder, you will find that it is not in fact itself a folder, but a sym(bolic)link to the real folder, which is "~/.wine/fake_windows". If you were to click on the "c:", to go to the c: directory, you would actually be taken to ~/.wine/fake_windows, and the contents of that folder would be displayed.

This is critical to how Wine works, of course, since Windows applications are hard coded to look for support files in C:\whatever, and such hardcoded mount points as C:\ for the system root do not exist in Linux. Therefore symlinks are essential to fool Windows into thinking that there really is a C\:Windows, while in fact using the regular Linux filetree.

But you can use this functionality for anything; one of the most useful things you can do as a normal user is symlink the ~/.wine folder to ~/wine, so that you don't always have to turn on hidden files and folders just to edit your config.

In Nautilus, just select the folder you want to make a symlink to (naturally, turning on Show Hidden Files and Folders in the Preferences first), right-click and choose "Make Link" from the menu. A file called "link to .whatever" will appear; change the name to "wine" and you're done (just make sure to remove the dot, so it doesn't become hidden, and that the final name is unique to the folder in which the symlink lives).

In Konqueror, which I rarely use, not being much for KDE, it looks like you would go to the folder you want to create a symlink in (for this example, it's going to be your ${HOME}$ folder), and choose Edit=>Create New=>Link to URL. In the resulting dialog, browse to the hidden Wine folder (use the little wrench in the toolbar to turn on show hidden files in the file browse dialog, or just hit F8) and select it (using CTRL+left-click, in order to select the folder without entering it). This will fill in the folder's name in the "name" field of the Make Link dialog-- remove the preceding dot to make the symlink name "wine" instead of .wine (leaving the dot on would 1) mark the file as hidden, which is exactly what we don't want, and 2) result in the same name as the target folder, which is not allowed).

The result is a "*.desktop" file, which seems odd to me, but when double-clicked does in fact open the target folder in a Konqueror (fm) window, so weird or not, it does work.

There are also some symlinks in your system tree; the most famous one is /usr/src/linux, which will be created any time you install your kernel source (automatically, if you install a kernel package under an RPM distro, manually by you, if you use a more hands-on distribution), so that you may use and compile multiple kernel sources on the same system (the current one-- meaning the one that you are considered to be using by programs or drivers that must compile against said source-- is always the one that the /usr/src/linux symlink actually targets); the second most famous one is /boot/vmlinuz, which is a symlink to your actual compiled kernel, so that, again, you may have multiple compiled kernels on your system, but the one that will actually be loaded by the bootloader will always be the one that is targeted by the /boot/linuz symlink. This symlink, again, is created automatically by a kernel package install, automatically by using the 'make install' command when compiling your own kernel, or manually by you under all other circumstances.

But it's easy to change the symlink's target at need, which is why they are used.

Hope this helps, and good luck getting your lag straightened out. Glad you got the game working.

I have the same problem now... any solution yet...?

I receive this error too, I am using Windows XP- Do I need to download wine? Linux? Simple instructions please,

Any help appreciated

Try cleaning the CD. Simple enough ?

You might do better to ask your question on a forum that supports Warcraft under the Windows operating system. This forum supports users with the Linux operating system.