Okay; fair enough. I'll uninstall the one I have, then dig out the Carolina version (I do know where the repo is for that!) I'll give it a try, and let you know how it makes out.
Cheers, guys.
Mike.

Just did a test and it wasn't as hard as I thought. I copied my save dir from sda1 to sda2 and renamed the original (backup). Ran blkid from terminal to get the uuid of sda2 and changed that in grub4dos menu.lst. Booted straight away and am posting from it now.Mike Walsh wrote:Hi, rg66.
Okay. Answer me this one, if you will. If I move the xslackosave folder out of 570's partition, and back into the correct one (i.e., X-Slacko's), what exactly will happen? I've got a fairly good idea that all the paths will be wrong, and that just about everything will need resetting.....or will it?
I would like to re-organise that, and get things where they ought to be, but.....just how much work am I letting myself in for?
Mike.
Code: Select all
terminal --working-directory=$PWD
Click OK to save.terminal --working-directory="`echo "$PWD" | sed 's/ /\\ /'`"
Wahoorg66 wrote:I've decided to off my lazy arse and start working on X-slacko-4. Beta 1 should be out in a day or two (hopefully).
Ya, I know. With 6.0.5 out, I might have to start overstarhawk wrote:X-Tahr is still in beta... just sayin'.
Yea, I run 1b3 alongside 3.1n on all the Pentium Ms and the one Bay Trail box I have farmed out. Sometimes one, sometimes the other. Both completely stable over a fairly long time with user users. Some have even ventured to use the menustarhawk wrote:A shame it was a pain -- it really is great stuff. I'm using it right now and not only does it run on dang near everything, but it's super stable for what's labeled as a beta