Recommended Posts

32bit support won't be removed for a long long time, like a decade or more.

I think we will start to see Microsoft depreciate the 32-bit version of windows, starting with windows 8.

By this I mean that there probably will be a 32-bit version but they will only ship the 64-bit version, and considering the uptake of the 64-bit version of Windows 7 I think that's a fair bet.

I also think that windows 9 won't have a 32-bit version available, and that windows 10 will see the removal of WoW64 and any related 32-bit code.

I think we will start to see Microsoft depreciate the 32-bit version of windows, starting with windows 8.

By this I mean that there probably will be a 32-bit version but they will only ship the 64-bit version, and considering the uptake of the 64-bit version of Windows 7 I think that's a fair bet.

I also think that windows 9 won't have a 32-bit version available and that windows 10 will see the removal of WoW64.

guesstimating win10 it would be around 2019/20

why bother remove wow64? with increasing size of hdd ,they could instead make it optional subsystem that you can remove from control panel if you don't went it

guesstimating win10 it would be around 2019/20

why bother remove wow64? with increasing size of hdd ,they could instead make it optional subsystem that you can remove from control panel if you don't went it

But by then who is going to be using 32-bit programs anyway?

the whole UI needs to be redone on top of a better file system.

What file system would you like to see?

Don't say WinFS because that was just a relational database on top of NTFS.

On that subject there is nothing wrong with it.

But by then who is going to be using 32-bit programs anyway?

I have a customer who still uses a 16bit accounting package that runs in DOS. They have no intention of changing it as it does exactly what they need. Who know's but they still might be using it in 2020 :)

But by then who is going to be using 32-bit programs anyway?

i mean what harm would it be if they just make it removable component instead of tear it off altogether?

remember this?

post-254628-1259803042.png

i renamber it was project it after ten year we would have as big storage drive as 12TB !! or something of that sort

I have a customer who still uses a 16bit accounting package that runs in DOS. They have no intention of changing it as it does exactly what they need. Who know's but they still might be using it in 2020 :)

16bit won't run in 64bit windows,so that is irrelevant anyway

i mean what harm would it be if they just make it removable component instead of tear it off altogether?

remember this?

post-254628-1259803042.png

i renamber it was project it after ten year we would have as big storage drive as 12TB !! or something of that sort

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.

Edited by neo158
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.

We could be running on 256bit processors, that won't change the fact that we have 20 years of 32bit programs.

And on 128Bit CPU's, we'd have a "Windows64 on Windows128" layer just to run 64Bit apps.

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

Windows 8 is scheduled for release in three years and will support an architecture that doesn't exist yet? Get real.

Really? Windows 8 MAY be based on Windows 7 and its refactored core (MinWin=refactoring work being done)? Are you saying there's a chance they could base it on Windows 3.11 instead?

How should they start building Windows 8?

Should they build off of previous OS releases and their code, or should they start from ABSOLUTE scratch and build everything from the registery to the calculator from nothing?

I can see benifiets on both sides, where you can cut time and resoucres starting on top of other OS's, or start fresh and build the bare nessities. I can only imagine they have improved their code writing and how they organize stuff.

Starting from scratch is pretty much impossible if you want to release it in less than 5 years.

I haven't laughed this much in a long time.

Windows 8 is scheduled for release in three years and will support an architecture that doesn't exist yet? Get real.

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.

I think they should work on refining the NTFS for SSD's, or just make another file system with the same idea as NTFS but obviously designed just for SSD's.

MS already made changes in Win7 to support SSDs better. Windows 7 makes use of the TRIM command on supported SSDs. This optimises when erase cycles are performed, thereby reducing the need to erase blocks before each write and increasing write performance. However, as of November 2009, hardware support for this command is limited with many drives requiring new firmware or not supporting TRIM at all.

If anything, SSD's have to better support the changes MS made to the file system first.

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.

They won't be though, there's no reason to jump to an 128bit address space when current hardware doesn't even use the full 64bit address space (most CPU's only use 46bits or something)

There's no reason to go to 128bits for a very long time.

They won't be though, there's no reason to jump to an 128bit address space when current hardware doesn't even use the full 64bit address space (most CPU's only use 46bits or something)

There's no reason to go to 128bits for a very long time.

Microsoft haven't stated anything about Windows 8 apart from a launch window of 2012, so you can't say that they won't support 128-bit, honestly, no one knows for sure what windows 8 will support.

Microsoft haven't stated anything about Windows 8 apart from a launch window of 2012, so you can't say that they won't support 128-bit, honestly, no one knows for sure what windows 8 will support.
128-bit processors could become prevalent when 16 exbibytes of addressable memory is no longer enough (128-bit processors would allow memory addressing for 340,282,366,920,938,463,463,374,607,431,768,211,456 bytes (~340.3 undecillion bytes or 281,474,976,710,656 yobibytes ). However, physical limits make such large amounts of memory currently impossible, given that amount greatly exceeds the total data stored on Earth.

http://en.wikipedia.org/wiki/128-bit

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!