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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • 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
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!