Previous Top Next
Local List Search Method: There are a couple of new ways to search your local lists in Autoget 7. The old/slow way of doing things is still available for compatibility purposes. The two new ways both employ a dll to make list searches faster and less cpu intensive. The Fast and Accurate method taxes this dll quite heaviliy and you might get an error saying that you tried to do a search while one was already in progress. If this happens you need to increase the Search dll List Change Tolerance. If you experience any crashing of mIRC after you load Autoget 7 this search dll is the likely culprit and you should set your search method to Quick And Dirty or Slow and Steady. Increasing the tolerance could also stop crashes.
· Slow and Steady: This method is the same as the tried and tested version in Autoget 6.1. It's accurate but very slow due to it's reliance on the /filter command in mIRC. This causes the search to be extremely cpu intensive making your mIRC almost unusable while the search is taking place.
· Quick and Dirty: This method is the same as in OS-qsearch made by TipiTunes. This method is faster and much more stable but it is somewhat inaccurate when searching online lists only since it doesn't filter out online lists until after the search is done. So if it comes up with 500 results, and all of those results are from offline servers, then you will see no results in your Autoget dialog.
· Fast and Accurate: This method is a hybrid of the previous two. I uses the same dll as Quick and Dirty but does so in a broken up manner so that online search results are perfectly accurate. Again, this method taxes the search dll very heavily and may cause instability. 90% of you will be able to use this method, but for the 10% that have problems you can adjust the tolerance to get it working, or just fall back to a different method.
Local List Search Order: This option lets you change the order in which your list database is searched.
· Alphabetical By Nickname: This is the standard way AG7 has always done things.
· Alphabetical By Channel: If you're more concerned about what channel the server is in you might want to choose this option. Remember that just because you downloaded the list in a channel doesn't mean that you have to download from the server in that same channel.
· Fastest To Slowest: Since Autoget stores the speed at which a list downloads, you can use this setting to get results from the fastest servers first.
· Biggest To Smallest: Looking for a large number of results from one server? This is the way to get it.
· Random: List database is completely randomized before you start your search, this is the default setting.
Show files not requested via Autoget in completed area as ?Completed: If you want to use Autoget a catch all for your incoming files it can be pretty handy, but over time you'll accumulate a whole bunch of random files in your Autoget completed files list. This can make it tougher to sort out what you've downloaded. This defaults to off.
Allow changes to order of files in waiting list (slower): This option will enable some new commands in your waiting list. You'll be able to move files up or down in your waiting list but still keep them grouped according to nickname. Files at the top of your waiting list are requested first, so you can now completely control what order your files get requested in. However, if you have a few thousand files in your waiting list this method may be too slow and you'll want to resort to the old method by unchecking this option.
Show delete line confirmation dialog: If you have the bad habit of accidentally deleting files from your completed, waiting, or queued lists, you'll want to keep this option on, since deleting lines is not undoable.
Check for servers joining under different nicknames: Sometimes a server will leave then come back under a different nickname, normally Autoget would check their nickname and address to see if they are in your queue. However, this method has proven to be overly cpu intensive on some slower systems when you are in a lot of large channels. This is only a minor increase in reliability that can cause a lot of trouble for some users, but should be fine for most. Enabled by default.