Yeah, I thought it was a bit ridiculous, too.
I was reading this piece on Slashdot a couple of days ago, slightly infuriated, because I’ve actually had very few issues running Windows 7–with some exceptions. I’m glad that Ars Technica has come out to set the record straight.
Turns out that there’s some speculation the individual who brought the memory issues to the forefront is a fraud.
Anyway, look forward to seeing another link of the week in a few days. I’ve been getting caught up with a couple of things, including a personal project in my free time that might be of interest (more on that in another post). Actually, I have several; there’s one in particular that I’ve found rather captivating. Stay tuned! If I get around to it, I’ll post a little tomorrow.
I discovered earlier this week that Windows 7 has another annoying holdover from Windows Vista. It turns out that if you have CD or DVD burner, Windows will conveniently eject the tray for you if you double-click the drive from Windows Explorer (or single click it from the file save/open dialog).
That’s a great idea EXCEPT when you have a case like this one. (Mine’s an older Sonata but the same situation applies.) Let’s think about it: Ejecting the tray when there’s a lid outside the drive that operates to keep it closed. Thank goodness I didn’t damage anything.
Thankfully, there’s a solution. It’s not a great solution. They don’t have an obvious “uncheck this to prevent Windows from stupidly ejecting your drive during accidental clicks.” Instead, you have to disable and remove burning features from Windows explorer using the group policy editor (gpedit.msc).
TLDR version/I don’t like clicking links:
To disable ejecting your CD tray after an accidental click, enter gpedit.msc into the
run menu or the start menu’s search bar and then browse to: User Configuration -> Administrative Templates -> Windows Components -> and click on Windows Explorer. From here, set Remove CD Burning Features to Enabled.
Windows’ cmd.exe is pretty anemic and just doesn’t have the feel of a real command line. (It isn’t.) PowerShell is cute and has its uses for poking around with COM objects and the likes, but for common tasks it seems ridiculously verbose and unnecessary. Cygwin alleviates much of this in an Windows environment and grants those of us who use proper shells a method of interfacing with Windows. Well, kind of!
Unfortunately, Cygwin 1.7 has moved a few things around. Geeks like me tend to use
telnet to verify connectivity to other hosts, communicate directly with certain services (hey, HTTP isn’t that difficult), and troubleshoot. However…
[gridlock-x:~]$ which telnet
Hmmmm… this isn’t good. Windows’ telnet is terrible. More importantly, it doesn’t work in Cygwin. After some exploration, it would seem that the Cygwin folks have consolidated telnet and a few other useful utilities into a single package.
If your distribution doesn’t have telnet available, make sure to run the setup utility again and select the “inetutils” package. Once you’ve finished up the installation (again), it’ll install only the changed package, and you’ll have access to telnet again. Horray!
Although Cygwin 1.7 is still in beta, the developers are encouraging everyone to give it a try. What can I say? It has a lot of nice improvements over the 1.5 branch. Heck, it even finally comes with a decent icon for a pre-configured rxvt shortcut! Now that’s classy.
Try it out!