Recommended Posts

Don't see why it would be bad as long as you've got drivers for everything and Windows is behaving. Personally I'd only really consider x86 for systems that obviously couldn't run x64 (old Athlon XP's, etc or have old hardware that doesn't have 64 bit drivers), or systems that only have like 2GB memory where 64 bit would probably do more harm than good due to the overhead.

This PC has never run x64. The specs are pretty low, 1.5GB RAM, 3GHz single-core processor. I was just worried that it might not last long until it crashes or something.

Don't worry, x86 or x64 will not cause your hardware to fail on its own

x64 has its advantages over x86 if your machine can run it, if you only have a couple gigs of RAM, then x86 is probably better, but neither is going to waste your hardware any faster

EDIT - How did you install Win 8 on 1.5GB of RAM ?

This PC has never run x64. The specs are pretty low, 1.5GB RAM, 3GHz single-core processor. I was just worried that it might not last long until it crashes or something.

That's surprising, the Win 8 installer let you do the install? The minimum RAM for Win 8 64-bit is 2 GB, it doesn't sound like the machine meets the minimum requirements.

Without thinking, I installed Windows 8 64-bit on my old PC from 7 years ago that initially ran Windows XP, and I upgraded it to Windows 7 32-bit when it came out. Now I've upgraded it to 64-bit since I upgraded my other computer.

Is this bad? Should I install 32-bit instead?

why??? old hardware, new windows = never a good deal. drivers missing, slow / poor performance... the list goes on.

But hey, if you are happy with it.. i once installed Windows XP on my old trustee Pentium 200 MMX that came with Windows 95; sure it worked (upgraded everything on that puter except the board, PSU and CPU) but i could eat lunch or take a nap while the puter was booting :laugh: :woot: still did lots of Photoshop work in that, though. :rofl:

I don't see why it should be a problem if the hardware supports it. The 64-bit version requires more RAM (I think 2GB whereas 32-bit only needs 1GB). Are you having any issues? If not then I don't see a problem.

Unless you run XP, there is absolutely ZERO reason to run anything other than an x64 OS on hardware that will support it. (And even if you DO run XP, the support for x64 by XP-era hardware is a lot greater than you would think - the issue iwth XP64 and support is applications - not hardware.)

Look in the Hardware Hangout archives - I've made several posts covering migration from x32 to x64 over XP, Vista, and 7 - including my own migration (during the Vista era). The issue has by and large been applications-related, and especially since the release of Windows Vista - between that and just plain FUD, crossover was scarce during the Vista era.

Unless you run XP, there is absolutely ZERO reason to run anything other than an x64 OS on hardware that will support it. (And even if you DO run XP, the support for x64 by XP-era hardware is a lot greater than you would think - the issue iwth XP64 and support is applications - not hardware.)

There are plenty of reasons not to run 64-bit on old hardware. The biggest one being that 64-bit uses more resources and creates more processes. The OP having 1.5GB of RAM is going to be hurting himself in performance by running x64. And finding drivers will be a nightmare. Honestly, the only upside I can think of for him to run x64 would maybe be security. And even that's a stretch.

Plus, I think we first need to know the specific CPU he's running. There are very few single-core CPUs out there that support x64, so he might be mistaken in thinking a Pentium 4 or something supports it, when in reality it doesn't.

  • Like 2

Unless you run XP, there is absolutely ZERO reason to run anything other than an x64 OS on hardware that will support it.

Maybe for home PCs, definitely not for office/corporate PCs. There's a huge amount of software, middleware, plugins, drivers, etc. that are specifically 32-bit. Getting this type of stuff to work in a 64-bit environment is often difficult or impossible, good luck trying justifying all the extra expenses to your boss/client. And frankly, most office PCs won't have more than 4 GB RAM.

But yeah, if all the software/hardware you're using is 64-bit compatible & you have 4+ GB RAM then it makes sense to go 64-bit.

Maybe for home PCs, definitely not for office/corporate PCs. There's a huge amount of software, middleware, plugins, drivers, etc. that are specifically 32-bit. Getting this type of stuff to work in a 64-bit environment is often difficult or impossible, good luck trying justifying all the extra expenses to your boss/client. And frankly, most office PCs won't have more than 4 GB RAM.

But yeah, if all the software/hardware you're using is 64-bit compatible & you have 4+ GB RAM then it makes sense to go 64-bit.

Again, you are referring to application issues - not hardware issues. (I specifically mentioned applications as being the bugbear with Windows in general, and XP in particular, in terms of migrating to x64 - I covered it in my posts covering migrating folks I support to x64 - starting with, in fact, XP64.) Further, NONE of my migratees had 4 GB of system RAM at the time of migration. None at all. (Over half had less than 2 GB of RAM - two had a mere 512MB of RAM. However, all of these were home users - not corporate or enterprise users. However, most were also using refurbished corporate or enterprise PCs - which shipped with either Windows XP Professional or even Windows 2000 Professional. Nearly the WORST of possible cases for an x64 migration; however, due to the lack of application issues with home users, I had far easier a time than would have been suspected.

The 4 GB issue - go back to Hardware Hangout and read my posts again. I started the migration trend because of - not in spite of - what I uncovered in my investigation of this particular rubric. My uncovering is, in fact, easily duplicated by anyone with access to virtualization software - simply configure identical virtual machines with each OS in the consideration pool. (Naturally, the host must support at least VT-X for both x32 and x64 to face off in this manner.) The virtualization software itself won't matter. Once the application and driver issues are addressed, the 4 GB floor is, in reality, half that. (It can be , in fact, lowered all the way down to a single gigabyte of RAM - or less - for computers used exclusively for Internet-based tasks - such as Web browsing and e-mail usage - that is exactly why smartphones, tablets, etc - which typically have memory loadouts of that size, or less - are eating PCs for lunch. It's also why I am FAR from surprised over slower sales of larger desktops.)

[snip]

Just out of curiosity, what is your justification for installing XP 64-bit on a PC, especially if it had 2GB or less of RAM?

A 64-bit word takes up twice as much memory as a 32-bit word, so with a small amount of RAM, it's a very very bad idea to go x64.

64-bit simply raises memory limitations, and the benefits on old hardware basically stop there.

I think you're overplaying it a bit. 64 bit applications do consume a little more memory than 32 bit apps but it's certainly not double.

I never said that. The memory for the instructions is double.

A 64-bit word is double that of 32-bit and whether or not you're using all the bits, that memory space is still allocated.

I tried x64 Win 7 on an early Core 2 Duo with 1GB of RAM, and the performance was pretty bad. x86 was better since more memory was freed.

  • 1 month later...

I never said that. The memory for the instructions is double.

A 64-bit word is double that of 32-bit and whether or not you're using all the bits, that memory space is still allocated.

I tried x64 Win 7 on an early Core 2 Duo with 1GB of RAM, and the performance was pretty bad. x86 was better since more memory was freed.

However, the memory USAGE of the application itself is not double - and what was the hardware in question? (One thing that has to be taken into account is badly-written or piggy drivers - while not as large an issue as it used to be, it's still an issue, especially for lower-tier hardware and peripherals.) Given identical loadouts, what's the memory usage comparison between Firefox, PaleMoon x64, and Waterfox? One reason I prefer IntelliPoint Pro (and now the Microsoft Keyboard and Mouse Center driver for Windows 8) to SetPoint for my Logitech V220 is due to SetPoint's piggishness - a porky driver that is less usable compared to an alternative gets replaced by that alternative without a quibble. Love the V220 as a wireless mouse physically, but I loathe the porkiness of SetPoint.

I've run Win 8 on older hardware, as long as the CPU supports it, needing NX bit as I recall, I see no reason to not install it. If you're running under 4GB RAM then I'd personally install the 32bit version but that has alwasy been a personal preference to ensure I'm able to take full advantage of all my system RAM. I've personallay seen a big performance improvement with Windows 8 on older hardware that was previously running XP.

I don't see why it would be a problem. Windows 7 64bit runs awesome on low powered systems, even with aero enabled,

and supposably Windows 8 requires the same specs or lower.

Should work even better than XP anyways, as long as the hardware is compatible.

I'm even thinking of picking up some old piece o junk pc just to try Win 8 on. Wouldn't want to install it on a good computer.

I never said that. The memory for the instructions is double.

A 64-bit word is double that of 32-bit and whether or not you're using all the bits, that memory space is still allocated.

I tried x64 Win 7 on an early Core 2 Duo with 1GB of RAM, and the performance was pretty bad. x86 was better since more memory was freed.

Pointers and such will be double the length, but that's basically it, the actual stuff stored in memory will be about the same.

Edit: And when using 64bit, SSE/2 support is guaranteed, unlike 32bit mode.

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

    • No registered users viewing this page.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      228
    3. 3
      PsYcHoKiLLa
      161
    4. 4
      Steven P.
      76
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!