Mirror’s Edge

Thanks to three Best Buy gift cards, I was able to buy three games: the Game of the Year Edition of Oblivion, the Enhanced Edition of The Witcher, and Mirror’s Edge. I started with Mirror’s Edge. The sense of movement is incredible – the way you can run across rooftops, vault fences, slide under pipes, and roll after a fall are amazingly believable and well-realized. This is clear even as the GeForce 6800 in my weaker rig struggles to run the game. The concept is an amazing one. That said, the controls, while usually responsive, sometimes feel inconsistent. For instance, the roll move after a long fall is executed by holding the low movement key when you’re about to hit the ground. It took me many, many frustrating times in the tutorial to pull off this move, and when I did, it didn’t seem like my input had changed at all. Even after completing the game I can’t manage to pull it off all the time. I found some of the puzzles difficult to finish because I could not get my character to perform the correct moves. My first thought was that the strange control scheme was due to the game being designed for consoles, where buttons are limited, but upon reflection it seems they are oversimplified. There’s a jump button, a lower action button, a rarely used walk button, WSAD for movement, mouse for looking around, and mouse buttons for combat. That’s it. This makes the game figure out what you want to do, whereas I might prefer dedicated buttons. Although this abstract control scheme has its benefits, it can be frustrating if the game does not correctly interpret your intent.

From a higher-level standpoint, while I understand that DICE are telling a story, I felt they often let it get in the way of the amazing freerunning concept. The story itself is not very well defined, with a vague to nonexistent background. I didn’t care about the characters much, to the extent that when things happened to them, I either didn’t feel much of anything or just laughed at the story’s absurdity. (To be fair, I only laughed once, and that was a misunderstanding on my part.) I was many times forced into loosely story-related combat situations where I had to either perform disarming quicktime events, (which are especially frustrating with some of the tougher units later on) melee people, or attempt to find my objective under fire. While health regenerates, much like Portal, it seems like you can only take two shots before going down. This really breaks the flow of things as you are forced to either run into the line of fire, and thus risk a quick death, or cautiously dart between bits of cover. To be fair, the sequences where I had to avoid sniper fire were fun, but having to face five or so armed guards in a room wasn’t so great. You cannot save at will, and instead must depend on checkpoints. This leads you to replay entire sequences instead of starting from a point where you might have saved if you could. It makes me appreciate the Source engine even more. I now understand why Valve does not generally have someone on a radio in your ear, and instead might give a few directions and step back. The tech on the radio talks rather frequently, sometimes with helpful information, sometimes pointing out the obvious, and other times nagging if you don’t solve a puzzle fast enough.

It seems whenever it gets frustrating, I find something awesome and forget about the problems until they once again surface. The concept is amazing. Although oversimplified controls and frustrating combat get in the way, and can be pretty aggravating, in the end it’s still worth it for the running.

I should mention that the music is nice, too.

EDIT: Unfortunately, now that I’ve started the time trial portion of the game, I’m finding the control scheme to be much more of a problem.

Published
Categorized as Games

Cables, Infections, and More!

A few days ago I brought my desktop over from Dad’s and set it up at Mom’s, along with a switch to connect both desktops to the network. Someone accidentally bumped the switch, and the cable that brought the network connection up from the basement could not be wiggled back into working again. My hasty crimp had given out. I took my single remaining cable end, and managed to, after maybe two tries, get what seemed like a flawless crimp. Only having one end, and thus one chance at crimping to get online, was a very powerful motivating force. Upon further inspection it is not perfect, but it’s better than other crimps I’ve made. Maybe the loading bars I anticipate getting will help.

I cleaned up a machine at KI that was very badly infected. Our tools took care of the infection, but what took me a really long time to realize was that ndis.sys had been infected and deleted by the scanners. Everything was working except for networking devices, which showed up with corrupted drivers. Fresh drivers did nothing, and uninstalling the drivers did not actually seem to do so. Copying ndis.sys over from another machine fixed the problem.

My Dad sold his house, and we have now moved to Wendy’s house. At this point my room has no blinds, and my desk is in pieces. My room has the feeling of a LAN party in a metaphorical tornado – there are objects one might expect to find in a bedroom, except in strange locations and often not assembled. I hope this gets sorted out somewhat quickly.

AT&T

I feel foolish. I moved the modem to my communications closet so that it would be more difficult for Mom to accidentally turn it off in preparation for a storm, but forgot that I had changed my email password. On my first try I failed to get a DSL signal when running it through a surge protector, so I ended up running it only with an extension. I was confused because the modem’s tests all passed, and both the connection and DSL were listed as up. I could ping whatever I wanted to, although AT&T was redirecting all my traffic to some strange password mismatch page, and traceroutes timed out. (Why not “incorrect?” “Mismatch” confused me into thinking it was set to my mom’s email and my password or something.) I was too worked up over the fact that they were hijacking my traffic to take into account the possibility that AT&T was correct that the password was wrong. I feel bad for wasting their time, but on another note I think that assuring customers that a password utility that requires an executable download is legitimate simply because they continue being redirected to it is not the best way to go.

Published
Categorized as Hardware

Zombie 6 Version 2

Zombie 6’s problems seem to be due to a capacitor that was bent until a pin ripped out of it. The only way I might be able to fix this is ordering a new capacitor off the Intertubes, removing the old one, and very carefully soldering on the new one. That likely won’t happen soon, if at all. I got a Pentium 3 @ 866 MHz board with 512 MB RAM from KI. I was very impressed when I was able to just put the board in the case and fire up Debian, which had been booting an Athlon, presumably with an entirely different chipset as well. At this point the ethernet device was named eth1, which was annoying, so I went into /etc/udev/rules.d/70-persistent-net.rules, commented out the eth0 line, changed the name of the new one to eth0, then rebooted. I also commented out the old entry for the optical drive, under which it was on a different IDE channel. For whatever reason, to get networking functional, at each house I had to set the interface to DHCP, restart networking, then set it to static and restart networking again. I’m trying to find out what that does, and why it works.

Published
Categorized as Hardware

TX Underrun

Ever since I set it up, once my pfSense box has been running for a while it seems I will plug in the monitor to find two, three, or more messages about TX underruns, such as

dc0: TX underrun -- increasing TX threshold

However, my network started being slow to respond on the 6th, going so far as to drop one packet when I pinged Google. The LAN side was just fine. Yesterday I plugged the monitor into the router to see what was up, as I was unable to find a system log of console messages. The last message was

dc0: TX underrun -- using store and forward mode

My understanding is that this is why it became slow. This machine is not screaming fast by any means. It has 504 MB of RAM and a 499 MHz Pentium 3. Looking in the WAN interface settings, I realized I had misunderstood and set the wrong MTU. I saw the size for PPPoE, and given its mention in my modem’s configuration, I had understood, incorrectly, that my router would use PPPoE. (Even though the WAN interface was visibly set to DHCP on that very page.) I now do not know why I felt the need to set this manually, and as I reread my modem’s status page I feel more and more mystified as to how I came to that understanding: PPP on the modem (Public IP for LAN device). I left the field blank as to allow pfSense to set the MTU,  and my WAN connections are speedy again.

Cats and Overheating

It seems we now have five cats. I’m looking into options for filters so my heatsinks aren’t clogged with all the cat hair. It’s far easier to brush things off a filter than blow them out from between heatsink fins. I should also renew my efforts to get our machines off the ground so they act less like vacuums. I really don’t understand the thought that went on in this decision, and in some ways doubt it occurred.

In other news, Zombie 6 started making an alternating tone, and it was only when I installed a sensor kernel module that I discovered:

$ sensors

acpitz-virtual-0

Adapter: Virtual device

temp1: +60.5°C (crit = +65.0°C

w83697hf-isa-0290

Adapter: ISA adapter

VCore: +1.74 V (min = +0.00 V, max = +0.00 V) ALARM

+3.3V: +1.52 V (min = +0.14 V, max = +2.05 V)

+5V: +4.78 V (min = +0.05 V, max = +1.72 V) ALARM

+12V: +12.16 V (min = +0.43 V, max = +0.49 V) ALARM

-12V: +2.11 V (min = -3.07 V, max = -13.59 V) ALARM

-5V: +0.33 V (min = -7.71 V, max = -7.71 V) ALARM

V5SB: +5.59 V (min = +0.22 V, max = +0.00 V) ALARM

VBat: +3.07 V (min = +0.00 V, max = +0.00 V) ALARM

fan1: 5192 RPM (min = 168750 RPM, div = 2) ALARM

fan2: 0 RPM (min = 8881 RPM, div = 2) ALARM

temp1: +33.0°C (high = +12.0°C, hyst = +16.0°C) ALARM sensor = thermistor

temp2: +60.5°C (high = +60.0°C, hyst = +55.0°C) ALARM sensor = thermistor

beep_enable:enabled

I really hope either the default rail voltage ranges are somehow wrong, that the CPU overheating was leading to strangeness, or that I’m misunderstanding something, because if those are the rails’ actual voltages, I’m surprised the machine was still running and not on fire. Ranges including 0 seem weird, I don’t know if it’s listing acceptable variance from the stated voltage, and if so it seems in some cases too wide a range for normal operation. It’s probably not seeing a rotation speed for fan 2 because if I recall correctly it’s running off molex. I should add some sort of temperature monitoring to my machines. I will probably have to reseat a heatsink in the near future. For now the machine is off and unplugged – it’s unplugged just in case the PSU is really that broken and the 5V rail might do something nasty.

Zombie 1 PSU

When I went downstairs to check for water leaking into the basement during the storm last night, Zombie 1 was making weird noises. I powered it down and today found that it seemed that the PSU, not the optical drive or hard drive, was making the weird noises. This is a shame for many reasons. I don’t really need an optical drive in the thing, I have many spare 3.5″ IDE hard drives, and the PSU is a weird one that’s the wrong shape. Even if I bought a normal PSU and connected it from outside the case or something crazy like that, it would likely cost more than the machine cost me in the first place. At this point I’ve turned it back on and I guess we’ll just see how long it will last. This feels oddly sad.

EDIT: It is no longer making strange noises, at least for now.

Published
Categorized as Hardware

Hate Gun

Behold! We made this during robotics. Click for the original. It’s somewhat messy, but still amusing.

Click through for the original.

Published
Categorized as Life

Mail

Today I learned that the proper way to check system mail on a Linux box is not by moving or deleting files from /var/mail, but using the mail command. Imagine that! I had to read the man pages to figure out how to use it, which is to be expected for a command line utility. I’m also looking at rdiff-backup to see if I can use it for real, scheduled and incremental backups instead of the current full-backups-when-I-remember system. (Please don’t hurt me for admitting it! I’m not proud to say it!)

EDIT: Daily backups are now scheduled.

Published
Categorized as Software