PREUSENET

[itsjustme34]

just change the part in line 259 and 269 from:

"%TARGETLOCATION%\%FILENAME%.rar"

to

"%TARGETLOCATION%\%FILENAME% - your text here.rar"

Thank you very very much... this has made life allot easier... top top man

[itsjustme34]

Hi,

Is it also possible to have the SFV files and also the PAR files with a set name?

as per my previous post question which worked a treat.

[P3tr0ck]

sorry i don't work on it anymore, because i also don't use it anymore.

you can try doing it yourself if that m2r has a commandline, look at the commands and play with it a little in windows "cmd window"

So what do you use now?

[cr4zyfr4g]

I simply do not use windows anymore

[P3tr0ck]

your a better man than i   

[soritose]

   
Hello

werst it is a horny Program (bat)

jest, we have a broplem Wür from Windows 2003 to Windows 2008 jest geweselt he does not want mer as it pertains to

Who do you also have no windows mer fieleicht you can do that again working on the windows is 64 bit version

hir times a lock file

---------------------------------------------------
Now processing Set 1: test
creating Targetlocation: C:\Neuer Ordner\\Neuer Ordner
using Rarsize=15, Par2blocksize=768000 and Redundancy=10
Creating Rars

It does not matter what I settings.bat in the entries, he always wants to rare

danke schon mal

sory Googel Übersetzer

[blitze]

Thank you, cr4zyfr4g - amazing work on this. 

Noticed some error messages scrolling by when trying it out, and worked out a fix for it. It happened when it tried to write to the log file, the default filename was created including the system date, but it has slashes ('03/10/2009', illegal in a file name).

A small edit fixes it. Original code :

@ECHO OFF


set PVERSION=01_10_08
set TDATE=%DATE%
set TADD=%time:~0,2%_%time:~3,2%_%time:~6,2%
SET INSTALLPATH=%~dp0

Line 5 (in bold above) was the problem - fixed with :

@ECHO OFF


set PVERSION=01_10_08
set TDATE=%date:~0,2%_%date:~3,2%_%date:~6,4%
set TADD=%time:~0,2%_%time:~3,2%_%time:~6,2%
SET INSTALLPATH=%~dp0

This worked fine, producing this log file : "log.03_10_2009.16_16_17.txt" on my system.

Reading the previous thread pages, I noticed ajp's post, he was referring to these same error messages.

Again, many thanks - this tool is so easy to use. Great work.

.

[blitze]

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.

[blitze]

Just added another modification to my PreUsenet script. Tested and it works, solved the problem as intended.

Issue : smaller .MKV files (increasingly more common, as people adopt h.264 for encoding), those files did not feel right if packaged with the default 50 MB RAR part size. For a large .mkv, that is fine; for one under one GigaByte, I would prefer the smaller 15 MB RAR part sizes.

Fix : Reading thru the code, it's not far from the beginning. You can see a block of code where the filesize is checked and the decision of RAR and PAR sizes is made (line 73 on the original PreUsenet copy):

Code:

if %SIZE% LSS 2147483648 ( ....

This check triggers a couple other checks - for a filename with .MKV extension (setting the MKV size variables, BIGSIZE, BIGBLOCKS), or use the blue ray megasizes (100 MB RARs).

Easiest fix (without editing the test conditions) is to bypass this whole block if the filesize is small, in my case, smaller than 1 GB. Used a simple GoTo to skip over the block of code and let it use the smaller RAR and PAR part sizes.

I inserted two lines of code :

Just before line 73 :

Code:

if %SIZE% LSS 1073741824 goto NoBigBlocks

Just after the original line 88 (a ')' closing the test loop), add the exit label for the goto :

Code:

:NoBigBlocks

Quick and dirty, yet it works without me breaking the test loops.

The full block of code now looks like this :

Code:

rem --- Disabling large block size for small MKV files (less than 1 GB size), blitze modded v.103 :
if %SIZE% LSS 1073741824 goto NoBigBlocks

if %SIZE% LSS 2147483648 (
if "%MODE%"=="A" (
if exist "%PATH%\%FILENAME%.mkv" (
set RARSIZE=%BIGSIZE%
SET PAR2BLOCK=%BIGBLOCK%
ECHO mkv detected
ECHO mkv detected >> "%INSTALLPATH%log\log.%TDATE%.%TADD%.txt"
)
)
) ELSE (
set RARSIZE=%BLUSIZE%
SET PAR2BLOCK=%BIGBLOCK%
ECHO big file detected!
ECHO big file detected! >> "%INSTALLPATH%log\log.%TDATE%.%TADD%.txt"
)

:NoBigBlocks

[klepto]

I have been looking everywhere for a script that would do this.
I saw that on the first page of this thread it shows the versions from 2008.
Where do I download the most recent version?

[std69]

for people that have windows 7
edit PREUSENET.bat with a text editor
search for these lines:
SET MODE=A
if "%SIZE%"=="0" ( SET MODE=B)

change to :
SET MODE=B
rem if "%SIZE%"=="0" ( SET MODE=B)