Freelancer working with Wine 1.1.20

@StarTrader:

@M0tah:

I think to get Freelancer to connect to FLServer I had to specify the computer’s IP address when starting FL with the -s command line option. It’s been a while though, so I’m not sure.

But this is running in Linux. Do you mean you did this in Linux too?

Yeah, in Linux. I was also using native directplay DLLs, though, which may have had something to do with it.

@StarTrader:

May be a firewall problem.

In Windows, as well as permitting Freelancer.exe and FLServer.exe, you need to permit Microsoft DirectPlay8 Server, the file is C:\WINDOWS\system32\dpnsvr.exe

This was my problem a couple of times until I started remembering it! :lol:

And… I don’t think Linux has an equivalent to this? So - are we back to another barrier? Shame if so, it will be a big plus to get through this problem.

Pumpurumpum…
Windows with firewall disabled and Pardus…
I dont see anything by “ps -A | grep iptables”
Or Pardus may use another firewall?

2 tai: Dunno how in Pardus getting newer version, may be i need to compile it from sources…
Patch 1.1? Will check…

@M0tah:

Yeah, in Linux. I was also using native directplay DLLs, though, which may have had something to do with it.

I am out of my depth here, maybe if you can explain what you mean to the guys here they can succeed with this?

@tai:

I know what it is:

You just take a normal windows .dll file out of the win/system32 dir and use it with wine

Often it solves Problems, but also creates new ones. Sometimes it works with one version, with another not!

And where to take “true” win32 dlls for wine ? 8 [ ]
I was using winetricks script than dependency walker to find missing dlls…

I’m very interested in this solution guys, hope you can find a working method soon.

@tai:

You could use some site like this

Or search it on Google

Btw: Freelancer can’t create IDs with Wine, I’ve got a workaround for that but before releasing it, I have to ask in the private section.

Khmm … Ok! I thought there same dlls as well as windows xp for example.

@tai:

FLServer prints a hell of messages into my terminal when I open it, so it’s very likely that there is some Bug in Wine.

Yep, its true.

@Win: Vista may be? Check out your antiviruses

I know that I always had that problem on windows, too. But I just don’t know the solution now!

Was redirected to this part of your posting ^^

May this thing help? http://dplay-masq.sourceforge.net/faq.html

Can I use this thing to run a DirectPlay server?

You sure can! As of version 0.2.00 you can use the “host=www.xxx.yyy.zzz” command when insmod’ing the module to specify a local host to use as a server. Any incoming DirectPlay connection attempts will be forwarded to this host. Future versions will hopefully include dynamic host lookups by hostname, as well as the ability to change the host without having to remove the module and re-insmod’ing it. I’ve tested this functionality with three external (Internet) clients connecting to my local host and it worked fine. However, any clients on your LAN that are ALSO connected to the same game host will not properly communicate with clients connected from the Internet. See the Known Bugs section of the README for more information about this problem. Finally, be aware of the inherent limitation in the DirectPlay protocal that only ONE host behind your masquerade server is supported at a time. Other computers may act as clients to games on the Internet at the same time, but only one local computer can host a game at a time. This is inherent to the fact that the server port can NOT be specified by clients connecting to your game, and every incoming connection will always hit the same port.

Sorry, haven’t read the whole thread, is FL Server (!) working with linux now?

No. You might be able to get it to somewhat work using native directplay DLLs though.