"Reader Has Stopped Working" error

Technical support and discussion of Newsbin Version 6 series.

"Reader Has Stopped Working" error

Postby GrouchoBarx » Fri Oct 03, 2014 3:12 pm

I have been having some problems the last couple of days.

I tried to do a Download All Headers to see if that might fix my issues (it has in the past), but now I can't start the program.

I am using 6.53 Build 3311 (which I just downloaded and re-installed).

The screen opens then fades out and I get the "Reader Has Stopped Working" error.

I am using Giganews as my server(s).

:(
User avatar
GrouchoBarx
Active Participant
Active Participant
 
Posts: 50
Joined: Fri Jun 26, 2009 4:03 pm

Registered Newsbin User since: 06/03/07

Re: "Reader Has Stopped Working" error

Postby GrouchoBarx » Fri Oct 03, 2014 4:52 pm

So I was fiddling around in the DataPath directory. I renamed spool_v6 as spool_v6-old. Now I am able to start the program and download all headers!

It looks as though everything is fine. I will muck around a bit, and then I think I will delete the spool_v6-old directory. Unless you think that I would cause any other issues.

:)
User avatar
GrouchoBarx
Active Participant
Active Participant
 
Posts: 50
Joined: Fri Jun 26, 2009 4:03 pm

Registered Newsbin User since: 06/03/07

Re: "Reader Has Stopped Working" error

Postby Quade » Fri Oct 03, 2014 5:24 pm

You can pretty much delete anything and Newsbin can fix it. It sounds like some file got corrupted.
User avatar
Quade
Eternal n00b
Eternal n00b
 
Posts: 44918
Joined: Sat May 19, 2001 12:41 am
Location: Virginia, US

Registered Newsbin User since: 10/24/97

Re: "Reader Has Stopped Working" error

Postby GrouchoBarx » Tue Oct 07, 2014 10:32 am

So the problem has cropped up again. Is there any way to figure out which file has become corrupted rather than delete/reload everything?
User avatar
GrouchoBarx
Active Participant
Active Participant
 
Posts: 50
Joined: Fri Jun 26, 2009 4:03 pm

Registered Newsbin User since: 06/03/07

Re: "Reader Has Stopped Working" error

Postby Quade » Tue Oct 07, 2014 4:56 pm

I'd start with the files in the "Import" folder. Move them out of that folder temporarily. Start and see if it crashes.

Then the DB3 files in the data folder. Maybe move them out one at a time. Start and See what happens.

Then rename "spool_v6" and see if that does anything.

You're going to want to do these changes, then start Newsbin.

Spool_v6 you can rename back when you're done testing.
User avatar
Quade
Eternal n00b
Eternal n00b
 
Posts: 44918
Joined: Sat May 19, 2001 12:41 am
Location: Virginia, US

Registered Newsbin User since: 10/24/97

Re: "Reader Has Stopped Working" error

Postby GrouchoBarx » Tue Oct 14, 2014 12:56 pm

I have played with the Import and Spool directories, and it appears that the import directory is the culprit.

My question is, what are the implications of deleting the import directory? Do I lose any headers? Is there anyway to determine which file in the import directory is causing the issue?

BTW, thanks for the support! You folks still are my favorite support service!
User avatar
GrouchoBarx
Active Participant
Active Participant
 
Posts: 50
Joined: Fri Jun 26, 2009 4:03 pm

Registered Newsbin User since: 06/03/07

Re: "Reader Has Stopped Working" error

Postby Quade » Tue Oct 14, 2014 4:01 pm

You will lose some headers. You could move all the GZ files out, then move them back in a little at a time till you figure out which group is causing the crash.
User avatar
Quade
Eternal n00b
Eternal n00b
 
Posts: 44918
Joined: Sat May 19, 2001 12:41 am
Location: Virginia, US

Registered Newsbin User since: 10/24/97


Return to V6 Technical Support

Who is online

Users browsing this forum: Google [Bot] and 2 guests