Like I said earlier, try copying this file over your original and then run the game.

http://dl.gamecopyworld.com/dl_awpos...=w3loaderpro11!rar&u=66.79.189.95

Woops, sorry guys.

http://www.ad724.com/download.php?w3loaderpro11!rar

If that don't work, try this one.

http://dl.gamecopyworld.com/dl_awpos...w3loaderpro13d!rar

FrostBot, its not a problem with running the game, its a problem with installing it. Any suggestions for that?

Nightfrost, are you, perhaps on amd64? I am, but I copied the winex 32bit binaries so its supposed to work. I haven't tried much else, but Winamp 5 gave me some error about not finding a plugin so it couldn't install and Macromedia Studio said it wasn't supported on this operating system. So since I haven't gotten anything actually INSTALLED yet, I suppose it COULD be a problem with my winex install. But all the autoruns, etc seem to work fine.

Does anyone know of some small little app that diffinately works to test winex?

Thanks.

Oh... thanks for mentioning that you are on AMD64.

I'm not, but "I copied the winex 32bit binaries so its supposed to work" seems to leave a lot of room open for problems, like... did you compile support for 32-bit binaries into the kernel? Are there any special instructions or FAQ on the Transgaming site for 64-bit users?

If you want a small little app that definitely works to test WineX, try notepad... you can get it from the Wine Project page at Sourceforge.net. Scroll down the page to near the bottom, and look for the "Win32 Packages" section. Download wine-prgs-20040813.zip, extract it somewhere, and you'll find notepad in the extracted folder. Run it normally with WineX and see what happens.

By the way, is this actually WineX you're trying to install, or Cedega? I ask because I really question whether WineX (version 3.3.2 or lower) would actually run on 64-bit machines, though Cedega (WineX version 4 or above) might. Possibly.

Hope this helps.

I'm running winex3.3.2 and I tested notepad, which opens and saves files just fine.

But I think I have the problem (but not a solution). For some reason wine is cutting all the file names down to 8 characters. So when browsing the CD the path to the file it's looking for in the error message is:

support\BattleNet\(Mac)BNetMenu.html

But the actual path to the file as it shows up when browsing the CD is:

support/battle~1/(mac)b~1.htm -- (also note it tool the extention down to 3 characters)

It seems this is the case with any CD I put in there. Is there a way to fix that?

Thanks.

You could try recompiling your kernel with support for Joliet extensions, if it has been compiled without (Filesystems=>CD-ROM/DVD Filesystems=>Microsoft Joliet CD-ROM extensions). That's the only thing I can think of that would "enable" what is essentially Long Filename Support for CDs (as otherwise, it's just plain old ISO9660, which is a regular 8.3 setup, which is what you're seeing).

motub, Thanks - that did the trick. I just needed to compile Joliet extensions into my kernel. I installed WC3 and WC3:FT without any problems and I also patched Frozen Throne to 1.16.

But when I try to play it I get the error about not being able to find War3.exe and make sure the CD is in the drive. The CD IS in the drive and I have also tried applying the 116 crack from gamecopyworld, but it still asks me for the CD. Any ideas there?

Thanks agian.

What process are you using to mount your drive? What process are you using to run the game?

Many Wine(X)/Cedega-installed titles prefer to be started from within the game directory, rather than with a complete path. Try using cd /mnt/cdrom/whatever/ before you then run cedega/wine/winex3 War3.exe.

If this works, you can write yourself a little scriptlet to automate cding and running the exe and point your shortcuts to that instead (that's how I run NWN, which is native, and several Wine-installed games which specifically want to be started from within the program directory).

If you're using supermount, automount or the ivman/hal/dbus supermount "replacement", try ejecting and reinserting your CD-- sometimes the various automated modules get confused as to what CD is really in the drive. If you mount manually, naturally make sure that the drive is in fact mounted.

Hope this helps.

I'm also trying to get Warcraft III (ANY version) going on my box.

Wine works great for Halflife.
WineX works great for Soldier of Fortune, and Quake III

But neither Wine nor WineX will successfully run /mnt/cdrom/install.exe

I read the only way to get Warcraft III going is with a no cd crack. I have one, but I'm not really up to the point where I need it yet, so it doesnt help me much.


When I try to 'wine /mnt/cdrom/install.exe' I get some wierd error messages like 'Missing Program Start Menu'...

And when I try to 'cvswinex /mnt/cdrom/install.exe' I get mass pages of stuff... cant even remember what it says sorry, but theres alot of it.

If I come home tomorrow and try to copy your .wine/config to my ~/.wine in a vain attempt to get it going, there shouldn't be any problems, right?

But other than that, do you guys have any suggestions as to what I can do to get the installer going? I could try using Cedega instead of CVSWineX, but this is what I have, and I would rather not try to get rid of one and put another one on. I'm too newb.

What version of Wine? If not 20040813, then update to the current version. For CVSWineX, you're kinda on your own, as it's frankly something of a mess imho. Not a big surprise, since WineX/Cedega CVS is supposed to be for testing and debugging, not to give you and me a freely-downloadable source of crippleware.

You might, however, want to try the precompiled CVS RPMs available here (yes, they're legal, all this person has done is compiled the exact same CVS source you can download into binary form for easy installation).

Hope this helps.

Yeah, I have the 20040813 RPM for Wine.

I think we should ignore CVSWineX for now, since
a) It works fine for other things
b) I would really like to install it using Wine instead of WineX

What folders do I need to create in ~/.wine/ for Wine to work properly? Because I'm NOT sure I've done that correctly. Also, can you give me a sample Wine config, because I can't find one anywhere. Only a sample config for WineX, which I've been using for Wine (oops)

The config file is deprecated (though not yet obsolete); Wine is in the process of moving the configuration settings into the Wine Registry, and there's some new tool called wineconfig or something (haven't used it yet as I'm in the middle of a reformat and reinstall).

You don't need to create any folders; you need to create symlinks in the ~/.wine/dosdevices folder and name them according to what you want your setup to look like. Some of these will be created the first time you run wine; like a symlink to ~/.wine/fake_windows will be made in /dosdevices and named "c:"; /home/username and /tmp/ should also have symlinks, as should / . If you then wanted your CD-ROM at /mnt/cdrom to be considered the D:\ drive, you would make a symlink to /mnt/cdrom and name the symlink d:.

The fake_windows folders, containing \windows, \program files\ et. al. should also be created automatically by wine the first time you run it. Run it the first time without arguments, to make your life simpler, then when you are returned to the prompt, try to run your program with it.

Let us know what happens, and we'll try to solve specific errors when you have some .

the wine setup tool is called winesetuptk and that is a GUI that should help you configure everything

Sorry, Moebius, but you are behind the times. Winesetuptk is the old third party setup tool, which assumes that Wine still reads its device mappings from the config file, which it does not do anymore, for about 3 or 4 months now. This is probably why it's no longer mentioned on the Wine download page... it's pretty much useless since the drive mappings it creates are irrelevant, and the Path settings it creates are no longer used, having been moved to the Wine Registry.

Wine has changed significantly in the past several months. The new, integrated, configuration tool (still in develpment, but apparently available in current versions) is called Winecfg, and may perhaps be accessed either by using it's name, or by using a command called winesetup, or may possibly not be accessible to users at all-- as I said, I have not yet reinstalled Wine, so I don't know the details, I just know that this tool exists and is used in current versions of Wine. The Wine Weekly Newsletter and the wine-devel list discuss this tool, but in a way of people who know how to access it, so I haven't been able to get more information without a copy of Wine in front of me to see how it works (meaning, is it only able to run automatically when you first run Wine-- which, atm, I suspect is the case-- or is it a userspace app, and if so, how does a user run it?).

But since the drive mappings are now actually easier (make a symlink), the PATH being set in the Registry is not a big problem (since one usually puts the full path to the executable in a script or shortcut, or runs the executable from the directory where it lives), and per-app settings are still set from the config file just like before (meaning, usually manually), winesetuptk is not really useful for much anyway (unless the user has a hard time changing a "Y" to a "N" in the [x11drv] section, or really can't find the hidden .wine folder, thus needs a GUI to do those minor tasks for which winesetuptk can still be used).

It might be worth your while to check out Frank's Wine Tools, though-- they are in the process of being updated to the new Wine standards, and I don't know how far they've gotten with it at the time of this writing, but Frank's site (Frank's Corner), and his tools, are always worth watching if one is a Wine user.