Okay... I'm going to download and try the new Libre Office 4.0.
I don't' exactly know how (or why I need it) but if you're running Debian Sid, you might as well get the benefits of running bleeding-edge.
Any ideas before I go all "mad scientist" in an hour or two?

After the last install, my Realtek 802.11n chipset couldn't be recognized.
Ten years ago, if this had been the only problem encountered with a new install, it'd be golden!
But after looking on the Debian forums, I tried this in the command line;
aptitude update
aptitude install firmware-realtek wireless-tools
... and nothing.  But, I know from past experience on other distro's, this should work.
Hum. Okay, we'll try this;
sudo apt-get install network-manager-gnome && sudo apt-get remove wicd
It worked. This is being posted over wifi, so worth mentioning.
Is it a crude fix? I assume so, but it works, and might help someone else if I post it. 
9% CPU usage,  15% (567mb/3.62gb) RAM - nice!

For anybody who doesn't already know me for the CrunchBang forums, I'm Jim.

Whenever I feel like I know what I'm doing, I try a new distro, and immediately getting lost, find my ego deflated down to a manageable size again. Such is the case with VSIDO.

Clean, fast install. No problems with the Windows Ocho partition (gotta have it for work) or dual-booting - but no Secure Boot EUFI on this machine either. Runs like a greyhound after a rabbit! Any application I want is found with a quick search on Debian and a short apt-get install later, it's there...

Aside from thanking @VastOne [very nice of you to put this out there... appreciate it], much thanks to @Sector11 for the lesson on how to use wget! http://jims2011.blogspot.com/2013/02/vsido-it-continues.html Bloody Hell! Always so much more to learn, and only so much coffee to facilitate the learning...

The only two drawbacks I've found? 64-bit only. I've got a netbook and a laptop that are 32-bit, and won't accept anything higher. Naught to be done about that, but the second? My wifi-N chipset won't recognize under Wicd (or network-manager-gnome which I replaced wick with... this usually fixes things). Have it research on my own a bit further, but hey, as long as I have a text-editor, root access, and the command-line, it's fixable.

So: see you-all when I'm running on all cylinders!

-jim