Recommended Posts

Can some one please explain the difference to me, as i am a little confused.

i remmeber back with the 939 was released with 64bit architecture, correct?

Then didn't hear much of it, other than XP 64.

now i recently bought a laptop with vista basic, Toshiba satelite L30 Core Duo 1.73

Which platform is better and why and can my lappy take it?

Just a bit of explanation would be good

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/
Share on other sites

I tried Vista 64-bit on my laptop, you can do a lot more than simply use notepad.

Vista 64 runs most 32-bit applications. It seamlessly ran all my regular 32-bit applications, although playing games is a hit and miss affair, Battlefield 2142 didn't run, and Enemy Territory worked only without punk buster enabled.

Driver support was seriously lacking, I was able to get drivers for my sound and graphics card and printer but my web cam and a few other things had no drivers. That was 6 months ago, there are probably more drivers available now.

Also, there isn't really must performance gain to be had by running the 64 bit version, from a performance point of view 32 bit is pretty much the same.

Unless you're wanting to run more than 4GB or ram in your PC then I'd stick with the 32-bit version for now and perhaps consider 64-bit when the next version of Windows is released.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588679556
Share on other sites

On my modern hardware, I haven't had any driver or software compatibility issues. I run Office, Visual Studio, Adobe CS3, Source games, Red Orchestra, BF2, 2142 demo and loads of other stuff without any compatibility problems at all. Where there are issues, a simple Google search or trying the compatibility mode will fix it in seconds.

You can check and make sure all your software will work before you buy, but I would recommend 64-bit to get the most out of your processor and RAM.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588679632
Share on other sites

I have absolutely no issues running Vista x64 on my machine. Hardware in signature.

Latest games such as Supreme Commander, Shadowrun run superbly. The majority of older games do work fine also.

No performance issues either.

Sure, there are a few things that aren't nice to use, or don't work at all on x64, but they're few and far between. I use Vista x64 as my daily OS and am more than happy.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588679899
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

WOW, that post is SO full of utter crap its amazing.

I run Vista x64 on 3 machines and have ZERO usage problems. HAve you ever used the software because you act like you are just going off of what other idiots have read then retold you.

Hell I'm in Vista x64 as I am typing this. I found all teh x64 drivers for my machines in under 10min of looking for ANY OF THEM.

LEARN WTF YOU ARE TALKING ABOUT BEFORE YOU POST!

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588680147
Share on other sites

Hey guys, i have just finished installing 64bit vista and i have to say its very nice and a bit faster... however now my PC gets a lower score ?

Ram used to have a score of 4.3 but now in 64bit it has 3.1? how odd ?

also does anyone know if there is a 64 bit version of firefox 2.0 ?

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588681192
Share on other sites

also does anyone know if there is a 64 bit version of firefox 2.0 ?

You can get firefox-3.0a6pre.en-US.win64 (2007-06-12):

http://www.mozilla-x86-64.com/download.html

[Threads Merged]

I had no troubles running applications with Vista-64. Perhaps you might run into issues with older games or something but it did not affect me.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588681791
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

Well, I see one of the Elmer "FUD" crowd has replied. People 'IN THE KNOW' will ignore that.

64 bit Windows gives you some advantages over 32bit.

Most Windows virii are of the 32 bit variety and you should 'theoretically' have a bit more immunity from because of the nature of the code: the virus expects 32 bit addressing and even if it does manage to corrupt 64 bit files, the memory pointers and such will be off and the virus will crash... and Vista x64's 32 bit subsystem (which the virus will run under) will crash as well... maybe... instead of the whole system.

Intel and AMD processors usually run 32 bit code in x64 mode nearly as well as a 32 bit processor running it. That means that 32 bit programs run almost as well on 64 bit processors as they do on 32 bit processors. A lot of development was put in by AMD to make sure it worked that way, and Intel adopted a similar strategy.

As for drivers- I've installed 64 bit Vista on my primary home computer, after running 32 bit Vista since beta 1... and it ran XP Pro SP2 before that (for about a year). SO that gives you the idea that my hardware is about 2 years old. And 64bit Vista had drivers for my entire system.

Gigabyte (my mobo maker) doesn't list anything for Vista 32 OR 64 bit... but Microsoft nailed it down and installed drivers.

It works like a charm- every piece of software I have to run- mostly office-type stuff works fine. Even the specialty software I have to use (from Anritsu- cellular test equipment) runs fine.

I don't game on it much- I've got Tron 2.0 and some older games like Obsidian and others. But they work fine.

Maybe newer games that were in development while Vista was being worked on won't work... YET... but I have no complaints.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588681797
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

Wow. That's utter crap.

If you have the hardware, and the plans to go above 3gigs of RAM, go with 64. Otherwise, stick with 32.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588681840
Share on other sites

Lets not mix Vista driver support issues with 64-bit issues, please.

Vista driver support is coming. 64-bit driver support is coming slower, but it's coming too.

Application support is the slowest, but there really is negligible difference between 32-bit apps and 64-bit apps unless you're dealing with really high-end stuff (databases, virtual machines, etc). A 64-bit version of Firefox for example is largely pointless not to mention useless -- you'd need 64-bit plugins. Granted it would offer some protection (still, placebo), but really, there's a reason why even the 32-bit IE7 is default on Vista-64.

I've had no problems with various games, but can't answer to specific ones listed in this thread. Currently I'm working on getting MAME working, but haven't spent too much time on it.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682121
Share on other sites

I have Vista Ultimate 32-bit and 2 GB RAM, and it ran smoothly. Apps load as fast, if any faster, as XP.

Just a thought but I'm surprised that my P4 with HT is supported when the Vista reqs came out.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682139
Share on other sites

I run x64 vista on my main machine (amd x2 4200+). I can run the latest mame (actually I use the unofficial mame32 plus build; but mame32 works fine too) on it without any problems. I don't play alot of pc games. I just like playing games from yester year via emulation (I love the speed up feature of some emus; it's so great to speed through stuff like intro movie). Most of the PC games that I've tried works (Oblivion, Doom 3, GTA3:SA, Titan Quest, C&C 3, Morrowind) without having to use compatibility mode. Gothic 3 ran really slow for some reason but that game is buggy to begin with (Gawh, when will they release a patch to fix all the bugs?). I used to run x64 windows XP before vista x64. What can I say? Once you go 64-bit it's hard to go back to 32-bit. 32-bit is soooo yesterday (or make that 5 years+ old technology). :)

I did have to wait forever for VIA to release their 7.1 audio drivers for x64 vista. That was the last driver missing for me.

So, for me, x64 vista is the only way to go.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682162
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

I didn't read the rest of the thread yet, but i'm sure someone has corrected you!

I have my specs in my sig and i am running Ultimate x64 with only ONE problem....my 5.1 surround only works in Winamp with a special surround sound plug-in...everything else i have NO problems with. Every program I ran in Xp Pro runs PERFECT in vista x64. So basically your comment is useless and worthless....

Maybe it might hold some truth if your hardware is outdated as all hell!

Do a little research before you post that comment. If you tried it and it didn't work for you then say "i personally have tried it and my experience wasn't that great"....because i'm running it as my main OS now without dual booting anything else....no problems what so ever....there are a couple little glitches but there has been a work around for EVERY single one of them that takes a minute TOPS to complete.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682273
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

You're prolly thinking of XP64 there. Vista x64 is just as usuable as x32 is, even when dealing with games. I've seen two of my mates running that OS without a glitch so far, even playing the latest games, which has prompted me to consider it now as I've got 4GB.

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682306
Share on other sites

XP is better.

Vista 32 if you want a somewhat usable OS.. Vista 64 if you only want to be able to use notepad, and possibly MSpaint.

Theres little driver support for vista to begin with, and no one is writing decent 64-bit compatible drivers...

Not my experience at all. Vista 64-bit works just fine..... on 3 different computers of mine!

Link to comment
https://www.neowin.net/forum/topic/572046-vista-32-vs-64/#findComment-588682343
Share on other sites

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

    • No registered users viewing this page.
  • Posts

    • it would've been better to just have a screenshot with claude running instead of using a generic thumbnail that doesn't fit the narrative.
    • Helium Browser 0.13.2.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.2.1 changelog: 6b6fbd0f revision: bump to 2 (#1907) cb3f77bd helium/ui/zen: fix cmd+s shortcut sidebar preference in zen mode (#1849) e3980159 deps: bump onboarding (#1905) c99531d5 helium/core: add an option to copy URLs from tab context menu (#1904) c1aba0ea helium/search: add kagi image search params (#1899) eb6711f4 helium/core/hibernate: add an option to hibernate other tabs (#1901) 425306f5 merge: update to chromium 149.0.7827.102 (#1897) ae94c3c8 helium/core/update-pref: improve auto updates strings (#1896) 06897c1d patches & domain_substitution: refresh for chromium 149.0.7827.102 d09826d0 merge: update ungoogled-chromium to 149.0.7827.102 9aeb58da helium/search-engine: reject default engine urls without %s (#1893) 4d7bb965 Update to Chromium 149.0.7827.102 fa67665c i18n: fix "add shortcut" string collision (#1891) 6894bd30 devutils/i18n: parse meaning into source.gen.json dc3fe739 helium/kb-shortcuts: disambiguate "Add shortcut" string cbf38eb4 i18n/apply: pass meaning to fingerprint generator 53ea9920 extra/disable-jit-flag: build drumbrake only if supported Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • ExplorerPatcher 26100.8457.70.2 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.2 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Fixed Windows 10 taskbar and Start menu crashes on builds 26220.8474 (Beta) and 26300.8493 (Experimental). Update ExplorerPatcher as soon as possible. Without this update, Explorer and the Windows 10 Start menu may stop working on future builds. Microsoft removed Windows 10 Start menu components from StartTileData.dll on these builds, so the Windows 10 Start menu option has been removed where it is no longer supported. Temporary workaround: replace C:\Windows\System32\StartTileData.dll with the version from build 26xxx.8457 (x64/ARM64). This may stop working in future builds. Work is ongoing to restore Windows 10 Start menu support. Highlights Fixed Windows 10 battery flyout crashes on build 25951+. Network flyout buttons reverted to pre-24H2 behavior as a side effect. Taskbar location changes now apply instantly. Windows 11 taskbar auto-hide is no longer modified when Explorer starts. "Open Start in All apps by default" is now hidden when using the new Windows 11 Start menu. Fixed Windows 10 Start menu crashes on builds 21996–22000.51. Fixed Regedit crashes when switching to thumbnail view in registry import/export dialogs. Improved compatibility with recent Windows builds, including 26H1 ARM64. Improved ARM64 performance. Added Greek translations. ep_taskbar Now supports all 43 Windows 11 languages. Fixed issues in the system tray and other components. Updated DLL naming scheme for mod developers. Improved TrayUI compatibility and vtable stability on builds with multiple ITrayUI revisions. Fixed a taskbar initialization deadlock. Windows 10 Start Menu Added a new tile layout engine to restore support removed in build 26xxx.8474. Restoration is currently partial: Tiles may overlap when pinned using "Pin to Start". Restarting StartMenuExperienceHost.exe or explorer.exe fixes the layout. Further improvements are planned. Other Changes Added an executable blacklist to prevent shell extensions from loading in selected applications. Updated Windows 10 Start menu animation support for ARM64 builds 28xxx.2149+. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.2 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft: Windows 11 KB5094126, KB5093998 finally stops trusting a critical system threat by Sayan Sen This week Microsoft released the Patch Tuesday updates for June 2026 with KB5094126 on Windows 11 25H2, 24H2, and KB5093998 on Windows 11 23H2. On Windows 10 22H2 it's under KB5094127. Alongside the announced release notes for the new builds, Microsoft has revealed another change that is coming to Windows with these new releases. It has been confirmed that custom folders are getting a significant change with the June 2026 updates as such folders or folder names defined by desktop.ini will no longer appear after this update is successfully installed. While you may inititally think this is a bug with the new release, Microsoft has stated that this is in fact "expected behaviour" in its new support article regarding this which Neowin spotted today while browsing. Essentially it's a security hardening measure such that custom folder presentations are treated as potentially unsafe whenever Windows is not sure about their origin and whether that desktop.ini folder can be trusted or not. Here is list of such untrusted files and folders: Files downloaded from the internet that carry Mark-of-the-Web (MOTW). Files copied from certain remote locations, such as some WebDAV or HTTP-based locations. Files on network paths that are not classified as intranet or trusted by zone policy. For those who may not be familiar, Desktop.ini is a special configuration file used by Windows to customize the appearance and behavior of individual folders. Basically Windows can read specific instructions stored in Desktop.ini instead of displaying every folder with the same default settings. This can be used to apply custom icons, thumbnail images, localized folder names, and such informational tooltips (infotip). The file can also influence certain folder-specific behaviors and properties. It is typically stored as a hidden system file within a folder that has been designated to support Desktop.ini customization. However, because Windows Shell automatically reads and applies these attributes whenever a customized folder is opened, they have historically (since the Windows XP days) presented an attack surface as a result of an unchecked buffer in the Shell component responsible for extracting custom attributes from Desktop.ini files. As such an attacker could create a specially crafted Desktop.ini containing a malicious or corrupted attributes and place it on a network share. So if a user were to browse that folder, Windows would automatically process the file, potentially triggering a buffer overflow. This could allow arbitrary code to run with the same permissions as the logged-in user. Hence a seemingly harmless folder could become a security risk when their contents are not properly validated. For admins and users alike looking to manage this behaviour, Microsoft has shared a few ways. One of them is to assign a trusted mark on the folder in case you are sure of its source. Secondly a policy can be used to revert back to the previous state. Finally, the MOTW can be removed too to indicate to Windows that this is a safe file. The company explains: Option 1: Add the source to Trusted Sites (Recommended) If the affected content is stored on a known internal or managed source, add that source to the Trusted Sites list. Once the source is treated as trusted, Windows processes desktop.ini from that source normally. This keeps the protection in place for other locations and is the lower-risk option. Option 2: Use policy to restore previous behavior Organizations that need broader compatibility can enable the policy Allow the use of remote paths in file shortcut icons.Enabling this policy restores the pre-June 2026 behavior for affected remote or untrusted scenarios. Option 3: Check for and remove the Mark of the Web (MotW) If the desktop.ini file has a Mark of the Web (MotW), Windows may treat it as coming from an untrusted source and block customization. Verify whether MotW is present and, if appropriate, remove it from the desktop.ini file. This can restore expected behavior, but should only be done for trusted content, as it removes the associated security protection. To remove the MotW tag, open PowerShell and run one of the following commands: For a single desktop.ini file: Unblock-File "C:\Your\Folder\Path\desktop.ini" For all desktop.ini files in a folder: Get-ChildItem "C:\Your\Folder\Path" -Recurse -Filter desktop.ini -Force | Unblock-File Microsoft has warned though against using a broad opt-out using the provided policy as it reduces protection against potentially malicious remote folder-customization content. As such the tech giant recommends trusting only controlled internal sources and keeping trust settings as strict as possible. You can check out the official support article here on Microsoft's website.
    • LAV Filters 0.82.0 by Razvan Serea LAVFSplitter is a multi-format media splitter that uses libavformat (the demuxing library from ffmpeg) to demux all sorts of media files. LAV Splitter is a Souce Filter/Splitter required to demux the files into their separate elementary streams. LAV Audio and Video Decoder are powerful decoders with a focus on quality and performance, without any compromises. Supported Formats: MKV/WebM, AVI, MP4/MOV, MPEG-TS/PS (including basic EVO support), FLV, OGG, and many more that are supported by ffmpeg! LAV Filters are based on ffmpeg and libbluray and is aimed to offer a all-around solution to perfect playback of file-based Media as well as Blu-rays. LAV Filters 0.82.0 changelog: LAV Splitter NEW: Support for demuxing Dolby Vision Enhancement Layer streams NEW: Support for Animated WebP images Changed: When demuxing Blu-ray discs, Dolby Vision metadata is available on the primary video stream LAV Video NEW: Support for Animated WebP images Changed: Hardware decoding support for DVDs has been removed Download: LAV Filters 0.82.0 | 15.5 MB (Open Source) View: LAV Filters Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      PsYcHoKiLLa
      207
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      79
  • Tell a friend

    Love Neowin? Tell a friend!