Download via wireless

No, but that is more a function of direction, east coast to west coast is uphill and into the wind. West to east is a bit easier, prevailing wind at your back and way more downhill miles.

fundamentalism, fundamentally wrong.

How old are you and how long (time) does that take you? Needless to say, for a non-pro, I'm impressed.

fundamentalism, fundamentally wrong.

Prolly ought to ask in uk.rec.cycling or somesuch, but there's a route from from Morcambe Bay to Whitby which is very attainable in a day - ISTR people do it as an overnight trip occasionally. . My cousins also take part in a triathlon from Kintail, which is a from the west coast, a swim down a loch, then a cycle to inverness, on the east coast. Mark McIntyre

Way older than I like to admit! :)

My average for a typical long ride was/is roughly 15 mph (making for a nice

Thanks. It helps to have a really good bike, in my case Bianchi and Trek.

Many of my favorite day rides have been in the Napa valley. The Callistoga-Napa loop is about 65 miles (round trip). Add on some valley crossovers and side trips to special wineries for a total of 80-100 miles (as measured by my bike computer), heat permitting. :)

Sadly, my knees aren't what they used to be (thanks to years of intense sailing dinghy racing), so I'm more of a 50 mile person these days. :(

The tool that Microsoft offers for the downloads that I was referring to is the Microsoft Transfer Manager, there are no other tools.

It permits a maximum of 2 concurrent downloads.

There are business critical situations where a download will not arrive in time, patience is not an option.

I'm done, you're arguing for the sake of arguing your point that dial up is fine for many purposes. It's totally unusable for many more too.

David.

Late to this thread, ftp won't get it for your needs?

fundamentalism, fundamentally wrong.

No, because the protocol that MS use in this instance is not ftp. MS Transfer manager is the only tool available and it's a pain.

David.

David Taylor hath wroth:

Is that Message Transfer Agent?

I've never noticed MS FTM before

I downloaded something huge from Microsoft using the Real Download Manager. This was an add-on for IE, and I just clicked the download link as normal, and Real did the download. It worked over several days as I connected and disconnected the dialup normally. By the time it finished, I had actually forgotten that it had started. I used to have a link to Real Download, even after it wasn't obviously offered, but that has gone away.

I have also been using the Sun Download Manager, which works with ftp or http links.

No, Microsoft Transfer Manager as used by the MSDN site (and others), it's nothing to do with Exchange and is not the MTA in that context.

No, it's specific to certain MS sites.

Haven't had to use it yet -- please give me an example.

I already did when I said the MSDN site as one example.

Go and download Windows Vista and say "hello" to the Microsoft File Transfer Manager.

Here's another

How about something that doesn't require registration?

Why? That's irrelevant, I can't help that you have no access to the sites that use (and force the use of) FTM! MSDN Subscriber downloads is a pretty important part of the Microsoft download system.

These sites exist and that's all you wanted to know. :)

David.

I actually just wanted to verify that it's really mandatory. If that's not worth it to you, then I'll simply wish you a nice day.

I don't need you to verify that it is mandatory. I already *know* that it is!

:)

David.

Correction: You *claim* that it is.

I'm assuming, by "download", you mean from the internet and not local file transfers.

If your wireless pipe is bigger than your internet pipe, then there /should/ be no difference between downloading over a wired connection versus over-the-air.

I.e., Roadrunner gives me 5 Mbps downstream, which both my 802.11a and

Now, local file transfers -- thats different. Good ol' CAT5 still comes out ahead. 802.11g (and 802.11a) give you mid to high 20'ish Mbps, which isn't bad, but can be a little painful to transfer huge amounts of data around such as doing Ghost backups.

BTW: If you are using Windows, before even start looking at wireless, the first thing you want to do is open your RWIN size. Its a value stored in your registry as TcpWindowSize. By default, Windows has you bottlenecked. Value you want to use is your (advertised internet speed x average latency) divided by eight...

Google/deja for more on it..

Have fun...