Are you getting a 0xc1900201 error installing Windows 10? I got both that and 0xc1900200. Here’s how I fixed it.
I upgraded my venerable Dell E1505 to Windows 10 over the weekend. It was harder than it needed to be, but I got it running. It’s an old machine, but the CPU is fast enough to run Windows 10, and if you max out its memory and put an SSD in it, I think it may even run Windows 10 better than it ran Windows 7.
I went looking for a reliable, modern controller to use on my Retropie setup. I eventually settled on a Logitech F310, betting the Logitech F310 on Retropie would make a nice combination based on my experience with other Logitech peripherals in regards to their quality and value for the money.
The reviews I found suggested the F310 continued in this tradition, and I found enough people who said they got it working with Linux to feel confident I could get it working on the Raspberry Pi. And sure enough, I did.
I paid $18 for mine, and my first impressions of the quality were good. It’s precise, and button pushes register with a slight click. It’s no worse than a Sony, Microsoft or Nintendo controller, and if anything, I think I liked it a little better. A pair of Logitech F310s costs more than the Raspberry Pi board, but playing games is a lot more enjoyable when the controller does what you want it to do all the time, not just most of the time.
The F310 wasn’t a drop-in replacement for the controller I’d been using, though. I had to configure it for Retroarch, the software that provides most of Retropie’s console emulation.
I bought a Raspberry Pi over the weekend intending to turn it into a retro gaming system. I’d rather not have a mess of systems and cartridges out for my kids to tear up and to constantly have to switch around at their whims; a deck-of-cards-sized console with everything loaded on a single SD card seems much more appealing.
I followed Lifehacker’s writeup, which mostly worked. My biggest problem was my controllers. NES and SNES games would freeze seemingly at random, which I later isolated to trying to move to the left. It turned out my Playstation-USB adapter didn’t get along with the Pi at all, and was registering the select and start buttons when I tried to move certain directions, pausing the game.
When I switched to a Retrolink SNES-style pad, the random pausing went away. The precision reminded me of the really cheap aftermarket controllers of yore for the NES and SNES. I concluded my controller, which I bought used, was worn out. Ultimately I ended up switching to a Logitech controller, which worked well. Read more
In the wake of Truecrypt’s sudden implosion, someone sent me a link to this curious blog post. I can see why many people might find the timing interesting, but there are a number of details this particular blog post doesn’t get correct, and it actually spends most of its time talking about stuff that has little or nothing to do with Truecrypt.
What’s unclear to me is whether he’s trying to say the industry is deliberately sabotaging Truecrypt, or if he’s simply trying to make a list of things that are making life difficult for Truecrypt. His post bothers me a lot less if it’s just a laundry list of challenges, but either way, the inaccuracies remain. Read more
A few months ago I bought a Gigabyte GA-Z77M-D3H to learn computer forensics on, because at the time I thought that was the direction my career was going. I dropped it into a neglected Compaq case and installed Linux on it, since most of the free forensics tools run on Linux. The current version of Debian loaded effortlessly and ran nicely, as you would expect on a dual-core CPU with 16 gigs of RAM.
Then my career went another direction. Today I analyze Windows threats and vulnerabilities for a living. That’s a better match for my experience and the pay is the same, so I’m perfectly fine with that. But my mind turned to that hotrod computer in the basement. I suppose I could still use it to learn forensics, but I probably won’t, so why not see how Windows runs on it and bring it upstairs? Read more
A security professional’s nightmare happened to AMI this week. Tons of confidential data, including the source code for the UEFI BIOS for Intel Ivy Bridge-based systems and an AMI-owned private key for digital signatures, turned up on a wide-open FTP server for all comers to download anonymously.
The implications are nearly limitless. To a malware author, this is like finding a hollowed-out book at a garage sale stuffed with $100 bills with a 25-cent price sticker on the front. If you’re a budding security professional, count on being asked in job interviews why you need to protect confidential information. The next time you get that question, here’s a story you can cite.
Another question from the big bag ‘o search queries: When you’re shopping for an SSD, is TRIM better than Native Command Queuing?
It’s an interesting question, and my first inclination is to say no, because TRIM and NCQ solve two similar but distinctly different problems. But the more I think about it, the more I understand why it’s possible to confuse the two.