26
fzammetti
31d

Step 1: Run to the store to buy a USB card reader because all of a sudden you have a need to use a 16Mb CF card that was tossed in a junk drawer for 20 years (hoping it still works, of course), but that was the easy part...

Step 2: Realize that the apps - your own - you want to run on your new (old) Casio E-125 PocketPC (to re-live "glory" days) are compiled in ARM format, not MIPS, which is the CPU this device uses, and the installer packages you have FOR YOUR OWN APPS don't include MIPS, only ARM (WHY DID I DO THAT?!), so, the saga REALLY begins...

Step 3: Get a 20-year old OS to install in a Hyper-V VM... find out that basic things like networking don't work by default because the OS is so damn old, so spend hours solving that and other issues to get it to basically run well enough to...

Step 4: Get that OS updated so that it's at least kind/sorta/maybe (but between you and me, not really!) safe online, all without a browser that will work on ANY modern site (oh, and good luck finding a version of Firefox that runs on it - that all took a few hours)...

Step 5: Okay, OS is ready to go, now get 20-year old dev tools that you haven't even seen in that many years working. Oh, do this with a missing CD key and ISO's that weren't archived in a format that's usable today, plus a bunch of missing dependencies because the OS is, again, SO old (a few MORE hours)...

Step 6: Get 20-year old code written in a language you haven't used in probably almost that long to compile, dealing with pathing issues, missing libs, and several other issues, all the while trying to dust off long-dormant knowledge somewhere in the deep, dark recesses of your brain... surprisingly, it all came back to me, more or less, in under an hour, which lead to...

Step 7: FINALLY get it all to work, FINALLY get the code to compile, FINALLY get it transferred to the device (which has no network capabilities, by the way, which is where the card reader and CF card came into play) and re-live the glory of your old, crappy PocketPC apps and games running on the real thing! WOO-HOO!

Step 8: Realize it's 3:30am by the time that's all done and be VERY thankful that you're on vacation this week or work tomorrow would SSUUCCKK!!!!

Step 9. Get called into work the next day for a production issue despite being tired from the night before and an afternoon of errands, lose basically a whole day of vacation (7 hours spent on it) and not actually resolve it by after midnight when you finally say that's enough :(

Talk about your highs and your lows.

Comments
  • 3
    Sorry man, nothing in my life comes close to this saga! 👍

    I do love those sudden urges to relive the glory days. It's a sign you have things in order!
  • 1
    I they call you in during your vacation that should lead to your vacation being prolonged by at least twice the time you worked.
  • 1
    Spending enormous efforts to get old, basically obsolete hardware to run.. on vacation... well, I totally haven't done that to boot a usable OS on a 16 year old Laptop from Asus with a shitty incomplete acpi last week, during my vacation.
    (In the end I didn't manage to get it to boot without disabling acpi, since all possibly working modded BIOS are offline - and so are their mirrors, and so is sourceforge DSDT list.)
  • 1
    @saucyatom Well, I don't know about double, but I'll get the time back at least. My job is usually pretty good about that at least.
  • 1
    @saucyatom Birds of a feather, sir!
  • 1
    this story makes me happy for you. im glad for your adventure.
Add Comment