Forté Agent versions

v8.0 [Sep 17, 2014]
MegaJoining: Collapse binary archives together into a single header.
No more hunting around for all the pieces. One header contains your RAR/PAR/Split files.
Navigation is easy. One entry for one binary file let's you focus on the end result, not all the pieces.
Keep up to a hundred times more messages in your group folder. A single header may have hundreds of elements, but the entire archive only counts as one entry.
Repair damaged files.
Agent computes how many PAR files are required to repair an archive, then downloads and uses only those files.
Files are fixed automatically. No unnecessary commands or downloads, no third-party software, no trouble.
Preview a binary file.
Before you download all the elements make sure this is the archive you want.
Previews start at the beginning of the binary file and last as long as you want.
Identify and view poster-created sample files.
If an archive has a sample included then Agent puts all the sample files into their own MegaJoined header. This is another way to make sure this is the archive you want.
Handle password-protected archives.
Agent checks at the beginning of the download to see if a password is required, allowing you to avoid downloading files you can't open.
When the download is complete Agent asks for the password, then saves or launches the file.
Start where you left off.
Need to interrupt your download? Agent restarts where you left off, saving time and disk space.
Use NZB files anytime
MegaJoining works seamlessly with NZB files. Just import the NZB file. Agent does the rest.
All the features described above work with NZB files also.
Third party software like WinRAR and QuickPar is not needed. Agent provides all the functionality you need.

v7.2 [Aug 30, 2013]
1. Increase in Connections to Agent Usenet Servers
- increased the maximum number of connections allowed at our Agent Premium Usenet service (APN) to 30. To make it easy for Agent users to take advantage of the change, Agent 7.2 increases the default number of connections from 10 to 30 for new Usenet servers you set up. Also, when you first run Agent 7.2, it will automatically increase the number of connections to 30 for servers you have already defined, but only when:
- The number of connections was set to 10, the old default value
- The number of connections was set to 25 and the server definition is for an APN server.
2. Notes
- Agent customers who subscribe to APN aren't required to update to version 7.2, because you can always change the maximum number of connections manually. To do that, open the News Server Panel of the Servers and Accounts dialog box.
- Of course, Agent customers who don't subscribe to APN do not need to update to version 7.2. However, you might want to review Agent's maximum connections settings to make sure you are using all of the connections available. It never hurts to set Agent's maximum to a value that is greater than the number of connections actually available, because Agent automatically detects when it hits the limit set by the server and adjusts accordingly.
3. Bug Fixes
- accidentally introduced a bug in Agent 7.1 that sometimes caused Agent to fail to retrieve bodies for messages imported from NZB files. Agent would incorrectly report that the bodies were unavailable. We actually fixed the bug in Agent 7.1 Build 1214 but did not formally announce the change. The fix applies only to users who installed Agent 7.1 Build 1212. If Agent's About dialog box says you're already running build 1214, you do not need to upgrade to version 7.2 to get the bug fix.