wanderingbison9 said:Nah, the lights aren't flickering at the contact points or anything; everything looks fine until I actually turn the key. Every time I hear that click, the lights just cut out and come back on. It feels like a relay is skipping, though I don't hear the starter engaging. My battery is a Yuasa, maybe 2 or 3 years old—my last one lasted me 11 years, and the one before that got 6, both made by Panasonic. It started up totally fine this morning and a few times after that, then just... bam. We'll definitely check the battery, though; if it jumps when I jump it, I know the starter is fine.
If you're hearing clicking, it probably means the solenoid is doing its thing, but the starter isn't actually cranking. You could always take it to a local auto electric shop; usually, a repair runs about $400$167 and if they actually know what they're doing, it'll be way better than some cheap aftermarket part.
About a month and a half ago, my battery totally died on me. It was a Sunday, around 1:45 AM, right when I was trying to make it to Walmart before they closed at 2. I had a charger and everything, but no luck—it was charged, but the engine just wouldn't turn over.
Then, a few days later, my water pump belt snapped. I ended up being without a car for about two weeks.🤣
Good luck sorting yours out. I’ve heard that pop-starting a car can be pretty risky if the belt is old, so maybe watch out for that...
You didn't actually lose anything; based on what you put in ($8.75), you just ended up with a bigger slice of Category A. It's the same amount of money, you just got more units because the price per share in Category A is lower than Category B.
The voltage readings from HWiNFO are pretty much useless because:
1. Motherboards usually do a crappy job of reading those voltages correctly. 2. Even if you use a multimeter directly on the PSU and the voltage looks "fine," you won't see how messy it actually is until you hook up an oscilloscope.
Since you’re running both integrated and discrete graphics, maybe try pulling that dedicated card out entirely? If your motherboard has the right ports, just plug the monitor straight into the board and see if the system behaves itself.
If this glitch only happens when the PC is cold, I guess there might be an issue with the power supply (what model are you running?). Capacitors in a PSU can lose their charge, and sometimes once they warm up, they stabilize enough to stop acting up—which would explain why you're getting these stupid errors during a cold boot.
Michael Jackson10 said:Maybe if people actually read what’s being said, we wouldn't have so much unnecessary noise on this forum...
Windows XP is the main "backend" system? I don't get it. Are you trying to say they're using Windows XP as a server or something? 🤦
Those "point of sale" systems you're talking about are probably just glorified digital receipts used in local diners, where nobody besides the owner knows what the actual inventory looks like, and even then, they "creatively" adjust numbers based on how many receipts they pocket... there's a more sophisticated way for those types of "users": they use an Android app on their phones, which handles the official reporting perfectly fine... but it's a nightmare to pull any actual sales data from them, because the developers are just enthusiasts who barely figured out one-way data transmission from the user to the tax authorities... My work is strictly with "Point of Sale" (POS) systems, where the application interacts with a robust SQL database, whether it's local or remote, handling full inventory and all kinds of transaction documents during sales and shipping...
Look, I walked away from Clipper applications that stored everything in "reliable" DBF "databases" over twenty years ago, even though I used to build them myself... nowadays, they don't even meet basic legal standards...
And if you do find them still in use... well, plenty of Stephanie-types use Windows XP just to forward emails, having mastered nothing more than copy-paste... exclusively via mouse...
"American style" dictates that you don't go for the latest version of anything; you go for the "stable and polished" version that came before it. Windows 11 -> Windows 10 -> Windows 8.1 -> Windows 8 -> Windows 7 -> Windows XP (with all the available service packs)
Go back to the eighth week, but stick with XP...
Basically, you don't even need new versions of Windows unless you want to wreck your systems and your business operations. 🙂 Hah, I'm not even joking.
Even in my own company until recently, the entire technical and business side ran on XP. Windows 10 was just one machine used for converting certain formats that wouldn't run on XP, like h.265/HEVC, or maybe updating Garmin maps, and that was it.
So, that statement above is such a massive lie it's almost impressive. Even though insight regarding XP isn't even the topic here, but whatever.
Like I said, try reading with comprehension... Formats? I clearly stated: the formats of modern applications. Meaning, modern Microsoft Office versions (not the 97 stuff...) won't run on XP at all, to continue the list...
Now, considering the facts from the paragraph above, I think knowing Windows XP will require a bit more than just installing some cheap Chinese diagnostic tool.
Because let's be real, what is Windows 10? It's an OS for kids. Look at the attempt to follow trends, especially with Android, which people went crazy for during the smartphone evolution, when they tried to fix things with Windows 10 systems on Nokia smartphones. They even have their own "Windows Store," which has been obsolete on Nokia for a year already. And that's a "new" system!
Let’s be real here—you can't even tell the difference between a GUI and the kernel...
Windows 11 -> Windows 10 -> Windows 8 -> Windows 7 -> Windows Vista -> Windows XP
A lot of people skipped Windows Vista, and probably Windows 8 too. Honestly, 8.1 felt more like a service pack than a real OS upgrade, and I guess plenty of people will probably skip Windows 11 as well.😁