Crimea holds some interest for Russia, but they couldn't care less about Eastern Ukraine. It’s merely a byproduct. In a sense, they can't truly secure Crimea unless they seize everything else. How exactly does one claim Crimea without also taking over those other regions where Russians have always been the majority?
Jeffrey Edwards76 said:it’s actually pretty similar. You’ve got this mess brewing on someone else's turf, and now everyone thinks Russia is the center of the universe just because there are five Russians involved. And they blame Putin for carving up Crimea—which he only did for some other strategic reasons anyway—but honestly? He doesn't give a damn about territory for territory's sake. It's more about the bigger picture. But then, suddenly, the domestic separatists get a taste of power and start wanting the whole thing. I don't follow all the nuances, but if you ask me, we're looking at a predictable script: once the pressure gets too high, Putin will just cut them loose, and then it'll be a total mad dash through Moscow. 😁
Quite the opposite. Crimea was handed over to Ukraine by Khrushchev about fifty years ago. The Russians didn't move in there; they were always there. Well, maybe not "always," but there certainly wasn't a Ukrainian presence to speak of.
Walter Grant5 said:Anyone actually follow the details on that recent plane crash? A buddy was lecturing me all day yesterday about Americans. Obviously, he "hates" them, but that doesn't mean his facts are wrong. Honestly, I couldn't retain a single thing he said because he was just rattling off info non-stop while we were out. Also, how much weight do the Russians actually put behind those pro-Russian types in Ukraine? How much (or little) support are they giving them? How, and why? If anyone knows their stuff, give me the short version. Thanks.
I'll take a crack at it.
In the region, you have both locals and ethnic Russians living side-by-side, with a significant portion of the population speaking Russian. The current government came to power via a coup led by right-wing nationalist factions. This understandably infuriated the Russians, who felt pushed away and decided to assert their own sovereignty. Putin gave that movement his blessing. And now, the fighting is in full swing.
As for the aircraft... honestly, what kind of fool flies a commercial passenger plane directly over an active war zone?
If I’ve interpreted this correctly, the warning stating "There are no quotas for quoting archived posts if someone forgets" can be safely ignored whenever one is responding specifically to the constructive elements within an archived post.
In truth, the warning should have read: "There are no quotas for quoting archived posts—unless you are addressing the constructive portions—in case anyone forgot."
Thanks for the clarification (and for the double standards, though I'll spare you the direct accusations this time).
So, here was the initial explanation I received from the admin, ego: "We don't have a rigid rule regarding quoting posts from users who have been sanctioned. Feeding the trolls or responding to insults is strictly discouraged and can result in a warning. Generally speaking, there is no issue with addressing the constructive elements within a sanctioned user's post." (In that first part, it’s pretty obvious ego meant "sanctioned" rather than "quoted"—just a slip of the pen)
Then today comes this warning from the moderator, Cuka: "And there is no quoting sanctioned posts, in case anyone forgot."
steelfox36 said:It’s possible that was already pre-installed. To be honest, I didn't quite follow your logic on how exactly you'd go about fixing it. Are you saying a fresh installation of Windows won't cut it? Should I be downloading Linux and running it alongside my current setup? I suppose I could put Linux on the D drive and keep Windows on the C drive, but I'm struggling to wrap my head around the mechanics of it all.😉
I’ve run into a bit of a headache with my PC lately. Every time I hit the power button, I'm greeted by nothing but a black screen and a glaring error message: "A DISK READ ERROR OCCURRED. PRESS CTRL+ALT+DEL TO RESTART." It’s incredibly frustrating. After several failed attempts and a fair amount of luck, I occasionally manage to get the system to boot up properly. Has anyone else dealt with this kind of instability?
Go ahead and install Windows, but make sure to leave a few extra gigabytes of unallocated space on the drive. Why bother rushing the process only to run into storage issues later? It’s better to have that breathing room from the start. Once that's finished, go ahead and install Linux on that partition.
When you boot up, the system will prompt you to choose whether you want to load Linux or Windows.
I realize this might seem like a bit of a lazy workaround, but since it appears you haven't quite mastered the nuances of Linux yet, I suspect this is the simplest path available to you.
Either find someone who actually knows what they're doing and let them fix it for you. Or just leave it alone.
Are you absolutely certain you actually have Windows installed?
It looks like GRUB is attempting to boot your Windows partition. To put it simply, that's a Linux thing.
You likely had a Linux distribution running on this machine previously, and Windows just isn't quite handling the transition well.
My suggestion? Install a Linux distro after Windows—just a minimal installation on a small partition. That should force GRUB (or LILO) back into the picture. It’s probably your easiest way out.
George Sanders37 said:Looking at everything sitting beneath those two fans—the side case fan and the CPU cooler—it looks to me like that graphics card is running purely passive.
Just to be absolutely certain, check the next photo where I've circled the area in red. Is there actually a fan located right here, View on imgur?
If you don't see one, your best bet is to pick up an 80 mm fan and zip-tie it directly to the passive heatsink.
I agree. Though, just to be safe, he should probably take a look at the underside of the card to see if there's a fan tucked away there.
Neither of those two fans belongs to the graphics card. Do you see that component plugged directly into the motherboard, sitting perpendicular to the board? Take a look at the underside of that part—check if there's a fan there and whether it's actually spinning.
I honestly have no clue. All I know for certain is that hitting 70 degrees Celsius while idling isn't normal behavior for a graphics card. Once you put even a minor load on it, those temps spike north of 85, and that's when the whole system either shuts down or just freezes up entirely.
You should probably check if the cooler is actually seated correctly on the card. Maybe a clip snapped, or perhaps the thermal paste has completely dried out—who knows?
We’re talking about the fan on the graphics card itself, not the one attached to the motherboard. We need to look at the video card—that massive component, likely the largest thing in your rig, plugged straight into the main PCIe slot on the motherboard. Check the fan on that unit.