Category: Tech

Buggy Messes

I had some harsh words yesterday for the EaseUS software for Mac. Mainly, it constantly locked up and didn't do much of anything.

I'm not quite ready to let EaseUS off the hook just yet, but I'm seeing that same behavior in a lot of programs now. At this point I'm pretty confident that, in setting my Mac up to run like a Hackintosh, I have wound up with a system that has all the stability and reliability of a Hackintosh.

Regrettably, I'm having much the same problem with MIUI, which I installed on my phone the other day (as something to do while I waited for diags to run on my Windows 8 drive). It's slow and it crashes like a motherfucker. I really think the monthly release cycle is a pretty poor idea; what we've got is bleeding-edge code (in this case Jelly Bean running on a phone that was never meant to support it) instead of stable code.

Which is a pity because there's really a lot to love about MIUI. For starters, it's the most paranoid OS I've ever seen -- its security settings are granular as hell; it doesn't just tell you what data your program is going to have access to at install time, it defaults to warning you at access time, too -- and giving you the opportunity to refuse.

Trust the Chinese to be thorough about who's listening in on them.

It also comes with a lot of mostly-pretty-useful programs out of the box.

Except that weather program. The one that thinks I live in some place called Temperanceville (and that's not autocomplete on me typing in "Tempe", that's the location it automatically set itself to), consistently tells me I have no network connection even though I have a network connection, and can't be uninstalled. I don't like that one very much.

So I don't think I'll be sticking with MIUI. I guess the question is whether I should just restore CyanogenMod 7 from backup, or try some other ROM.

Decisions, decisions...

TestDisk

I guess I was overdue for doing something monumentally stupid and sloppy, because Friday night I went to format an external 1TB hard drive and accidentally formatted my internal one instead -- the one with Windows on it.

Now, after a moment's panic, I realized that I didn't have anything vital and irreplaceable on there -- I had backups of my resume, my password wallet, things like that. I hadn't backed up my financial spreadsheets or work search log in a couple weeks, but I could reconstruct those if I absolutely had to from my bank statements and E-Mails. And I had a Mass Effect 2 save that was maybe an hour farther along than my backup.

So, nothing life-or-death. But I'd still just as soon not have to take the time to reinstall Win7, reinstall Win8, reconstruct my spreadsheets, and replay that last hour of ME2 if I could avoid it. And I knew it was just a quick format, so my data should all still be intact on the drive -- it was just a matter of getting to it.

I was booted to OSX at the time, and the first piece of recovery software I found was EaseUS. It was a free trial for a $90 piece of software. Now, I knew going in that there was no way my lost data was worth $90 to me, but I figured I'd see how far I'd get with it.

Not fucking very.

You'd think a trial for a $90 piece of software would be designed to make you think the software was worth $90. Instead the fucker just kept hanging -- I might, might get as far as it displaying all my disks and partitions, but after that (or, just as frequently, before that) it would just lock up, static unresponsive window, Spinning Beach Ball of Death, all that shit.

So then I stumbled upon TestDisk. I missed the part where it said there was an OSX version, so I rebooted to Linux to see if I could install it.

And found that my OpenSUSE boot had somehow become hosed too. (I would later find out that this was not a coincidence and that OpenSUSE actually goes into Emergency Boot Mode if it fails to load a filesystem in its fstab. I did not consider this at the time because (1) I was very tired and (2) Linux failing to boot because it can't mount a Windows drive is the stupidest fucking thing I have ever heard.)

But fortunately I still have my old Kubuntu drive onhand, and it was not only able to boot, but it already had TestDisk installed, with no worrying about having to fuck with repos. I think it may even be part of the basic Ubuntu installation.

Now, there's a lovely step-by-step guide at the TestDisk site called Recovery of Reformatted Partition.

The bad news: I spent yesterday trying to recover the drive and never did get it to work, and I'm finally giving up the ghost because it's just not worth fucking with it any longer. But I figured I'd put this up here just in case you have better luck with it than I did. I had a hard time, in my initial search, finding a good listing of Linux software to use to try and recover an NTFS partition that has accidentally been reformatted. Maybe somebody will stumble across this page in a similar search someday, and find TestDisk as a result.

Again, it didn't work for me -- but it looks like a solid piece of software, and it's worth a shot. (Unlike EaseUS, which is a piece of crap you should not waste your time with.) Good luck.

Why KDE?

I just switched from Kubuntu to OpenSUSE. I plan on writing a bit about my experience, but it occurs to me -- people may wonder why I went with OpenSUSE.

Well, the answer is because I've seen various reviews saying OpenSUSE is the best KDE-based distro -- so the question then becomes Why KDE?

I've preferred KDE over GNOME since about the KDE 2.x/GNOME 1.x era. And I think the bottom line is customizability.

I never much liked the look-and-feel of GNOME, not even in 2.x. The Apple-style system bar across the top of the screen without the Apple-style integrated menubar -- that's just wasted space.

But it could be worse. It could be GNOME 3.

Image: Wasted Space in GNOME 3

I liked KDE3 better than 4, but 4 got to the point of being passable. Even if it's still missing basic functionality like being able to right-click on a launcher to change its shortcut settings. In fact the whole "Show a Launcher When Not Running" feature (an overly-verbose version of MacOS's "Keep in Dock" and Windows 7's "Pin to Taskbar") is pretty damn broken -- I can't get it to work at all with LibreOffice. (Well, I mean, I can get it to show a launcher. Just not one that works.)

So okay. It's pretty far from ideal. But XFCE and LXDE aren't exactly rolling in GUI-based configuration options, and the simpler WM's are worse still. So KDE it is, for now.

Triple-Booting a Mac Pro: Legacy Edition

Well, it's been a pretty exasperating few days, but I've successfully gotten my old (2006/1,1) Mac Pro set up to triple boot Lion (with a 64-bit kernel), OpenSUSE 12.2, and the Windows 8 Release Preview.

First, I set up Lion. I followed Jabbawok's Mountain Lion guide exactly, with one exception: since I was installing Regular Lion and not Mountain Lion, I didn't need to alter OSInstall.mpkg to skip the motherboard check. (As far as drive bays: I put the installer hard drive in bay 1 and the Lion drive in bay 2.)

After this I found that I could only get the 64-bit kernel if I used Chameleon's flag for Safe Mode (-x). Otherwise I got a blank gray screen on my helper card and a white screen with a frozen mouse pointer on my main card. This fixed itself once I yanked the helper card -- but I'll get to that in a minute. If you've got a helper card and you're following this guide, don't remove it until you've got all 3 OS's installed and get a nice clean GRUB menu when you boot. (Or a stupid-looking light-gray-on-bright-green GRUB menu, as the case may be.)

Anyway, after setting up Lion, I set up Boot Camp and tried to install Win8 (on a drive in Bay 3). I got the ol' "Select CD-ROM Boot Type" prompt where everything froze and failed to recognize any input.

I'd dealt with this years ago when I first set up Windows 7; I had to bootstrap my install disc. I decided I would just as soon not fuck with that procedure ever again, so instead of bootstrapping Win8, I used my already-bootstrapped Win7 disc to install Win7 and then upgraded to the Win8 preview from there.

And then I installed OpenSUSE (over the Lion installer partition in bay 1).

The OpenSUSE install DVD gave me the same "Select CD-ROM Boot Type" prompt freeze, so I tried the OpenSUSE KDE LiveCD -- that one worked just fine.

And after I'd installed OpenSUSE, I found that my computer had set itself up to automatically boot straight to the GRUB boot prompt. And, better still -- it had correctly set up Windows and both 32- and 64-bit kernel boots for OSX. Chameleon was totally redundant and unnecessary by this point.

The trouble? GRUB had the same problem Chameleon had: OSX would lock on boot unless I ran it in safe mode.

So that's when I popped out the helper card.

(Don't know what a helper card is? Then you don't need to know about it. But the gist is this: my Mac Pro came with a GeForce 7300GT graphics card. Last year I upgraded to a GTX 570. While current versions of OSX do recognize the GTX 570, the EFI boot firmware does not -- so I needed to leave the 7300GT plugged in to see the boot menu.)

Once I popped the 7300GT, everything worked great -- the GRUB menu came up, and booted any of the 3 OS's without any trouble. Success!


Or at least, success until earlier today when something got fucked up and broke everything and I spent my entire day trying to fix it. Ultimately it appears to have been a weird fluke -- I think my partition table got corrupted somehow, because I found that even a format/reinstall didn't fix the problem; I had to actually repartition (the Chameleon/OpenSUSE drive) to get it working again.

So that sucked. And is the second time in two days I found myself chasing down help pages for the last line of a boot log only to find it had nothing whatsoever to do with the actual problem I was having. What a damn bummer.

The upshot, though, is that I've got a 64-bit kernel working in OSX, which should let me set up the RAIDZ array I wanted to put together for my grandmother's home movies.

And last night I played Mass Effect 2 for an hour or so without getting a BSOD. Could be just a coincidence, but I'm hoping that removing the helper card and booting from GRUB instead of EFI fixed the constant crashes I'd been having before.

Next I'll try it under WINE -- maybe I won't have to reboot to Windows at all anymore.


As for how I feel about Macs, Windows 8, and OpenSUSE...well, those are all ripe topics for another day.

Reinstallating

Decided that, now that I've got more free time, I may as well give my computer a clean install of everything.

For OSX: Attempting to install Chameleon Bootloader so I can use a 64-bit kernel.

For Windows: Trying out the Win8 Release Preview.

For Linux: Switching to OpenSUSE.

So far it's been rocky. Something's not quite right with Chameleon and I can only boot OSX in 64-bit mode if I do it in safe mode. Haven't been able to determine where the problem is, as the last few lines of verbose boot happen whether it's in safe mode or not. If it's not in safe mode I get a freeze on a white screen, with mouse pointer visible. While I'm considering trying to upgrade from Lion to Mountain Lion to see if that fixes the problem, I've seen people report similar issues in ML and I wouldn't want to spend $20 on discovering I still have the same problem. (Plus if I switch to ML I won't be able to fall back to a regular, non-Chameleon EFI boot like I can with Lion.)

Win8 -- well, it's set up. The parts that look the way they're supposed to look pretty damn good; the icons, tiles, and fonts are all really attractive. A lot of legacy stuff -- like program installers -- looks like blurry hell, but I'll give MS the benefit of the doubt and suggest that maybe that's because I'm using a beta. Not sold on the Start Screen yet, the shit that's moved is not easy to find, and switching between Metro and Oldschool-Style programs is unintuitive as fuck.

As for OpenSUSE, well, haven't had time to install it yet. Stay tuned.

Adventures in Unemployment: Contact Quotas are Dumb

I reapplied for unemployment on Friday afternoon, right after completing my last day of work.

On Sunday I logged in to see if I was in the system yet and if they'd let me start filing claims. Sure enough, I logged in successfully and it let me fill out information for the week -- even though it was last week, when I was still working. (Before I go any farther, let me make it perfectly clear that I reported all my income for last week and will not be receiving any money from unemployment for a week I was still working. All I did was go through the motions to make sure everything was working for next week.)

Everything worked much the same as a year and a half ago when I last did this, except that I was already in the system after two days (rather than having to wait a week like last time) and -- and here's the part this post is really about -- they've added a section where you have to log the contacts you've made over the past week in your job search.

Now, that in and of itself isn't a bad thing. I've been keeping every contact in a spreadsheet anyway. And I think it's perfectly reasonable to ask my to copy-paste that information into a text field and submit it every week -- hell, if I do get audited, that's going to save on paperwork.

The problem is that, thanks to a new federal requirement which I assume was a condition of the latest extension of unemployment benefits, they now require that you contact people at least four days in each week. To prove you're seriously looking for work.

This is one of those things that sounds like a good idea to government bureaucrats but is just fucking stupid out here in real life.

Yes, by all means there should be a standard for determining that someone is seriously looking for work and not just cashing unemployment checks and sitting around playing Xbox (provided he hasn't pawned it yet because he's unemployed). And "looking for work four days a week" is a pretty modest standard for that.

But when you actually make it a requirement? A quota? Now you're giving people a bare minimum. And when you give people a bare minimum, you're going to find that a whole lot of people only meet that bare minimum. Think "pieces of flair" in Office Space.

This sends the message that a person who looks for one job Monday, one job Tuesday, one job Wednesday, and one job Thursday is more serious in his job search than a person who looks for ten jobs Monday, ten jobs Tuesday, and ten jobs Wednesday but then spends Thursday and Friday doing other Responsible Adult Things like paying bills, going to the doctor, applying for warranty repair on his laptop, getting his tires rotated, and studying up for certifications that might help him in his job search.

Obviously this is designed to encourage people to Seriously Look for Work instead of just collecting unemployment while doing nothing. That's a laudable goal. But in practice, people who are out just to collect unemployment while doing nothing aren't going to expend any more effort than before this regulation passed -- in fact, they might actually expend less now that they know they only have to apply for four jobs a week.

Meanwhile, it's an inconvenience for people who are seriously looking for work, because now they actually have to game their way through and make sure they don't just apply for multiple jobs, they do it across four days.

I got a call from the agency this morning, and they scheduled an interview for Friday. Boom -- that's two different days; I was halfway done with my required job search for the week by 10:30 Monday morning.

If I was the kind of guy who was only interested in doing the bare minimum to collect unemployment, instead of actually getting a job, I would call it a day and then look for two more jobs later in the week.

But of course I'm not. I'm going to spit-shine the ol' resume, update my profile on a few different job sites, and go hunting for other positions that are available.

But I'll make sure I don't actually click the "Submit" button on any of them until tomorrow. And then save some for Wednesday, too.

I sure hope CareerBuilder's fixed that damn memory leak in its JavaScript since the last time I had to do this. Because I'd very much like to be able to leave a few of its pages up in a browser window without worrying about my entire system locking up.

Took me weeks, and multiple browsers, to figure out what was happening last year.

Setting Up MikG on an Evo 4G

As recently noted, I finally joined the twenty-first century and got me a smartphone. It's an HTC Evo 4G, purchased from friend and Brontoforumgoer TA, and I'm rather enjoying it. But it was a bit of a pain to set up, and, as I am wont to do when I find myself banging my head against the wall over a technical problem, I'm inclined to write up a little howto. (My #2 most popular post is the one about filesyncing with Unison. And because I know you'll ask, the #1 post is the one about FF7 mods.)

The first hurdle was that the phone was running Cyanogenmod. (So, first of all, it was already rooted. This is not a rooting guide; my phone was already rooted when I got it.) Now, from all appearances Cyanogenmod is great -- but what TA and I didn't know is that you can't activate your phone with Cyanogenmod on it.

The guy at the Sprint store suggested I unroot the phone and restore it to factory default. As I found out from a helpful thread on XDA Developers, you do not have to unroot your phone to activate it. You do have to flash it with a Sense-based ROM. (Sense, BTW, is HTC's UI.)

I found several recommendations for Sense ROMs, many outdated (and many of those unavailable for download since MegaUpload's been taken down). One that is recent and still available, and which I saw recommendations for all over the place: MikG.

Now, guides to flashing your Android ROM are legion (here's one from Android Authority), and recovery software varies, so the exact menu options may be different from one to the next. But here are the basics:

Download the MikG ROM.

Copy it to your phone's SD card.
I actually found that I couldn't mount my phone as an external drive on any of my computers when it was booted to Cyanogenmod for some reason; fortunately I was able to mount it when I booted to recovery mode -- see next step. Copying the zipfile straight to the sdcard root is probably the easiest way to go -- at any rate, don't unzip it.

Boot to Recovery Mode.
If your phone is already rooted and already has a custom ROM, like mine did, then you've most likely already got a recovery boot enabled. Shut your phone down, then power it back on, holding the Power and Vol- buttons. From here the touchscreen won't work; you'll only have access to the Power button and the Volume rocker. The rocker moves the cursor up and down, and the power button operates like the Enter key.

Back up your shit.
There should be an option to back up your system. Do this, because you're about to wipe everything out and you're going to want to be able to restore if anything goes wrong.

Wipe userdata, cache, and dalvik cache.
Seriously, this is a necessary step; do not skip it or it will fuck everything else up. Just don't do anything stupid like wipe your SD card in the bargain; you need that.

Flash the ROM from zip. That'd be the zipfile you copied to the card earlier.

Troubleshooting: Kubuntu lies. I just couldn't get the thing to flash; I kept getting errors. I found that the zip's checksum on the SD card didn't match the one on my computer, I copied and tried over and over again and even reformatted the card -- long story short, don't trust Kubuntu when it says the file has finished copying or when it says it's safe to remove the device. I don't think it's a KDE problem per se since I had the same problem using Nautilus, but at any rate -- start the filecopy and then go do something else for a little bit; give it more than ample time to copy. Just in case. I did the same thing with the unmount -- after I'd let enough time pass that I was sure the file had copied, I clicked Unmount and then waited awhile just to make sure that had happened cleanly. Patient waiting and the file finally copied correctly; MikG installed and was running.

But I still had to actually activate the thing.

Rather than take another trip to the local Sprint store (which would likely have been easier and taken less time, in hindsight), I did it through the Sprint website.

The first bit's easy enough: assuming you've already got a Sprint phone, you just deactivate that and tell them to move your number over to the new phone. You'll need to enter a serial (which you have to remove the battery from your Evo to get at), and they'll send you an E-Mail.

Follow the instructions in the E-Mail, not the ones on the website. They are not the same and the ones on the website are incomplete.

The E-Mail looks something like this (I've redacted my personal information):

You may need to enter the following information in your new phone to complete the activation process:
6-digit programming code: [...]
MDN (Phone number): [...]
MSID (IMSI): [...]

If you are programming a used phone, look in the manual programming instructions for your steps. If you don't find the instructions to program a used phone, follow the steps below to clear or reset your phone to its factory settings. Important note: This will remove all personal information, including texts, pictures, contacts, applications, etc.

To program a used phone:

  1. On the dial pad, press ##786 followed by an additional # symbol
  2. Follow any on-screen prompts to Reset your phone
  3. Enter the 6-digit code
  4. Select Reset
  5. Confirm any on-screen Reset to default messages
  6. After the reset, press ## followed by the 6-digit code, followed by an additional # symbol (Example: ##123456#) Note: The last # entered will not show on the display

It's easy enough when you do it like that; my problem was that I followed the guide on the website. Which didn't quite work right.

Anyhow, hopefully I've saved somebody somewhere some trouble -- maybe it'll be my new #2 most popular post.


So far I've stuck with MikG, for a couple reasons. One is that Sprint's data plan is ridiculously overpriced and I'm tempted to jump ship to Virgin Mobile or some other Sprint reseller -- and it'd be nice to still have a Sense ROM on there so I can activate.

But another is that I'm really kinda digging the design of Sense. It's fast, it's straightforward, most of the built-in widgets are actually useful and the ones that aren't are easy to remove, and if you had asked me if someone would be able to convincingly pull off a smooth, intuitive seven-workspace layout on a damn phone screen I would have told you you were out of your mind -- but damned if they didn't do exactly that.

I'm a tinkerer by nature, so I may not stick with it. Maybe I'll switch back to Cyanogenmod. Maybe I'll fuck around and install Ice Cream Sandwich or Jelly Bean -- I'm not really that concerned about watching Netflix on my phone or using the front-facing camera, and Sprint doesn't even have 4G in my state.

Food for thought, anyhow.

TV Computers are Stupid

Last night I watched the first episode of Alphas. It's a decent enough setup; there's potential there despite its heavy reliance on an Idiot Plot.

But there was this one scene -- okay, they're watching a video. And then it cuts out. And the autistic computer expert kid goes and fiddles with some stuff behind the TV and fixes it, and then explains "It was the VGA display port."

Okay, first of all: nobody computer-savvy, least of all somebody with autism, would use the phrase "VGA display port". Because while VGA is technically a port for a display, DisplayPort is the name of a completely different interface.

Second: How the fuck could it be a problem with the VGA port if the video was working fine and then cut out? Did somebody step on the cable and accidentally yank it out of the TV? If so, how the hell come we don't see that happen and nobody makes any reference to it?

Third: VGA is only video. If the VGA cable got unhooked, why did it cut off the audio, too?

(The one thing that is perfectly plausible: a room full of people who are so dumb that they need a computer genius to check whether a cable is unplugged. That, sadly, is perfectly true to life.)

It's a little thing, and not really important to the story. But it's just so damn weird. Why is it in there? And why is it nonsense? Why couldn't it have been something that actually made sense? "You changed the channel instead of turning up the volume; you have to switch it back to VGA In." Something like that. Easy.

Here's the thing: fact checker is an actual profession. There are dudes whose whole job is to make sure that the physics on Big Bang Theory or the biology on Bones is more-or-less plausible.

And yet Bones clearly straight-up does not give a fuck whether its computers behave plausibly.

Last year had an episode where the new Moriarty character booby-trapped a skeleton so that when Angela scanned it into her computer it would load a virus onto it and make it catch on fire. (In last week's episode, Angela could not even pronounce "parameterized" correctly.)

Now, I get that, for a variety of reasons, TV shows and movies may not want to actually show Mac or Windows interfaces, and instead do some kind of MofOS mockup. That's fine and understandable. My complaint isn't "That's a fictional computer interface", it's "That computer interface does not seem to operate on any kind of rules or logic." Indeed, it's entirely possible to design a fictional computer interface that looks and behaves more or less like a real computer should; my recollection of last season of Dexter is that they did a pretty solid job of this, with only a couple weird moments.

Another thing I don't get is how they still get away with this nonsense in an age where everyone has a computer.

It was one thing in the '80's and '90's when you could pretty much bullshit computers doing absolutely anything and most of your audience would be none the wiser. But in this day and age even your most out-of-touch viewer most likely owns a computer and has used Facebook.

And knows that when you look for a person, your computer does not say "SEARCHING ..." in a giant stupid angular font that takes up half the screen, then start cycling through black-and-white photos at a rate of several per second while making stupid deet-deet-deet noises until it finally finds the person you're looking for, then make more stupid beeps in time to the giant red flashing "MATCH FOUND" text across the screen, then pull up a page with white all-caps text in the Spider-Man font against a black background.

People own computers. They know what computers do and how they behave, at least on a basic, cursory level. So how come TV shows still depict computers as these flashy magic boxes?

I'd kinda like to write an episode of some TV show where a guy comes into one of these offices and then starts turning around with a quizzical look on his face every time a computer makes a stupid noise. And eventually starts asking people what the hell is wrong with their computers. "Why does it keep making that noise? Ugh, how can you stand being in a room with that all day? Jesus Christ, how can you read that all-caps, weirdly-spaced font?"

What Now?

So today I got the old "Well, the project's almost over and we don't know what that means for you" talk.

As per usual, if it were up to the discretion of people I have actually met, I'd have the job. But, as per usual, I am at the mercy of west-coast bean counters.

The thing about that: when you complete a project weeks ahead of schedule, the people who have actually met you think, "Hey, maybe we should keep this guy around." But the bean counters tend to think, "Oh good, that means we can cut him loose that much sooner." Here's hoping the people who value me win the argument for a change.

Apparently I've got, at the very least, two weeks left. Which could mean I become unemployed just in time for my thirtieth birthday. I don't think it'll be that soon, but man that would be a fun little extra coincidence.

So it goes. I'm sanguine, I guess. I'd like to keep my job -- it's a good gig, it pays fairly, I'm settled and I like the people I'm working with -- but you know, if I'm forced into another change of scenery, I'll make the best of that too.

If nothing else, there are plenty of companies that could still use a guy who can handle a Windows 7 migration.