WZOR Talks About Windows (Codename) 9, Is a DP Imminent?


Recommended Posts

Nah, I don't really care what MYCE found about non-MS guys, it's what @h0x0d found in MS guy's linkedin profiles that's interesting, hopefully more of these would come up eventually.

 

btw, I guess you had mentioned some Windows build 98xx, maybe this post by @arseny in MDL could be interesting:

 

http://forums.mydigitallife.info/threads/55109-News-Discussions-On-Windows-Upcoming-Products-W8-1Update-x-W365-WThreshold-Win9/page131?p=933213&viewfull=1#post933213

 

"Windows Phone current: Although the phone about screen says OS version: 8.10.12397.895, that does not easily tell us the actual version of the Windows Phone OS. We need to mount a .ffu image of a firmware intended for flashing to know this for sure, since the above notation is custom versioning of the platform. Let's take for instance the latest Lumia 930, so if we mount the firmware, we can find out that the build of the underlying Windows 8.1 that the Windows Phone 8.1 OS is based on, is 6.3.9651.0.winbluephone_rtm.140521-1530 (those who wish to confirm, may do so). This if we don't include the phoneOS-specific tweaks, which cause them to rebuild it with the custom versioning using the Windows Phone buildmachine, causing for it to be 8.10.12397.895.wpbldlab.140530-2215 as per the buildinfo.xml that is included in the archive by the above link."

 

And I had some ask-around and discussed with arseny later:

 

http://forums.mydigitallife.info/threads/55109-News-Discussions-On-Windows-Upcoming-Products-W8-1Update-x-W365-WThreshold-Win9/page151?p=935131&viewfull=1#post935131

 

Seems there is actually no rule against WinBlue or WinThreshold to use build nos. higher than the win9 prototype build No. 9622, i.e. WinBlue, WinThreshold and Win9 could all share build nos. higher than 9622. :) 

 

If it doesnt come with new icons (and the hidden vista and windows 95/98 icons removed) its stil the same OS

Who knows, it might not even have icons in the traditional sense at all.

I wonder if they finally took the time to update the installer itself, it's still got ties to the old Vista/Windows 7 days till you hit the post install process.

It says Windows Technical Preview.

So they are doing something similar as they did with Windows 8, of which the first preview was called "Windows Developer Preview", not Windows 8... Let's hope the september/october rumors are true. :)

Brad, any indication when Microsoft might be planning to announce this?

 

 

Late September per Foley, I have only been hearing 'soon'.

 

So they are doing something similar as they did with Windows 8, of which the first preview was called "Windows Developer Preview", not Windows 8... Let's hope the september/october rumors are true. :)

 

Correct.

 

Any Screenshots of Splash Screens of Threshold that have ben updated to say preview that you could show us?

 

Yes and no. Yes there are screenshots but they can't be shared for obvious reasons.

 

 

 

Current build is 982X.

  • Like 3

Oh. I wonder if some how WZOR or Faikee could leak those out for us!

Sorry, man, I have never leaked builds, just a messenger to report on builds being leaked. :)

 

Btw, I'd like to mention what happened in 2011: In May canouna mentioned "a new name on win8 builds", in June a OEM guy posted screen-shot of "Windows Developer Preview" in PCBeta, in Sept. MS released WDP - so make a wild guess based on this time-line.

I now know why FaiKee thinks that Threshold and Windows 9 are two separate things, not saying that I agree, but I know where it is coming from.

Care to elaborate?

We all would like to know :)

I now know why FaiKee thinks that Threshold and Windows 9 are two separate things, not saying that I agree, but I know where it is coming from.

 

I understand you have to protect you're sources.

 

So if you don't respond that's fine.

 

But is it because of 2 branches one with W9 and the other W365? Or W9 and W9RT merge? That rumors started? Or just because at some point when build conference happen the plan was to release a 8.2 instead of August update and work at W9 at the same time 2 branches existed?

I understand you have to protect you're sources.

 

So if you don't respond that's fine.

 

But is it because of 2 branches one with W9 and the other W365? Or W9 and W9RT merge? That rumors started? Or just because at some point when build conference happen the plan was to release a 8.2 instead of August update and work at W9 at the same time 2 branches existed?

 

 

Nah I can answer it, has nothing to do with a single source. I'll turn it into a blog post but it has to do with the design updates to the OS. If you were to put two builds right next to each either, they look totally different.

Nah I can answer it, has nothing to do with a single source. I'll turn it into a blog post but it has to do with the design updates to the OS. If you were to put two builds right next to each either, they look totally different.

Now I guess I know what you are thinking, and it's not why I said Threshold is not win9, anyway, I would like to see your blog, it will be really interesting for our members.

 

Leaving for China for the day, hope to see it to-night. :)

This topic is now closed to further replies.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      260
    3. 3
      Skyfrog
      84
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!