Usenet Explorer

Hi!

My hard drive got almost full and the program stopped the download process (as it is supposed to). The problem is that I have cleared up +750mb of free space for the transfers to resume and it isn't restarting to transfer where it was at.

Shutting down and restarting yeilds no results, there is no pauses (low priority or main pause). Any ideas on how to get it back at work?

Thanks.

if there is not enough space newspro gives a warning box and suspends tasks, they are resumed shortly (i think it checks for space every 7 seconds) after there is enough disk space.

ensure you freed space on the right drive (invoke file menu->switch database to see the drive).

also there are other conditions like scheduler, accidentally setting other than 'ignore' option in dial-up (if the menu is disabled all is ok), a server reached download limit etc, but if you didn't change anything in settings and it is not a server it should be the disk space.

There is 500mb of free space on both drives with a 40mb trigger to suspend, way more than needed. Recycle bin is empty (unused).

Scheduler is disabled on start and is still disabled. Dialup is at ignore. Next things to try?

EDIT: I can download headers fine at the moment.. but articles are still pauses *sigh*

if it downloads headers articles also should be downloaded, it is something with servers, check whether there is a server with download limit reached, the only thing i can think of it waits for the server to become available (also header tasks consume task slots if you have header tasks with higher chance to run and all slots used it also may be the reason).

I had the same thing happen today. My drive reached it's limit, and NP suspended all tasks. Then, after clening driver to over 3.5 gig, it did not resume. Shutting down NP and restarting did not help. Rebooting windows did.

regards,
Michael

Do you have any undeleting software so maybe the files were not actually deleted and deleting is committed later?

Restarting Windows doesn't change anything from the newspro point of view.

Next time check in the drive properties how much actual space is free, I think it uses the same system functions as newspro to determine the free space.

I believe, the original poster resolved it, but I don't know how exactly.

Maybe to try to check the drive for errors (no rescan, just directory structure) or some form of cleanup, if you can cause it again you could try to fix it without resorting to the system restart (if it would newspro restart which helped it would be rather suspicious, but since it doesn't change anything and given that newspro doesn't store such info between session and relies on the system function to determine the disk space it must be some system issue).

Now you can very easy to reproduce it by setting 4000 in properties->general, low space, suspend when x MB left (it is the max value, if you have more than 4GB free on the drive it won't work). When it will suspend the tasks set it back to the former value, see whether tasks will resume (they will), it will prove newspro functionality works.

Then set it to some smaller value a bit larger than the free space available; when it suspends free enough space and then check what is happening with the disk properties and also initiate the disk cleanup or whatever you'll find there.

Yes, I did manage to find what was the cause of all this but was (way) too busy to come back with the explanation

I am using 3 Subnets with the servers in each subnet having this priority:

Free - 100
Private - 50
Misc - 25

ISP NewsServer is the only one out of a subnet with priority 125. Every server has download by msg-id and STRICT. All subnets usually don't have anything enforced (# connection / limit per server).

That time, I had enabled the "Free" subnet with 0 connection, 0 limit to make sure it wouldn't download from that subnet. My ISP has a 5-10% completion, so it downloaded all it could from it and stopped. Since the servers of the free subnet weren't directly disabled, it wouldn't skip them due to the Strict setting, even if, overall, I was kind of disabling those servers by setting 0 in the max connection of the subnet. I though the software would be "intelligent" to see the (0) in the subnet = skip but it was instead waiting for an available connection...

Disabling the servers in the subnet made the batch restart so I figured all this out. Works fine now.

alex wrote:Do you have any undeleting software so maybe the files were not actually deleted and deleting is committed later?

Restarting Windows doesn't change anything from the newspro point of view.

Next time check in the drive properties how much actual space is free, I think it uses the same system functions as newspro to determine the free space.

I believe, the original poster resolved it, but I don't know how exactly.

Maybe to try to check the drive for errors (no rescan, just directory structure) or some form of cleanup, if you can cause it again you could try to fix it without resorting to the system restart (if it would newspro restart which helped it would be rather suspicious, but since it doesn't change anything and given that newspro doesn't store such info between session and relies on the system function to determine the disk space it must be some system issue).

Now you can very easy to reproduce it by setting 4000 in properties->general, low space, suspend when x MB left (it is the max value, if you have more than 4GB free on the drive it won't work). When it will suspend the tasks set it back to the former value, see whether tasks will resume (they will), it will prove newspro functionality works.

Then set it to some smaller value a bit larger than the free space available; when it suspends free enough space and then check what is happening with the disk properties and also initiate the disk cleanup or whatever you'll find there.

Well this just happened to me. Thought I had enough space, but didn't. Newspro suspended task when disk space got low. I've since freed up 1.6gig. Newspro still hasn't started the tasks. Showing 1624 pending. Disk properties shows 1.7gig free. Just ran scandisk. No errors. About ready to try restarting Newspro. When I exiting Newspro it gave me a warning box saying I was about to run out of space on the data drive, and it gave me some suggestions on how to move .npr files around. A bunch more free space appeared after exiting Newspro (up to 2.46Gig now, must be the backups getting erased).

Restarting newspro fixed the problem. I'd say there is a bug in newspro that causes it to stop checking diskspace after running out. I'm using 3.74.

alex wrote:Do you have any undeleting software so maybe the files were not actually deleted and deleting is committed later?

Restarting Windows doesn't change anything from the newspro point of view.

Next time check in the drive properties how much actual space is free, I think it uses the same system functions as newspro to determine the free space.

I believe, the original poster resolved it, but I don't know how exactly.

Maybe to try to check the drive for errors (no rescan, just directory structure) or some form of cleanup, if you can cause it again you could try to fix it without resorting to the system restart (if it would newspro restart which helped it would be rather suspicious, but since it doesn't change anything and given that newspro doesn't store such info between session and relies on the system function to determine the disk space it must be some system issue).

Now you can very easy to reproduce it by setting 4000 in properties->general, low space, suspend when x MB left (it is the max value, if you have more than 4GB free on the drive it won't work). When it will suspend the tasks set it back to the former value, see whether tasks will resume (they will), it will prove newspro functionality works.

Then set it to some smaller value a bit larger than the free space available; when it suspends free enough space and then check what is happening with the disk properties and also initiate the disk cleanup or whatever you'll find there.

Well this just happened to me. Thought I had enough space, but didn't. Newspro suspended task when disk space got low. I've since freed up 1.6gig. Newspro still hasn't started the tasks. Showing 1624 pending. Disk properties shows 1.7gig free. Just ran scandisk. No errors. About ready to try restarting Newspro. When I exiting Newspro it gave me a warning box saying I was about to run out of space on the data drive, and it gave me some suggestions on how to move .npr files around. A bunch more free space appeared after exiting Newspro (up to 2.46Gig now, must be the backups getting erased).

Restarting newspro fixed the problem. I'd say there is a bug in newspro that causes it to stop checking diskspace after running out. I'm using 3.74.

That's happened also to me, after freeing ~15gb the downloads and a machine reboot the downloads didn't restarts;
i don't remember very well now, i tried to change a lot of options, then i tried anything it came to my mind and finally it started to download again; last options i remeber to change are disablling scheduler (there was the suspend task tag active) , reset server counters and limits and mark for download same new headers.
I don't know if any of this actions made it restart or it did by himself.