Update 1809

Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.

--
croy

croy wrote:
Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.


The URL is only valid for 24 hours.

Your link had better hurry up!

Win10_1809Oct_English_x64___10.0.17763.107.iso

5,075,539,968 bytes

That's the 64 bit one. The 32 bit one is probably
a bit smaller, but I didn't bother to download it.
It's probably 1GB smaller.

The revisions of 1809 before that one, are a bit
smaller. The previous disc had only 8 versions of
Windows 10 on the same disc.

The reason that one is so big, is Microsoft has
squeezed 11 versions of Windows 10 into the disc.
Microsoft could easily have placed the more obscure
versions on their own disc.

Paul

On Tue, 16 Apr 2019 20:36:39 -0400, Paul wrote:

croy wrote:
Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.


The URL is only valid for 24 hours.

Your link had better hurry up!

Hmm, when I set up time-limited web links, I always allow connections in
progress to continue as long as they take. I only block new connections
after the time has expired. I would assume MS to do likewise, no?

Char Jackson wrote:
On Tue, 16 Apr 2019 20:36:39 -0400, Paul wrote:

croy wrote:
Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.

The URL is only valid for 24 hours.

Your link had better hurry up!

Hmm, when I set up time-limited web links, I always allow connections in
progress to continue as long as they take. I only block new connections
after the time has expired. I would assume MS to do likewise, no?


I've not seen any reports from a persistent user who
is waiting the 24 hours to test this.

It could be link invalidation.

It could be file removal.

It would be too expensive for a dialup user to test for this
and tell us how it works. (Besides, if a user was actually on
dialup, the phone system won't leave a phone call running
long enough to find out. The call will get dropped at
some point.)

I've only had one download, where the proposed download time
was longer than 24 hours, and the connection was running
consistently. The server seemed to be enforcing a 60KB/sec
limit or so. On your end, if you had a router that had
bandwidth adjustment capability, you could simulate dialup
speeds and test the behavior of these ephemeral URLs. My router
doesn't have that function.

Paul

On 4/28/2019 12:46 PM, Char Jackson wrote:
On Tue, 16 Apr 2019 20:36:39 -0400, Paul wrote:

croy wrote:
Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.


The URL is only valid for 24 hours.

Your link had better hurry up!

Hmm, when I set up time-limited web links, I always allow connections in
progress to continue as long as they take. I only block new connections
after the time has expired. I would assume MS to do likewise, no?

I just came across this thread, so do not know all of the information
transmitted. A couple of updates ago I had one that stuck and was
taking hours to download. After a period I broke the connection, by
turning off the Wireless receiver on my computer, I waited a 5 or 10
minutes, and turned it back on. When the computer realized there was a
download in progress, it reestablished the connection and the download
complete in a very short time.

I assumed there was a faulty server modem, or for some reason the
connection failed so it appeared the down load was continuing. When I
broke the connection the problem was corrected and the download
proceeded quickly to completion.

My experience, I don't know the facts.

--
2018: The year we learn to play the great game of Euchre

On Sun, 28 Apr 2019 14:28:15 -0400, Paul wrote:

Char Jackson wrote:
On Tue, 16 Apr 2019 20:36:39 -0400, Paul wrote:

croy wrote:
Is 1809 the number of gigabytes for the download? It looks like just the dl will cover about
24 hours. It's at 24% now, and it's been running for 6 or so hours.

The URL is only valid for 24 hours.

Your link had better hurry up!

Hmm, when I set up time-limited web links, I always allow connections in
progress to continue as long as they take. I only block new connections
after the time has expired. I would assume MS to do likewise, no?


I've not seen any reports from a persistent user who
is waiting the 24 hours to test this.

It could be link invalidation.

It could be file removal.

Link invalidation makes sense; file removal not so much. I would think
that each download link actually points to the same physical file, via
one or more layers of obfuscation. That's how I do it, anyway.

It would be too expensive for a dialup user to test for this

Expensive in terms of time spent? Certainly not expensive in terms of
financial cost.

and tell us how it works. (Besides, if a user was actually on
dialup, the phone system won't leave a phone call running
long enough to find out. The call will get dropped at
some point.)

About a year ago, I needed to set up a troubleshooting bridge and I used
Spectrum Voice (VoIP). Spectrum was my ISP at the time. I established
the bridge on a Thursday morning at 10:00AM and by 2:00PM the issue had
been identified and resolved. We agreed to drop off the bridge and call
back in the next morning at 10:00AM, but out of laziness I left the
bridge up. Friday morning, everyone called back in to get current
status. Everything was still good, so we agreed to reconvene on Monday
morning at 10:00AM for a final status check, a detailed post mortem for
upper management, and to begin a data backfill operation. Again out of
laziness, I just left the original bridge up, and lo and behold, Monday
morning it was still up and everyone was able to dial back in. I don't
know if Spectrum places a call duration limit on their Voice product,
but 4 days clearly wasn't enough to trigger a drop. I was surprised,
especially since Google Voice has a hard stop (call drop) at 3 hours.
That GV behavior was what brought me to try Spectrum Voice.

I've only had one download, where the proposed download time
was longer than 24 hours, and the connection was running
consistently. The server seemed to be enforcing a 60KB/sec
limit or so. On your end, if you had a router that had
bandwidth adjustment capability, you could simulate dialup
speeds and test the behavior of these ephemeral URLs. My router
doesn't have that function.

I *could* test that, but I don't plan to.