Quote:
Originally Posted by effCup
imgbox is currently unresponsive--thanks to deezer for analysis/spotting nature of problem. 
Running halvar's tool over threads with imgbox links in them I think will produce "empty" dot files, i.e. containing no image filenames, so file size = 0.
You could simply decide to try them again later. 
One way to "discover" where such files might lie is: on windows, use cmd to cd to the directory in which you've saved the folders output by halvar's tool, then run this (all one line):
Code:
forfiles /m .* /s /C "cmd /c if @fsize EQU 0 echo @path" > output.txt
It should produce a text file containing a listing of the paths of all such files, so you can re-check them later. Hopefully that may be less work than e.g. re-running halvar's tool?
edit: ha! Just after that imgbox seems to be back up & running.
Hmm, & the above also finds dot files of zero size that correspond to missing -bam files as well, which is less helpful. 
|
You can also use the report to get an overview of missing files. It takes some time to generate the report and the resulting file is rather large ( up to 100MB or more). The report is a csv file containing:
threadId, threadTitle, pageNr, postCount, postNr, poster, thumbnailURL, imageUrl, imageFileName, imagefile size
imagefilename and imagefilesize are 'n/a' and -1 for failed downloads, e.g.
Code:
3164;Loni_Sanders_Classic_Pornstars;17;166;1481827;Curtis23;http://thumbnails39.imagebam.com/12068/857a3b120672517.jpg;http://www.imagebam.com/image/857a3b120672517;gfb42646.jpg;27399
3164;Loni_Sanders_Classic_Pornstars;17;166;1481827;Curtis23;http://thumbnails40.imagebam.com/12068/b63e56120672520.jpg;http://www.imagebam.com/image/b63e56120672520;n/a;-1
The report is generated from local files only, nothing is downloaded. It scans your whole storage folder. You can start the report using the button 'Create report of local files' on the second tab.
The report generation cannot run in parallel with downloading. The report file is stored in the working folder.