By the way. If you have to ^C it and perl goes bellyup again, immediately bring up the task manager you should be able to see the child perl process that is still running when the parent died and kill it. That would sort out the messed up cmd session.

In the long term, rather than running perl from a cmd session, then shelling out from that to start another cmd session which starts another perl to use lwp to do the download, you'd be much better off to cut out the two middlemen and just use:

use LWP::Simple;

for ( @urls ) {
    getstore( $theUrl, $theOutputFile ) or warn "Failed to fetch $theU
+rl: $!\n";
}
[download]