ACL command parameter not worked after upgraded from 2.8 to version 2.9

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start Windows XP command prompt
2. go to mongoose installed folder
3. type command 'mongoose -l "-0.0.0.0/0,+127.0.0.1" ', w/o the single quote 
and press enter.

What is the expected output? What do you see instead?
Expect the server will start and only allow localhost to access. 
But server not started and only show parameter options.

What version of the product are you using? On what operating system?
Just upgraded from 2.8 to 2.9 on Windows XP SP3 English

Please provide any additional information below.
In version 2.8, typing the command 'mongoose -acl "-0.0.0.0/0,+127.0.0.1" will 
only allow localhost access to the server. 
But after upgrade to 2.9, the option changed to -l, it doesn't start the server 
but showing the options list available.

Original issue reported on code.google.com by mira...@gmail.com on 6 Sep 2010 at 2:43

[GoogleCodeExporter]

I've managed to introduce a bug during refactoring.
Fixed. I plan to build windows executables from the recent sources to make it 
easy for people to test things, http://code.google.com/p/mongoose/downloads/list

Please note that in that recent version, windows code is not console-based 
anymore.
I am putting service management and some minimalistic systray GUI into windows 
version.
So service could be registered by "sc create Mongoose binpath= mongoose.exe" 
command, etcetera. srvany.exe and installer will not be needed.

Please verify and confirm that ACL problem is fixed.

Original comment by valenok on 6 Sep 2010 at 8:55

• Changed state: Fixed

[GoogleCodeExporter]

Thanks. The ACL parameter working now with the new executable.

Also, using sc command to register has Windows service on XP is OK

BTW, how to set parameters for a service, e.g. root directory? As the sc 
example provided will use %SystemRoot%\System32 as root directory, it is very 
dangerous.

Original comment by mira...@gmail.com on 7 Sep 2010 at 1:25

[GoogleCodeExporter]

The only way to set parameters for windows service is to use config file.
Create mongoose.conf file in the directory mongoose.exe is located.

Original comment by valenok on 7 Sep 2010 at 7:02

[GoogleCodeExporter]

In that case, could the root folder being set inside the folder where 
mongoose.exe reside by default instead of %SystemRoot%\System32, even there is 
no config file present, especially when configuring as a Windows service? 

Original comment by mira...@gmail.com on 11 Sep 2010 at 9:00

[GoogleCodeExporter]

I don't like this idea.
Default document root should be a current directory - for the vast majority of 
use cases.
Windows service is probably the only exception, and I don't want to change the 
default behavior just to accomodate windows service case.
I believe using a config file is a solution.

Original comment by valenok on 11 Sep 2010 at 10:01