I've searched the forums for AMD64 and IPX but couldn't find a solution here. I am running Debian Lenny 2.6.26-1-amd64 on an AMD Turion 64x2 1.60GHz system with 1GB of RAM. I have Wine running and it runs my older games just fine (this is a laptop with an ATI1100M so no new games here!) but it doesn't seem to work with IPX. I installed the IPX tools package and ran the commands below as root. Code: modprobe ipx ipx_interface add wlan0 802.2 0x00000001 If I check the interface, it is there, even after rebooting, so I believe that it is working. However, if I try to play a game that requires IPX for LAN-play, such as Lords of Magic SE, I can get into the IPX screen and enter a game name, but it won't create the game, as though IPX is not installed. The game runs flawlessly in single-player despite what the AppDB says. Then again, the AppDB has a very old review of the game. I am running 1.1.17, clean install. Do I have to configure Wine to tell it that IPX is installed, or is this a problem with 64bit Linux. I came to Linux to try this since IPX in XP Pro x64 is a broken, unsupported 64bit version that doesn't work with anything.
Anybody? I'd like to be able to play some of my older Win9X games on the laptop via Wine, but I don't see a tutorial or FAQ page on IPX, much less IPX on an AMD64 build of Linux. What do I have to do to make IPX work in Wine?
Sephiroth wrote:> I am running 1.1.17, clean install. Do I have to configure Wine to tell it that IPX is installed, or is this a problem with 64bit Linux.Check config.h file to see if Wine detected and compiled support for IPX. There are might be some problems with 32<->64 bit compatibility as well for things that no one uses now days.
I downloaded a deb from the repository instead of building my own. I assumed that Wine supported everything that Windows games would need by default. If not, I can build my own.
Red Alert had a UDP patch to allow LAN play via UDP/IP. 99% of the games out there that used IPX did not get their code changed from IPX to UDP. In fact, Red Alert is the only game that I know of with such a patch. In fact, most games that used IPX for multiplayer wound up only being playable online through tunneling via a service like Heat, Kali, MPlayer, or others. Also, I don't see why you would need to be root to use a protocol installed on the local machine available to all users. That sounds like a major Wine bug. I'll try running LoMSE as root to see if it fixes the problem. If it does, we should file a bug report if one hasn't already been filed. I know for a fact that normal Linux applications don't need root access to use IPX because I have done so in the past.
Still not helpful, even if root is the only one that can manage IPX (design flaw in the kernel, not good) Wine still won't operate as root. What good is having IPX in the kernel (or in Wine for that matter) if it's useless due to being root-only?
How? I've tried the standard method of using "su" followed by the user and then the command-line, but it won't start, complaining about being root.
Two problems with that. Wine doesn't run in the shell, and root isn't allowed to login to X. I tried using the "root shell", but that is just a different color terminal that appends "su" to every command issued. Therefore, I no of no way to get an X display as root.
I didn't mean that shell in KDE, I meant a REAL shell. In other words, raw Linux. As in, without X installed style shell. The shell you get to when you use ALT+N at the KDE login. I didn't mean it wouldn't run from a terminal in X. As for enabling root to login to X, not going to happen, too much of a risk. I still need a working solution however.
When trying that, I get the same error described above. Code: ~/.wine/drive_c/Games/Sierra/LOMSE$ su - root wine ./lomse.exe Password: /usr/bin/wine: /usr/bin/wine: cannot execute binary file Since "-" and "-l" are the same, I tried "-l" also with identical results. You are right though, 1024+ are usable by normal users. I cannot understand for the life of me why they even bothered putting in IPX support if it's broken and useless. I am really aggaravated at the insane amount of trouble I am having with such a reliable protocol in Linux. I probably have around 30 games that rely solely on IPX for LAN games that will be unplayable if this can't be fixed. I love Linux, but with the alpha-state of the ath5k module being included in new kernels and this broken IPX crap, I am beginning to lean towards XP again. At least I can dual-boot 32bit and 64bit XP and use my games.
Too much trouble, I guess Linux just isn't worth anything beyond TCP/IP or UDP/IP yet. I know this isn't a Wine problem now, however. The whole thing with Linux is not having to run as root. Locking out IPX is the incredibly large loop-hole in that sense, since some of us still use IPX programs and Novell shares. Guess I can close my post about not being able to talk with Novell machines over on the other board as well. I now know why nobody can talk with the Novell machines. Back to Windows we go unless we get a quick kernel patch to fix this bug. Thanks to everybody that helped!
On Tue, Mar 31, 2009 at 7:44 AM, Sephiroth <wineforum-user at winehq.org> wrote:> Locking out IPX is the incredibly large loop-hole in that sense, since some of us still use IPX programs and Novell shares. ?Guess I can close my post about not being able to talk with Novell machines over on the other board as well. >Novell has been recommending IP for AGES.... IPX is mostly dead and only seen in old applications. A separate project implementing IPX over IP on Windows, that is also tested to work under Wine might be the best solution... (Wine would probably need to implement proper DLL load orders if wsock32 is replaced and calling the normal version thereof... (http://msdn.microsoft.com/en-us/library/ms682586.aspx and http://bugs.winehq.org/show_bug.cgi?id=14980 all seem related...)) Gert
It's used for more than gaming, but yeah I have a ton of games that use IPX and I am sure other people do as well. IPX is also lower-latency than TCP or UDP, but it only works on a LAN. I have often considered using IPX only on my LAN and using a Linux server between my DSL modem and LAN to convert the IPX data to TCP data and send it on its way, but never got around to implementing it. That'd make hacking my network rather difficult! You are right about only root dealing with mounting, but my normal users can mount, unmount, read, and write NTFS drives both internal and external, as well as optical and flash media. They can also share files in their home directories using KDE. Not allowing IPX the same privilege and not having an easy way to do so is just bad design.
You're right, I wasn't thinking that my common programs like Firefox might not even know what IPX is. Still, it would be one heck of a sweet setup if it was possible! As for IPX being superior, it simply is. The problem is with range. I don't remember the specifics, but IPX doesn't travel very far for some reason. I do know that Intel (maybe IBM?) has a buried cable running from an office somewhere in the northwest USA to another office southwest and a state or so away. Why don't they use the Internet? They use IPX! They also have some hardware on that line every so many yards to clean up the signal and send it on its way again. I imagine it's very expensive, but they want to use IPX for some reason. I also never tried using the root group before, so I honestly didn't know that it didn't grant root privileges. I've used Linux for years, but never had this sort of problem before, so I never tried such a bad thing. Thanks for the information though!
That's what the reason was. I had forgotten what the problem with IPX was that made it unacceptable for the Internet, but that was it. Still, I have a friend who worked for Intel and he once told me about that private line running between two big offices in separate areas. I'll ask him about it when I see him again.