Still lots of errors and crashes in 6.30 RC1
Posted: Sat Feb 18, 2012 6:09 pm
With 6.30 RC1 (build 1825) I am getting a lot of errors.
Possibly because I'm still with 32 bit Windos XP - still trying to decide which motherboard to use for my new PC - I can't find one that suits me 100% - it drives me crazy. I should have had the new PC long ago.
I am getting many many various errors, some only a few times, but these seem to be prevailing:
many many of those:
ERROR - INT_AssembleFile: Assembly Failed
ERROR - INT_AssembleFile: Assembly Failed
ERROR - INT_AssembleFile: Assembly Failed
many many of those:
ERROR - FileIOThread - internal crash
ERROR - FileIOThread - internal crash
ERROR - FileIOThread - internal crash
many many of those:
ERROR - INT_AssembleFile Crash
ERROR - INT_AssembleFile Crash
ERROR - INT_AssembleFile Crash
sometimes these, maybe caused by the other ones:
ERROR - Resolver: Unable to find Download data
And once I had a wrong destination drive (no free space left), then I got a lot of these:
ERROR - CFileIOWorker: Unable to Write to SpoolIO
ERROR - CFileIOWorker: Unable to Write to SpoolIO
ERROR - CFileIOWorker: Unable to Write to SpoolIO
So these perhaps OK, but still, perhaps the download should be paused or skipped in the case when the drive is full, not many repeated messages.
And it refer to spool - all the header data is on a different drive which has a lot of free space on it. I don't know if there is any spool on the destination drive?
Only nb2 files.
BTW, the "Critical Error Messages" window - is it possible to make it a regular view inside Newsbin, as a log or download list, etc.
It is either is popping up independently or can be closed altogether.
And if it is closed it is not possible to bring it back?
I just want to be able to add it as a view to the Newsbin interface.
Possibly because I'm still with 32 bit Windos XP - still trying to decide which motherboard to use for my new PC - I can't find one that suits me 100% - it drives me crazy. I should have had the new PC long ago.
I am getting many many various errors, some only a few times, but these seem to be prevailing:
many many of those:
ERROR - INT_AssembleFile: Assembly Failed
ERROR - INT_AssembleFile: Assembly Failed
ERROR - INT_AssembleFile: Assembly Failed
many many of those:
ERROR - FileIOThread - internal crash
ERROR - FileIOThread - internal crash
ERROR - FileIOThread - internal crash
many many of those:
ERROR - INT_AssembleFile Crash
ERROR - INT_AssembleFile Crash
ERROR - INT_AssembleFile Crash
sometimes these, maybe caused by the other ones:
ERROR - Resolver: Unable to find Download data
And once I had a wrong destination drive (no free space left), then I got a lot of these:
ERROR - CFileIOWorker: Unable to Write to SpoolIO
ERROR - CFileIOWorker: Unable to Write to SpoolIO
ERROR - CFileIOWorker: Unable to Write to SpoolIO
So these perhaps OK, but still, perhaps the download should be paused or skipped in the case when the drive is full, not many repeated messages.
And it refer to spool - all the header data is on a different drive which has a lot of free space on it. I don't know if there is any spool on the destination drive?
Only nb2 files.
BTW, the "Critical Error Messages" window - is it possible to make it a regular view inside Newsbin, as a log or download list, etc.
It is either is popping up independently or can be closed altogether.
And if it is closed it is not possible to bring it back?
I just want to be able to add it as a view to the Newsbin interface.