For THIS I have DSL?

Sam writes:

Sean just called me - he beat me, darn it-) As did David Stone and Julie here - thats what I get for doing nose down in some code-)

[Sam Gentile]

Well, for those of us who are silly enough to (try to) download it on day 1, looks like it could be a long one. I'm currently showing 25 kb/sec. with an estimated time of completion of 8 hours. And that's not including the MSDN library, which is apparently 1.9GB in three ISO images. Well, I really wasn't going anywhere for the next 8 hours anyway, right?

384k SDSL, and all I get is a measly 25kb/sec. How about some more servers and bandwidth, MSDN?

4 Comments

  • I am downloading it right now with 2 ds-2 connections, and i am only getting 56kbps, i usually get 4-5mbps

  • Could be worse, you could be out here in the hinterlands on a 56K Frame Relay line...3.6 KB/sec...53 hours 42 minutes and counting...

  • Andrew,





    DSL Sucks. I can say this with authority, as I worked for the Qwest DSL Group for 6 months, and was the one that re-architected their entire troubleshooting process. While the idea is great, you should always be leery about running 21st century technology on top of 19th century technology. There are about 500 (literally) different problems that can take down DSL, from sunlight on the side of the house to lots of rain getting the phone lines underground wet. Take it from a friend man.... get cable.

  • Cable? CABLE? I HAD cable! Why do you think I got DSL? :-)





    Besides, are you forgetting that cable is a shared pipe while DSL (mine is routed SOHO business plan) is not (or at least, there's much less shared pipe)?





    It's not the DSL that's the problem here. I get very consistent throughput at +/ 300kbps. No, the problem is the popularity of this *particular* download.


Comments have been disabled for this content.