New
#390
< 100 hours ???????????????
Screenshots from Windows 10 build 10022 leak - Page 4 - Windows 10 Forums
I do remember this Jimbo, I still have a Tandem 286 laptop with a 10mb harddrive circa 1992 running 3.1 updated from 3. and previouly MS-dos in the loft.
It was "lofted" when I started using 95 on my desktops. Subsequently updated to 98, millenium( 2 weeks waste of money), Xp, Vista (next waste of money I tried for about a month before reverting), 7 (still on a couple notebooksa and desktops), 8 (awful) updated to 8.1 (livable with once customized to look like 7) and now 10 TP.
Various flavours of Linux tried but need for office and playing highend games mean they did not last long.
I had all those too. Including DOS 2.0 thru DOS 6.22.
I never did understand all the angst about ME though. After a few simple tweaks, it worked flawlessly for years.
And I have several customers still using Vista, with no problems at all.
But out of the bunch, it looks like Windows 10 will be the Keeper!
It's going to be the next XP, with a long and prosperous life.
"Live long and prosper, Windows 10".
Windows 3.11 for workgroups. It's what we ran at work and what I ran at home. Just a coincidence really. :) That was the first Microsoft OS I ran at home. The PC was a bunch of scrounged and donated parts. Ah, the old days of DOS. You could do so much and so little, lol.
Just found this here:
Frequency and predictability of builds for Windows Insiders
Why it is a challenge to just tell a date for the next build
It is counter-intuitive, but doing this actually makes builds get published more slowly and have less fresh content than by leaving the date open ended. Why?
- If we announce a date, we’ll want to have a very high confidence of hitting it. It’s frustrating for you to hear a date and be let down if we miss it, and it’s frustrating and distracting for us too. Not only that, but it slows down our engineering since many of the same people who are scrambling after a missed date would otherwise have been making more forward progress on the product.
- Because we’d want that very high confidence we’d pick a date that was further out than if we were living on the edge. We’d give ourselves some time to deal with bugs and re-spin builds if we needed to.
- If we have a great build in hand, as often happens, leading up to the date we would hold on that build rather than ship it. We call this putting the build in ‘escrow’. Why not just ship it early? Well, some people get upset about the surprise, but also it sets expectations that sometimes we really mean a date and sometimes we don’t. We want people to know that when we say a date they can count on that date.
- In the worst case, if we’re chasing down a tough bug and run out of time, we may miss the date. This is of course way worse than being early. We’d have let down people who were counting on us to deliver on the date we said we would.
Microsoft considering third ring for Windows Insiders, allowing more frequent Windows 10 drops
http://www.winbeta.org/news/microsof...ndows-10-drops