5.0.0.132 Would not start and more

2011-01-23 Thread Rick
This morning, v 5.0.0.132 would not load I had 40 messages scheduled to go out over the next 4 days. v 5.0.0.132 dumped them ALL at once yesterday -- Rick Have you ever wondered if the one-dollar bills in your wallet were ever in a stripper's butt crack? If not, you're wondering now. v4.2.42

Re: 5.0.0.132 Would not start and more

2011-01-23 Thread Rick
This morning, v 5.0.0.132 would not load I had 40 messages scheduled to go out over the next 4 days. v 5.0.0.132 dumped them ALL at once yesterday I was able to start the beta AFTER I cleared out 10,140 files from the imgfiles folder - over 400 mb I can use CCLEANER to clean that out every

Re[2]: 5.0.0.132 Would not start and more

2011-01-23 Thread Marek Mikus
Hello all, Sunday, January 23, 2011, Rick wrote: This morning, v 5.0.0.132 would not load I had 40 messages scheduled to go out over the next 4 days. v 5.0.0.132 dumped them ALL at once yesterday I was able to start the beta AFTER I cleared out 10,140 files from the imgfiles folder - over

Re: 5.0.0.132 Would not start and more

2011-01-23 Thread Rick
Hello all, Sunday, January 23, 2011, Rick wrote: This morning, v 5.0.0.132 would not load I had 40 messages scheduled to go out over the next 4 days. v 5.0.0.132 dumped them ALL at once yesterday I was able to start the beta AFTER I cleared out 10,140 files from the imgfiles folder -

Re[2]: 5.0.0.132 Would not start and more

2011-01-23 Thread Marek Mikus
Hello all, Sunday, January 23, 2011, Rick wrote: The log is enclosed, although I doubt it will be helpful. please send me thebat_exceptions.log privately, thanks -- Bye Marek Mikus Czech support of The Bat! http://www.thebat.cz Using the best The Bat! 5.0.0.132 BETA under Windows 7 6.1

Re: 5.0.0.132 Would not start and more

2011-01-23 Thread Rick
This morning, v 5.0.0.132 would not load I had 40 messages scheduled to go out over the next 4 days. v 5.0.0.132 dumped them ALL at once yesterday I had this problem AGAIN after getting an error that the message had already been destroyed followed by an un labeled progress bar that never