I spent a bit of time this evening shifting my blog from Blogger to WordPress. Why? Well, I have my own hosting service that I use, and I used to use blogger because it was an easy way to publish and control the posts. But blogger depends on FTP / SFTP if you use an external hosting service, which means it’s another service that I need to open up on my hosting box. Also, it’s another set of login / password credentials that I have to maintain. Now since my l/p information is stored in a database, which is actually hosted on a seperate SQL server, it just became too complex to change anything. This was fine as long as it worked…however, when I moved my hosting database to a different server, the hash key changed, and I can’t be bothered resetting the blogger password for the hosting service (phew!).

So for the past couple of weeks, I haven’t blogged. Well, technically I have, I just haven’t been able to publish anything. So I switched to blogger’s internal hosting, spent some time making sure all my posts were in the published state, and used the built in WordPress import function to bring them all in to WP. I’ve not changed the theme at all, because I’m a little lazy and I wanted to put more content up instead. Oh, by the way, blogger does not maintain the image files on their servers when you do your own hosting. They upload and link straight to your server. This means, when you move to wordpress, the images do not get imported into WP. Now, as long as the URL for the image files remains the same, everything is peachy. What I did to keep everything the same is tell WordPress to use the old blogger image directory as it’s own. So now they will still all be in the same place :)

So now I shouldn’t have as many problems with logins etc. as WordPress is publishing to the local file system (yay!). Plus it’s flexible, so I might get around to adding some more features…like plugging my photo gallery into this properly :)

Written on September 24th, 2008 , Serious

I like Quake 3. It’s still one of my fav FPS games. I have the Linux, Mac and Windows binaries installed in my licenced (yes I bought the game) install directory of the game. However, it is getting a bit dated, and computers have come far enough where you want to make sure you have every possible settings in Q3 turned up to the highest.

Most of the documentation on the web points to adding the q3config.cfg or autoexec.cfg files to the baseq3 directory in your installation directory. This isn’t quite right in MacOSX. Mac OS X stores the config files for Q3 in the ~/Library/Application Support/Quake III/ directory. You’ll find your q3config.cfg file there.

Also, if your graphics card isn’t properly supported (the 8600GT on my Macbook pro is not) then Q3 will attempt to use the default driver. The default driver is actually software rendering. It will make your CPU hot. And it will look like Duke Nukem. No pretty textures, no detail. If that happens, Macs seem to have the Mesa OpenGL library installed, which identifies in Q3 as the Voodoo driver. Just change the driver in the settings to use that, and you’ll be good to go! Unfortunately that restricts me to 1024×768 on a monitor that normally does 1440×900, but it still looks way better!

Written on September 1st, 2008 , Informative

SirSpanky.com – The Secret Diary of James Pearce Aged 20-Something is proudly powered by WordPress and the Theme Adventure by Eric Schwarz
Entries (RSS) and Comments (RSS).

SirSpanky.com – The Secret Diary of James Pearce Aged 20-Something

Personal jorunal of a professional geek – James Pearce in Perth, Australia