Also, orioncd.ini should basically just contain a single line containing the path to the CD.

Ah, the tribulations of attempting to get Moo2 running under Vista Ultimate. The installer won’t run, of course, so it was necessary to simply copy the entire disc to drive. Setting the .exe’s to run in Win 95 compatibility mode was the first step; next was copying dplay.dll from the DIRECTX directory of the disc to c:\Windows\SysWOW64

That allowed the game to start, at least, without issue – other than a missing orioncd.ini; the contents of which are noted above.

The game starts and appears to run okay. No real problems yet, other than the mouse cursor being kind of… flickery.

I can say that things look ugly on a 30″ monitor, but, well… When you’re blowing up low resolution that much, you can’t expect otherwise.

Now if you’ll excuse me, I have some galactic conquest to attend to. With my hawt Elerian science chick. Research labratories FTW!

The files appeared in the program’s save/load dialogue boxes; inside explorer, they were nowhere to be found. They also didn’t appear via the command line. Checked properties from within the program’s dialogues; nope, the files were not hidden – permissions were correct.

…Of course it’s completely obvious that I’d need to hit the ‘compatability files’ button. Oh, yes. That makes perfect, intuitive sense.

Listen, Billy G, if I wanted to be told how to use my own computer, I’d be running OS X.

Absolutely hidden files, really? Now what do you suppose would happen if this was a directory where I wasn’t aware of these files, or simply wasn’t paying attention, and had to copy it to say another machine?

My kingdom for a decent desktop operating system! (No, Linux doesn’t count – sorry, I like getting work done instead of screwing about with configuration files for a week beforehand. :p)

Looking through some of my old (previously organized) pictures – trying to figure out if I have a picture of my living room wall before the paint inexplicably started running (protip: never use flat paint in a house with bad windows and a condensation problem)… Noticed, half the images weren’t tagged. Odd. I’ve been making it a point to tag the images. Indeed, tagging is one of the more awesome features of Vista.

Okay, maybe I just missed a few – I usually do organization at 3 AM when I’m bored to tears and awake solely due to deployments.

I go to retag an image and – nada. Error 0x88982F50: No error description available.

I do some Googling; nothing but some BS about Roxio, which ain’t my problem. I give up on Google, searching for the words ‘tag’ and ‘tagging’ is pointless thanks to everyone and their mother having a blog these days. Well, I open up a tagless file in notepad and – there are my tags. Just sitting there. Odd.

Well, at least they aren’t gone.

On a hunch, I open up a file whose tags are working and the tags are there, albeit in a weird, different format.

The plot thickens.

On another hunch, I open the tagged-but-tagless image in Photoshop and re-save it. And now the tags appear in Windows Explorer again.

Lovely – so basically, I need to run every tagged-but-tagless image on my box through Photoshop. For no explainable reason.

Man, I wish Linux didn’t suck so badly for desktop work. :p

Update: Or maybe I don’t have to run everything through PS. After choosing a small directory, sorting tags by Unspecified, selecting all images, opening with Photoshop, and re-saving… Windows Explorer crashed.

Upon restarting Explorer, all tags are now visible. Even ones that weren’t previously displaying. Gods below, I hate computers.