Odd issue starting login_server.exe in cygwin

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Compile server from source code (win7 using cygwin)
2. Attempt to start server's in proper order.

What is the expected output? What do you see instead?

I expect the server to start, but I am getting multiple errors.

{{{
$ login_server.exe --nodaemon
/usr/local/share/sylverant/config/sylverant_config.xml:3: validity error : 
Validation failed: no DTD found !
<sylverant_config>
                 ^
[2011:08:08: 05:22:32.348]: Invalid Tag welcome on line 7
[2011:08:08: 05:22:32.350]: Invalid Tag colors on line 8
[2011:08:08: 05:22:32.353]: Invalid Tag raremonsters on line 10
[2011:08:08: 05:22:32.355]: Reading quests...
[2011:08:08: 05:22:32.366]: Couldn't open param/param_files.txt
}}}

I added the {{{ and }}} to indicate the entire error message.

What version of the product are you using? On what operating system?

Latest SVN, compiled on Win7 64bit via cygwin

Please provide any additional information below.

Based on searches within the googlecode it appears that this is a required file 
for Blue Burst, but there doesn't seem to be any documentation on all the 
files. Nor does it seem the files are included. Soooo.... how do I go about 
fixing this? hahaha

Original issue reported on code.google.com by hakugin....@gmail.com on 8 Aug 2011 at 5:29

[GoogleCodeExporter]

I apologize for not noticing this report earlier. Anyway, the real issue at 
hand is the fact that the documentation for everything other than ship_server 
hasn't been updated in a long while. The validity error is because the 
sylverant_config.xml file that you're using isn't making a reference to a DTD. 
The invalid tag messages are because those tags are no longer used or allowed 
in the XML (just remove them entirely).

The Blue Burst related stuff is a bit more work to take care of. I do not 
actually distribute those files with the source code or anything of the like, 
as they are data files that the server sends out, and not actually part of the 
source. Also, they were all originally obtained from Sega's servers by dumping 
the packets as they were sent. I believe most of the files that I use came from 
Fuzziqer's newserv. You should be able to find most of the files in there. The 
exception will be the param_files.txt file, which is just a listing of the 
files to load as Blue Burst parameter data.

I wasn't aware anyone was even trying to use login_server at all other than 
myself, so I haven't worked on the documentation for it for a while... Its sad 
to say, but documentation writing is rather tedious to me, and not something 
that I generally enjoy all that much...

Original comment by bluecrab on 3 Sep 2011 at 2:22

• Added labels: Type-Other, Priority-Low, Usability
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Original comment by bluecrab on 3 Sep 2011 at 2:25

[GoogleCodeExporter]

Original comment by bluecrab on 16 Feb 2012 at 2:35

• Changed state: Done