Recommended Posts

Exclusive:

I come to know by one source that Microsoft already working on the successor of Windows 7, or the successor and the successor of Windows 7 (Windows 8 and Windows 9).

The Project is the name Midori "Windows Codename Midori." This is aimed to rebuild entirely Windows, it will be goodbye to NT kernel? This will not be programmed in C / C + + code but in mixed as C #, F #, etc

More: http://<< spam >>/2008/07/06/exclusivoi...ndows-8-midori/

Seriously, research people! Midori's aim is to eliminate the dated idea behind "Windows" before someone - such as VMware beats them to it. The idea is to make the operating system hot swappable (via VHD's), and fully in the "Virtual Operating System" realm.

  • 4 weeks later...

Meh, you guys are such liars, they already said that to commemorate bush's 4 years in the white house, they would named Windows 8 "Windows Codename Bush"...

lol what a bunch of winners. A guy shares information and instead of wondering, everyone keeps saying what he says its BS and yada yada. I know u must had a lot of this... but everyoone blaming on the same thing? With wrong arguments of programing?

U dont need to believe everything u read.. but there's not even a margin of doubt here! lol

but yeah... there were rumours thar singularity and midori would turn into something... :p

Midori? wasn't that the code name for that failed project MS did to get people to like Vista? :unsure: anyway, I'd say fake as Win7 isn't even finished yet...although I'm sure they are at least thinking about Win8, considering it's only ~4 years away (roughly).

Midori is such a porn name. :D

"‘Midori,’ is a new Microsoft operating-system platform that supposedly supersedes Windows. Midori is in incubation, which means it is a little closer to market than most Microsoft Research projects, but not yet close enough to be available in any kind of early preview form." Midori is closely related to Singularity in that it is written entirely in managed code.

Its purpose is to "supersede" (replace) Windows, not be a part of it.

Edited by Skulltrail

by "working on" do you mean, thought of the code name for the project? LOL...

also, did you hear Microsoft is working on Windows 12? They wrote it on a board! omfg...

This doesn't mean they have actually coded anything for windows 8 or 9. This thread is (N).

This is not true, C# has built in support for unsafe code via a compiler keyword which allows pointers to be used (important for access directly to regions of memory).

At the end of the day, most kernels consist of high level language + assembly. C# can do everything C/C++ can do, and it is still backed by assembly stubs (Or even inline assembly via crafty delegates) to execute the ring 0 instructions.

The C# code is directly compiled to x86 instructions, as opposed to JITed and cached.

Now, you may ask why this has an advantage over C/C++? Well C# code (assuming you minimize unsafe code usage, which is possible for 90% of the kernel) can be "proofed" or guaranteed to be safe (it wont be vulnerable to buffer overflows or memory corruption of any kind).

Why is this important? Well, when you can make inherent assumptions about the status of a piece of code in software, you can remove the hardware restrictions on it. So instead of having applications and services run in Ring3, they can all run in Ring0 since they are guaranteed to never touch each others address spaces -- or more importantly the kernel's address space.

This essentially means that message passing IPC is zero-copy, making it much better than shared memory mapping while negating the performance hit. This results in an extremely resilient kernel, which has the advantages of a microkernel without the inherent performance hit.

You see, in a normal situation (Monolithic, like the NT Kernel) applications run in a different processor privilege level called Ring3. However, this means that there are heavy performance hits in frequent context switches, to alleviate the issue most systems share mapped memory -- but that's also prone to corruption.

For more information, you can read some papers on Software Isolation and Channel-based Communication. Another interesting read, is the ability to selectively use hardware sandboxing to enforce virtual-machine'd native code. (Useful for example, for win32 backwards compatability).

I guess the point I'm getting at, is that all of this is very feasible from an engineering standpoint. Singularity paved the road for a lot of exciting changes in how Operating Systems are approached. Everything in Singularity is a good idea, and one can only pray that even one of the features in Singularity make it to any iteration of Windows.

Cheers.

I'm suprised to find such a well thought out and informative post, in a rumor thread.

  • 5 weeks later...
bulls**t

But yeah, I've come to take anything like this with a pinch, or two of salt, heck, why not an entire skip-full...heh

Microsoft generaly looks 2 generations in the future of what is on the market. First one past the current version is what they are programing and the one past that is just a bunch of people talking about what it will be. So now they are building 7 and talking about 8 "UnOficially" of course.

  • 1 month later...
Like they are going to develop a Windows "8" and Windows "9" right now, especially when Windows 7 is only in ALPHA.

I smell a topic that was MEANT to start a flame war :/

Well, If I remember correctly, an early Whistler build (codename for what would become XP) found its way to the internet a mere days after Windows 2000 went gold. It was obvious it had been worked on for weeks, if not months.

That's not to say this is real. I'm on board with the fake train, but my point is, It wouldn't surprise me at all if the next version of Windows after Windows 7 was already in the planning stage.

Well, If I remember correctly, an early Whistler build (codename for what would become XP) found its way to the internet a mere days after Windows 2000 went gold. It was obvious it had been worked on for weeks, if not months.

That's not to say this is real. I'm on board with the fake train, but my point is, It wouldn't surprise me at all if the next version of Windows after Windows 7 was already in the planning stage.

Thanks for clearing that up :)

Seems I was wrong. Oh well, you cant always be right.

But it still seems stupid that they are not ALL concentrating on W7 so it could be 100% Effort and not 95% effort. :/

While some product planner guys might be dreaming up what they can and can't do in win8 and 9. I think the only thing getting any seious attention would be 8. Win 7 if it is going to hit beta1 soon means it is basically done and product mangers are naturally in a transition point to 8 or whatever they want to call it.

I hope that it is a little more ambitious than 7 seem to be.

  • 2 weeks later...

Well I smell a huge development in the next windows after 7

This midori you speak of could be a revolution

I really believe they should build it back up from the ground using totally new concepts

and designs..

Also save PC gaming!!! We need better direct X optimization!!!!

I suspect windows 8 (midori) Is already in development

EXCLUSIVE

Microsoft are scrapping Windows 7 and are going to make an entirely new OS that is not under the "Windows" moniker and will be constructed entirely out of Fairy floss

I can not disclose my sources! not fake!!

I can vouch for this. I have also heard various stories linking the Windows development cycle and Fairies.

Seriously guys, concentrate on facts.

Like they are going to develop a Windows "8" and Windows "9" right now, especially when Windows 7 is only in ALPHA.

I would be shocked if Microsoft did not have plans for the next two versions of their OS on the table.

This does not mean they are in active development. They may be nothing more than "wish lists" of features and technologies that they plan to incorporate into these future releases. But, this is planning nonetheless. You can't start actual development without a plan.

EXCLUSIVE

Microsoft are scrapping Windows 7 and are going to make an entirely new OS that is not under the "Windows" moniker and will be constructed entirely out of Fairy floss

I can not disclose my sources! not fake!!

O SRSLY?> 0_0

OMG FAIRLY FLOSS THAT R LIKE GON BE SO COol

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!