Hard drive evolution could hit XP


Recommended Posts

^ They don't have to but you see, companies are driven by profit. And if they don't make stuff compatible with the operating system that is used by 50% of the market, they are killing off a lot of customers therefore losing profit. It only makes sense to.

^ They don't have to but you see, companies are driven by profit. And if they don't make stuff compatible with the operating system that is used by 50% of the market, they are killing off a lot of customers therefore losing profit.

I can understand that, and I know its not going to change anytime soon. But it is still those people that are holding back technological advancements.

Take 64bit for example. It provides huge amounts of benefit over 32 bit, performance and security being the major ones. But companies are reluctant to code 64bit apps because of the people who are still on 32bit. So instead of us moving forward and embracing new technologies, we keep having to return to the past. And as a result, we and the rest of the tech world is held back.

hmm maybe im confusing this with a file system, but isnt NTFS already 4096 bytes per sector by default?

from the anandtech article

"NTFS, EXT3, and HFS+ all default to 4KB clusters on modern hard drives. So 4KB physical sectors map perfectly with 4KB file system clusters, which in turn map perfectly with 4KB memory pages. And hence 4KB is the largest practical size for a hard drive sector at this time."

The 64-bit app debate is different. They aren't coding for it because of the 32-bit users.

However, this debate we're having is about a new hard drive being back-compatible. I don't see the issue with this, as it's still new technology for new computers that also work on older ones.

also... the performance problems that comes from 512 byte writes being emulated in a 4k block, couldnt that be solved with clever firmware in the hard disk like what they do on SSD's , as well as modified file defragmentation which takes the 4k blocks into account?

I can understand that, and I know its not going to change anytime soon. But it is still those people that are holding back technological advancements.

Take 64bit for example. It provides huge amounts of benefit over 32 bit, performance and security being the major ones. But companies are reluctant to code 64bit apps because of the people who are still on 32bit. So instead of us moving forward and embracing new technologies, we keep having to return to the past. And as a result, we and the rest of the tech world is held back.

That's why Microsoft will need to only make a 64bit release soon. To force the change.

When the time comes that the cost of making a 32-bit version outweighs the profit it's bringing in, they'll stop making it.

As long as you're viewing "profit" and "cost" as deeper variables than immediate numbers on the balance sheets, yeah. (i.e. why would anyone ever develop anything new if it was solely about current profit and cost?)

Most of the questions being in the thread are already answered in the topic. It won't be that the drives won't work on XP, but they won't work as well. There's only so much you can do with emulation and drivers.

That's why Microsoft will need to only make a 64bit release soon. To force the change.

It's sad but many users have older computers and yet they expect new hardware and new operating systems to work just fine on their old junk. At some point in time it's time to move on to newer stuff.

jumping on the offtopic bandwagon myself...

but isnt microsoft beginning the split of current gen hardware with 'classic' hardware, with their mobile OS strategy? as in windows phone 7 , and windows phone classic...

so if this was brought over to the desktops, all the outdated computers will still run a new OS, but it will be stripped down and pretty miserable compared to the '64 bit' OS that has all the latest features and all that...

Hard drives are in dire need of an update, the technology is as dated sounding as Floppy Disk. :p

Some of the technology used in a hard drive is pretty damned modern. The nobel prize in physics was only just awarded for giant magnetoresistance a couple years ago, which is a relatively cool quantum effect which modern drives use in their heads.

We'd go a lot further with innovation if we would stop hand-holding the decade-impaired people who refuse to adopt change. With PC prices the lowest they've been in ages, there's no excuse anymore. If your business is important enough to depend on computers, then you're doing yourselves--and your customers--a disservice by sticking to obsolete software, because it's dangerous and counterproductive.

Dont see why MS cant/wont release a patch for that tbh :p

Because they want to encourage people to ditch XP and buy a new copy of Windows 7. ;)

XP had its place, but if you are throwing good money into your old PC by buying a hard drive, maybe it is time to also invest in a modern OS (or a free one, if you really *hate* to spend money that much)

Will BSD, FreeDOS, ReactOS and Haiku be ready for this (all four are opensource OS's)?

For now, no.

After reading this article earlier last night, I began to entertain the idea of getting a WD10EARS (I've been wanting to get a backup hard drive for some time now), and came across posts with people stating that parted currently cannot align the partition correctly (there is a workaround posted).

So for now, it appears that only WinNT 6.x can initialize drive correctly and easily.

Windows XP is ancient.

It is going on NINE YEARS OLD. This is in a world where the average life cycle is around 3 years. It may have been able to last 5 or 6 years because of the time Microsoft took on Vista, but that still is no reason to keep using it for 9 years!

* The home version is 32-bit only and can't take advantage of 4 Gigs or more RAM.

It's common to find many systems with well over 8 Gigs RAM now. Valve reports almost a 3rd of its users have 4 Gigs or more of RAM.

* Windows XP does not support partitions larger than 2 TB.

Guess what? 2 TB drives have been out and are very affordable, and many NAS boxes that use RAID have well over 2 TB partitions available. "Not supported by Windows XP" is a sticker that has been made for drives already.

* Windows XP does not support 4K physical clusters and can not take advantage of newer drives without hacks.

* Windows XP is not "SSD aware" and will not take proper advantage of newer drive features and speed enhancements.

* Windows XP does not natively support SATA drives or any of the speed enhancements and features of such drives.

* Windows XP does not support security features like UAC or account elevation; something that has existed in Mac OS X and Linux for many, many years.

* Windows XP does not support 3D acceleration of the Desktop.

* Windows XP is based on some very old technology and is incredibly insecure by default.

* Windows XP is now several versions behind on DirectX, and cannot take advantage of the newest gaming technologies.

* New hardware components like 64-bit, Dual-Core+ processors, 2+ Gig RAM kits, and fast DX10+ video cards are incredibly affordable, more so than ever before.

Get it? XP IS OLD. It is out-dated. It is a relic of an OS that doesn't take advantage of any of the new technologies available.

If it doesn't support "YET ANOTHER" new technology. Who cares? It's like crying that Windows 98SE won't take advantage of it either, or that your VCR can't play a Blu-Ray Disc.

People who run ancient operating systems probably aren't the type that go out and buy new technology anyway. If you can't seem to purchase a new version of Windows, why would you purchase an SSD, 4K drive, DX11 video card, or anything else remotely "modern"?

Don't complain that you can't use some new piece of hardware, XP users seem to be stuck in some sort of time warp and become more of a joke with each passing day.

  • Like 1
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'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | 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
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!