Recommended Posts

Adding to the already impressive pile of Vista-deflating features we're expecting to see in Windows 7 is WARP, a tech which will allow your PC's CPU to act as a graphics accelerator, possibly doing away with the need for integrated graphics hardware to render user interfaces and low-end games. Not-so-seductively described as a ?fully conformant software rasterizer?, WARP requires nothing more than an 800MHz processor for complete?if comically slow?DX10 compliance.

At this stage WARP won't be intended as a gameworthy replacement for dedicated graphics cards, but it could help avoid another "Vista Capable" type debacle by standardizing essential graphics capabilities across virtually all hardware. That said, it's not that slow: Microsoft reports that when paired with the rather awesome i7, it runs Crysis faster than Intel's integrated DX10 solutions. Like, 42% faster. Granted, that's still only 7.36FPS on the game's lowest settings, but don't miss the point here: Windows 7 will run Crysis?or any other game?without a video card.

Source

As we already know that Windows 7 will feature 'WARP' which allows the CPU processor to render GPU functions/features. But, while this may be great for people who run old hardware like a Radeon 8500 (for example), allowing them to use Aero features like transparency and so on. I doubt it'll be so great on the processor. If anything, people would be worse off since the CPU would have to do it's primary job as well as Graphical effects. Does anyone else agree this is a false positive?

Don't get me wrong, I love the idea, it just doesn't seem logical. If you haven't got a computer that doesn't render Aero, then you are seriously behind in the technology world. What does everybody else think of this?

Source

As we already know that Windows 7 will feature 'WARP' which allows the CPU processor to render GPU functions/features. But, while this may be great for people who run old hardware like a Radeon 8500 (for example), allowing them to use Aero features like transparency and so on. I doubt it'll be so great on the processor. If anything, people would be worse off since the CPU would have to do it's primary job as well as Graphical effects. Does anyone else agree this is a false positive?

Don't get me wrong, I love the idea, it just doesn't seem logical. If you haven't got a computer that doesn't render Aero, then you are seriously behind in the technology world. What does everybody else think of this?

I work on a lot of computers that run perfectly fine with vista... but have crummy video cards. I dobut these computers would be taxed by the extra processing power needed. Not to mention by the time 7 comes around... more people will have modern hardware/upgraded/purchased a new pc.

I work on a lot of computers that run perfectly fine with vista... but have crummy video cards. I dobut these computers would be taxed by the extra processing power needed. Not to mention by the time 7 comes around... more people will have modern hardware/upgraded/purchased a new pc.

Yeah, but really, is there any point of using 'WARP'? It's like. Yay! I can run Crysis, but at 7fps (On a i7 based processor). Hardly playable.

Yeah, but really, is there any point of using 'WARP'? It's like. Yay! I can run Crysis, but at 7fps (On a i7 based processor). Hardly playable.

Running crysis vs having glass are completely different things.

I fixed an old P4 1.4GHz 512MB of ram computer running vista ultimate. I got a 1.1 on the index iirc.

We upgraded the graphics card and it ran glass just fine... so I doubt any other computer is going to have an issue. And if you're running Windows 7 on a P4 1.4GHz... thats their problem.

Microsoft got it all wrong again which is natural for them. If they wanted to make Aero in Windows 7 to work on machines with no video card to support it for God sake they don't need Pixel Shader 2.0 to run aero, infact Pixel Shader 1.1 is enough which is supported by old Geforce 3, Radeon 8500 cards.

Why is everyone talking about WARP as it's meant to just run aero? You say MS got it wrong? Maybe you're missing the bigger picture? WARP is meant to take advantage of x86 CPUs better, sure the GPU should be running your games, and that's what it'll do, the fact WARP can even run Crysis at 7FPS just shows how good MSs code is, it's an example, not what it's meant for.

Setting a performance base for future versions is one thing, and this does that in one respect, but the main part is to better support future x86 CPUs. When Intel has it's larrabe chips out, which are nothing but lots of mini-x86s made to take just this sorta code and work with it, then WARP comes into play even more.

Why is everyone talking about WARP as it's meant to just run aero? You say MS got it wrong? Maybe you're missing the bigger picture? WARP is meant to take advantage of x86 CPUs better, sure the GPU should be running your games, and that's what it'll do, the fact WARP can even run Crysis at 7FPS just shows how good MSs code is, it's an example, not what it's meant for.

+1

What's all this about running Crysis at 7fps on an i7? :blink:

Well, not exactly 7fps, but why does it work badly on an i7?

Back on topic, is it really necessary to put the CPU or even GPU to heavy use when it comes to Aero? I mean, you get the Aero theme when installing Vista during setup regardless of whether your PC can handle Aero or not.

What's all this about running Crysis at 7fps on an i7? :blink:

Well, not exactly 7fps, but why does it work badly on an i7?

Back on topic, is it really necessary to put the CPU or even GPU to heavy use when it comes to Aero? I mean, you get the Aero theme when installing Vista during setup regardless of whether your PC can handle Aero or not.

Actually, you don't. That's just a still image. You can't move it or anything.

Why is everyone talking about WARP as it's meant to just run aero? You say MS got it wrong? Maybe you're missing the bigger picture? WARP is meant to take advantage of x86 CPUs better, sure the GPU should be running your games, and that's what it'll do, the fact WARP can even run Crysis at 7FPS just shows how good MSs code is, it's an example, not what it's meant for.

Setting a performance base for future versions is one thing, and this does that in one respect, but the main part is to better support future x86 CPUs. When Intel has it's larrabe chips out, which are nothing but lots of mini-x86s made to take just this sorta code and work with it, then WARP comes into play even more.

+1....Some people hate MS without any particular reason saying that vista is crap and that Win7 will be worst...MS is a giant software/hardware company that tries to facilitate our lives...can't they face it?

CPU's are usually running at 1% capacity most of the time, this is a great way to put them to use, just like how superfetch makes use of memory when it's otherwise not being used. This will be great for improving aero performance on netbooks, and nettop PC's.

Why is everyone talking about WARP as it's meant to just run aero? You say MS got it wrong? Maybe you're missing the bigger picture? WARP is meant to take advantage of x86 CPUs better, sure the GPU should be running your games, and that's what it'll do, the fact WARP can even run Crysis at 7FPS just shows how good MSs code is, it's an example, not what it's meant for.

Setting a performance base for future versions is one thing, and this does that in one respect, but the main part is to better support future x86 CPUs. When Intel has it's larrabe chips out, which are nothing but lots of mini-x86s made to take just this sorta code and work with it, then WARP comes into play even more.

Taking advantage of x86 CPU that way, are you freaking kidding me? Intel's Larrabe is going to suck big time.

CPU's are usually running at 1% capacity most of the time, this is a great way to put them to use, just like how superfetch makes use of memory when it's otherwise not being used. This will be great for improving aero performance on netbooks, and nettop PC's.

Well, my laptop does not need this cause it has ATI X3000 video chip unlike others with crappy Intel Integrated Video Chip. Either way Aero can run using Video Cards such as Geforce 3, Radeon 8500, and even Integrated Intel Video Chip capable of running 1.1 Shader Model which is enough. As I said Microsoft does everything wrong. Maybe the best way Steve Jobs summarized it saying that what is actually 'sad' is that Microsoft writes 3rd grade Software and Operating System.

Why is everyone talking about WARP as it's meant to just run aero? You say MS got it wrong? Maybe you're missing the bigger picture? WARP is meant to take advantage of x86 CPUs better, sure the GPU should be running your games, and that's what it'll do, the fact WARP can even run Crysis at 7FPS just shows how good MSs code is, it's an example, not what it's meant for.

Setting a performance base for future versions is one thing, and this does that in one respect, but the main part is to better support future x86 CPUs. When Intel has it's larrabe chips out, which are nothing but lots of mini-x86s made to take just this sorta code and work with it, then WARP comes into play even more.

+1

Since 7 is an upgraded vista this is important. IF your notebook cant run Aero then the os will not let you run movie maker and other programs.

This sounds like microsoft being lazy and instead of fixing their programs they came up with a bandaid solution.

I thought WARP was intended to be used for Aero like the thread title says. Just because it will run a game doesn't mean that's what they intended it for. ;) And the Intel GPUs are fine as long as you don't want to play an intensive game. The 945s and 950s seem to run Aero just fine.

What's all this about running Crysis at 7fps on an i7? :blink:

Well, not exactly 7fps, but why does it work badly on an i7?

Back on topic, is it really necessary to put the CPU or even GPU to heavy use when it comes to Aero? I mean, you get the Aero theme when installing Vista during setup regardless of whether your PC can handle Aero or not.

That is just a tech demo. Either way, it's a relatively impressive feat, to use the CPU to give such a boost to graphics performance.

Everyone in this thread has got this wrong (unless I skipped over someone who explained it correctly already, in which case I appologise).

WARP's primary purpose is to allow application developers to build applications (not games) that run on DirectX 10, and only on DirectX 10, whether most people have capable hardware or not. Writing a DirectX application to target two platforms (Dx9, Dx10) is time consuming. By writing to one platform that can target everybody, a developer can save time and money. It is not designed to allow demanding 3D games to run without a dedicated 3D graphics processor, nor is it designed to allow Aero to be run on any system (although this may be a possible by-product of this tech). It is simply another tool that allows developers to target DirectX 10, even if hardware support is not available.

Everyone in this thread has got this wrong (unless I skipped over someone who explained it correctly already, in which case I appologise).

WARP's primary purpose is to allow application developers to build applications (not games) that run on DirectX 10, and only on DirectX 10, whether most people have capable hardware or not. Writing a DirectX application to target two platforms (Dx9, Dx10) is time consuming. By writing to one platform that can target everybody, a developer can save time and money. It is not designed to allow demanding 3D games to run without a dedicated 3D graphics processor, nor is it designed to allow Aero to be run on any system (although this may be a possible by-product of this tech). It is simply another tool that allows developers to target DirectX 10, even if hardware support is not available.

most logical thing i've read all thread

Everyone in this thread has got this wrong (unless I skipped over someone who explained it correctly already, in which case I appologise).

WARP's primary purpose is to allow application developers to build applications (not games) that run on DirectX 10, and only on DirectX 10, whether most people have capable hardware or not. Writing a DirectX application to target two platforms (Dx9, Dx10) is time consuming. By writing to one platform that can target everybody, a developer can save time and money. It is not designed to allow demanding 3D games to run without a dedicated 3D graphics processor, nor is it designed to allow Aero to be run on any system (although this may be a possible by-product of this tech). It is simply another tool that allows developers to target DirectX 10, even if hardware support is not available.

this is in direct responce to the vista debacle with the 915 chipset. I have an old 915 notebook that was vista capable. they didnt tell you that aero wouldnt run and half of the included apps would not work because aero wasnt caspable of running.

This makes windows 7 fully run on any pc . which goes back to my complaint. instead of fixing their apps to not require a gpu they built a sub system to fool the apps to run. Example on my acer which has an 915 chipset which movie maker works perfectly well on xp in vista on the same pc movie maker refuses top run because i cant run aero.

I feel this is microsoft just being lazy and trying to get out of legal trouble. that is all .

Everyone in this thread has got this wrong (unless I skipped over someone who explained it correctly already, in which case I appologise).

WARP's primary purpose is to allow application developers to build applications (not games) that run on DirectX 10, and only on DirectX 10, whether most people have capable hardware or not. Writing a DirectX application to target two platforms (Dx9, Dx10) is time consuming. By writing to one platform that can target everybody, a developer can save time and money. It is not designed to allow demanding 3D games to run without a dedicated 3D graphics processor, nor is it designed to allow Aero to be run on any system (although this may be a possible by-product of this tech). It is simply another tool that allows developers to target DirectX 10, even if hardware support is not available.

This was what I was trying to get at with my post, why I said it's a base for developers to target etc. But you pointed it out even better.

Cool technology and the potential applications and implications of it are going to be quite big I think. But, I do imagine there will be cries of complaint of people running Windows 7 on vastly underpowered computers with Aero turned on, complaining that the CPU usage is too high...

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

    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      596
    2. 2
      +Edouard
      188
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!