but seriously, i just typed in "Seciors" and it showed me the three uploads in a really nice format. Maybe I'm missing something, but this confirms I had a successful upload like over an hour before your beloved binsearch.
njvc said:Have just uploaded another BD successfully, and have found that a quick and easy way to check which files have been successfully/unsuccessfuly uploaded is to ignore what camelsystem powerpost tells you about which files are in error etc, and just search the edit on binsearch.info. I'm not sure why, but powerpost occasionally gives me error messages for files that were successfully uploaded, and the ok for files that weren't.
You might be making the mistake of trying to repost the old files in their entirely, again. If you are trying to do that then that might be the issue.
Try the following:
1. In your newsclient look for the files that are the problem.
2. Highlight one of them and then look in your newsclient for a way of showing the 'Properties' of that post. What you are looking for is to find out what segments of that file have been properly posted and what segments are actually missing.
3. Take a note of the numbers of the segments that are missing.
4. Now go to the same file in the listing that CamelSystem shows.
5. Right-click on that file and select the 'Task Properties' option. That will open up a dialogue in which you will see all the numbered segments for that file.
6. Put a tick in each box that is the same as the missing segments numbers that you got out of your newsclient. Tick only those numbers, leave all the others blank/unticked. (Remember the numbers you are leaving blank have already been posted correctly. If you try to repost them again then that might be the cause of the errors you are getting.)
7. Once you have all the correct segments ticked, 'Okay' the dialogue (so that you exit it).
8. Now right-click on the same file and select the 'Re-queue selected files...' option.
9. Now you can start posting that file again. (All you will be 're-posting' is the missing segments.)
Lastly, you can set-up multiple files for reposting missing segments and once all the files are set-up, and re-queued, you can then just repost the lot in one go i.e. just hit the 'Post' button of CamelSystem.
Q2 said:MultiPar is the updated version of QuickPar. While the directions below refer to QuickPar, they are exactly the same for MultiPar. ... Leave the default settings of QuickPar and click the Create button.
Q2 said:To create an SFV file is simple: go into the directory where all your RAR and PAR files are and select them all.
njvc said:Hello again usenet uploaders, I'm back for today's fun usenet challenge.
I created my par2 recovery files for my ROTLS AVCHD using multipar, but when I go to post them using powerpost, I get
Warning: par2 packet size 1152068 incompatible with lines/part
Creating the par2 recovery files using exactly the same settings resulted in a successful upload for other big files, the BD version of ROTLS included, but now this... and it's happening for the WTWTA BD recovery files too.
Anyone else faced this little problem and solved it?
geminigod said:shit got all fucked up with a different posting app I switched to. Those two should be golden though. Going to switch back to uploading with Powerposter, so it should be up soon.
geminigod said:Anyone think this is too high? Not high enough? I haven't ever tried downloading something from usenet that is years old to see how badly it is degraded. The idea being I don't want to ever have to re-upload this shit again.)
geminigod said:Multipar: Check "restrict block size to multiples of preferred size."
Brumous said:I have downloaded fanedits that needed more than 2% PAR redundancy to repair the files. Most guides recommend 10%.
wabid said:I feel like it is a good idea to err on the side of too much par. A user can always NOT download the last file, and check first to see if they need it. There is no mechanism that would force people to download all the pars you make available.
LastSurvivor said:Okay, have decided to have another go at this uploading to newsgroup.... Following the guide, I've added the files to Camelpost, but the PAR2 files are coming up with "Warning - par2 packet size 1280068 incompatible with lines/part".
So, before I started posting all the files in the queue, I wanted to check with you guys to see if you had any ideas?
Thanks
LS