Mal and Weasel’s Tech Crap

About this time last month, we had our Verizon-provided router die on us. Well, maybe the router itself didn’t die, but I had noticed that the power cable (a standard “wall wart” type) appeared to have warped a bit. Lacking money, I called Verizon to get them to ship me a new router.

That router showed up after a week. Took ‘em long enough, I thought, hooking up the replacement router (while first checking to see if the power cable would fit in the old one…it didn’t). This router somehow completely failed to connect to the internet, after three hours of it attempting to ping the ISP. So another router showed up in two days. This third router succeeded in getting the family back online, at least enough to browse websites and play World of Warcraft (which is really all my parents seem to care about, ‘Net-wise).

Unfortunately, this router being a slightly different model from the previous one, has quite a different web interface than before. It looks similar, and in fact the instruction guides are almost identical, but there are little things that prevent it from being as friendly as the old one.

Little things like, well, port forwarding. This router has absolutely failed to allow me to forward ports for things like serving files outside the LAN, hosting games on Skulltag or Half-Life, and seeding for BitTorrents. In some cases I can’t even join other peoples’ game servers. Even wireless support seems to be dropping the ball, with my XBox 360 being, at times, unable to connect to the Internet at all. This was not the case with the other router. Setting up port forwarding through the front-end proved to be a frustrating experience, even for Malachai, who does this sort of thing for a living. After three hours of fiddling about with it, neither of us were capable of getting my Linux server (Ferretcage) to have any presence outside of the LAN. There goes one of the main reasons why I set the thing up.

I am most displeased with this router, and I am not sure I trust Verizon to provide more. I might as well quit while I’m ahead, though, considering that if I were to get another router, there might be a chance that it’ll have an even more frustrating front-end than this one. Malachai continues to recommend that I buy the same model of router that he uses; that might actually be an option, but I’d need to keep this router around, assuming his model doesn’t have an Ethernet Coax port with which to serve Verizon’s FiOS TV channel guide and on-demand programming. (No idea why the cable boxes aren’t hooked up with Cat5 ethernet or similar.)

I’ve just had my first experience programming in PHP. What was it, you ask? Well, about six months or so ago, I created a World of Warcraft Private Server on my computer, using a piece of software called MaNGOS. The “Massive Network Game Object Server.” MaNGOS uses MySQL to store all of it’s data.

One problem. The only way to create/delete accounts, or to change the passwords, is to either directly manipulate the SQL using something like SQLYog, or to use the server window to issue Admin-level commands to the server. That was unacceptable. There are also no good PHP frontends for MaNGOS, to do this for you. So, in my infinite wisdom, I decided that I would create my own. I created a HTML/PHP/MySQL script that, when used correctly, is able to create/delete/ and change the passwords of accounts.

Eventually, I will set it up to sanitize the database inputs, so that malicious code can’t be run using it, and then I will post it up here, so that anyone else who cares to create a MaNGOS server won’t have to deal with all the crap that I have.

My poor old HP Pavilion has sure been through a lot lately, having had its OS replaced approximately 8 times, the hard drive formatted for 5 of those. It originally shipped with Windows Millenium Edition (puke), its previous owner mercifully replacing it with Windows XP Home with Service Pack 2. I, however, found performance under Windows XP to be less than optimal, and many of the programs (i.e. games) that I wished to run on it simply wouldn’t agree with XP, or would otherwise choke at the system’s lack of video acceleration and/or DirectX 9.0 support. (Game Maker, I’m looking at you.)

So the first thing I did was stick Windows 2000 Professional on it. Performance was actually somewhat better than before, all my drivers still worked, and, most importantly, Slam Tilt Pinball worked (finally). Though as time went on, I found that Windows 2000 still didn’t suit my needs, and wondered if there was a flavor of Linux that would agree with it. So I ran down the list. Condensed version of my various attempts and findings below.

Xubuntu 8.10
I found that Xubuntu didn’t have enough memory to even install, and upon using the Alternative installer, had several read errors and eventually screwed up my boot sector (see Boot Loaders Suck).

Puppy Linux 4.2.1
Puppy actually ran from its LiveCD surprisingly well. I was highly pleased with it – until I learned that it was next to impossible to install to hard drive. (I realize that Puppy isn’t supposed to be installed to a hard drive, but it seemed like a good idea at the time.)

Damn Small Linux
DSL installed quite comfortably and even ran pretty well, but this was when I first became acquainted with the ridiculous things one needs to do to get a wireless card working in Linux. I hate you, ndiswrapper. Also, the package manager didn’t work for some reason, so I couldn’t get apps that I needed.

Debris 1.0.4
This one looked promising, until I learned that APT was connected to a very old Ubuntu database that no longer existed, and I unfortunately was unable to figure out how to set it to multiverse. Then, well, more ndiswrapper nonsense.

Fluxbuntu 7.10
Not only did APT actually work on this one, the installer acknowledged the existence of, but still didn’t know how to use, my Linksys WPC54G wireless card. More ndiswrapper nonsense later (and with heavy assistance from Malachai), I realized that ndiswrapper wasn’t even treating my wireless card as wlan0 like it was supposed to, but rather eth1, rendering it essentially useless. Default desktop settings were very pretty, though.

Tiring of all this open source stuff, I opted to just nuke the hard drive again and load up Windows 98 SE. This is an OS that I am extremely, intimately familiar with, having learned just about all of its quirks and tricks. Plus, Linksys’ driver CD supports 98, I can get mass storage drivers working very nicely, and basically I wonder why I didn’t just load Win98 on it in the first place. Since, well, that’s essentially what the darned thing came with to start with!