Recommended Posts

I think you should just go ahead and install the 64-bit version. That way you can see for yourself what it's like and how it runs on your system. You're going to be reinstalling in a few months anyway, so there's nothing to lose. It's true that the 64-bit version uses more RAM, but it's not a lot, and the marginal (for most things) performance improvement might make up for it. You'll have to be the judge of that.

Go 64-bit *now*, despite having but 2 GB of RAM. I've run not only 7 (and Vista) Ultimate on *half* that, I've actually run Vista Ultimate x64 on (don't faint) a *quarter* of that. On a single-core Celeron. (That is a mere 512 MB of RAM.)

Performance (in terms of increased speed) wasn't the point. Increased stability, however, was.

Datapoint: Given equal driver support, in no case have I found Vista 64-bit lacking (or, most importantly, lagging) compared to Vista 32-bit under identical application loads. With particularly troublesome 32-bit applications (especially games), the WOW64 thunk layer (included with every 64-bit version of Windows) provides a welcome additional layer of insulation.

The *only* problem I have had (both in terms of home users I've helped migrate, and my own migration) is entirely due to the lack of plug-ins for 64-bit Web browsers. For most home users, more often than not, your applications AND your games will thank you for the additional infrastructure of a 64-bit operating system underneath. I run Windows Vista Ultimate 64-bit on a *daily* basis with but a single gigabyte of RAM; yet it is more stable (not less) than the P4 Northwood-C (with twice the RAM and Vista Ultimate 32-bit) that I upgraded from; and I had no real complaints with Vista Ultimate in 32-bit form. I actually am *harder*, not easier, on Vista 64-bit, despite the RAM deficit. I run hungrier applications, and more of them at once.

The very fact that I've increased the application load, despite decreasing the system memory, should speak quite plainly about just how solid Vista 64-bit is.

If your applications will work (and, except in very limited circumstances, there is absolutely little reason why any home user other than a telecommuter should have many, if any, issues) if you have a supported 64-bit-ready CPU and as little as 512 MB of RAM, and the driver support is there, I would go 64-bit right now (either XP64 or Vista 64), and don't wait for Windows 7 64-bit. And that is even true if your processor has but a single-core.

What's the point of having a 64bit os when all applications are still 32bit?

Stability, in my case.

Consider that one of the largest areas of griping other than Windows as an operating system in general (or hardware support for it) is buggy code in games. Given that, wouldn't you want to reduce the amount of crash possibilities due to crappy game coding and development?

Enter WOW (Windows on Windows), the thunk layer for all 32-bit applications (including games) on 64-bit Windows. Any 32-bit application running on WOW is not just isolated from the operating system, they are also isolated from other applications, whether they are on the thunk layer or not. Yes; there is minor additionall overhead incurred; however, in most cases, it's not noticeable to either the user or the application (or even the game); unless the application or game crashes. The application or game will crash; however, the rest of the session (and every other application in the session) will keep right on running, unaffected. I don't know about the rest of you; for me, that's the sort of stability that is worth serious money.

While speed is okay, stability (to me) is far more important.

That probably won't come until there are more native X64 web browsers. At the moment all we have is the 64 bit version of IE which doesn't really get used too often, and some really bad X64 firefox compiles.

Weak. Microsoft should set an example and release as much software as possible in 64-bit. With something as new as Silverlight, there's just no excuse.

Consider that one of the largest areas of griping other than Windows as an operating system in general (or hardware support for it) is buggy code in games. Given that, wouldn't you want to reduce the amount of crash possibilities due to crappy game coding and development?

Enter WOW (Windows on Windows), the thunk layer for all 32-bit applications (including games) on 64-bit Windows.

A WOW process has the same access to the graphics card as a 64-bit process, and is perfectly free to run code on the GPU that crashes it.

Any 32-bit application running on WOW is not just isolated from the operating system, they are also isolated from other applications, whether they are on the thunk layer or not.

32-bit processes are free to do anything they want to each other (and to a certain extent also 64-bit applications). WOW is designed for maximum compatibility, not to be a sandbox environment.

Yes; there is minor additionall overhead incurred; however, in most cases, it's not noticeable to either the user or the application (or even the game); unless the application or game crashes. The application or game will crash; however, the rest of the session (and every other application in the session) will keep right on running, unaffected. I don't know about the rest of you; for me, that's the sort of stability that is worth serious money.

Much like they would in the 32-bit version.

i just upgraded my PC and added another 2 Gigs of RAM so now i have 4GB and 64 bit works great.

Just out of curiosity would Windows 7 32 bit use all my 4GB of RAM or only 3GB of RAM. Someone wrote that 32bit can use up to 3GB or maybe that was for XP only. Im not sure.

Weak. Microsoft should set an example and release as much software as possible in 64-bit. With something as new as Silverlight, there's just no excuse.

Exactly. They claim it's all that great, but with it being 32-bit only, it's just as backwards as Flash :x

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

    • No registered users viewing this page.
  • Posts

    • Nothing is stopping you from continuing with your testing cadence. If updates are released every 2 weeks instead of 4, and you test once every 4 weeks, the exact same amount of patches will still be available for you in those 4 weeks. For example: Before 4th week - patch 1, 2, 3, 4 After 2nd week - patch 1 and 2 4th week - patch 3 and 4 Still the same amount after 4.
    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!