Not sure how SS is to be started with the new logging.  Is --logfile <path> is still valid?

Using the following to start up on Windows XP from the console:

C:\>C:\Perl\bin\perl.exe "C:\Program Files\SlimServer\server\slimserver.pl" --playeraddr 192
.168.9.3 --httpaddr 192.168.9.3 --httpport 80 --cliaddr 192.168.9.3 --streamaddr 192.168.9.3
 --noupnp

I get the following error:

Can't open  (No such file or directory) at C:\Program Files\SlimServer\server\CPAN/Log/Log4p
erl/Appender/File.pm line 87, <DATA> line 164.

With --logfile D:\slimserver\slimserver.log appended to the startup command, I get the following.  If the file exists, SlimServer actually _deletes_ the existing log before crashing.

'D:\slimserver\slimserver.log' is not recognized as an internal or external command,
operable program or batch file.
[19:59:14.0455] main::init (245) SlimServer OSDetect init...
Cannot write to 'D:\slimserver\slimserver.log': Invalid argument at C:\Program Files\SlimSer
ver\server\CPAN/Log/Log4perl/Appender/File.pm line 210, <DATA> line 164.
[19:59:14.0462] Slim::bootstrap::theEND (335) Got to the END
Cannot write to 'D:\slimserver\slimserver.log': Invalid argument at C:\Program Files\SlimSer
ver\server\CPAN/Log/Log4perl/Appender/File.pm line 210, <DATA> line 164.
END failed--call queue aborted, <DATA> line 164.