Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
IM having trouble getting the post processing script to run. I've made a RoboCopy.cmd file doing some string manipulation and moving files from the SABnzb computer to my NAS. Running the script manually works flawlessly. Looking in the logs it seems as it should work, or?
The double backslashes are OK, that's just a Python habit of displaying strings.
Be aware that all parameters passed to your script have double quotes around them.
What I do find strange is that your stuff is installed in "C:\Program\SABnzbd".
Normally it is installed in "C:\Program Files\SABnzbnd".
Is "C:\Program\SABnzbd" the correct location?
If not, how did you specify the location of your script to SABnzbd?
I'm running SAB as a service and the path is correct (all languages doesn't use "Program Files" ).
the double quotes, they could be the reason... unless it's some user right thing. THANKS for the tip!
A bit OT, but why specify dependency to TCP/IP when configuring as a service (from the wiki)?
The service stops working if i log in and the out from the system and Im suspecting the TCP/IP dependency...
Still cant get the service to survive log off.
From information of srvany.exe:
Programming Considerations:
For WIN32 graphical applications: when the currently logged-in user is
logging-off, all WIN32 top-level windows receive WM_QUERYENDSESSION and
WM_ENDSESSION messages. Some WIN32 applications choose to terminate upon
receipt of such messages. In order for your WIN32 application to survive
logoff, it must not do that: instead, your windows procedure should call
the default windows procedure on these messages.
For WIN32 Console (i.e. character-mode) applications: when the currently
logged-in user is logging-off, all Console applications receive a
CTRL_LOGOFF_EVENT event from the Console. If your Console application has
registered a Console event handler (via SetConsoleCtrlHandler), it must
ignore CTRL_LOGOFF_EVENT in order to survive the logoff.
I tried all sort of tricks to avoid killing the application even tried the sabnzbc.exe -d switch (wich i dont knof if its needed)
You are very clear, and Im thankfull for that.
Im using the SABnzbd-console.exe file.. a strange thing though, both have the exact same size 79360bytes... could this be right?