I am starting to find using Sunrise XP really wonderful. It is much faster and works great. I did have a crash on the Tx. I know that the problem was with plucker viewer 1.8, though. But it was a really large file that sunrise XP generated for me. I did have to clear the cache of the plucker list and things started to behave normally after.

On occasion, Sunrise XP seems to hang at 99% while updating or switch to "generating" and sit for 20+ minutes at a time or all 5 threads sit in generating. I have had to kill it and generate the file again on occasion. Any ideas? These are large files being sent to the SD card. 3-36megs+. I was pulling info from brighthand on the TX. I can send you the links if you like.

It seems to not be when I do 1 thread, but I have 5 running at a time.

No idea. Testing such large files is way too much of a hassle and I will not get to it. Sorry. Maybe it's not such a good idea to pull in so much content in the first place. Do realize that bandwidth has to be paid for. Please don't abuse this tool.

I seem to be getting the same 99% error even on small files (<200 KB).

I seem to be getting the same 99% error even on small files (<200 KB).

Send me your SXL, so I can try to reproduce it here.

Laurens, I've had this same problem happen to me over the past couple weeks. In my case, it is a quite large Plucker document (>40MB) generated, but I've noticed that it happens in much smaller documents as well, and the freezing is not consistent from day to day.

I've attached the SXL for the one website that froze at 99% this morning.

Also, I have a question, Laurens, that relates to the "banned" thread. If I regularly download from a site like the one in my SXL, and most of the content does not change daily, when Sunrise goes to check to see if there have been updates to each page, does it make the same bandwidth demands for "unchanged" as for "new"? In other words, if a site creates a plucker document that is 40 MB in size, but 39 MB of the 40 is already cached and does not change on a daily basis, is the bandwidth demand on the site as large as if all 40 MB were downloaded?

Also, I have a question, Laurens, that relates to the "banned" thread. If I regularly download from a site like the one in my SXL, and most of the content does not change daily, when Sunrise goes to check to see if there have been updates to each page, does it make the same bandwidth demands for "unchanged" as for "new"? In other words, if a site creates a plucker document that is 40 MB in size, but 39 MB of the 40 is already cached and does not change on a daily basis, is the bandwidth demand on the site as large as if all 40 MB were downloaded?

Caching works the same as in a web browser. If the site implements caching using ETag, Last-Modified and cache control headers and the downloads are in your internet cache, it will not download the resources again.

BTW, the "99%" thing is a threading issue. Unfortunately, threading issues are the hardest to fix since their behaviour is unpredictable (inconsistent) and as such they cannot be easily reproduced. It's going to be a long while (possibly several months) before I get round to fixing this.

I have seen this occasionally as well. Would it help if I send along my SXL, or do you have enough to work with?

No need to send any more SXLs.