An update to my post above, I found a small glitch and a fix to correct it.
(
fix_#2) When PreUsenet was running in
Folder mode, testing with 3 small files, I noticed an error message regarding 'settings.bat', file not found. This displayed right after the 'PAR creation completed' message.
Source of error was on
line 60 :
-was : call settings.bat
-fixed to : call "%INSTALLPATH%settings.bat"
This also fixed a problem I noticed with the files ending up
in nested folders; i had a test1 folder, with 3 small avis. The resulting package (before fixing) was :
test1\ video1.avi rars, pars, sfv
test1\test1\video2.avi rars, pars, sfv
test1\test1\test1\video3.avi rars, pars, sfv
All those folders placed in the Destination folder set in settings bat. This gets fixed by the
line 60 modification.
(
fix_?) I noticed another funky bit, if there are files with parentheses in their names, PreUsenet sometimes aborts very early in the run process.
This only happens in
File Mode, interesting enough there's no problem if it's running in Folder mode. The command line closes very fast, can't catch if there's any error message there.
The logfile gets initialed, but all that is on it is the version number (this one showing my test version 102) :
PREUSENET 01_10_08_[blitze_102] - 18_36_15
---------------------------------------------------
Tested with 3 small files, named ABC(123).avi, ABC[456).avi, ABC(789].avi ; used very short filenames on purpose, since I wasn't sure the file I originally encountered this behaviour on had a filename too long.
A couple work-around solutions for this :
a. Rename the file, replacing parentheses '
( )' with square brackets '
[ ]'. There's no problem processing it in
File Mode then.
b. Or simply run the job in
FOLDER Mode instead, there will be NO errors in that case. (select the folder where the file is in, not the file itself, for processing.
As I read thru and test things, hopefully I can learn more about Windows scripting commands and find a fix.
----[ topic change ]-----------------------------------------------------------------------------------------------------------
On another subject, I did some reading and testing on settings for optimal RAR and PAR2 filesizes for posting.
Created
another thread here in the forum for that topic since it was a long message and it's best to have a focused thread.
Hope that sharing these fixes and info can be useful to all. Cr4zyfrag was very supportive when I asked if it was ok to post fixes and mods, so I will be sharing any modifications I work on.
Thanks cr4zyfrag, it's clear that you spent a lot of time making PreUsenet such a simple to use, yet so feature rich script.