Ok, i'm almost there, i have installed it, i can run it, sounds good right? Only one problem, my keyboard wont work at all in game, everything i write appears in a terminal, or if i dont have a terminal up, it just dissapears I had the same problem with SC before, but i fixed it with this:

; Enable DirectX mouse grab
"DXGrab" = "Y"

I dont understand why i have a problem that is already fixed ;( Getting confused now

Are you running it full-screen? I haven't experienced that problem, though I do remember having similar issues with other programs under Wine. A couple of other config options you might want to try are:

"UseTakeFocus"="Y"
"Managed"="Y"

Though those are just a guess... These work for me, though.

Yes, im running it fullscreen, and those options were already enabled

Edit: I have one more problem with d2, besides the keyboard problem, i cant play a TCP/IP game. It says "Cannot detect a valid TCP/IP adress". Well, that doesent matter until i got my ketboard to work anyway :/

I guess the first question I should've asked is which version of Wine you are using. If it's an older version, maybe there are problems with it. I've also had better luck installing from source, but it can be a pain collecting all the necessary libraries for that.

Another thing that you might try is running it from a Gnome or KDE "run" dialog, or by using a shortcut, rather than running it from a terminal window. Maybe the terminal window is trying to keep the focus.

Im using Wine 20031016, I tried with WineX first, but i had problems with almost all games. Im wondering if i should install WineX again to test, but i dont want to remove wine, because warcraft 3 and other games works fine with it. If i compile winex from CVS, can i install it without removing wine then? If that would work, i think the problem will be solved.

Im running D2 from Fluxbox, so it cant be the terminals fault.

Well, I am stumped then Maybe someone else will have some ideas.

You have Warcraft 3 working in regular Wine (not WineX)? I may have to give that a shot. WC3 is about the only thing I miss about Windows.

just because you're in fluxbox doesn't solve anything. fluxbox has a "run" type utility also, and all those things do is to launch your program from the actual terminal instead of a virtual terminal (like an xterm or rxvt) but those virtual terminals could be trying to hold onto the keyboard focus so it's a good idea to try it.

Hi... I *think* I have the solutions to your problems

For the keyboard problem, I have it also in may games (DeusEx through Wine is a pain because of this!) but found out that if I ran it under an X failsafe session (you know that option that gives you GDM), since there the focus will follow the mouse and in all apps runing trhough wine the mouse will be set at the top left corner, the child window will inherit that focus that is lacking running a WM. Why is this so, I don't know, but that is the only way I've found I'm able to run DeusEx's Zodiac mod .

Regarding your problem about the IP address (the game complainting it is not a valid IP, if you are behind a Router or something, you can try this (may work if you dial up, also, mind you):

In a terminal su to root, and open (with your favorite text editor) the file /etc/hosts, then just modifiy as you like:
In the event you're on dial up, you may simply have commented out the second line, then when connected to the Internet, simply verify the IP your ISP gave you (with ifconfig ppp0) and put that address instead of <LAN IP>. The tag <computer name> is the name you'd like your computer to be identified as. Also you may check that with the neat program (in case you have it) under the DNS tab. If you don't have this program, the /etc/hosts file should suffice.

Good luck!

There has got to be a better way than running in fail safe mode

rile - well, I went and got Warcraft 3 installed, and what do ya know - I'm having the exact same keyboard problem in it now! In fact, although the game appears to be running full-screen, if I move my mouse against the edge, it displays the rest of my X desktop. Keyboard commands just go into the terminal window I ran the game from.

I will definitely be more motivated to find an answer now, so I will let you know if I figure anything out. Now that I see it happening, I remember having the same problem with Diablo II when I was first attempting to run it in Wine. I think it was some registry setting that I messed with that fixed it, but I forget since it's been so long.

My keyboard is working now! I found this on google:

http://ting.homeunix.org/cvs_wine/GetWineX.html

Just download a script, it will download the CVS and then install it so it doesnt collide with wine.

I still have the TCP/IP problem, because i cant remember what my localdomainname is. Can i run a command to check computername, localdomainname and localhostname? If i now that, the thing that Thetargos wrote probably works

you don't need to know them. They are aliases in the /etc/hosts file. What happens is this:
For instnace my /etc/hosts file looks like this:
What goes in there is like this:
The computer by the IP <LAN IP> has the name of Thetargos and the alias localhost and another alias localhost.localdomain.
This is so some programs (remember that the intrisics of Linux tend to do thing in such a way that processes and programs run with a server-client logic) assume that the IP concerning this computer is the one to which they should connect (likewise in the case of the 127.0.0.1 address) So you simply are calling your computer by three names, in my case Thetargos, localhost and localhost.localdomain, so programs looking for the string localhost (like Quake3 and other programs) know the name of the computer is really Thetargos. So you don't have to know the name of your localdoman

I have changed my /etc/hosts now, it looks like this:

But it still says "Cannot detect a valid TCP/IP adress" in D2. The problem is that i'm not really sure that my computer name is Overlord, i think that can be the domainname, or something like that :/ Can i check my computername somehow?

Comment out your first line (127.0.0.1)

The name of the computer should be on that file (hosts) and by issuing this command:

Ah, its working now! I dont know how to thank you :> Thank you very much!