Recommended Posts

Windows 8 won't support 128bit processors since there's no reason to make them in the next few decades.

It's taken us 50 years to use 4GB of RAM, we won't jump to 16.8 million terabytes of RAM in 3 years.

Maybe not, but you can bet that Microsoft will add support for the processors in Windows 8.

Seeing as most people don't even use 16GB or more of memory in a 64-bit system yet, they still have 64-bit support.

Yes I do know the Turn Windows Features On or Off Dialog, however, AMD is working on 128-bit processors (Microsoft's 128-bit indiscretion) and Windows 8 and/or 9 is supposed to support that architecture. So, by windows 10 we won't need a 32-bit compatibility layer anyway, so why include one.

alright,

on the note .

FYI 16bit is not included in 64bit windows because of hardware limitation not software

Thats just it, it's a prediction, just like all the other posts on here.

Fact is, we just don't know anything about Windows 8, apart from the release date being three years away!!!!!!

Actually 128-bit processors could be here as soon as 2011, especially if AMD's Bulldozer and Intel's Haswell Architecture turns out to be 128-bit.

Hasewell are projected at earliest 2012,last i checked

128bit would be rather useful for high-ended Servers/Supercomputers

but not to much beside that atm.

hecks, Microsoft has just only recently dropped 32bit server release (WS 2008R2)

...

Hasewell are projected at earliest 2012,last i checked

128bit would be rather useful for high-ended Servers/Supercomputers

but not to much beside that atm.

hecks, Microsoft has just only recently dropped 32bit server release (WS 2008R2)

In 20 years they might be useful for supercomputers, but at the moment nobody in the world is anywhere near the limit.

We're talking about somebody using up 13,107,200,000 GB of RAM, that is very unlikely.

Edit: Whoops, got the number wrong, it's actually 17,203,200,000 GB of RAM.

Hasewell are projected at earliest 2012,last i checked

128bit would be rather useful for high-ended Servers/Supercomputers

but not to much beside that atm.

hecks, Microsoft has just only recently dropped 32bit server release (WS 2008R2)

Usually when they drop something from a server release, the client version follows, hence the reason why I think that windows 8 will be distributed as 64-bit only.

Edited by neo158

Why do people only think about memory address space when talking about 64bit and 128bit? Being able to use more ram isn't the only advantage to have the ability to crunch through larget ammounts of data per cycle. You do understand that a true 128bit CPU running any type of HPC app would crush any 64bit CPU?

Performance isn't just about how much RAM you can access. 128bit CPU's would be a vast improvment over what IT uses today in it's massive datacenters and mainframes. Reducing the need for insane ammounts of CPU's and blade servers, cutting back on power usage and overall costs.

Saying we don't need 128bit because we'll never have the need to use more ram than what we can get with 64bit for the next 20+ years is missing the whole point.

Why do you think there's this big push to using GPGPU mroe for things other than games?

So I know what the whole 128bit CPU thing is about, it's about register length for some instructions.

SSE and such already use 128bit registers and operations, so you can add or multiply 2 64bit floats (4 32bit floats, etc.) in one go, these future registers are 256bits, allowing for storage of 2 128bit integers or floats in a single register.

So the CPU will still be 64bit, but it can operate internally on 256bit registers containing 2 128bit values (same kinda way a 32/64bit CPU can operate on an 128bit register containing 2 64bit values). And apparently there are plans for future 512bit and 1024bit registers (512bit allows for 4 128bit floats, etc.)

So I know what the whole 128bit CPU thing is about, it's about register length for some instructions.

SSE and such already use 128bit registers and operations, so you can add or multiply 2 64bit floats (4 32bit floats, etc.) in one go, these future registers are 256bits, allowing for storage of 2 128bit integers or floats in a single register.

So the CPU will still be 64bit, but it can operate internally on 256bit registers containing 2 128bit values (same kinda way a 32/64bit CPU can operate on an 128bit register containing 2 64bit values). And apparently there are plans for future 512bit and 1024bit registers (512bit allows for 4 128bit floats, etc.)

that kind of huge :huh:

So I know what the whole 128bit CPU thing is about, it's about register length for some instructions.

SSE and such already use 128bit registers and operations, so you can add or multiply 2 64bit floats (4 32bit floats, etc.) in one go, these future registers are 256bits, allowing for storage of 2 128bit integers or floats in a single register.

So the CPU will still be 64bit, but it can operate internally on 256bit registers containing 2 128bit values (same kinda way a 32/64bit CPU can operate on an 128bit register containing 2 64bit values). And apparently there are plans for future 512bit and 1024bit registers (512bit allows for 4 128bit floats, etc.)

Exactly, it's all about running apps faster not about being able to use xGB of ram.

that kind of huge :huh:

It's a wide data type, but due to how it's used it's not really that big (a 128bit data type can store 4 32bit integers (say, for a 2x2 matrix), 2D drawing engines use 3x3 matrixes)

Exactly, it's all about running apps faster not about being able to use xGB of ram.

Well sure, but the CPU will still be 64bit. We don't call old Pentium's 128Bit CPU's since they have a 128Bit data type.

FYI 16bit is not included in 64bit windows because of hardware limitation not software

AMD64 processors can run 16-bit code. The reason it isn't supported in 64-bit Windows is because there is so little demand that adding support for it costs Microsoft more than they get back. Simple business decision.

AMD64 processors can run 16-bit code. The reason it isn't supported in 64-bit Windows is because there is so little demand that adding support for it costs Microsoft more than they get back. Simple business decision.

How does adding support for something they've owned for decades cost them anything? It's a simple subsystem, I can see it being removed for security or better stability but cost? Nah.

How does adding support for something they've owned for decades cost them anything? It's a simple subsystem, I can see it being removed for security or better stability but cost? Nah.

I don't think you fully understand the amount of Q&A and bugtesting that needs to go into every piece of code of a operating system especially one as widely used as Widnows where the economy of one of the worlds largest companies rely on that product. even if it's old ancient code known to be stable. and it still needs to be modified to fit inside the new OS and interpreters and the systems to support the sub system needs to be built. which requires more code work and even more bug testign and Q&A for something that there's absolutely ZERO demand or need for.

Just because something is relatively cheap compared to stuff like a new graphics system, new audio system, new shell/task bar and any number of big visible changes in vista and 7, doesn't mean that they don't cut it for the costs.

If they where to keep everythign that was relatively minor and relatively cheap, windows would be REALLy bloated, especially in code.

How does adding support for something they've owned for decades cost them anything? It's a simple subsystem, I can see it being removed for security or better stability but cost? Nah.

Because it has to be modified to work on the new platform. You can't just drop the old files in and have it work. Also, it's not a "simple" piece of code (and not a subsystem, Windows only has half a subsystem). It wasn't removed, it was never added.

  • 4 months later...

Is there any fresh news about Win 8 yet? Some leaked screenshots, or something? It's too quiet, that's a little unusual for a Microsoft product. whistle.gif

Was exactly the same thing with Windows 7. No official screens from MS before PDC, even though builds leaked months earlier. We've already seen some alleged post-RTM builds but they're visually identical to 7.

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

    • No registered users viewing this page.
  • Posts

    • 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
    • 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'.
  • 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
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!