Recommended Posts

so what's new, directx always had a software emulator for features not supported by the the GPU. I've used it a lot when I did 3d programming on my laptop while travelling.

And nowhere is said that it will be used for aero, I can't believe the kind of **** people keep inventing

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 .

Get over yourself, you bought a crappy computer, and now microsoft has got a fix for you, if you are willing to wait about one year (or run the beta).

So...microsoft is lazy?

The reason vistas movie maker does not work is it's rendering process is based on WDDM.

And it's capable? it's running vista isn't it?

So please, stop complaining. No-one forced you to buy it that computer:p

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...

Vista all over again. People thought their eight year old XP certified computer could run it without problems :p

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.

Sure, there's no point in running Crysis with WARP, but Aero Glass is another matter. Aero Glass should be exponentially less taxing than Crysis, after all. I'd guess a medium-range dual-core should be able to handle the 3D computations required by Aero Glass with little overhead to the whole system performance.

whether MS will really let it support Aero Glass on sub-DX9 systems, that's another issue.

Just think of the idea - spending extra CPU cycles just to run eye candy. This is not productive. This is meant to be used in games. And probably Win7 won't even come with drivers for 8500 video card - thats old man!

Ugh, it's just the goddamn reference renderer. Just because they've slapped a silly name on it, everyone's suddenly jacking off.

just like mmmm

ah yes !

GIVE us WinFS !!!! NTFS SUXor ! :laugh:

btw :

i like the cartoon in your sig ;)

I'm surprised people see this as a bad thing. Apple are doing a similar thing in Snow Leopard (except offloading CPU tasks to the GPU instead of the reverse) and people praise it as being a good idea, MS does it and suddenly it's bad.

Ugh, it's just the goddamn reference renderer. Just because they've slapped a silly name on it, everyone's suddenly jacking off.

i love how everyone keeps saying what it is...the sdk or white papers havent even been released and we barely know anything about it yet

well then mr smarty pants has anyone figured out how to actually run applications on the software renderer? i think not...now we have that ability...why is that a bad thing?

The renderer is with the SDK. Install it to use it. Just because it's suddenly bundled with Windows 7 main, doesn't make it the second coming of Jesus.

The renderer is with the SDK. Install it to use it. Just because it's suddenly bundled with Windows 7 main, doesn't make it the second coming of Jesus.

Does'nt make it the first coming of satan either :p

Microsoft; "Hey,we have made a software rederer to make it easier for developers to test and develop software"

People who don't actually have any knowhow; "Wasted development time, i don't need it, i'm egoistic"

Again, this has nothing to do with running Aero on machines that don't support the DWM currently. It simply won't happen.

My understanding is that WARP 10 is about the DirectX team listening to developers and their biggest complaints about DX9 and OpenGL... caps. Now that caps are gone they need a way to fill in any gaps in the hardware, especially if they want to support DX10+ on the broadest range of hardware possible.

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

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.

There are Intel integrated graphics chips that can run Aero in Vista today. The X3100 (common in a lot of notebooks, not to mention the odd desktop) certainly does (even on x64), as does the nForce 630i and AMD's 780G. The big advantage is for VM software (VMWare, VirtualBox, and hypervisor-based software such as Xen or Microsoft's own Hyper-V) which lets thin clients take advantage of the same tricks as full systems (a real plus for enterprise deployments, especially those with lots of thin-client desktops). What's wrong with that?

I have 6956 installed both in a VM (VirtualPC 2007) and a native install, and, for once, both have Aero support.

Or maybe WARP is just a playground for developers?

Actually, while WARP is certainly useful for developers (especially those that use VMs for software development, which is becoming commonplace), the real gain will be on thin clients, which will be nearly indistinguishable from full-system clients from a desktop-capability POV.

WARP is actually based on older technology (that appeared in Windows 2000 Professional, which was the first NT-based OS to specifically support DirectX). Does anyone remember Windows 2000's Hardware Emulation Layer (acronym is, unfortunately, HEL)? It basically defined a floor set of capabilities for any Windows 2000-based desktop (the floor was DX 5). WARP brings it up to DX10 emulated capability. This is bad how?

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 actually think that those that run 7 in VMs (sandbox testers and developers now, and enterprise deployers, especially those deploying to thin clients, in the future) will seriously enjoy the capabilities of WARP. It's not even new technology; it's an enhancement of a feature that's been present in NT since Windows 2000 - the Hardware Emulation Layer. The Hardware Emulation Layer defined a floor set of capabilities for all hardware that could physically run Windows 2000/XP/Vista (and now 7); WARP in 7, however, has really ramped up that floor to the point that Aero and DX10 is part of the base capability level of any system running 7 (rather than an option, as it is in Vista today). Remember, Aero in Vista doesn't even require DX10 in hardware (AMD's R300, which is pre-XP SP2, is Aero-capable, as is nVidia's FX series and even Intel's X3100). I'm wondering just how fast WARP will run in practice, and a WARPed 7 VM makes a great sandbox.

Why are we even still talking about pre DX9 hardware, it'd be so old that the rest of the computer wouldn't even run Vista, let alone Windows 7.

Datapoint:

One of three P4-based computers I have upgraded to Windows Vista is a Dell OptiPlex GX260 (P4 2.4 Northwood-B, 1 GB of RAM, but only Radeon 8500DV AGP graphics, which replaced the original Radeon 7500 AGP graphics). Another is a similar P4 with 512 MB of RAM and Radeon 7500 AGP graphics. Both run Vista Ultimate (x86) today.

My own current daily beater is another P4 (albeit a Northwood-C) with 2 GB of RAM and the Aero-capable Radeon x1650 Pro AGP; it dual-boots Vista Ultimate (with SP1) and Windows 7 Ultimate (6956).

The problem isn't whether or not there are capable AGP graphics cards for Vista (or even 7); there certainly are (starting with AMD's HD2xxx series, which supports DX 10, and the HD3xxx series, which supports DX 10.1). In fact, there's versions of the HD2400 Pro in PCI (not PCIe, but plain old PCI).

Proof: http://www.newegg.com/Product/ProductList....42&name=PCI

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
      594
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      74
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!