Posts by Nancy Hayes75

I’m thinking this might be tied to your BIOS settings. You probably need to make sure a UDF option or something similar is properly configured and supported by the BIOS. I ran into a nightmare of a problem just like this once—honestly, I nearly lost my mind before I finally stumbled upon the fix...

ruggedfalcon62, with all due respect, you're talking nonsense here...
Linux and Windows don't share even remotely similar drivers for anything. Linux drivers are compiled and operate on a completely different principle entirely. So, your logic—that Linux started working because you updated your Windows drivers (not to mention you ended up using an Uninstaller on Windows right after)—is just as silly as your claim that data is easily recovered after a format.
I already gave you a rough breakdown of what a "format" actually does. I explained why it's virtually impossible for a virus to "survive," despite how you so charmingly described the process, let alone drivers built for a totally different OS platform...
And honestly, what are you even trying to imply with that term "peasants"?

Honestly, I don't think a full disk format is necessary; a quick repair should do the trick...
My guess is that while the uninstaller was running, it accidentally wiped out some crucial system .dll file or maybe even messed with some DirectX components...
He could try running SystemRestore first, and if that doesn't cut it, then move on to SystemRepair?
There are plenty of great tutorials floating around online that can walk him through it...

Look, just to clarify how formatting actually works—like someone else mentioned earlier—you aren't actually wiping the data off the drive itself. All you’re really doing is clearing out the address entries in the disk's allocation tables.
Those allocation tables are basically what tell the system which specific data lives on which cluster; without them, the drive and everything on it becomes pretty much useless.
To put it in layman's terms, think of it like the "Table of Contents" or an index for the entire disk.
Now, despite what some of the "experts" in this thread are claiming about how easy it is to recover files from a formatted drive, it’s honestly not that simple. The data gets scattered across different clusters, and if you want to reconstruct a usable allocation table, you're looking at a massive amount of heavy lifting and deep knowledge of complex algorithms, blah, blah, blah...
If anyone’s skeptical, just try reaching out to a specialized data recovery firm like DriveSavers and ask them for a quote...

Also, let’s get one thing straight: computer viruses aren't "alive." They don't have some kind of survival instinct where you can just hit them with "antibiotics." Once you wipe that allocation table, the virus is effectively neutralized because it doesn't even know where its own pieces are anymore, and nobody can "reassemble" it since it's been fragmented all over the disk.
With a standard cluster size of 4KB, if you're dealing with a nasty little 400KB virus, just imagine how many different clusters that thing is spread across. 🙂

Honestly, I can’t quite put my finger on the exact timing, but it was definitely somewhere in the ballpark of a year or two ago...
I'm positive it wasn't a 64-bit setup, though, mostly because I never even owned a 64-bit processor back then. Plus, now that I think about it, I clearly remember seeing that Program Files (x86) folder and dealing with that whole 4.00GB RAM limit in System Properties... 🙂

MrGoode; I won't say for certain because it might have been a few years back, but I remember installing the x64 version of Windows 7 on my old rig, and I am absolutely positive I didn't even have a 64-bit processor at the time.
I was doing a little digging online just now and noticed plenty of other stories where people tried to force an x64 OS onto a 32-bit system. My guess? It probably just worked out as a total fluke in those specific cases...

I only ran into this issue when I was running a Dual Monitor setup and my HDMI port was basically "empty"—meaning it was active, but there wasn't actually an HDMI cable plugged into the port.
It was a total fluke, but I noticed that as soon as I actually plugged the cable in, the whole thing stabilized.
Following my personal philosophy of "if it ain't broke, don't fix it," I just left it exactly how it was, and honestly? It works just fine...

Honestly, I haven't even checked yet, which is probably for the best...

You totally can.
The only thing is, you aren't really gaining much from just having it, but a 64-bit OS lets you actually use the full power of a 64-bit processor. Plus, there are some nice little perks—like being able to actually utilize more than 3.76GB of RAM. I don't know if you've noticed this on your own rig, but if you have 4GB installed, the system often shows you only have 3.76GB available. It’s those kinds of little wins that make a difference...
I'm not sure if we're talking about video games or whatever else, but honestly, I couldn't tell you if the OS or the processor even matters that much to them...
But look, nothing is stopping you from installing a 64-bit OS. You've got nothing to lose, maybe aside from a few niche apps that only run on 32-bit systems, but those are incredibly rare nowadays...
Or, you could just go with DualBoot...

Haha... 🙂
It’s going to be pretty tough for them to spot anything specific since they haven't even installed the drivers yet. They'll probably just see some generic "Standard VGA adapter" or something along those lines in the system settings...
If they happen to have a newer BIOS, they might be able to dig up some more detailed specs there. Honestly, though, I figured they'd just head straight over to the Intel site and run the AutoDetect tool. If that doesn't turn up anything, then they can just jump over to the Nvidia page and deal with it there.

Honestly, I’m pretty sure the BIOS is actually loading up, it just isn't showing itself on your primary Display...

I don't think you can actually block Facebook through the hosts file. Even if you could, a proxy would just bypass that entirely because it uses its own DNS. It’s basically going to hand the host whatever results its own DNS tells it to...

I mean, is it even showing up for you in the BIOS or during the POST process?

Whatever you do, don't go disabling Windows Update. Believe it or not, there's actually some useful stuff tucked away in there. Usually, drivers get tucked under the optional updates section anyway, so you aren't forced to install them if you don't want to.
I'm guessing the headache is coming from the graphics card's HDMI port when it tries to send a signal to a secondary display. It feels a little weird to me, though, because during the POST process and while the drivers are loading, the signal should always default to the primary display—which, in your case, would be the laptop screen.
Anyway, why not try plugging a monitor into that secondary HDMI port just to see if you can catch an image during the boot sequence?
Also, once you hit F2 to get into the BIOS and hear that beep, does the system eventually load into Windows on its own, or are you stuck having to hard reset the laptop every single time?

Look, it’s just like Nathan Ramos said; once you set your Cisco to Repeater mode, it basically acts like a standard signal booster, grabbing the signal from your chosen AP and pushing it out through your WiFi transmitter.
You’ve gotta keep in mind, though, that anyone jumping onto that TP-Link isn't going to see lightning-fast latency or anything fancy. It’ll work fine for basic browsing and checking emails, but don't expect miracles.
I actually just hooked up my General Electric unit at home to check, and sure enough, even on the AT&T firmware, there's an option for Repeater mode. I haven't actually flipped the switch myself, but hey, that should make your life a whole lot easier.

You can pick up a Netgear at basically any decent electronics store or big-box retailer out there...
But honestly, if you want my two cents, go hunting for an old AT&T Cisco Catalyst router—the kind they used to hand out back in the day for ADSL connections. Just flash the original firmware on it and you’ve got yourself a solid repeater. The User Interface is super straightforward, so you'll have it all dialed in before you even finish your coffee. The real kicker compared to those cheap Netgear units is how much better it handles a weak signal; it actually manages to "repeat" the connection effectively. Those off-the-shelf extenders often just give up the ghost when the signal starts getting spotty, which is a total headache.