Mal and Weasel’s Tech Crap

IIIITY bitty living space.

Malachai’s got a new rig.

For those of you that may be interested, I’ve gotten some new gaming muscle. As some may know, I have a habit of playing the newest, most graphically intensive games possible. The old machine (a modest AMD Athlon64 X2 at 2.67GHz. I’ll post the other stats below.) had previously been enough beefcake to handle everything I could throw at it. However, about the time Orange Box came out, it had ceased being beefcake, and had dropped to the category of boca burger. Thus after having beaten Left 4 Dead, which played horribly, as well as the new Wolfenstein, and some other rather graphics-intensive games, I decided to throw together a new one. The new machine, a not-so-modest AMD PhenomII X4 965 Black Edition, raises the bar back to ‘Beefcake Dominator’. (Alright, enough with the burger bun… I mean, puns.)

The Old:

AMD Athlon64 X2, 2.67GHz
Western Digital Caviar 320Gb SATA
2Gb OCZ Fatal1ty PC2-8500 (1066MHz)
Asus M2N-MX SE MicroATX
Apevia XCruiser-Black Midtower
EVGA nVidia GeForce 8600GTX 512Mb
Creative SB5.1d Sound

The New:

AMD PhenomII x4 965 Black, 3.4GHz
Western Digital Caviar Black 1024Gb SATA
Hitachi Deskstar 1024Gb SATA
Western Digital Caviar 320Gb SATA
Hitachi Deskstar 80Gb SATA
MSI NF750-G55 ATX
Ultra M923 ATX Fulltower
EVGA nVidia GTX 260 Core 216 Superclocked 768Mb

Thanks to TigerDirect, I was able to put this all together, (plus some) with under $1100 including shipping.

As my good friend Weasel (who’s right next to me right now) says, “It eats green berets for breakfast, and right now, it’s hungry.”

Images

Just recently, (last Friday, if you’re interested…) I picked up three Palm handhelds. Two III series, one ‘x’ and one ‘e’, and a Zire 21. Acting very kid-in-a-candy-store, I got home and started playing with them. I found out rather quickly that the Palm hotsync manager (which has stopped being developed long before the Pre came out.) doesn’t support Vista 64bit or 7 at all. (I use Windows 7 64bit.) So to work around it, I installed Virtualbox on my computer, and a copy of Windows XP Pro atop that. After that, I was finally able to get the Hotsync Manager working, and have been spending my time since getting ebooks, OS hacks, programs, and other related goodness working on two generations of devices.

The programs thus far:

YAHM (Yet Another Hack Manager)
-This program allows me to ‘beam’ OS hacks back and forth between generations of device.

HackMaster
-This is the actual OS Hack manager I use. Works flawlessly, and is fast as hell.

Marbles^2
-The best damn timewaster puzzle game ever.

eReader
-Good ebook reader for palm. Supports the old OS 3.1 that’s on the IIIx, and has full grayscale support for the Zire 21. All-in-all quite good. Also has a DropBook windows client, and supports the PML markup language for creating your own ebooks from html and txt sources.

(Or, the continuing adventures of Zoey the Laptop.)

I’ve mentioned my HP laptop in the past – a Pavilion N5170 that was phased out of production ten years ago. Its age shows, pretty plainly, but a few extra attachments later and somehow I’ve got it playing more games than it has before. It’s becoming my old-games machine more than anything else.

I was at first disheartened that Half-Life somehow dropped to 2 seconds per frame when running in hardware-accelerated mode. But I wasn’t upset. After all, Zoey’s performance in software rendering was quite good, given its Pentium 3 processor clocked at 600 MHz.

Lately, though, I’ve been experimenting with games that can actually put the onboard S3 Savage/IX graphics chip to use, all the while discovering new limitations on what the laptop can do. I’m amazed at how relatively locked-down the hardware is; there are some things that the drivers refuse to let it do, and I know of no way to allocate additional memory to the graphics chipset. (Though that’s only become a problem in one large instance.)

The first game I tested recently was Tom Clancy’s Rainbow Six: Rogue Spear, the game that turned me into a gun nut. I wasn’t impressed with how it completely failed to display the in-game graphics, but then, I had assumed that it needed to run in Software mode. Upon (begrudgingly) setting the renderer to the S3 chip, though, not only did the game display graphics, but it actually looked just like the game used to on the Pentium 2 that I first played it on – right down to the texture filtering!

Then I remembered, I had some old discs for games that didn’t work on Francis (the Dell XPS gaming rig), among them being Star Wars: Jedi Knight. I remembered this game coming out at the precise moment that 3D accelerator cards were coming into fashion, and figured that if my S3 didn’t run it, then I wouldn’t bother with the thing again. To my amazement, it worked at a perfect 60 frames per second – even despite the game running from an ISO (which tends to negatively affect poor Zoey’s hard drive performance).

Here, though, is where I discovered the major limitation. The S3 Savage/IX does not have enough onboard memory to run at any higher than 800×600 with 16-bit color. Any higher, and the game will usually complain about it and revert to a “safe” video mode.

Zoey’s also played host to games that Francis suddenly decided to dislike, such as Links Extreme (with its Demolition Driving Range), Balls of Steel (with its Duke Nukem table), and a couple others that escape me at the moment. Ah, backward compatibility…even though I dislike it sometimes, I enjoy the fact that I don’t need to rely on it!

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.)

Those of us that run our computers with multiple displays have long known that Windows’ multiple display support is…well, somewhat lackluster. To run a game in fullscreen mode is to dedicate your “primary” display to the game, and nothing but the game, usually with no choice as to which screen is considered primary (except through some video card driver settings, which are not the easiest things to get to sometimes). Running a fullscreen game at anything less than your desktop resolution makes the other monitor scale and malform itself, moving any windows you might have had open. And if a game isn’t smart about not letting your mouse cursor “escape” from the game screen, a mis-aimed click could accidentally minimize your game, potentially killing you.

All this time, I thought that was the worst it could get. Then I played SWAT 4.

SWAT 4 is, presently, the last game in Sierra’s heralded police action game. It was released in 2003 by Irrational Games, better known for System Shock 2, and runs on the Unreal 2 engine. Unreal 2’s engine was pretty far ahead of its time, but there’s the problem – the developers assumed that, even though it performed slowly on the hardware of the day, that the load times and such would just speed up as time went on. Problem is, it doesn’t. Having a faster computer with a speedier hard drive and four times the RAM doesn’t affect load times one bit; the game still requires upwards of two minutes to load each level, and should you fail a mission, it has to reload the entire level.

I’m getting a bit off the point though…

SWAT 4, running on the Unreal engine, ought to be friendly towards the people that want to run their games in a window – that is, the people that run dual-monitor setups. Unfortunately, the game has a complete fit if you attempt to run it while a second monitor is active. When attempting to play the corporate logos, the game begins changing screen resolutions repeatedly, assumedly fighting with my NVIDIA drivers over whether or not there is a second monitor active. The game changes screen resolutions ad infinitum, while I can almost hear the music of Sierra’s logo video. This only stops when I press Control-Alt-Delete to open Windows 7’s “panic” menu. From there, I either have to terminate the Swat4.exe process, or wait for it to crash, with a claim that it cannot set its screen resolution.

After three such attempts to run the game, I finally checked to see if my multi-monitor setup was the cause of such issues. After waiting about three minutes for the game to start again (unsure of what it’s doing outside of showing a splash screen and wasting my CPU cycles), the intro videos play perfectly and I’m in the menus. Hmph.

The game seems to run just about perfectly outside of that; well, insane load times notwithstanding…I have no idea why the game is so hateful of extra displays, but I’m pretty sure this is the only Unreal 2 engine game that does this. (Feel free to correct me, though.)

What really sucks, though, is that since this game is over five years old and Activision has already bought out Vivendi Universal (the owners of the Sierra label that published SWAT 4), it is extremely unlikely that an official patch will be made that corrects this. Let it be known, though, in case someone in the future has issues with it: SWAT 4 doesn’t like multiple monitors!

By “popular” request, we’ve opted to run some benchmarks on this paper-thin pugilist. DoomRater posted in the comments that he was interested in three specific benchmarks (thankfully none of which included running Crysis): ZSNES running Contra 3, Project64 running Legend of Zelda: Ocarina of Time, and Soldat running a botmatch.

The first test, naturally, went off with no hitches: ZSNES, being written for x86 assembly and optimized for Pentium 2, proved no difficulty whatsoever for the Mini 12. Contra 3: The Alien Wars ran at a perfect 60/60, showing no faltering and almost no tearing (and no tearing whatsoever once I remembered to turn VSync on). Default settings were proving to be no issue at all. So I stepped it up, beefing the screen resolution up to 1280×800 fullscreen and turning on the HQ3x filter. Still no performance loss whatsoever. I even threw the more complicated games at it – Super Pinball: Behind The Mask, a game making heavy use of the SA-1 coprocessor, also displayed no issues.

Project64 was where the first hiccups began. As the Mini 12 does not have proper video hardware acceleration, the Intel Graphics chip was all we could make do with. Set to the default settings, the introduction of Ocarina of Time ran at roughly half the intended speed, with the sound making horrible stutters all the way. I didn’t check to see if there was a software-only renderer included; I doubt this computer could handle that sort of thing, if it can’t handle it even with an onboard graphics accelerator.

Soldat sounded significantly easier, yet still presented a headache. Upon setting the game up, the program displayed an error that it could not initialize DirectX video and promptly peed itself over the available memory. By the time I could get to its process in Task Manager, it had racked up about 64 MB and was still increasing. Conclusion: Soldat doesn’t work.

So, the Dell Mini 12: too much gaming muscle? Well, it really depends on what kind of game you want to run. If it needs video hardware…you’re basically screwed.

(All tests were performed at default settings unless otherwise noted; testing OS was Windows 7 Ultimate Release Candidate, with a system rated at performance index of 1.9.)

Mal already got down to the nitty gritty of the Dell Mini 12, something of an in-between as far as laptops go: it’s not quite large or powerful enough to be a full-on desktop replacement, but it’s not exactly small enough to be considered a netbook or ultra-mobile PC. The thing is less than half an inch thick, weighs less than a paperback novel, and actually performs better than my current laptop, an HP Pavilion N5170.

The Mini 12 isn’t really considered a gaming machine, yet it holds its own on more than a few applications. This particular Mini came loaded with Ubuntu Linux, evidently quickly replaced with the Windows 7 RC, which as predicted, runs significantly better than my ill-fated and ill-advised attempt at emulating it via Virtual PC (which, admittedly, would probably have gone better if I’d used VirtualBox or VMWare). Malachai mentions to me that the OS will probably also get replaced with Win XP or such. The Mini 12, jack of all OS’es, master of…some? Wonder if you could put Windows 2000, BeOS 5, OS/2 Warp 4, or most of all, Hackintosh the thing and make it run OS X Leopard?

I’m pretty satisfied with this thing and kind of want one of my own. (psst, give me some money, Adecco, so I might buy something!)

On a slightly more tech-ish note than my previous post:

I’ve just purchased a Netbook. I’d sworn to myself a long time ago that I would never purchase an underpowered, tiny-keyboarded little laptop. God was I wrong. The minute I picked this little thing up I was sold. It’s a Dell Mini 12. This thing is so light that I could carry it in a backpack and never even notice it. It weighs less than most of the books on my shelf. (Truthfully, I just weighed it by hand along with my desktop’s keyboard. The keyboard was heavier.) Currently, it’s running an RC version of Windows 7, but I’m not sure how long that will last. Probably only until the person I bought it off of gets me the Windows XP CD that it came with. Win7 is pretty and all, but it just ain’t great enough for me to keep on this underpowered little system. (Also quite truthfully, even with a 1.33GHz processor, and only 1Gb of RAM, this thing seems to scream. It starts in about 30 seconds, and most programs start up in only 3 or 4 seconds.) It has a great little wireless card that gets a better signal than just about anything else in the house, and a little webcam at the top of the screen.

Performance Overall: 8/10
Processor: 5/10
RAM: 6/10
Graphics: 5/10
HDD: 8/10 (For a netbook.)
Screen Size and Realestate: 8/10
Webcam: 8/10
Wireless: 10/10 (Amazing reception.)

Form Overall: 9/10
Size: 8/10
Ease of use/typing: 7/10
Weight: 10/10 (Light as a feather @ roughly 2 pounds.)
Stylings: 8/10 (A nice looking black-silver-white combination.)

Overall Thoughts: 8/10 (Definitely worth a look.)

This pearl of wisdom was once said to me: if you really want to learn how to do something in Linux, all you have to do is go into a Linux-centric IRC channel and shout, “Linux sucks because [insert issue here] and it works fine in Windows!” They might have been right. I just don’t have the balls to do it.

The issue in question is voice chat. I need to use Ventrilo – because it’s the only voice chat client Malachai is comfortable with – and there is no suitable version for Linux. Running the Windows version through Wine is also proving difficult, as it not only does not recognize my USB headset, but also fails to receive audio due to the codecs being missing.

Particularly telling is this post from UbuntuForums:

Not that I’m bitter, but I posted details of how to run the Windows client on Linux using Wine several times on their forums, only for it to be removed… repeatedly, and I just recieved abuse when I complained about it…

I also don’t see why the Linux forum on the Vent site is locked, or why a Linux client has been “Coming Soon” for almost 3 years.

IMHO, just use Teamspeak instead.

So yeah. One more reason why I can’t just leave my main computer booted into Linux all the time.

The Silver Machine lives again.

It took me all of half an hour to return Silvermachine, my deliberately-aged DOS rig, to a glory not seen since 1996. I had previously tried to install Windows 95 on it (chronicled in my last post, more or less) and basically totally blew it up.

Today, all it took was a freshly-burned copy of FreeDOS 1.0, a quick backup of the C drive (just moved all its contents to D, really), and then a nuke-and-reload. FreeDOS 1.0, with Windows 95 Service Pack 1. An easy-as-pie dual boot system.

“That’s it?” I asked myself. Well, I did have a system that could run Slam Tilt Pinball at 100% without any issues – but my more recent laptop can accomplish much the same feat. So I took it one step further, and rifled through Dad’s stash of old PC hardware. (He regrets hanging on to all that old stuff, but it’s saved my ass on several occasions now.)

The treasure was found: a Creative Labs 3D Blaster Voodoo 2, the same video card that got me through the days of Quake 2, Jedi Knight, and Tomb Raider.

It took virtually no effort to plug the thing in, alongside the Diamond Stealth 64 Video. Voodoo cards can’t render everything by themselves; they only render 3D. Everything else needs to be handled by a 2D card. The two cards are connected by a VGA crossover cable. It’s also possible to daisy-chain a second Voodoo 2 with another crossover cable, and enable a special driver setting for Scan-Line Interleave (SLI, before NVidia made it popular). Unfortunately for me, this requires me to have two identical 3Dfx Voodoo 2 cards (same brand and everything), which I don’t have. Admittedly, there are third-party drivers available that enable SLI to work between two different kinds of Voodoo 2 cards, but I didn’t feel like digging for a second card or messing with said drivers.

The card installed and the drivers in diagnostically working order, I needed something to test it with. The first thing I pulled out of my ever-increasing stack of “CD’s That Will Run On Silvermachine” was Tomb Raider 2.

I’ll go on record to state that I didn’t really like the Tomb Raider games back in the day. The more recent ones by Crystal Dynamics aren’t too bad, but I didn’t much like the originals. Though I was willing to forgive control issues and the fact that I got mauled by a tiger in the first level, over the sheer awesomeness that is Voodoo. (And the fact that TR2 only takes up a meg of disk space, as the whole thing is run off the CD-ROM. Since space is at a premium with only two 500 MB hard drives, this is a godsend.)

So, yeah – Silvermachine is rocking again, and do not mock the Voodoo.