The one thing I noticed about the Knoppix distro was that the
driver for my Sound Blaster Audigy X-Gamer card didn't work. I'm
sure the problem can be fixed somehow, but installing Linux on my
system will first require me to partition my hard drive somehow
hopefully without having to format it (probably I'll use Ranish
http://www.ranish.com/part/, if it supports that feature but I
don't know if it does), and also I'll need to locate drivers for
all my legacy peripherals. I know it's possible, but right now I'm
busy working on kitchen cabinets and with the holiday season.
You might want to start looking into some of the linux hardware NGs.
Someone has probably already walked that sound card isle and might
offer some suggestions. If you can't find an acceptable method to
partition your drive(s), you can find a few on the linux side to do
the job (parted comes to mind).
Surprisingly enough, linux generally works exceptionally well with
older hardware. The way $MS uses the term 'legacy' doesn't apply in
my opinion.
Heh. Wish I could simply dump Windows and migrate, but as you
probably know it's not that simple. I'll need to keep Windows
working during the process somehow.
That's why I mentioned a "dual-boot" setup via (most likely) LILO or
Grub. Going this route will allow you to maintain both OS's. At
boot-up, you can take your pick of wME or linux. Having windows
around as a fall-back will come in handy when first starting out.
Ooops. s/encrypted swap partition/encrypted file-system
Not sure how I would go about doing that. Sounds like a great idea
though.
I should have worded that better. What I was referring to was
'conservativeSwapfileUsage' in system.ini. I don't think it's set by
default. I only bring this up since I had done a new install of wME
(only for the holidays and the relatives youngsters and their
games), and I noticed the swapfile was usually there after shutdown
(right around 75Mb). With nothing more then what wME starts up by
default, 256Mb of ram onboard, that somehow didn't seem right.
As I said, this probably isn't what your problem is, but I've not
been seeing any of what you've been describing. Nothing at all
consistent with win386.swp on my end. Take a quick look in
system.ini under [386Enh] for the above.
Well now, that is indeed interesting. I thought that it was just
normal behavior for the OS.
Unless I misinterpreted what you described, totally consistent
swapfile behavior from one session to the next was something I never
really saw. Could it be you have too little ram and precisely enough
stuff running in the background to cause this kind of paging
activity at start-up?. Even so, still seems odd.
Hopefully, you'll get this sorted out. And do consider the linux
alternative.
Max