Fascinatinger & Fascinatinger!!!!

They both rely on the 'sliced sausage is delivered faster than whole sausage' model.

So far, they seem to be able to run together, simultaneously doing downloads!

FDM is much more friendly for dialup, allowing you to set 3 levels (L,M,H) for the total percentage of dnld capacity chewed up by FDM- High can be 100% or a specified Kb/Sec thruput. It can thus chew away at a low permanent thruput, while net surfing normally. It sometimes backs off in the thruput level, to allow other net traffic, but apparently, not always. It quite often locks up though, and when things such as IE windows stop responding (as in connecting to the Mudcat threads), you need the Vulcan Nerve pinch to get to the process menu to kill the fdm.exe.

IDM just looks like IE download on coloured steroids, and you CAN get access to a console to allow you start and stop each dnld individually - but it just gulps the whole available bandwidth. It DOES have a 'site grabber' which I haven't tried yet. It seems less crashable than FDM though. Unlike FDM, it doesn't seem to want to back off and let go to allow other net thruput though.

FDM just chews away automatically at a dnld list, and you can specify how many concurrent ones can run, and even the total number of threads per site, etc, set and forget. IDM just does as many dnlds as you tell it to manually. When they stop, no others are started automatically.

FDM isn't easy to instantly stop all dnlds, as if you stop one, the bugger just starts the next on the list (which CAN be useful) - you need to shut it down to 'stop all', while IDM does have a 'stop all' button.

The thruput for IDM 'seems' faster - maybe the algorithms for talking to the remote site are better.

Will soon be able to hear GBs songs - all 4 nearly completed now!