Although some users have reported success, most installations I've tried of MySQL 5.1 on Vista have failed, even on fresh Vista installs. The first problem appears at the end of the service instance configuration. All appears to be well, however the server refuses to start with Could not start MySQL service or Could not start the service MySQL. Error: 0.
The trick is to start MySQL from the console so that you are able to see the error message (you can access the command console by typing cmd into the Run dialog):
cd "C:\Program Files\MySQL\MySQL Server 5.1\bin" mysqld -nt --defaults-file="C:\Program Files\MySQL\MySQL Server 5.1\my.ini" --standalone --console
In my case, MySQL always returned the same error message:
Plugin 'InnoDB' init function returned error. Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Unknown/unsupported table type: INNODB Aborting Forcing shutdown of 1 plugins
This message is a symptom of the log file size problem (just google InnoDB: Error: log file .\ib_logfile0 is of different size for more information). All you need to do is to clear the following files from the folder C:\ProgramData\MySQL\MySQL Server 5.1\data:
Restart the MySQL server and all should be well. Note that the C:\ProgramData\ folder is hidden, so unless you have enabled hidden folders from the Folder Options dialog, you will need to copy/paste that folder path directly into the address bar in order to access the folder.
So... Here's what I have been doing during the past 5 hours:
I was noticing some odd behavior from my PC, which runs Fedora Linux as its primary OS but it also has Windows Vista installed for gaming. The machine would boot without any indication of trouble, but once it had been up & running for about 5 minutes, the system would hang and the hard disk activity light on the case would stay permanently on. A soft reboot wouldn't fix the problem either - a complete shutdown was required. At first I thought it was an OS problem, so I rebooted into Vista but found it was affected too. I immediately thought, "hardware". I tried leaving the computer alone for an hour to see if it it would eventually come out of the freeze, but it clearly wasn't doing anything with the disk because the system remained frozen and I could not hear the disk heads moving (and on a 10K RPM drive, those are pretty loud). I ran memtest86+ and did a 3 minute S.M.A.R.T self-test on /dev/sda in Fedora, but oddly enough both came up clean.
Since my hardware seemed OK, I powered down the PC, opened the case and made sure there were no loose cables. Sure enough, the problem was the SATA cable which connected my motherboard to my hard disk. After disconnecting it, blowing off some excess dust and reconnecting it, everything was fine. But that's not where the story ends.
By the time I had reproduced the problem, tested the RAM & hard disk and reconnected the SATA cable, I had done about 15 power cycles. Linux handled the whole situation pretty gracefully - it logged the specific SATA errors (Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK) and put the root filesystem into read-only mode. After reconnecting the cable, Fedora was up and running as if nothing had happened (it did do an automatic fsck upon booting, but the check came up clean). Vista, on the other hand, didn't take it so well - it informed me that I need to run CHKDISK upon starting up, so I let it repair C:\ and it orphans thousands and thousands of files... After CHKDISK completed I was (surprisingly) able to boot up, but many programs - including explorer.exe - were crashing. Judging by the amount of orphaned files, I'm guessing that quite a few system files were missing or corrupted.
So, long story short, if you have any SATA problems and Vista starts orphaning a tons of files during CHKDISK, save yourself some time by canceling the CHKDISK and make sure you have your Vista installation DVD handy.
PNG images are great for Web work, but there's one problem that was really getting on my nerves: the color correction problem. PNG images, like many other formats, support embedded ICC profiles for color management. For websites this feature can become a big hassle since some Internet browsers (namely, Safari 3.x and up) will adjust the gamma and colors of images according to their embedded profiles, but the colors defined in CSS stylesheets are viewed with the native color profile. So if an image with an embedded ICC profile is used in combination with "background: " rules defined in a CSS stylesheet, the image will not match the background color of the page!
Fortunately, GIMP is capable of converting an image's embedded profile into the sRGB profile which was designed for use on the Internet.
First, GIMP requires a bit of setup:
Select the color profile for your display by selecting Edit > Preferences from the menu and clicking on the Color Management section
Set Mode of Operation to Color managed display
From the Monitor Profile drop-down box, choose Select color profile from disk... and select the ICC profile which is you are currently using (tip: On OS X, ICC profiles are stored in /Library/ColorSync)
Once GIMP has been informed about which ICC profile your display is using, it can convert embedded profiles to the sRGB workspace:
Open the image you want to convert
Select Image > Mode > Assign from the menu and ensure that the sRGB profile is currently assigned
Select Image > Mode > Convert from the menu and select the ICC profile that your display is using (the same one you chose in the setup sets)
Save the image and if applicable, pass it through pngcrush to make it smaller
I read an article on Ars Technica about the new Windows advertisement titled "Lisa and Jackson get a Sony VAIO". In the advertisement, Lisa and her 11-year old
son Jackson are looking for a $1500 computer, choosing a PC over a Mac. While I think it's good that Microsoft is recovering from the "Vista blunder" and starting to retaliate against Apple's aggressive ads, it bothers me that these ads are based on absolutely nothing.
After watching the ad (several times), the only valid point I could find was that Apple computer don't include Blu-ray drives (yet). Here are the things Jackson says he needs:
A big hard drive
A good gaming computer
Price under $1500
Hm, so we have one quantifiable objective and 3 other subjective ones.
Jackson starts by takes a look at the Macs and decides they are "a little too small" and immediately moves on. While I'll agree that the MacBook's 13.3" screen is a bit small (and the MacBook Pro is outside his price range), Jackson and his mother completely ignore all specifications! They move on to the PCs where they discover that they can use a remote to control the computer... Of course, no mention that Apple's computers have also this feature (and for years before it became mainstream on PCs, might I add). So in short, because the Sony VIAO Jackson is looking at has a Blu-ray drive and a 16" screen, he's sold. What happened to checking for "speed", "a big hard drive" or a graphics card? A large screen is always nice, but useless for gaming unless you have a decent GPU.
I did a quick search on bestbuy.ca (16" laptops, price range >= $1500) and it found two matching Sony VIAOs, so I took the more expensive one. For $1349.99, the Sony VAIO 16.4" Laptop (VGNFW275DW) (click for specs) features:
Display output: mini-DisplayPort (VGA, HDMI (HDCP compliant), DVI and dual-DVI available via $34 adapters)
Dedicated GPU: None (nVidia GeForce 9400M, 256MB shared system memory)
Battery: Lithium-ion (approx. 5 hours)
Multitouch trackpad (supports gestures such as three-finger swipe for back/foward and two-finger scrolling)
Extremely environmentally friendly: EPEAT Gold rating + more (see spec page for more info)
MagSafe power port: Magnetic power latch
I've left out any sort of software comparison since that is very subjective and opinions vary from user to user. As well, I did not list components which were equivalent such as the built-in webcam or wireless 802.11a/b/g/n.
Let's return to Jackson's original criteria:
Speed: VAIO wins by a tiny margin... The difference between the P7350 and the P8400 would be negligible during "real world" use.
Big hard drive: VAIO wins by a large margin, as Apple tends to be very conservative with their laptop hard drive size.
Good gaming computer: In reality, neither computer has a dedicated graphics card which is what really matters for gaming. Ignoring that fact, the MacBook wins by a huge margin. nVidia has reported that their 9400M is up to 5x faster than Intel's GM45 integrated graphics chipset. As always reports like that should be taken with a grain of salt since the "up to" can be a bit misleading. The 9400M, however, is still a much better choice than the GM45 even if it's only 2-3x faster on average and in one or two cases, 5x faster. Finally, we must also consider the RAM size and type. Sure, it makes the VAIO look great if you say "4GB of RAM!" but let's take a look at the bigger picture. The GM45 is using up to 1750MB of system memory, so that means that if you're gaming on the VAIO, you only really have 2GB of RAM... Just like the MacBook. The 9400M used in the new MacBooks only uses 256MB of system memory, which is much smaller than the GM45 - leaving 1.75GB available for system use. Let's not also forget that Apple is using faster RAM than the VAIO; DDR2 800MHz versus the DDR3 1066MHz RAM on the Macbook.
I'm not even going to compare the features outside of Jackson's criteria, I think you can see where this is going ;)
I have to admit, I'm pretty curious about what the giant botnet of Conficker-infected computers is going to start doing tomorrow. A large-scale denial of service attack is my first guess, but my instinct tells me there's something bigger in store... Either way, my clock currently reads 11:53PM so we're about to find out!
Edit: Did some quick research and it looks like the media hype got me. The only thing that's changing is the method which one variant (and not even the most popular one) receives new instructions.
The 500GB SATA drive in an external enclosure that I use for backups (eSATA/USB 2.0 connectivity) is currently NTFS-formatted for compatibility reasons. I would much prefer to use ext3 or HFS+, but it's pretty hard to get those two working correctly on all operating systems. Thanks to NTFS-3G and (Mac)Fuse, I can reliably access NTFS partitions on Linux, OS X and Windows (of course) so it's become my FS of choice when it comes to compatibility.
Unfortunately, that means that the drive becomes horribly fragmented (and pretty quickly, too). I decided to do a defrag today and found that the NTFS partition was 38% fragmented with 78% file fragmentation... Yuck. I'm going to be really happy when there's a filesystem that I can use on all operating systems that doesn't fragment or choke all the time. Ext2/3 was looking like a pretty good for the "doesn't fragment" part, but the ext2fsx project for OS X seems to have died out and ext2fsd, the only driver I've found for Windows that supports ext3 filesystems with inode sizes > 128, tends to bluescreen a lot. Back to waiting, I guess...
I realized that I had my Drupal permissions set wrong and users who were not registered could not vote (I have also disabled user registration for now). I fixed the settings so if you cannot see the voting options, just refresh the page and they should appear on bottom left side of the page. Please let me know who your favorite motherboard manufacturer is!
GIMP is a great program, but I always found it was a bit annoying to use on OS X (Leopard). First of all, whenever X11 starts, a new xterm window along with it. Besides that, when switching windows you need two clicks before GIMP (or any other program, really) registers the click and actually does something - the first click just switches the active window. Seeing as GIMP has it's tool palette in a separate window, this quickly became extremely irritating.
After a quick google, I found many sources saying that to disable xterm, I needed to copy /private/etc/X11/xinit/xinitrc to ~/.xinitrc and edit out the "xterm &" line inside. That's easy enough, but the only problem is that on Leopard with the latest X11 from XQuartz (220.127.116.11 at the time of writing) installed, /private/etc/X11/xinit/xinitrc doesn't exist! Although /usr/X11/lib/X11/xinit/xinitrc does, editing out all references to xterm doesn't work anyways. Instead, the app_to_run preference needs to be modified:
defaults write org.x.X11 app_to_run /usr/bin/true
/usr/bin/true is a command that does nothing (literally), so this essentially tells X11 to autostart nothing. I moved onto my next problem and found that to solve the two-clicks problem, the solution was to enable the "focus follows mouse" option like this:
I've been using that for a few months and I find it's still pretty annoying, but it's still less annoying than having to click twice on everything. Fortunately, I recently discovered the "wm_click_through" preference which is exactly what I had been looking for all along: