My old Logitech MX Performance, which I've been quite happy with, was starting to get a bit worn down (the outside/surface that is, just fine mechanically) so I bought myself a G700s as a replacement.
I did consider just getting another Performance MX but it was never a perfect mouse, the thumb-rest is far too deep for my grip (old MX Revolution was much better), the sideways tilt of the scroll-wheel barely works and it wore out far too quickly so I look at alternatives first.
I did look at some other mice before picking this one up but at this point I'm so used to Logitech's dual-mode scroll wheel (click a button and the scroll wheel can spin freely and scroll extremely quickly) that it's hard to imagine using a mouse without it.
Ultimately, the Logitech G700s is what I went with, this post details my thoughts on it.
Look at that, new version of the site.
Unlike the change last year which was basically just a swap of the CSS this is pretty much a complete rewrite.
I started fresh with new CSS and HTML (though there is probably quite a few similarities in the structure and naming). It's fun to look back at your previous designs and see how you're style has changed and what has remained the same.
The blog system got pretty much completely rewritten, I used to have a lot of duplicated code, for example the code that parses and formats the category links for a post. Now everything has been moved to a single file and written as functions, about time I did it that way, makes it so much easier to make changes. Also took the time to switch from procedural mysqli to object oriented mysqli, was a lot easier to get used to than I expected it to be when I first looked at it.
In the end not much has really changed in how things work in the front-end of the site. Notable things that did change is that the blog now also have proper support for link posts (as seen on, for example, daringfireball.com). I also removed the pagination from the front-page. Having the most recent posts presented on the front-page makes sense but I feel that if you want to read older posts going to an archive where you just get a concise list of post titles and links is much better than clicking through pages showing a couple of posts in full each.
Version 1.2.5 in itself is nothing big, just a few fixes. This version however is the first release to be released as a standalone and not just as a Joomla module.
I stopped using Joomla quite a while ago myself so it's been a while since I actually did the conversion of LeoClock to a standalone script, just didn't get around to releasing it for some reason.
1.2.5 also marks the last release to ever be done for Joomla 1.5. I'm not sure if there will be any future versions of LeoClock, it already does all I ever wanted it to, but if there ever is a new version it'll only be for Joomla 2.5 and up and as standalone. Just putting it out there.
Since it took me a long time to find this information when I needed it myself about a month ago when I was about to get a SSD and needed to switch my SATA-mode from IDE Legacy (which must have been the default in the BIOS that came pre-installed on the motherboard) to AHCI, I figured I'd make a short post so the information can be found in at least on more place on the Internet.
Windows only activates the driver needed for whatever mode is currently selected when Windows is installed. I did find a couple of solutions for how to make Windows accept a new mode instead of giving a blue screen of death but the were all registry hacks that changed or removed entries that either didn't exist in Windows 8 or simply didn't work.
I imagine the solution below will work for Windows 7 as well, in case you don't want to play around in the registry.
So here's what you do: Boot Windows in safe mode.
In more detail:
It's possible you might be able to use the F8 menu during boot to get to Safe mode but I never tried this. I can imagine this not working for Windows 8 since this option become available a lot later in the boot process, in other words, Windows might get to the point where it gives a blue screen of death due to having the wrong SATA mode driver before you get to the menu.
(Oh, in case you were wondering. Getting a SSD for your OS install is definitely worth it, the OS and any apps installed on the SSD will be a lot snappier, it's especially noticeable just after boot where all the startup apps will load pretty much instantly instead of Windows being slow for minutes. Sadly I haven't seen that much of an effect on games.)
Visit the archive for older posts.