Recommended Posts

Back on topic. I have been running the torrent for 7054 since yesterday. It shows 1 seed not connected. I know everyone says this is FAKE and maybe it is. I do know this build does exist. This torrent was originally posted by solidatbigviv. Where is he/she? Seed this puppy please!

Guess (s)he gave up seeding because it's a fake, and people weren't deceived by it :rofl:

I'll also say it's a fake until someone shows me a seput of 7054 with proper digital signature.

Besides, even if it wasn't fake, being 32-bit would make it instant fail anyway :pinch:

Guess (s)he gave up seeding because it's a fake, and people weren't deceived by it :rofl:

I'll also say it's a fake until someone shows me a seput of 7054 with proper digital signature.

Besides, even if it wasn't fake, being 32-bit would make it instant fail anyway :pinch:

Actually, I need an x86/32-bit build in order to install Windows 7 on my netbook. But I do run the x86-64/64-bit on all my other computers.

Most Atom processors hvae had the x64 instruction set disabled (and I'm pretty sure the Inspiron Mini 9 falls into this category) so you won't be able to run x64 software, not that there would be any advantage on a Netbook anyways

Back on topic. I have been running the torrent for 7054 since yesterday. It shows 1 seed not connected. I know everyone says this is FAKE and maybe it is. I do know this build does exist. This torrent was originally posted by solidatbigviv. Where is he/she? Seed this puppy please!

What is the size?

does your netbook have an Atom cpu b/c that is 64-bit

Yes, my Sony Vaio P netbook has a 1.33 GHz Atom processor. But even if it is 64-bit, the instructions are turned off, as it won't install the x64 edition of build 7048.

But I was able to install the 32-bit version last night, and now the Vaio P can finally run Aero Glass! That was the only real hindrance of running past Windows 7 builds on the netbook, and now it's fixed.

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

    • No registered users viewing this page.
  • Posts

    • According to Microsoft, Cause: One of the drivers controlling the device notified the operating system that the device failed in some manner.   https://support.microsoft.com/en-us/topic/error-codes-in-device-manager-in-windows-524e9e89-4dee-8883-0afa-6bca0456324e
    • This looks awesome, I will request access via Steam later this afternoon!
    • Personally, I’ve found that it’s usually worth investing in the infrastructure you don’t want to replace later, especially cabling. Running Cat6A (or better, depending on your needs) during an upgrade is relatively inexpensive compared to having to re-cable a few years down the road. For switches I try to balance current specs with realistic growth. If my budget allows it Ill choose switches with higher uplink speeds which leaves room for expanding later on, but I don’t necessarily overspend on access ports if the endpoints won’t benefit from them anytime soon. One lesson I’ve learned is that planning for scalability pays off. It’s much easier to add devices, VLANs, or higher-bandwidth workloads when your network infrastructure already supports it than to replace hardware later.  What is your budget like?
    • I hate the term, "future-proof." We saw it back in the 90's / 2000's, if not before. You cannot future-proof anything, since there is no definition of how far into the future you plan on prepping for. Best idea is to tell us what you currently have and what its use is at the moment, and we can then offer ideas about some areas that might need an upgrade and other areas that can be left alone.
    • I can agree that it is being used in a small capacity. I worked for a company where their engineers still used XP, and when asked why it was because their sensor software wasn't compatible with newer operating systems and the software was discontinued so they couldn't upgrade the software. Given that the sensors were still in use by companies, they had to continue using XP to support the sensor, otherwise the price to the company would have gone into the millions or billions. Our response was simple: Ok, you can keep the XP machine. But we're removing it from the network. "But then it can't access the Internet or folder shares!" Yup, kinda the point. If someone wants to continue using an unsecure OS they can do, I have no problem with that. But it should be isolated. Simple. I had a fight with a guy in the engineering department for weeks before he finally relented. But we digress.   What do I plan on doing to commemorate the anniversary? Nothing. I have fond memories of the OS, but at the end of the day it's just an OS. If I had some time I might see if I could install it on my Raspberry Pi for a laugh. But my reflex memory with today's OS ideas would probably get me frustrated and I'd uninstall it after 5 mins.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      539
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      154
    4. 4
      Steven P.
      99
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!