MegaPinger
- Thread starter mattseh
- Start date
- Status
Instead of graying out "Ping Sites", how about have it turn into a "Pause" button? Then once you pause the application, that button turns into a "Resume" button.
I think this would be helpful in better refining what site the application is on and also saving the progress. You could have the application write the sites left to ping into another file, then if that file is detected in the folder, if you closed out the application and reopened it, it'd be populated with those sites.
So, if someone wanted to pause or close the application and update to the current version during a run, or is getting that 99% completed error, they could start back where they left off.
I noticed that the application will randomly grab from the list pasted in, not necessarily in order, so it is hard to know where to resume too. I've tried starting at the url in my list of sites to be pinnged under the last once that failed/was successful, but noticed that they weren't corresponding in order.
By having the sites left to be pinnged in another list, it streamlines the whole process to be more accurate. You could also use this feature to load in a large list of sites without having to paste them in - so the application is more flexible overall.
I think this would be helpful in better refining what site the application is on and also saving the progress. You could have the application write the sites left to ping into another file, then if that file is detected in the folder, if you closed out the application and reopened it, it'd be populated with those sites.
So, if someone wanted to pause or close the application and update to the current version during a run, or is getting that 99% completed error, they could start back where they left off.
I noticed that the application will randomly grab from the list pasted in, not necessarily in order, so it is hard to know where to resume too. I've tried starting at the url in my list of sites to be pinnged under the last once that failed/was successful, but noticed that they weren't corresponding in order.
By having the sites left to be pinnged in another list, it streamlines the whole process to be more accurate. You could also use this feature to load in a large list of sites without having to paste them in - so the application is more flexible overall.
I think that may be when you use a threaded program? (guessing)
Also - I get the 99% stall everytime I use the program. Never ever hits 100% and I have Version 3. (Win7 64)
When I use it, it does hang on 99% for up to about 2 minutes. This is because it is retrying the last few pings that have failed (sometimes because a service is down). It does, however, get to 100% eventually.
If this is not the case for anyone, I'll investigate further.
If this is not the case for anyone, I'll investigate further.
I noticed that on V1 when I was first trying to get the proxies to work with it. It was while I was troubleshooting using one thread. I run the thing with 100 threads usually.
It's not that big of a deal, but would be handy to know which URLs haven't been pinged at all yet via another file. This would make it much easier to add a pause feature, since all Matt would have to do would be to have the program stop once it finishes the current pings in progress; negating having to even enter a resource intensive "while" loop.
Granted, that was using V2 since I posted my last comment after having spent 9 days pinging over 110k URLs and watched it sit on 99% for about two days.
I have since tried pinging 23k URLs using V3 and it has been hung up on 99% for about 14-15 hours.
I'm using Windows 2003 Server Standard version. Though, since others are using newer versions, it's probably not Windows version specific.
(You know, a likely quicker band-aid for this is a pause feature
so we can resume and it start back at 0% using the URLs that are remaining, if you don't feel like investigating the root cause at the present time.)It's not a big deal for me since all those URLs are for my own use, and not for clients, so I could care less if all of them get successful pings as long as the majority are.
Other than that, it's a very strong product.Version 4 is available!
stores unstored pings in notyetpinged.txt, which it loads of program start.
Pausing / resuming of pinging.
Numerical display of pings.
Now runs up to 500 threads.
Download link: http://dl.dropbox.com/u/2326797/MegaBots/MegaPinger_v4_456ABCE45.zip
Happy now Rexibit?
stores unstored pings in notyetpinged.txt, which it loads of program start.
Pausing / resuming of pinging.
Numerical display of pings.
Now runs up to 500 threads.
Download link: http://dl.dropbox.com/u/2326797/MegaBots/MegaPinger_v4_456ABCE45.zip
Happy now Rexibit?
I don't suppose you run Xrumer, or you'd know it's designed to run on a 32-bit system and 2003 is the most stable for it.
+1 Itrader. I hope to see results soon.
Hey Matt,
New updates are nice, thanks! I have one little bone to pick though - the failures list is kind of a bitch to work with since it has other stats in it. It would be really great if there was a second failures list that was just the URL's so it can be reloaded into megapinger for a second try. Other than that I am loving the update, great work.
New updates are nice, thanks! I have one little bone to pick though - the failures list is kind of a bitch to work with since it has other stats in it. It would be really great if there was a second failures list that was just the URL's so it can be reloaded into megapinger for a second try. Other than that I am loving the update, great work.
Have been looking for a pinger all day!
- Status