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

    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • OK, now ask yourself how are they going to enforce that law? By requiring every single adult to prove their age and provide their legal identity documents to an UNREGULATED 3rd party company that already has a long track record of multiple data breaches. Not to mention, parliament have voted AGAINST this ban, twice, and Starmer is going ahead anyway. So, where's the democracy here, because that looks like dictatorship to me. The solution here is parental responsibility, not government control. Run some public service announcements on TV and UK social media teaching parents how to setup parental controls. That's already been proven to actually work. But the, this is not and has NEVER been about keeping kids safe. It's about control and monitoring. Watching what you're doing online and controlling what you can see and what you can say.
    • Interesting read. I knew the adware was quite controversial at the time, however never realised to the point The Guardian wrote an article about Patchou. I just said no and enjoyed his creation, I’d probably be a lot more wary of something like that today though.
  • Recent Achievements

    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
    • Collaborator
      vjlex earned a badge
      Collaborator
    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      525
    2. 2
      +Edouard
      180
    3. 3
      PsYcHoKiLLa
      105
    4. 4
      Steven P.
      89
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!