0.6.15 must have done something very nasty during installation - 'cause now I can't get this working with any older version at all (and I'm not going to reinstall windows to test this...)
- this also is the case when I intall the other version in a fresh/new directory
odd thing is: e.g. on a cmdline, I don't have any issues with drive "W:\" - e.g. I can do "mkdir W:\Test" without any problems; I too can e.g. extract the archives from the incomplete folder to W:\ via Explorer - only the scripting behind sabnzbd all of the sudden refuses W:\ now... :-(
what can I do to debug this further? - any verbose logging-options for sabnzbd available??
maybe a hint to find what's causing this:
when I try to put the directory for all completed downloads on drive W:, I get following error (which I also get trying to access "W:" via its UNC name):
Cannot create complete_dir folder W:\UseNet
logfile (as of sabnzbd 0.6.1) reads:
2012-03-01 14:30:19,542::INFO::[misc:342] complete_dir directory: \\192.168.1.30\UseNet does not exist, try to create it
2012-03-01 14:30:19,542::ERROR::[misc:344] Verzeichnis \\192.168.1.30\UseNet konnte nicht angelegt werden
2012-03-01 14:32:24,690::INFO::[misc:342] complete_dir directory: W:\UseNet does not exist, try to create it
2012-03-01 14:32:24,690::ERROR::[misc:344] Verzeichnis W:\UseNet konnte nicht angelegt werden
I just looked deeper in the logfile: accessing W: did work with 0.6.14 - but after installing 0.6.15 the previous version (and all others I tested) also fail :-(
even though I still couldn't re-animate my drive "W:\" within sabnzbd (also not after resetting/restarting everything in line (routers,switches,the box itself...) plus re-asserting the drive-letter W:), I kind of workarounded this:
instead of using "W:\" I am now using the UNC name "\\WDTVLIVEHUB\WDTVLiveHub" - maybe that's how it was supposed to be from the beginning?
-> with this, it's working again (and even with version 0.6.15) :-)