V 2.9.55 Does not seem to handle "Image does not exist on server" at all well. It just stalls, with no way to proceed other than: Close VG Ripper and restart. This forcibly concludes the particular post thread which was interrupted by a missing image, and jobs.xml does NOT have any record of that aborted thread.
For examples, try:
http://vipergirls.to/threads/75260-Mariah-Carey and
http://vipergirls.to/threads/74776-Gillian-Anderson
both of which are quite extensive threads, which will stall a few times in the attempt to download.
Ripper appears to be waiting for image data when none exists on the error page. Maybe a check through the data received, looking for the "<img size" or "<img src" tags and a quick analysis could provide the clue as to whether the data received includes the wanted image or not.
It seems to me, that possibly maintaining a jobs.xml.bak as well as jobs.xml, updating each at the commencement of each new thread would provide a way for a savvy user to recover from that situation. A small amount of extra disk activity is a small overhead for the added ability to recover.
Inclusion of the post URL (Complete) in the xml file would also assist in checking just what causes any problems with that particular post.
That crazy tooltip "System is extracting..." is an annoying pest. - replace it with an optional "Always on top" mini-window which could list the thread title, post Nr. and image name IF the user requires the reassurance that the ripper is still functioning while minimised. -
Other than those problems, VG Ripper seems to function quite well, with very few incomplete, distorted image downloads. The only other improvement might be to recognise the "Image Removed or Deleted" images from the different hosts, but that could run into some complex coding as each host differs in the way that message is sent. - This occurrence is quite different than the first mentioned, because in this instance, the host is sending an image which indicates "Image Removed or Deleted", whereas in the first instance mentioned above, the host is basically sending a custom "404" replacement, and that is what stalls VG Ripper.
Keep up the good work, VG Ripper & PG Ripper are used and appreciated by many. A valuable tool indeed.
Comments: Downloaded VG Ripper 2-9-56 to nao avail. 2-9-56 does not want to co-operate at all, in fact, it doesn't want to do a damned thing. - dll's are the same in either version, must be in the .exe - back to 2-9-55 we go.
For examples, try:
http://vipergirls.to/threads/75260-Mariah-Carey and
http://vipergirls.to/threads/74776-Gillian-Anderson
both of which are quite extensive threads, which will stall a few times in the attempt to download.
Ripper appears to be waiting for image data when none exists on the error page. Maybe a check through the data received, looking for the "<img size" or "<img src" tags and a quick analysis could provide the clue as to whether the data received includes the wanted image or not.
It seems to me, that possibly maintaining a jobs.xml.bak as well as jobs.xml, updating each at the commencement of each new thread would provide a way for a savvy user to recover from that situation. A small amount of extra disk activity is a small overhead for the added ability to recover.
Inclusion of the post URL (Complete) in the xml file would also assist in checking just what causes any problems with that particular post.
That crazy tooltip "System is extracting..." is an annoying pest. - replace it with an optional "Always on top" mini-window which could list the thread title, post Nr. and image name IF the user requires the reassurance that the ripper is still functioning while minimised. -
Other than those problems, VG Ripper seems to function quite well, with very few incomplete, distorted image downloads. The only other improvement might be to recognise the "Image Removed or Deleted" images from the different hosts, but that could run into some complex coding as each host differs in the way that message is sent. - This occurrence is quite different than the first mentioned, because in this instance, the host is sending an image which indicates "Image Removed or Deleted", whereas in the first instance mentioned above, the host is basically sending a custom "404" replacement, and that is what stalls VG Ripper.
Keep up the good work, VG Ripper & PG Ripper are used and appreciated by many. A valuable tool indeed.
Comments: Downloaded VG Ripper 2-9-56 to nao avail. 2-9-56 does not want to co-operate at all, in fact, it doesn't want to do a damned thing. - dll's are the same in either version, must be in the .exe - back to 2-9-55 we go.