Friday, October 16, 2009

Dungeons and Dragons Online Linux

Introduction

As you may have noticed with the blog posts, I have been quite a gamer for a number of years, especially in my younger years. For the most part though, I have always been more of a solo player, which is why Massive Multiplayer Online games barely cross my mind in terms of gaming options. I have played some online games before and they never seem adequate. Great games have that special element that is not quantifiable. Things that you just know are there when you play it.

I have avoided MMO titles like the plague but what caught my eye was Dungeons and Dragons Online which has been running for a few years now. The title is now launching, or more aptly relaunching, as a free service and since D&D has been a huge game in my youth, I thought to give it a shot.

I write this article for two reasons: First to address this issue for Linux gamers looking to get this running, and second, my recollection of the experience.

Getting It Running

Linux has always been my platform of choice for personal computing, entertainment and everything else. Of course, on the gaming side, Linux has very few options although the landscape now has improved tenfold. Inspite of this however, much of the solutions in the horizon are not for the feint of heart. Sometimes, it just seems you have to earn your way to getting the game you like to play. So it comes as no real surprise for me that DDO does not have official support on Linux. I always knew that from the very start there was no free pass.

To start of this sojourn, I started browsing forum threads and articles discussing this and was pleasantly surprised to see that most of the game is running already, with emphasis on MOST. You will need several resources at your disposal to getting this game to work. The most fruitful resources I have seen are from the Wine Application Database and the Codeweavers Tips section. I presume that the free WINE flavour will work just as well as described in the Wine documentation, but I was fortunate to get CrossOver Games off the Lame Duck Promotion.

The first thing I noticed with most resources was that to get the game running, I needed to install and copy the files from a Windows box. OUT OF THE QUESTION. I do not use Windows and will not get Windows just to see this game. I searched and read even further and noticed an interesting detail. The old installer might work, so I began to look for that. and with a little guess work, produced download links to the old Stormreach installers. Fortunately, you do not have to look harder than I did. Here are the two download links for the Standard Version and the High Resolution Version.

As expected, the new installer did not show any signs that it was working and almost immediately, I had switched to plan B. These installers on the other hand worked very perfectly. I had downloaded the entire installer which had taken half a day and proceeded to install the game. The installers went on without incident and then I proceeded to apply the PyLotrO launchers (look at the Wine documentation earlier). From there, you need to spend more time waiting as you need to update the game to the latest version. MMO games can be such a tedium when it comes to these updates and frankly, I was having trouble remembering why I bothered to play this game. It took so long that I had decided to leave it running and went to bed.

Playing the Game

So alas, the next day comes and I have finally been able to get it running. My hunch proved right also. The Stormreach installation would update itself into Eberron Unlimited. I am pleased of the mere fact the game works on Linux, if it means more options for the Linux gaming public. In my opinion, finding out that little bit more information on the installers is reward in and of itself. Now it was time to try it.

I spent the next few days squeezing a little of the game into my free time and finished a couple of quests. I have come up with a word. Inadequate. In two? Inadequate again. MMO games are funny in that apart from what players do, it has always been NPCs standing around to give quests and monsters to slay. Roleplaying in these parameters are very crude at best and left solely to the players themselves. I have often wondered why paper and pencil games were more fascinating and I think it has been because of how much what you do or say matters. The Dungeon Master makes the world react to you, and you react based on the world. That has been severely lacking in DDO. It has hardly been an immersive affair, with a village choking full of players running and leaping, and how you know that all the players are going through the same quests and going through the same narrative as if they are the only heroes in the game. And for all the narration of the so-called DM, there has been nothing more to do than to slaughter and kill. I also found it funny that as soon as you leave the village, you come across even more monsters and cultists that are probably camping nearby just to see if they can get a jump on you. These game worlds need the little things to make it work. Not this lack of spontaneity and tremendously archaic style of play.

I have always enjoyed single player RPGs and only from a select few. DDO is functional, but lacks aspects that take it to the next level. I do not particularly rate MMO games very highly and chances are I do not ever see myself spending more time on another.

On the bright side, I have taken my loot from this endeavor and hope that for those who are looking to get this game running on Linux can see some value in what I have written.

Thursday, August 27, 2009

VS System - What? Is this another card game?

Here's a few pointless rambles...

Magic: The Gathering was an incredibly popular card game where players honed their playing skills and produced decks of cards based specific strategies to win. With the success of Magic, came a slew of other card games. The proof of success, after all, is by the advent of its clones. Each had its own rule set, and seemed to attempt to carve its own niche. I found it funny that the normal scene of gaming session would have coin flipping, as well as other convoluted rules. I came to regard these games as the 'Yet Another Card Game' category. There was just too many. There was just no freaking way I would ever consider playing any other card game.

Reminiscing about it made me look for pure software mediums to play Magic, being the only game I could and wanted to play. Unfortunately, never really affording to dive into the specifics of the game meant that I was never really that good with playing nor was I good at constructing a deck. I sought an audience with a long time friend and card game enthusiast, Joem Argao, who you may or may not have heard of. His life seemed to be a living Magic card game playing machine. If there was one person who could help hammer my deck to working condition it was him.

When I did manage to track him down online, things took an unexpected turn. The person who I thought had spent hours of his day meditating on what deck to play, the person who I thought would spend idle moments playing Magic against an imaginary opponent had stopped playing. Instead he was now spending his time and energy on this defunct fancy card game called VS System, which I presume was meant to be some sort of reference to Marvel vs DC.

Good grief. Yet Another Card Game and one that had died before I even heard about it, I remarked. I was not all too crazy about learning a new card game, but I could also feel the enthusiasm with just how quickly he carried the conversation discussing details about it. Since he was nice enough to point out a DS version of the game I could try, I figured it was worth a shot just to see what he dubbed as 'the game Magic should have been' was all about.

I took the game for a spin and was greeted promptly with a game tutorial that just simply overwhelmed me. The rules seem convoluted and I had been so tuned to Magic that any semblance to the aforementioned game, I would attach the same game mechanics. This card game clone was not easy to learn. To add to that, the DS was also by no means an easy introductory tool. Two screens and tapping micro cards to zoom the cards up close was not as simple as taking a card and browsing it. I also realized part of the problem was that the interface was extremely cumbersome and the tutorial had very poor presentation (Not to mention horrible art too!).

Deciding it was simply better to just play the game, I played the first game and subsequently lost. Half the time I had no idea what was happening and the other half, was me knowing that my endurance points just kept dwindling. Okay, that was fun. I tried and lost again and I was no better than the first time I played it. I must have lost more than five games when I decided that it was just not working out. Mayday, mayday! The ship is sinking! And so was my interest.

I managed to get a hold of Joem again and wanted a piece of his brilliant knowledge. This time he managed to clear up the basic rules with me. And he gave me a shopping list of cards to obtain and build my deck. This is what he gave me.

4 Human Torch, Johnny Storm
4 Boris, Doom's Caretaker
4 Medusa, Inhuman
2 Darkoth
4 Titania, Mary MacPherran
2 Volcana, Raging Inferno
4 Ghost Rider, New Fantastic Four
4 Dr. Doom, Victor Von Doom
2 Thing, The Ever-Lovin' Blue-Eyed Thing

4 Signal Flare
4 Finishing Move
4 Flying Kick
4 Acrobatic Dodge
4 Shrink
4 Common Enemy
4 Mystical Paralysis
2 Marvel Team-Up

One of the things about learning this game is that they can keep talking about how this deck is going to be good, but I had no idea how it was going to happen when half the time, I had no idea what the cards did. And I had trouble also because I could not find Shrink and upon hearing Joem's advise that it was not as critical, I replaced it with The Time Keepers which I think was like an even weaker version.

I gave the deck a test drive and I wanted to play against an easy opponent. I'll rattle off on what I remember. The first opponent I played kept playing Doom Guards and Dr. Hauptmann. For those wondering how this newly minted deck worked, it flowed very brilliantly. Boris came to play at turn two as expected and inspite of the opponents constant harrassment and team attacks, Boris survived thanks to the Acrobatic Dodge. Joem had told me that playing 1-Drop characters was not always an effective strategy and having many of them was not necessarily tantamount to winning the game. When I attacked, I realized that as long as the player controlled those 1/1 and 2/1 midgets, they were little windows of opportunities. Even if the opponent had the tougher characters in play, these weak characters would continue to let my assaults through and hurt him very badly. Hammering and hammering opponents seem to be the basic strategy of this game, and this deck certainly exhibited that same ability. The game was very easy and it was certainly a nice change from the usual 'L' column.

After the victory, I decided to put the deck on a tougher challenge, the game I kept losing. I drew Ghostrider and Dr. Doom at the first turn and had no characters for turns two and three. I decided not to play a mulligan and keep the hand half hoping that my next two card draw would yield Human Torch or Boris. As luck would have it, I had none of them. All I had was Mystical Paralysis, Flying Kick, and Acrobatic Dodge and no characters to play. The opponent kept bashing me with his cards and there was little I could do about it.

In the succeeding turns I managed to play Medusa, and Ghostrider which gave me some meager defense. I was down on endurance and I thought the game was certainly over. When the opponent played Puppet Master, I thought I had ran out of luck but I was surprised to see that my two characters were quickly levelling the game. I was mildly surprised that the game was starting to turn to my favour. On the next turn, I looked at my hand and I had another Dr. Doom and Mystical Paralysis. I thought about using Mystical Paralysis and exhaust Dr. Doom and recruit the Doom in my hand to effectively unexhaust him, which delightfully worked. Now, I do not even think the tactic was smart in any actual game, but I was happy to know that I had understood some part of this game rules. I exhausted Puppet Master to keep him from limiting my options and with Doom and Ghostrider, I managed to beat the opponent.

I came away with interesting thoughts on the VS System from those two games. First, unlike Magic, the battle tactics are more emphasized and that there is simply no easy way to beat the opponent consumately in such a short time. You had to establish your advantage incrementally until you totally take victory. Second is that the starting endurance points gives ample time for the you or the opponent to make a comeback or to at least give you a fighting chance.

Now, I do not claim to be a good player at all and I am still learning the game, but as far as I can see, VS System may not be the most original, but it certainly earns its own merits. I enjoyed the game but without Joem's help, I probably never would have. Hats off to you.

Thursday, August 6, 2009

Some thoughts of the day with Don King's Prizefighter

I went back to playing Don King's Prizefighter on the DS. At this point, I have totally beaten the game and have moved on so to add a little spice, I decided to played an exhibition match on hard mode using Archibald Moore vs Rocky Marciano on the classic 30s ring. I wanted to put everything as authentic as the game could to present the classic Marciano vs Moore battle and put myself on a real stiff challenge. Marciano on Easy and Medium is a cakewalk but on hard, he is deadly lethal. I really had to fight my heart out to a 12-round unanimous decision. I did not realize I had set the game on twelve rounds so I was really wondering while slugging out with Rocky how long the fight was and boy it was a thrill to get the final round and beat him.

At the opening bell, Rocky hurt me with some real lethal combos and I was in real trouble. I had not put my fighting cap on and that was a real wake up call for me to keep my defenses up. To literally walk into his combinations is not the smartest thing to do so I paced myself and worked on more defense and unloading shots and jabs when it was really open. I could tell at round one I was barely hurting him but I kept on the peppering jabs, focusing on the body mostly. I was able to rest a bit and keep most of lethal powershots at bay. That was survival mode and I survived round one without kissing the canvas.

As it turns out, the judges called the round even. I was surprised when my cornerman called it an even round. We had to work on slowing Rocky down and keep on hitting him when he was open. The plan was to wear him down and have the damage accumulate, focusing on the body combinations more than the head. It was foolish to try and go for the head when there was still a lot of power in his shots. For rounds two to six, this was the approach and I did not deviate from the game plan.

By round seven, I got my first knockdown and I noticed his power punches were getting slower. That was the first real sign for me that Rocky was getting hurt (also the first time I realized the game emulated this). I needed to start pouring in and opening up with the combinations because going in on the defense will allow Rocky to recover. Rocky did get a few hooks and uppercuts in but they did not do as much damage as they did before. I started to balance out my assault on both the body and the head while still maintaining a good defense. Rocky is darn dangerous at any point in the fight if you let him have his day, so do not forget about defense!

I started to get more power combinations in and hurt Rocky more and more. Still, I did not forget to apply defense. Rocky was getting a bit discouraged and frequently bobbed, and weaved instead of throwing his attacks. For rounds nine, ten, and eleven, I had Rocky backed on the ropes for a good half round, hurting him and giving him the time of his life. I finished round eleven with two knockdowns knowing full and well that I had control of the fight and I was way ahead on the scorecards. With round twelve I knew I had it and I sealed the deal with another knockdown.

The score card read Moore - Marciano, 360-302. I racked up a total of six knockdowns. The first few rounds were a bit of a knife's edge as Marciano had some powerful shots. As the fight wore on, it got a bit easier. I have no doubt that on another day, Marciano would probably knock me out. Today though, was my day.

Monday, July 6, 2009

No good.

This wireless problem seems to really be tenacious. I did a spot check a few minutes ago and yeah, the wireless was not working at all. This is very annoying that I have to keep reloading the driver, but well, I guess this is the only thing I can do. So much for Linux for Humans.

I don't want to update my kernel as that would might break my nvidia driver, so at the end of the day, I am stuck with this piece of crap driver.

Sunday, July 5, 2009

Intel Wireless Update

Today, I checked dmesg and this is the output I got:
[432892.672000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[432892.672000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[432892.676000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[432892.968000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[432892.968000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[432893.592000] iwl4965: Error sending REPLY_SCAN_CMD: time out after 500ms.
[432893.592000] iwl4965: TX Power requested while scanning!
[432944.556000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[432944.556000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[432944.556000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[432944.816000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[432944.816000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[432945.396000] iwl4965: Error sending REPLY_SCAN_CMD: time out after 500ms.
[432945.396000] iwl4965: TX Power requested while scanning!
[433072.148000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[433072.148000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[433072.148000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[433072.392000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[433072.392000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[581993.352000] iwl4965: Microcode SW error detected. Restarting 0x2000000.
[581995.384000] iwl4965: Can't stop Rx DMA.

Seems like there were a few errors on the iwl4965 driver. I tried to connect to a wireless network and it still seems to work. Hopefully, this means that the problem is solved.

Friday, July 3, 2009

The IntelPro Wireless Saga Continues

If there is one thing you learn from life, is that nothing is ever straightforward. That was the case when I lent out a hand over the Ubuntu/OSX dual boot, that certainly is the case now. As fairly evident with the previous entries, Ubuntu 7.10 support for the Intel Wireless WiFi Link 4965AGN has been nothing short of pitiful. This is a problem because of three main aspects.

The first is that Ubuntu opted to use the obsolete ipw3945 driver. This driver yielded very uneven results from what I gather online. My experience with this driver has been rather awful. The second is that the bundled official iwl4965 (and iwl3945) drivers are out of date. I have gotten far better results with these drivers than the obsolete ones, but the driver sputters out after a few days of operation. The third main factor is that Ubuntu chose not to fix it and instead peddle their fixes on the next release. This is not an issue of 7.10 falling out of support. This is an old issue in the Ubuntu bug tracker and one of which they were nice enough to mark as "Won't Fix".

Firstly, if the OS has old drivers, that is forgiveable if there is a fix coming, ideally providing a release with the same kernel. Second, if the folks opt not to fix this, the least they could do is provide an official workaround for poor old folks like me. If there is no official support, then that just makes the Ubuntu life that much harder to live with.

That being said, Ubuntu is still a fine distribution and one I intend to keep using. Maybe I was unfortunate to have picked hardware where Linux support is not what it is cut out to be.

Now, to push this particular problem forward, I found this comment on the Ubuntu bug tracker, one that I hope finally erases this bug forever.

Anton Khokhlov wrote on 2007-12-20

Yesterday I had found the solution. Ubuntu seems to use old Intel firmware and the issue will be resolved if you perform the following steps:
- Download the last firmware archive from http://www.intellinuxwireless.org/?p=iwlwifi&n=Downloads . The file's name is iwlwifi-
4965-ucode-version number.tgz
- Unpack the archive tar xvf iwlwifi-
4965-ucode-what version you got.tgz
- Copy iwlwifi-4965.ucode from the unpacked folder into /lib/firmware/your kernel version/
iwlwifi-4965.ucode and /lib/firmware/your kernel version/iwlwifi-4965-1.ucode (you should overwrite two files with the same data)

After that you need to reboot or just to say
rmmod iwl4965
modprobe iwl4965
Now on my computer it have been working for the 24 hours continuously without any disconnect. But I can not guarantee it works everywhere.

Of course, when I followed his instructions to the letter, I broke my wireless support. This is the warm and glowing message dmesg greeted me with.

[432944.556000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[432944.556000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[432944.556000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[432944.816000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[432944.816000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[432945.396000] iwl4965: Error sending REPLY_SCAN_CMD: time out after 500ms.
[432945.396000] iwl4965: TX Power requested while scanning!

You vermin! I am utterly irrate by the constant headaches this driver problem has given me. All is not lost however. It is a good thing I normally keep a backup of all things before fiddling them. So by checking the dates, and making sure to use the iwl4965 firmware in the context of the comment, I gave the iwlwifi-4965-ucode-4.44.1.20.tgz (posted November 27, 2009) firmware a try. We will see how this one goes. So far it looks like the driver is working after the good old modprobe -r/modprobe reloading trick. We will see how this one fairs.

Wednesday, July 1, 2009

Damn it!

After a few days of smooth sailing, I noticed that the iwl4965 driver crapped out. This is not nice. Seems like nothing is ever easy with this problem. I am going to try and update the iwl4965 drivers and see how that goes...

For reference, this is the problem I saw (dmesg | grep iwl):
[ 24.104000] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
[ 24.104000] iwl4965: Copyright(c) 2003-2007 Intel Corporation
[ 24.104000] iwl4965: Detected Intel Wireless WiFi Link 4965AGN
[ 24.440000] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[ 24.440000] wmaster0: Selected rate control algorithm 'iwl-4965-rs'
[135851.700000] iwl4965: Microcode SW error detected. Restarting 0x2000000.
[135909.124000] iwl4965: REPLY_ADD_STA failed

I fixed this by reloading the drivers again.
$ sudo modprobe -r iwl4965
$ sudo modprobe iwl4965

Not funny. Not funny at all.

Sunday, June 28, 2009

Update on my Ubuntu Intel Pro Wireless Woes

So, this is a few days since the switch to that bad news ipw3945 driver to the "new" iwl4965 driver on my Acer laptop and I am ecstatic to write this post to say that the iwl4965 driver works like a charm. Ubuntu has been running for a while now and I can switch to my wireless at any time. It has also been wonderful to see that the list of wireless spots detected by my network manager constantly get updated. I am very much relieved to see this finally get squared away.

Wednesday, June 24, 2009

Ubuntu and my Intel Pro Wireless LAN Card

Okay, I have been wondering why my wireless network card refuses to function after a few days and I cannot fix it by rebooting. I've always had to reboot to Vista to sort of give the hardware a little kick. Maybe there is some residue in the hardware buffer of the wireless card, but for whatever reason, it has been testing my patience.

I also happen to remember when I got this laptop new, that Ubuntu did give me frequent problems with the wireless card unable to find my private access point.

This time, I really got pissed because it was again acting up when I really needed the wireless access to be working. So I decided to dig a little bit about the problem.

The laptop I bought is an Acer Aspire 5920g, and apart from the abysmal wireless performance, Ubuntu has been handling this baby pretty well. I even got the Crystal Eye camera to work.

Back to this problem. I did some reading and thankfully, there is a lot of resources from Ubuntu's very own forum. I discovered that my laptop has been running on Intel Pro 4965 AGN wireless card and that the driver Ubuntu Gutsy Gibbon (7.10) had been using was the obsolete ipw3945.

I knew then from past experience with this sucker that I had to discard it and find a new one. Thankfully, the kernel already comes packed with the new (Well, relatively...) iwl4965 driver from Intel.

Ubuntu has a great documentation that I followed to switch over to iwl4965 from that dubious ipw3945 driver. Click here for the online documentation. I just changed it to modprobe iwl4965 instead of iwl3945 and of course, load iwl4965 on /etc/modules.

After the reboot, it seems to be working fine, but so did the last one. I am going to observe how this one operates, and hopefully, this one works better than the last one. If all else fails, I may have to use ndiswrapper, and I do not like using Windows network drivers on Linux.

Anyway, that is all for now and I will report back if this one takes care of the issue.

Monday, June 8, 2009

Thoughts: 428 〜封鎖された渋谷で〜

I have always been opened (or close-minded) as a gamer to odd and quirky genres. It is always interesting to see a fresh or unique take on familiar formula on the different game genre. So when I first came upon this strange 'Sound Novel' of a game, it was not surprising to see myself drawn on such a unique visual presentation.

428 ~Fuusa Sareta Shibuya de~ (note: 428 - In a Blockaded Shibuya, aka 428 - The World Does Not Change Even So) is a game that takes the typical visual novel formula that Japanese developers often produce and takes that idea for a unique spin.

Normally, visual novels tend to make for very bland products. Apart from a nice picture backdrop and heaps of heaps of Japanese to go through, they are not particularly very interactive. Some of these kind of games give you certain decisions and in essence provides a bit of a Choose Your Own Adventure style of play. That is not a bad idea as Choose Your Own Adventure books tend to be pretty cool assuming the narrative is right. Unfortunately, once you translate it into video game format, you are expected to have that little extra. Granted that my Japanese is severely limited, the visual/audio presentation as well as the content I come away with has been particularly boring.

If you are expecting 428 to miraculously make reading Japanese on backdrop stills to be exciting, you are definitely on the wrong mindset. 428 takes that format and instead provides the player with something that other visual novels seem to miss, total control.

In 428, you take the role of five character perspectives in a timeline that spans ten hours of a single day in city of Shibuya, a business district of Japan. Multiple characters are nothing new in this genre nor in regular adventure games. 428 also employs decision making for each character to progress the story. That also is nothing new either. But two distinct differences sets this game apart. The first is that the character decisions do have subtle changes on other characters. This allows one character to inadvertently assist or interfere with the progress of another character. The second feature, which I think is the real key to making this entire project work so well is that you can view a time chart of events that have transpired and change the decisions for all of the characters. Hence, while you may arrive at a poor decision causing the demise of another character, you have every chance to go back and rectify it.

Does that make for an easy game? Not necessarily either. Logic plays a huge part in this title, and we are not talking about the 'challenged' logic adventure game developers try to peddle into their products. When you start playing other characters, you will notice details and realize when and how something may have altered the events of another character. And managing five characters while remember key details is not always a straightforward affair. Of course, for non-Japanese players, the language barrier plays another role in adding to that difficulty. Having limited Japanese takes me longer to figure out how events are and sometimes even how the events are supposed to transpire, but it has gotten me pretty far yet. You will inevitably stumble on bad endings, but the game encourages you to take a step back in time and rectify these issues. It is the point of the entire game.

Couple this very neat idea with a very striking presentation style and you have a very engaging adventure title in your hands. Real actors are used in filming and screenshot backdrops of the story and they are adequate to deliver the events of the game. The soundtrack of this title is also amazingly solid. It really does give you a cinematic sense of the entire game.

If there is one complaint over this title, it would be that I would have preferred Chunsoft go a little extra and provide more in terms of visual delivery. For a genre that hinges on story for suspense and substance, it would not hurt to provide video cutscenes alongside the textual narrative to aid in delivering the atmosphere and story.

Albeit, this genre is for a niche audience, 428 manages to deliver a unique experience in spades. It can be slow at times, but it never takes too long to get back to the action and the time chart feature really makes up for it.

Adventure game developers should take some time and look at what other developers in other regions are doing. Sometimes, coming from two different regions provides two different perspectives on how something is done. 428 deserves a look for Western developers. It is a fresh take on a genre that no developer seems to be interested in pushing forward beyond the 1990s formula.

Thursday, June 4, 2009

Multiple running instances of nm-applet! OH NOES!!!

I've always had the notion that wifi support on Linux just plain sucks. And perhaps that's because the few times I have tried to make it work has turned into a tedious exercise of setting SSIDs, whatever keys and what not, not to mention the multitude of security options from WEP to WPA. I've also never particularly bothered with trying to improve my wifi solution on Xubuntu Gutsy install in my Acer Aspire 5920g laptop. That was until yesterday...

The weather yesterday was extremely terrible and with power failures and intermittent internet connectivity issues, I had a chat with a co-worker on how his experience was with wifi and Ubuntu. And he was being straight serious that it was a very painless affair. That perhaps got me thinking of what the bloody hell I was doing with my Xubuntu. I thought it was worth a try to dive in and see what was happening.

I remember having installed wifi-radar a while back as it was, I made a mental note of, the only way I could check for existing wifi hot spots. My friend never had a look at what his Ubuntu was using but after a short inspection he said I should be using NetworkManager.

What's strange is that I already have that running and wifi has always been a nightmare. Checking a bit further, I had noticed from Ubuntu documentation that my wireless setting did not have roaming enabled. And while this was happening, I had tried to manually run NetworkManager from commandline (Mental note: a BIG no-no! That's why this article is entitled like that).

After a reboot, I had found out that I had managed to get the wifi to spot nearby hot spots and connect to my brother's WEP-secured hot spot. I also remembered at that point I had foolishly disabled roaming when I freshly installed Xubuntu. That was real sweet to know, except I had two instances of nm-applet running (you know, the network icon on your system tray!).

After much trouble, I had realized two things. Apart from Gnome having its own startup sequence, XFCE storing my desktop sessions played a part in duplicating nm-applet. Second was that when I ran NetworkManager, it inadvertently let XFCE make a note that I needed to have it running. So, while Gnome would launch the nm-applet as planned, XFCE would start its own. Sweet to know how these problems happen.

In case anyone wonders how to fix that, check your ~/.cache/sessions/xfce4-session-* files. Open them and remove nm-applet entries inside. Save and log out without saving your session.
When you login, you should have only one running nm-applet instance (the one gnome starts).

Alright, that's all for now.

Wednesday, April 22, 2009

Notice on Gutsy Gibbon Users on Apt-Get Repositories

This is a short note. As we all know, Ubuntu has dropped support for Gutsy Gibbon. As we all know, at that point, your Synaptic will also stop operating. Open your /etc/apt/sources.list and update the Ubuntu URLs to point to: http://old-releases.ubuntu.com.

Here's a sample:
deb http://old-releases.ubuntu.com/ubuntu/ gutsy main restricted

This works for all other older, no longer supported releases of Ubuntu. Bear in mind though, if you want to upgrade distributions, you may have to change the url back to the URLs Ubuntu uses for their support distributions.

Just thought I'd just put that reminder out there.

Sunday, April 19, 2009

Apple eMac and Ubuntu: The Journey into the New World

The Journey into the New World



For many years, Linux has been a part of my computing world and it has been almost impossible to part with it. It is one of the most versatile and customizable operating systems I have ever had the pleasure of using. For sure the Linux user base is not as dominant as other operating systems, but the one thing I have learned through years is that we Linux users have been strong as an online community. This community allows us to roll up our sleeves and solve the challenges in Linux as we encounter them, but never are we alone, nor are we without the knowledge to undertake that challenge.

Before you read on, I would like to remind you this is a real lengthy account of what mostly, I hope, transpired. If you are just looking for help, that comes at the end of this sobby and long, drawn out boring article. Check the Full Monty section.

All it takes is a little push...

Most people who hear Linux often view it as an enigma. A mysterious unknown world that will only be useful to a niche audience. Perhaps there is truth in that criticism, but if you have someone to guide you through this journey, you may find yourself discovering a new and interesting world unfold before you. Some may never see Linux as an option to their personal computing, but you will never know if you never even try. And to try and see it for yourself, sometimes all it really takes is a little push.

I often visit Mixed Martial Arts forums to read view points and get into the countless debates on who is king of the hill and who is king nothing, but what I did not expect was to find someone who wanted to try Linux. Someone who wanted to get his feet wet. For reasons only he knows, he has taken that little push towards a new experience.

I could not say no to a plea for help on embarking this sojourn. How could I ever say no to it? To share, and to give someone a chance to learn a new platform, is one of the things that gives me satisfaction. Soon I realize though, as with all things in life, that this would not be an entirely familiar and ordinary affair...

The journey begins...

Thus our correspondence began. Introducing people to Linux is never a straightforward affair, even more so when all you know about the person is a faceless alias. And unlike helping someone who knows and already has gotten his first leap into Linux, throwing a bone is often never enough.

This person, who fondly calls himself 'Simple Jack', has started to give me the details of what he wanted to achieve. As it turns out, Simple Jack had wanted to dual boot his old Apple eMac with Ubuntu. Since I have never really owned anything Apple-related I knew it was going to be an interesting journey for the both of us. But was he biting off more than he can chew? Half of me was convinced that he may not get it done, the other half, was more hopeful. One thing was certain, deep down in my gut, I was sure as hell going to bloody try and help.

For the most part, installing Linux on the normal x86 architecture has been a streamlined and mostly smooth affair, and I was completely expecting powerpc architectures. And as if I needed a hard gut shot as a reminder, it was anything but that.

I had done a few light readings and he had burnt the PowerPC release of Intrepid Ibex. There, the first obstacle had made itself known. The bloody disc would not even boot! To make matters worse, I could not see what was actually happening save for descriptions Jack had thrown through forum private messages roughly at fifteen to twenty minute intervals. If this was our means of communication, I had hopelessly thought that by the time we get the bloody disc installed, an asteroid would have hit the Earth.

The remarkable thing I realized was that while Jack was seemingly always in his self-deprecating mode, this setback did little to put him down. I was going to do my own research, but he was more than willing to go the extra mile and do his homework (Bravo Simple Jack!). As the saying goes, it does take two to tango.

Our initial setback had taken us from one Ubuntu powerpc Desktop CD to a multitude of live discs all of which turned out to be fantastic failures. As he and I quickly realized, the powerpc machines that Apple concocted had been quite the wild beast, as if Apple had devised it to run amok if it had an iota of non-Apple operating systems.

The initial success...

From readings we had pinned our hopes on Feisty Fawn, ye old Ubuntu release and first of the non-official PowerPC builds by Ubuntu, I think. Thankfully, we had upgraded our communication channels to something more instant (ahem, instant messengers). At that point in time, I had already started thinking of alternatives to Ubuntu and the only one that came to mind was Yellow Dog Linux. It was an unfamiliar release to me, but if there was a last ditch effort, it was going to be from blokes who had been building Linux releases on PowerPC platforms.

Before I delved deeper into that, Jack had reported something that was a little different from the norm I was quickly getting accustomed to. Feisty did boot. And for a disc image that was bloody hell difficult to find, it was well worth this first tiny ray of light!

I knew that there was a light at the end of the tunnel, and that it had not been a train all along. Once Feisty booted, I was back into more familiar grounds. But that machine I was beginning to think of as Apple's Little Devil had more in store for us. The next problem was the graphics display.

From early readings, I had come to note that these are known issues and as Jack's Apple folks mentioned, X and the Mac hardware have always had their share of grief and conflict. We spent at least a few days walking through Linux commandline debugging work, hoping to manually hack that xorg.conf. As usual that little devil refused to give in. I was also realizing that finding articles talking about Apple eMacs and Linux was like finding a needle in a haystack.

Houston! We have a desktop... sort of...

I advised Jack to start asking around for help on the Mac communities he knew. If we were going to resolve this, it was likely to come from someone who knows the hardware more intimately. While we had several links to sample xorg.conf files that supposedly should have worked, none have been that silver bullet I had hoped, and manually dictating what to write on the xorg.conf was in and in itself a time leech sucking away at the short number of hours we had in common from the dreadful timezone differences. At the very least he had now become accustomed to the often feared by the ignorant Linux terminal. So much for being the 'Linux for Humans'.

The response when we laid out our cards before his Mac folks had been interesting. When one of them claimed one of the files looked good, I took a thorough look back at the links and fingered the one that made the most sense.

We were going to have another go at this thing, and I was a bit confident it would work. Jack, who to this day I wonder if he ever gets enough sleep, had enthusiastically reported the second victory we garnered over Apple's little devil. But this would not be an entirely smooth one though.

In many instances, the desktop would freeze upon start up which at first boggled me. Thankfully, the two brief and at that time, not very helpful Ubuntu articles on the PowerPC releases had shown their usefulness. We had managed to pin down our issue as the Linux Enlightened Sound Daemon, which did nothing to enlighten our desktop. Worse, it made sure all we had was a very dull brown screen. To be fair, Ubuntu desktops have always been very brown!

The little devil's last stand...

Oh but the little devil for sure did not like the progress we had made through the week's toils. I thought we had been through the worst but the devil had one final trick up its sleeve.

After getting the desktop up via Live CD, we had started talking of how to go about installing Linux. Jack did not like losing the OS X install, but I did not see any other option as repartitioning the disks was not going to save his Tiger. He was adamant about keeping it and I thought maybe there was something that could be done. Boot camp certainly achieved that when Apple decided to open its gates to other popular operating systems.

As we went through a number of articles and readings the name Intel Macs were starting to irritate Jack, as they were blessed with the Boot Camp capabilities. All the Mac-centric articles on non-destructive repartitioning I have come across had been for these machines that, in my opinion, had helped in making powerpc architecture such a neglected platform on Ubuntu and most other popular Linux releases for that matter.

Finally, we had an agreement. The Tiger must die. Blowing the partitions to kingdom come has always been easy, but trying to set the partitions up for our final step into this install had, expectedly, been many times more complicated.

I was not familiar with the means of which Ubuntu needed to boot into Apple hardware. We had learned, a tad bit late if I may add, that not only was the partition editor in the Tiger Install disc a piece of garbage, but also that we had to work with it and at the same time, figure out what sort of setup Ubuntu would deem usable. It was a battle long drawn out and it was back and forth with articles and different things. So close, yet so far.

While I had learned a few things about what Ubuntu needed, the manual partitioning that I liked to use so much was not cooperative. For some reason, it kept babbling about Apple_Bootloader of which I had no clue. It put us on a merry chase and one that I did not always know where we were heading.

The finale...

I would suppose that at the end of things, Jack had to use a different approach than what I normally like doing. The benefits of thinking outside of the box and having a person not afraid to pull that trigger. Instead of doing that bloody manual install that I kept harping about, Jack had gone through Ubuntu's guided install (of course, after OS X was reinstalled with a smaller partition), which at that point I was not betting any eggs on noting the success rate we had with Ubuntu. But then like magic, the install went through and we had two OS installs on the Apple eMac. It was not the result I had expected, but this entire journey the both of us had embarked had proven to be at the very least interesting and definitely an educational experience for both of us.

From there, I knew there were going to be issues with Ubuntu, especially since it is a fairly out of date version, but it was going to be a more familiar battleground. I firmly believe we had finally mastered that wily little devil. And I think at that point it would be more straightforward to advise what to do.

For Jack, he seems to like Ubuntu. There are a few nagging things but this is just the first step into Linux. I can only hope it proves to be a viable platform for him to be productive and at the same time learn more and have fun with it.

Had I not helped, we may not have achieved this goal, but as important as having a community that helps in Linux there was another important element to this. That is having someone willing to learn.

As a side comment, for a machine noted to have been under the so-called 'New World Macs', it sure seemed to be pretty old, and pretty stubborn. Like a grumpy old man. Take that you little devil!

So why did I have to read all this?

Actually, I do not think you needed to. But if you did, a trite thank you and at the same time an apology for being such a time vampire. The article you just read was really a personal rambling of sort. One that I like to do once in a while. But the true purpose of the writing is just around the corner.



The Full Monty



I have always wanted to use that phrase. And now, you will be spared of the colourful words, at least I try to make it sound like. Let us go through the hardware:

Hardware Overview:

Machine Name: eMac

Machine Model: PowerMac4,4

CPU Type: PowerPC G4 (2.1)

Number Of CPUs: 1

CPU Speed: 700 MHz

L2 Cache (per CPU): 256 KB

Memory: 640 MB

Bus Speed: 100 MHz

Boot ROM Version: 4.4.0f1



eMac Display:

NVIDIA GeForce2 MX

Chipset Model: GeForce2 MX

Type: i2c

Bus: AGP

VRAM (total): 32 MB

Device ID: 0x0110

Revision ID: 0x00b2

ROM Revision: 1105.2

Display Type: CRT

Resolution: 1024 x 768 @ 89Hz

Depth: 16-bit Color

Built-in: Yes

Core Image: Not Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

Burning Device - NEC DVD RW ND-3520A

Firmware Revision: 1.04

Interconnect: FireWire

Burn Support: Yes (Vendor Supported)

NOTE: Internal Optical Drive is busted. So we had to use his Firewire Optical Drive.

Hard Disk Capacity: 38.29 GB



Feisty Fawn PowerPC Image Download:

http://mirror.linux.org.au/ubuntu-releases/7.04/?C=M;O=A



Supplemental Readings:

Booting from firewire CD drive:

http://ubuntuforums.org/showthread.php?t=320690

Notes on the Graphics Xorg Problems:

Article on xorg.conf: http://www.linux.com/feature/58044

Apple eMac xorg.conf (From the Article Above):

http://homepage.univie.ac.at/georg.koe/XF86Config/XF86Config-4.emac700nvidia.working

NOTE: Be sure to change keyword from "de" to "en" unless you are Deutsch.

Gnome Desktop ESD Problems:

https://wiki.ubuntu.com/PowerPCKnownIssues#Gnome wont load

Specifically, this area:

Sound problems

There is a kernel bug that causes processes play sounds to hang. When Gnome plays its startup sound it hangs. You may hear the first fraction of a second of the sound.

Press CTRL+ALT+F1. Log in at the text terminal, if needed. Type

killall esd

and press enter. Press CTRL+ALT+F7 to return to the desktop. Go to Gnome's Sound Prefs and uncheck the 'ESD' box, this will allow stop the hang in future log ins.

Partitioning Supplemental Reading:

https://help.ubuntu.com/8.04/installation-guide/powerpc/partition-programs.html

http://penguinppc.org/bootloaders/yaboot/doc/mac-fdisk-basics.shtml



Brief walkthrough of what had transpired

I hope this gives you a good idea of what we did and hopefully this will arm you for your own adventure with the Apple eMac.



Booting the Live CD:

  1. When you put in Feisty and attempt to boot, you need to do somethings to boot the Live disc using the firewire drive. Of course at that point you need to have the disc in the drive! When the computer is starting hold down command (apple key) +option+o+f and then type the following:

boot fw/node/sbp-2/disk:,\install\yaboot

  1. When the LiveCD starts, you will not have a desktop but instead a black screen. To get the terminal, press (and hold) CTRL+ALT+F1

  2. We need to kill the esd sound daemon. Type in: $ killall esd

  3. Copy the xorg.conf file from the supplemental readings part to /etc/X11/xorg.conf. (You can use wget to download it, or you can type it in its entirety if you're a glutton for pain). $ cp xorg.conf /etc/X11/xorg.conf

  4. We need to restart gdm. Do the following

    1. To stop gdm. $ sudo /etc/init.d/gdm stop

    2. To start gdm. $ sudo /etc/init.d/gdm start

  5. In case there are prompts that pop up, all we want is the desktop, use that to determine any decision it asks from you. I seem to remember something like that. To forcibly go back to the desktop, press CTRL+ALT+F7.

  6. The desktop should be up on Live CD.



Partitioning Notes:

We unfortunately did not take enough notes down to definitively say what had happened but we can sort of make some vague guidelines.

  1. You need to wipe clean the disk. We used Ubuntu's installer to erase all the partitions.

  2. On Apple's disk utility, we create three partitions, one for Apple OS X's swap and then the other partitions for Ubuntu and OS X. By my best guess, it should look like something like this:

    • 2.8~ GB swap partition

    • 17.7~ GB Apple HFS (for Ubuntu, I think)

    • 17.7~ GB Apple HFS (for OS X, I think)

    • Bear in mind that by the end of all this we will have two swap partitions, one for Apple OS X and the other for Ubuntu.

  1. Install OS X and be sure to select the partitions you are going to use for installing!

  2. Install Ubuntu immediately after OS X (To boot from Live CD, check above)

  3. Use Ubuntu's Guided Install. It does not seem to like the manual partitioning and we could not get the Apple_Bootloader partition to get recognized. So this was what worked.

  4. By the end of the install our disk setup looked like this:

    • /dev/hda1 - partition map (31.5 KB)

    • /dev/hda2 - (28 KB) - AppleDriver

    • /dev/hda3 - (28 KB) - AppleDriver

    • /dev/hda4 - (28 KB) - AppleDriverATA

    • /dev/hda5 - (28 KB) - AppleDriverATA

    • /dev/hda6 - (256 KB) - AppleFW

    • /dev/hda7 - (256 KB) - AppleDriverIO

    • /dev/hda8 - (256 KB) - ApplePatches

    • /dev/hda9 - Apple_Bootstrap (977 KB) --> not created by the OS X installer , maybe by Ubuntu's Guided Install. Required by Yaboot.

    • /dev/hda10 - (2.8 GB) HFS --> Apple Swap partition. In OSX, Swap - diskOs10

    • /dev/hda11 - Ubuntu install - (17.0 GB) Detected as Apple_UNIX_SVR2

    • /dev/hda12 - OS X - (17.6 GB) --> 17.56 GB. In Mac OS X - diskOs12

    • /dev/hda13 - swap (806.5 MB) --> Ubuntu's swap. Detected as Apple_UNIX_SVR2

    • /dev/hda14 - (128 MB) free

    • /dev/hda15 - (8 KB) free



Hopefully, this helps you install Ubuntu on the Apple eMac. If this helped you dual boot, then fantastic! And good luck! Never give up!