Apparently there's a lot of redundancy in 'some of' the pins, whereas others are crucial. The photo is very difficult to make sense of without being able to look really clearly at the pins - I bought a jewellers magnifying glass to help with the straightening. They look pretty Eschery in real life and there's a bizarre perspective thing when you turn the board around and realise that the half that looked like dimples when the other half was little metal clips now look like little metal clips because they're bent in a different direction.
I decided to bend them straight because although I'm 99% certain I didn't do the damage - I'm really paranoid and careful when I move CPUs around and I've done it dozens of times - there's still that 1% telling me that I did it all and the processor won't work otherwise.
When I first examined the bent pins there were loads of straight fibres and bits of fluff in there that I blew away. I got the impression that some arse had maybe had a go with a cotton bud or microfibre cloth before discovering the Intel Velcro.
"the Intel Velcro "
WTF is that?
LGA sockets (as opposed to a PGA on the processor itself). It seems that when Intel first adopted LGA sockets for their CPUs, a number of hobbyists and system rebuilders were caught out. They were used to preparing a motherboard for a new CPU by giving it a quick clean with an air-spray cleaner and then running over the board with a cotton bud and some isopropyl alcohol or similar. Quick and easy when the socket has loads of holes for a PGA processor (pins on the CPU, holes on the motherboard). But with an LGA socket you have hundreds of miniscule bent over very sharp copper contacts in the socket on the board, exactly like copper Velcro. Bye bye motherboard when you give an LGA socket a good clean with a cotton bud.
I did the same after bending a small cluster of pins in a corner pushing a CPU into its socket. Worked fine.
It's a relief, isn't it.
As I said, I'm 99% certain it wasn't me. I managed to break the 'near-field' connector on my other half's phone when fitting a new battery - tiny little metal springy thing about a millimetre all round. She has never missed it but ever since then I've been absolutely paranoid about messing around near little metal springy bits and fit CPUs etc with enormous care. Even so, when I looked at the socket there was that nagging doubt in my mind. ZIF sockets are so much easier and I've never bent a CPU pin. I can see the reasoning: mobo with an average cost of say £75 vs CPU with an average cost of £250, so put the pins on the mobo (also 'not my problem' for Intel).
Scan are being slow over my CPU cooler refund. I assume they're relying on insurance to cover costs so have to wait to get it back. When I've returned stuff to the evil-empire of Amazon, I've had the ping of a text notifying my refund seconds after the pick-up point has scanned my returns parcel.
So now the little beast is up and running (silently), I'm starting the lengthy process of ripping a few hundred CDs to .flac format, oh, and picking a music player. I say a few hundred, but I don't really know how many. It may be 1000 or more. I always assumed that the software choices would be easy, after all there are dozens of rippers capable of churning out FLAC and dozens of media players to choose from. Not so.
The first thing I found is that Windows 10/Explorer/WMP etc. aren't really compatible with FLAC. Yep, you can make WMP play FLAC with the appropriate codec and then Windows and Explorer will recognise them as music files. Problem is that Windows doesn't handle the metadata tags in FLAC properly. It's a bug that's been there for years and MS have no obvious interest in fixing it. Most obvious symptom is that all things Windows will truncate the displayed track/song title to 26 characters. Nor can you correct this by editing in Explorer via the properties dialog as you can with most basic metadata. What you can do is royally screw the existing metadata. Top tip: if you try to correct this with another tag editor then Windows is quite likely to deny that the file has any metadata at all. It's all there. If you use WMP as a ripper then it rips just fine and even downloads and inserts metadata just fine (some of the genre decisions are a bit weird but MS isn't alone in that). Well, I say 'just fine' but that's if you know to turn off autoplay and autorip. Otherwise it has a habit of missing all info for the track it started to play. Oh, and sometimes it ignores your decision not to autoplay and autplays anyway, unless you manually add a registry DWORD just for CDs. Oh, and WMP totally relies on metadata as a player, so that's a bit sad for FLAC. WMP will take a squint at the library it happily ripped, and organise it for you. Only it will miss a few tracks from an album. It will give you odd un-named albums from unknown artists (made up of the missing tracks). And it will sometimes decided not to play a track, but the next one instead. So, all in all, best to stay clear of WMP as a ripper and player if you're interested in using FLAC.
I know that many will say that's an obvious decision even without experimenting. But then there's the fun I've had since with some other highly regarded software...
You really are taking advantage of all the extra time you have with retired life!
I'd obviously recommend some sort of command line based Linux thing (if I knew of one), but I doubt that really helps you right now.
I've had a quick search and I think I may have used CDex in the past for MP3s. I also remember Exact audio copy being popular.
I always use dbPowerAmp for ripping and VLC for playback.
I've a feeling I did OK with something called Media Monkey last time I wanted to batch a load of music ripping. Something like that, anyway!
MusicBee does Flac outtadabox. By far and away the best music player I've seen, wish it was on Linux too.