Leaf has got a point there. Using anything where third parties have access to transfer files will do no good.leaf wrote:Ahh, famous last words..
(btw, if it's 1MB package even I could host it)
Request: Precompiled Win32 CF server
Moderator: Board moderators
Well, I don't really see the problem with placing the binary on the supplied account. It should be fine if a checksum is provided for the download. If not, it's easy to sigup for a geocities site and place it on a personal webpage.
Perhaps someone in the dev team could place a precompiled Win32 server on the CVS. I'm currently considering making a new Win32 crossclient, but it would be from scratch and I'd need a localhost server for testing. I don't mind coding my own client from scratch, but I don't feel like spending a lot of time trying to compile the server myself since I don't have Python, Visual C++, or the patience.
Not sure how many Windows users would play CF if they had a working client, but right now the GTK client is extremely bugged and I can see why the game isn't attracting Windows players. The coding of a new client wouldn't be too difficult, just very time consuming and painful (it's always painful trying to implement other people's network protocols!).
Perhaps someone in the dev team could place a precompiled Win32 server on the CVS. I'm currently considering making a new Win32 crossclient, but it would be from scratch and I'd need a localhost server for testing. I don't mind coding my own client from scratch, but I don't feel like spending a lot of time trying to compile the server myself since I don't have Python, Visual C++, or the patience.
Not sure how many Windows users would play CF if they had a working client, but right now the GTK client is extremely bugged and I can see why the game isn't attracting Windows players. The coding of a new client wouldn't be too difficult, just very time consuming and painful (it's always painful trying to implement other people's network protocols!).
I think the point being made was not to give out the password on the web or it will get filled up with weird crap pretty fast.
Anyway, Please don't go off and start a new client on your own, it would be much more productive and better for everyone if you worked with the other people doing client related stuff and used the common client code for what ever you can. The reason the DX client and the Win32 client are no longer available for windows users is because they were self contained code base and not maintained. It is a loosing battle to maintain many versions of the client as the changes become very hard to co-ordinate. You certainly don't have to work on a GTK client if you prefer working in another tool (there is a developer or two working on a SDL client, there is a gnome client that needs work.), but I think that there is a consensus that the bulk of the client should be in the common code. I refer you to a recent remark on this very thing- http://www.metalforge.net/cfmb/viewtopic.php?p=944#944
The last thing we need is to have our skilled people all doing the same work on different clients.
Anyway, Please don't go off and start a new client on your own, it would be much more productive and better for everyone if you worked with the other people doing client related stuff and used the common client code for what ever you can. The reason the DX client and the Win32 client are no longer available for windows users is because they were self contained code base and not maintained. It is a loosing battle to maintain many versions of the client as the changes become very hard to co-ordinate. You certainly don't have to work on a GTK client if you prefer working in another tool (there is a developer or two working on a SDL client, there is a gnome client that needs work.), but I think that there is a consensus that the bulk of the client should be in the common code. I refer you to a recent remark on this very thing- http://www.metalforge.net/cfmb/viewtopic.php?p=944#944
The last thing we need is to have our skilled people all doing the same work on different clients.
> I think the point being made was not to give out the password on the
> web or it will get filled up with weird crap pretty fast.
If that was it then the points being made were irrelevant. All I need is the server binary placed there for one download, then the account can be deleted. Whether it is filled with crap is not important at all.
I was assuming people thought it was a problem because someone could secretl replace the server binary with a virus infected version.
About coding a new client --
I'll take a look at the SDL client, but I wouldn't even consider working on the GTK client. The crashes I'm getting are due to both assertion failures and library runtime errors. When applications start showing these faults--especially faults in the linked libraries--it's time to write new ones. The current major fault in the GTK client is a DC copy which is a basic (simple) Win32 function. The failure of the GTK client to save the DC to memory is a sign that there is a bug in the GTK Windows port, so working on the GTK client would be a bit pointless.
> web or it will get filled up with weird crap pretty fast.
If that was it then the points being made were irrelevant. All I need is the server binary placed there for one download, then the account can be deleted. Whether it is filled with crap is not important at all.
I was assuming people thought it was a problem because someone could secretl replace the server binary with a virus infected version.
About coding a new client --
I'll take a look at the SDL client, but I wouldn't even consider working on the GTK client. The crashes I'm getting are due to both assertion failures and library runtime errors. When applications start showing these faults--especially faults in the linked libraries--it's time to write new ones. The current major fault in the GTK client is a DC copy which is a basic (simple) Win32 function. The failure of the GTK client to save the DC to memory is a sign that there is a bug in the GTK Windows port, so working on the GTK client would be a bit pointless.
Uploaded
Ok, just uploaded the file.
You can find it at:
http://www.geocities.com/win_crossfire/ ... indows.zip
Note, there is only the exe.
I made a small readme, should be enough (read it before asking please
).
Or ask here & i'll try to reply.
Here's the MD5:
ceac54c84a286bff54e4f5ddcade5d52 *crossfire-server-windows.zip
Enjoy.
You can find it at:
http://www.geocities.com/win_crossfire/ ... indows.zip
Note, there is only the exe.
I made a small readme, should be enough (read it before asking please
).Or ask here & i'll try to reply.
Here's the MD5:
ceac54c84a286bff54e4f5ddcade5d52 *crossfire-server-windows.zip
Enjoy.
I tried to run the server but it has a pile of errors:
1. Lots of "Unknown color" reports
2. Lots of "Failed to find archtype" reports
3. Program exits and reports (exact wording):
"You need a archtype called 'map' and it have to contain start map"
I checked the cvs and couldn't find any file called 'map' for the share directory, and it wasn't in the archtype or bigworldmaps tarballs.
1. Lots of "Unknown color" reports
2. Lots of "Failed to find archtype" reports
3. Program exits and reports (exact wording):
"You need a archtype called 'map' and it have to contain start map"
I checked the cvs and couldn't find any file called 'map' for the share directory, and it wasn't in the archtype or bigworldmaps tarballs.