Recommended Posts

Well I just wanted to say is I have decided to rid myself of x86 Ultimate. I am now running Ultimate x64 Window 7. I can say it was the right choice to make, after being on 32 bit since XP(2002 ver.). I would rather the system use all my ram instead of half. Which the first thing I put on here was Waterfox and I think it's better then Firefox. Also, things seem to run smoother then before. So now I am officially 100% through with 32 bit operating systems. Right now I only have 2GB but will be upping it to 4.

To the hundreds of posters and thread makers alway's raising the topic of sending x86 into exile, I will agree all the way. 64 is the future and it's pure fact...maybe, lol

  • Like 3
Link to comment
https://www.neowin.net/forum/topic/1117073-goodbye-x86-hello-x64/
Share on other sites

Welcome to x64 land, i mad the jump with Vista in 2006 and never looked back!

Apart from been able to use all your ram you will probably not really notice much difference, although at the time the Dolphin emulator (GameCube / Wii) worked so much better on x64 Windows than x86.

Ever since I switched to x64 windows I have had no problems with software compatibility. So I wonder why people are still stuck on 32-bit, 64-bit works flawlessly. Am I missing something?

Windows 7/8 hasn't been too bad for 64bit drivers. However, when 64bit XP came out, or even 64bit Vista, drivers were next to non-existent and the ones that were there for hardware were very poor. Not only that, but 64bit drivers used to have to be signed as well. It made simple things such as some DVD burners incompatible between 32bit and 64bit systems.

Well I just wanted to say is I have decided to rid myself of x86 Ultimate. I am now running Ultimate x64 Window 7. I can say it was the right choice to make, after being on 32 bit since XP(2002 ver.). I would rather the system use all my ram instead of half. Which the first thing I put on here was Waterfox and I think it's better then Firefox. Also, things seem to run smoother then before. So now I am officially 100% through with 32 bit operating systems. Right now I only have 2GB but will be upping it to 4.

To the hundreds of posters and thread makers alway's raising the topic of sending x86 into exile, I will agree all the way. 64 is the future and it's pure fact...maybe, lol

Welcome to the Land of X64, TCA.

To be honest, x32 (regardless of operating system - it's far from unique to Windows) hangs on for two reasons - inertia of users and inertia of developers.

I was where you are RAM-wise when I crossgraded to x64 with Vista - 2 GB; however, that is simply an excuse, as I have crossgraded folks with less (Mom had 1 GB, and some had a mere 512MB of RAM).

Gettiing past the inertia and FUD is the hard part.

The problem is many developers still won't make 64bit until Microsoft ditches 32bit Windows. >.<

So long as an application has no need to access more than 2 GB of memory (assuming defaults), having a 64-bit binary isn't an absolute necessity. Though one valid reason to require 64-bit binaries is if it's an Explorer extension and of course drivers. Your browser or PDF reader doesn't need to be 64-bit especially if it's portable.

The OS being 32-bit or 64-bit is a different case. People don't realize the loss of user-accessible memory if they complement a standard system with 4 GB of RAM (which perhaps they heard from others is the upper limit) with a discrete graphics card whose VRAM cuts into that limit.

I suppose, though feel free to correct me wrong, any speed differences if noticed is down to the reduced need of throwing away data in memory to meet limits in a 32-bit environment, plus a boost to computational-related tasks due to the number of CPU registers - those aren't a night and day difference though in most everyday applications.

  • Like 1

The problem is many developers still won't make 64bit until Microsoft ditches 32bit Windows. >.<

EA said a 64 bit only title is in the works. I believe Stardock said they're planning to make 64 bit only DLC. Many devs are recommending 64 bit OSes instead of just newer OSes.

It doesn't seem like 32 bit has too much longer to live in gaming.

Been x64 for a long time on my Desktop, Laptop is currently 32bit and only has 2GB RAM but occasionally gets a 64bit install, depends which ISO is either already on a USB stick or easiest to find, makes no difference with the Laptops performance if I'm honest

EA said a 64 bit only title is in the works. I believe Stardock said they're planning to make 64 bit only DLC. Many devs are recommending 64 bit OSes instead of just newer OSes.

It doesn't seem like 32 bit has too much longer to live in gaming.

I could believe that, I felt 32 wasn'tinadequate for what I like to do. Which also, I think x86 is better suited for just casual browsing, gaming(windows pre-installed) etc. But for those that like us that are power users especially when it comes to playing higher level games 64 is the only true way to actually use your system how it should be. (bad analogy?)

I would like to move back to W8 because I am kinda missing it, go figure eh? But I am not sure how well Sims 3 would take to it....especially, now that Seasons will be out the 13th or 14th and the latest patch for it was issued days ago.

Sims 3 works fine in 8. It'll reset your display settings the first time you run it, but I haven't had any problems past that (in the preview releases the settings were hosed every time I launched unless I ran it in 7 compatibility mode.)

x86 isn't really better suited for anything but old games.

Sims 3 works fine in 8. It'll reset your display settings the first time you run it, but I haven't had any problems past that (in the preview releases the settings were hosed every time I launched unless I ran it in 7 compatibility mode.)

x86 isn't really better suited for anything but old games.

Ah okay I may have to go to W8. But I will give it another month before I truly decide. I had to re-install them all except pets...can't play it(deformed pets) so I sold it to my friend, When I get a dedicated GFX, I'll just buy it from Origin

I would switch to x86-64 (not x64) bar one thing ... AlfaClock doesn't work on x86-64 - it's 32bit only.

It doesn't even work if you changed it to backward compatibility?

Well I just wanted to say is I have decided to rid myself of x86 Ultimate. I am now running Ultimate x64 Window 7. I can say it was the right choice to make, after being on 32 bit since XP(2002 ver.). I would rather the system use all my ram instead of half. Which the first thing I put on here was Waterfox and I think it's better then Firefox. Also, things seem to run smoother then before. So now I am officially 100% through with 32 bit operating systems. Right now I only have 2GB but will be upping it to 4.

To the hundreds of posters and thread makers alway's raising the topic of sending x86 into exile, I will agree all the way. 64 is the future and it's pure fact...maybe, lol

"XP(2002 ver.)"

Windows XP came out in October 2001. There is no "2002 version".

Welcome to two or three years ago :D hehe ... Seriously tho, there's no massive obvious reason for most people to do it because systems are still being marketed with only 3 or 4 gb Ram and half the time that's shared with video. So most of those people wont notice the difference, but you made the right choice for future proofing and Ram increases :)

  • Like 1

Welcome to two or three years ago :D hehe ... Seriously tho, there's no massive obvious reason for most people to do it because systems are still being marketed with only 3 or 4 gb Ram and half the time that's shared with video. So most of those people wont notice the difference, but you made the right choice for future proofing and Ram increases :)

Most systems now, even budget laptops, come with 4 GB RAM.

Luckily, all currently sold systems/laptops that are currently sold come with x64 and not x32.

This topic is now closed to further replies.
  • Posts

    • 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
    • Too soon, I'm still not over this death!
  • 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
      593
    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!