Page 1 of 1

PicaLoader crashed by Keyword Test and pic download probs

Posted: Sun Jan 04, 2004 8:29 am
by zjboy
When I attempted to test a URL against a filter using the "Task -> Keyword Test" menu option, PicaLoader crashed on me. The Visual C++ runtime code posts the only error message which is simply: "abnormal program termination".
Here are the URL and the filter I used that caused the crash....... wrote: http://www.wonderfulgirls.com/list_thum ... egory_id=6

\Dlist_PagingMove=++++%3E+++;/search_display\.asp\?photo_id=\d+\D;/list_thumbs\.asp\?category_id=6
I'm using PicaLoader 1.40 (1.4.0.1222) under Windows 2000 Pro SP4.

I'd also appreciate it if you could take a look at this website http://www.wonderfulgirls.com/index.html and see if you could help me figure out how to download pics from it.

The project attached to this message is my failed attempt to download the wallpaper pics from the site. The problem I'm facing is that this site seems to navigate by having the user POST to a FORM. Is PicaLoader able to follow the links generated by a FORM??

Posted: Mon Jan 05, 2004 5:29 pm
by PicaLoader
Hi,
1.PicaLoader doesn't support this kind of pattern:++++%3E+++
2.This site uses FRAME, for example, http://www.wonderfulgirls.com/index.html is composed of menuie.asp, h_intro.htm and intro.htm, so if you use it as start url, the "Page URL Include Filters" should be menuie\.asp;intro\.htm;/search_display\.asp;category_id=6;/search_disp\.asp
3.PicaLoader can follow the links generated by standard FORM, but this site uses no named FORM, PicaLoader 1.40 can't process it, so you can only get pictures of first page. I will try to resolve this problem in next release, but I can't ensure...

Posted: Mon Jan 05, 2004 8:08 pm
by zjboy
PicaLoader wrote: 1.PicaLoader doesn't support this kind of pattern:++++%3E+++
:oops: Silly me, I forgot that "+" is a special symbol and needs to be quoted. I "obviously" meant to use \+\+\+\+%3E\+\+\+ :oops: :oops:

Were you able to reproduce the PicaLoader crash when using Keyword Test? This seems like something that should also be fixed in the next release, if not sooner. (If you can fix it, of course. I would not be completely surprised if the fault turned out to be in the M$ C++ runtime code :roll: )

-irrational john

Posted: Wed Jan 14, 2004 6:48 pm
by PicaLoader