Wesley's Tool-Box

Here it is... Korea's first imported Mac mini based on Intel's Core Duo processor! Of course, its older brother, the one with Freescale G4, was also the first to land on Korean soil. My earlier experiment with running the website on a Pentium M system with Windows didn't go so well, so it's back to Mac mini's job again. I'll probably try Linux next time.

While those of you who don't use a Mac or have large collection of video it may have gone unnoticed, there has been a weird and annoying hole in video playback compatibility in Mac platform. Specifically, AVI videos that use Windows Media Video 9 (a.k.a. WMV9 and also called WMV3) codec could not be played, let alone viewed with subtitles. Due to the availability of the 'WMV9 VCM' for Windows it has been possible to use that video codec in AVI container instead of the WMV container originally intended. However, in Macs playing this sort of file (and preferably with accompanying subtitle file) had following roadblocks until early this year.

I use a Diamondback 'Salamander Red' mouse from Razer. Yes, its something I won in AMD Mania Day 2004 AND 2005. The mouse is quite good, living up to its reputation. The problem is, I use it on my Mac mini. Razer's driver download page sadly tells me to "Download a third party Mac driver at USB Overdrive". I've used USB Overdrive a while back and I didn't quite like it. I've been in 'generic driver' mode since. However, that was about to be changed.

MySQL documentation gives some examples of creating users in MySQL. Among the examples are creating users that only have access to a specific database, or 'tied-to-database', as I say. This is preferred from a security standpoint because you can avoid using root to access services like s9y and use this 'limited' user instead. Let's look at one of the examples in there.

GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON bankaccount.* TO 'custom'@'localhost' IDENTIFIED BY 'obscure';

This is supposed to create a user called 'custom' on the 'localhost' domain that has the password of 'obsecure' and can only access 'bankaccount' database. Now this looks alright, but it poses a bit of problem with s9y.

Here's a minor annoyance that didn't affect the DVD creation process but still merits a mention. If you look at the 'Status' of the DVD being created, the maximum DVD capacity will show up as 8.0GB for double-layer project and 4.0GB for single-layer project.



The unit 'GB' is calculated under 'kilo is 1000', which is used by the storage device manufacturers, not 'kilo is 1024', which the operating system generally uses. Now, the unit itself isn't really a problem since as long as I know exactly how much I'll be using, I'm fine with that. The annoyance arises from the fact that under this unit, a double-layer DVD holds 8.5GB and a single-layer DVD holes 4.7GB. This means that iDVD does not let me choose to add 500 or 700MB worth of more video onto the disc even though the space is available. That's a sad waste of space. The extra space could have been used to either put more footage, or if 4-hour (or 2-hour for single-layer) limit must be kept, used to increase bitrate and thus quality of video.