Bad File When Converting Into Plucker?

[+slowspoke]

When I do a search query I receive the zip file OK and can unzip it

alright but when I try to update the "new channel" in the plucker program

it gets to a certain point and then stops. I do my query from 59105 for

active caches that I haven't found. This problem was notice yesterday when

I was working with it trying to put the info into my PDA, a Tungsten E, I

have been using for almost a year. Any ideas or help would be greatly

appreciated.

Thank you

Tom

[+Moose Mob]

Moving to software...

[+PDOP's]

What are you using to convert the Pocket Query zip file into HTML that Plucker requires?

[+caughtatwork]

Stop or dramatically slow down?

 

I used to have this problem and it seems that the log file 'fills up' and then gets dymaically extended each time plucker plucks a new record, effectively killing the process.

 

I switched over to sunrise to create the files and then on the palm use plucker to read them.

[+slowspoke]

It just stops. and won't go any further.

I did a query for Bozeman area and it worked fine, then did a query for Billings to update my previous one and thats when the problem showed up. Tried it 2 more time with same result. I then did a query for Missoula area and it worked ok. By this time I'd used up my allotted query searches. At this point I'm really confused.

Edited November 22, 2005 by slowspoke

[+Olar]

It just stops. and won't go any further.

I did a query for Bozeman area and it worked fine, then did a query for Billings to update my previous one and thats when the problem showed up. Tried it 2 more time with same result. I then did a query for Missoula area and it worked ok. By this time I'd used up my allotted query searches. At this point I'm really confused.

It would by wise to answer PDOP's question which would help us to help you.

 

What are you using to convert the Pocket Query zip file into HTML that Plucker requires?

 

This problem has occured in the past and often has been due to a cache page creator using "bad HTML" that Plucker doesn't like. The author's of the applications PDOP refers to have usually been able to come up with a fix.

 

Olar

[+slowspoke]

I'm using "Spinner" to unzip the file after I get it.

I am using the method for paperless caching found at Geocacher University. If it is a bad HTML file how do I find the bad one so I can get rid of it?

Hope this is the answer to your question.

Thanks for the help

Tom

[+Olar]

I'm using "Spinner" to unzip the file after I get it.

I am using the method for paperless caching found at Geocacher University. If it is a bad HTML file how do I find the bad one so I can get rid of it?

Hope this is the answer to your question.

Thanks for the help

Tom

I did a search on "bad HTML" and got some good hits. Here is the most recent discussion in which the author of Spinner (Lil Devil) responds. You may want to contact him for any further insight.

 

Cheers, Olar

[+slowspoke]

Ok, for the last week I could't figure out why Plucker would get to a

certain point for paperless caching and then just stop. I worked on

this for a week and think I finally got it.

It appears that "The Selector" doesn't work well with Plucker and it

sees it as a "bad HTML file". If anyone else has this problem please

let me know if my theory is correct.

Thanks

Tom