Thanks, Nilly. I will open a new browser window, clear the cache and try it again.

No go.

I wonder if something is going on, on my end. I had this same problem a week or two ago, but Tom Scola did something rock star-ish, and then the threadsuck worked. I do have a newish (month or two) firewall product and pop-up blocker, but so far, it hasn't interfered with anything but real pop-ups.

Cindy, I just did a threadsuck of the entire Natter 30 thread, and it worked fine. Also, I'm not seeing any error messages on the server like I did the previous time.

Unless someone else can confirm this, I'll have to assume that the problem is on your computer. Are you running out of memory? Do you have another browser installed that you can try? Are you using a dial-up connection? How long does it take before the "Done" message appears?

I'm using cable broadband. I only have the one browser. I don't think I am running out of memory, but I will ask dh. I did a cleansweep just yesterday. It doesn't take too long for the empty-ish page to load. I will try it again, and count.

It takes about 6 seconds to switch from the page where you enter in your threadsuck values to the page that ought to be the thread suck. It then takes about another 6 seconds to be "done" -- except the only information that appears is that stuff at the top of the page.

Last time, when you found and corrected the problem, I was able to threadsuck. I don't think anything has changed on this end, since then. The problem must be here, though.

For what it's worth, I have my number of posts displayed on a page set at 75, and it always loads quickly. For the heck of it, I just tried to change that to 1000, and then load Natter 30, starting at post 5000, but it was a no-go. I got all the information on the page (links, etc) but no posts.

Thanks, Tom.

I only have the one browser.

Gotta plug Firefox here. It might not solve your threadsucking problem but it'll definitely make you more secure against viruses, if the browser you have now is Internet Explorer. Free, small, and imports your bookmarks and settings from your old browser easily.

I can say -- I can't threadsuck from either machine at home, on any of three browsers (Opera, Firefox, IE), despite having a nice broadband connection.

I can do it from work just fine on IE or Opera, though.

Never bothered to troubleshoot it, because I figured it was just me.

Gotta plug Firefox here. It might not solve your threadsucking problem but it'll definitely make you more secure against viruses, if the browser you have now is Internet Explorer. Free, small, and imports your bookmarks and settings from your old browser easily.

That kind of stuff, I leave up to Dh. He uses this machine to dial into work, and they have very strict standards for what can and can't be on your machine. Thanks to them we have Symantec corporate virus stuff, and a firewall, etc.

I can say -- I can't threadsuck from either machine at home, on any of three browsers (Opera, Firefox, IE), despite having a nice broadband connection.

I can do it from work just fine on IE or Opera, though.

I have IE, for what it's worth. I always used to be able to threadsuck, before whatever the first problem DX or someone noted a while back, I could suck an entire thread or huge parts thereof. Never gave it a thought.

I am unable to threadsuck an entire thread on my iBook. (A year ago or so I could - nothing has changed on the computer.) I'm using Mozilla and the G3 900 mhz iBook has 640 Meg. I have a cable modem at home which is very fast.

eta: oddly enough, the iBook has no trouble threadsucking 9531 Bitches posts here at work. We have a SDSL line here - the download of the suck was averaging about 920 kilobits/sec, which is about a third of the speed I get at home on the cable modem.

ita, Nilly and I are still looking at the Firefly quotes to see which ones should be weeded. Once we are done, would you rather I send it to you as an unzipped excel file, or as the simple text file we have been working with?

Lee -- what I'd like is merely a list of the quote IDs.