Not now, I double checked it...didn't see that anywhere...or submit anywhere inside of the thread.
[center]
Edit
Last edited by SonsOfLiberty; 07-08-2009 at 02:47 AM.
[center]
SOL, can you please send me an NZB file that has this bug?
Not sure I understand how it's occuring.
Are you saying you upload it here, it's fine, then download it from here, then reupload it here and it's no longer good?
Please just send me one NZB with this problem when you upload it, along with where you got it from, and I'll definately take a look at this asap.
===
Not sure I even see any problem at all. I just downloaded an NZB from the first thread you linked to and it downloaded fine...
Bah, never mind
Last edited by SonsOfLiberty; 07-08-2009 at 02:48 AM.
[center]
I guess Binsearch shows the same....1/39, wonder why if you export it to a NZB it will show up 39/39 as oppossed to NZB only it will shows 1/39
But NewzLeech doesn't:
http://newzleech.com/?p=6622188
Last edited by SonsOfLiberty; 07-06-2009 at 10:46 PM.
[center]
Okay I just looked at a couple of NZBs you posted in that thread.
I'm looking at these:
Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA.nzb
Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA-EXPORTED.nzb
The first one (NZB created by efnet?) is the broken one.
Here shows an example of the difference between the two.
Looking at this file as an example:
"#a.b.mm@efnet - req 83972 - Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA - [15/25] - "krod.mandoon.s01e06.extended.hdtv-bia.r12" yEnc (01/39)"
In the efnet nzb:
And in the EXPORTED NZB:Code:<file poster="[email protected]" date="1246917273" subject="#a.b.mm@efnet - req 83972 - Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA - [15/25] - "krod.mandoon.s01e06.extended.hdtv-bia.r12" yEnc (01/39)"> <groups> <group>alt.binaries.multimedia</group> <group>alt.binaries.tv</group> </groups> <segments> <segment bytes="398296" number="1">[email protected]</segment> <segment bytes="398422" number="2">[email protected]</segment> <segment bytes="398231" number="3">[email protected]</segment> <segment bytes="398247" number="4">[email protected]</segment> <segment bytes="398165" number="5">[email protected]</segment> <segment bytes="398285" number="6">[email protected]</segment> <segment bytes="398432" number="7">[email protected]</segment> <segment bytes="397981" number="8">[email protected]</segment> <segment bytes="398124" number="9">[email protected]</segment> <segment bytes="398305" number="10">[email protected]</segment> <segment bytes="398177" number="11">[email protected]</segment> <segment bytes="398008" number="12">[email protected]</segment> <segment bytes="398060" number="13">[email protected]</segment> <segment bytes="398242" number="14">[email protected]</segment> <segment bytes="398382" number="15">[email protected]</segment> <segment bytes="398518" number="16">[email protected]</segment> <segment bytes="398151" number="17">[email protected]</segment> <segment bytes="398040" number="18">[email protected]</segment> <segment bytes="398285" number="19">[email protected]</segment> <segment bytes="398295" number="20">[email protected]</segment> <segment bytes="398122" number="21">[email protected]</segment> <segment bytes="397963" number="22">[email protected]</segment> <segment bytes="398152" number="23">[email protected]</segment> <segment bytes="398349" number="24">[email protected]</segment> <segment bytes="398431" number="25">[email protected]</segment> <segment bytes="397898" number="26">[email protected]</segment> <segment bytes="398068" number="27">[email protected]</segment> <segment bytes="398345" number="28">[email protected]</segment> <segment bytes="398127" number="29">[email protected]</segment> <segment bytes="398444" number="30">[email protected]</segment> <segment bytes="398472" number="31">[email protected]</segment> <segment bytes="398257" number="32">[email protected]</segment> <segment bytes="398336" number="33">[email protected]</segment> <segment bytes="398611" number="34">[email protected]</segment> <segment bytes="398064" number="35">[email protected]</segment> <segment bytes="398537" number="36">[email protected]</segment> <segment bytes="398483" number="37">[email protected]</segment> <segment bytes="398474" number="38">[email protected]</segment> <segment bytes="342324" number="39">[email protected]</segment> </segments> </file>
This proves there's a problem with the NZB file and not with how FST handles them.Code:<file subject="#a.b.mm@efnet - req 83972 - krod.mandoon.s01e06.extended.hdtv.xvid-bia - - "krod.mandoon.s01e06.extended.hdtv-bia.r12" (39/39)" date="1246924452" poster="[email protected]"> <groups><group>alt.binaries.tv</group></groups> <segments> <segment number="1" bytes="397312">[email protected]</segment> <segment number="2" bytes="397312">[email protected]</segment> <segment number="3" bytes="397312">[email protected]</segment> <segment number="4" bytes="397312">[email protected]</segment> <segment number="5" bytes="397312">[email protected]</segment> <segment number="6" bytes="397312">[email protected]</segment> <segment number="7" bytes="397312">[email protected]</segment> <segment number="8" bytes="397312">[email protected]</segment> <segment number="9" bytes="397312">[email protected]</segment> <segment number="10" bytes="397312">[email protected]</segment> <segment number="11" bytes="397312">[email protected]</segment> <segment number="12" bytes="397312">[email protected]</segment> <segment number="13" bytes="397312">[email protected]</segment> <segment number="14" bytes="397312">[email protected]</segment> <segment number="15" bytes="397312">[email protected]</segment> <segment number="16" bytes="397312">[email protected]</segment> <segment number="17" bytes="397312">[email protected]</segment> <segment number="18" bytes="397312">[email protected]</segment> <segment number="19" bytes="397312">[email protected]</segment> <segment number="20" bytes="397312">[email protected]</segment> <segment number="21" bytes="397312">[email protected]</segment> <segment number="22" bytes="397312">[email protected]</segment> <segment number="23" bytes="397312">[email protected]</segment> <segment number="24" bytes="397312">[email protected]</segment> <segment number="25" bytes="397312">[email protected]</segment> <segment number="26" bytes="397312">[email protected]</segment> <segment number="27" bytes="397312">[email protected]</segment> <segment number="28" bytes="397312">[email protected]</segment> <segment number="29" bytes="397312">[email protected]</segment> <segment number="30" bytes="397312">[email protected]</segment> <segment number="31" bytes="397312">[email protected]</segment> <segment number="32" bytes="397312">[email protected]</segment> <segment number="33" bytes="397312">[email protected]</segment> <segment number="34" bytes="397312">[email protected]</segment> <segment number="35" bytes="397312">[email protected]</segment> <segment number="36" bytes="397312">[email protected]</segment> <segment number="37" bytes="397312">[email protected]</segment> <segment number="38" bytes="397312">[email protected]</segment> <segment number="39" bytes="397312">[email protected]</segment> </segments> </file>
Not sure what to tell you...
Those efnet NZBs are automatically generated, possibly too early (before the files are fully uploaded).
Not sure where they're pulling those incorrect messageIDs from though.
Last edited by tesco; 07-06-2009 at 11:08 PM. Reason: Automerged Doublepost
So what I'm getting ad to the downloads still work with the "broken" ones from efnet?
Edit, today, yes they do
Last edited by SonsOfLiberty; 07-19-2009 at 06:32 PM.
[center]
Bookmarks