Hmm... alright, so it's not the clock card.
About the board saying you need more than 32 MB of RAM, even though you installed more... is this the old mainboard with the 166 MHz processor?
Both, the old mainboard and the new mainboard can have their memory upgraded (I have both, and it worked in both), but the old board has two separate banks of memory (for different types of memory that can be installed).
If I recall correctly, then the mainboard will "prefer" one of the banks (I think the one with the older-type, smaller memory slots), and not recognize anything that is installed into the newer bank of memory.
So, if you have a memory SIMM installed in the shorter white slots, and added some memory into the longer black (or brown... don't remember) slots, then it won't recognize it, and will just use the memory in the white/old slots.
Here's a link to a pic of the old board in the database:
http://www.sonido-7.com/d8b/photos/large/CPU1x.jpgIf anything is installed into the 4 white slots on top of the picture, and you installed something in the two black/brown slots shown below them, then only the memory in the white slots is recognized I believe.
If it's that, just shut down and pull everything out of the white slots, just leaving the memory in the darker/longer slots. This should get it recognized.
It IS really important to manually set all the BIOS settings to what is listed in the database for your board. Again, if it's the "old" board, then the settings can be found here:
http://www.sonido-7.com/d8b/files/d8b_old_mb_bios.pdfPersonally, I don't think the CF card vs. Harddisk thing is related to the memory not being recognized right. It's possible... but in the end, if the computer can load the operating system from what you got installed, then it would be weird that it would selectively decide not to read the part about addressing the memory correctly. The relevant parts of the OS written to the different types of drives are identical. IMO, CF vs. Harddisk issues should more likely look like the OS not booting at all, or "lagging" or behaving a bit odd (i.e. not able to read the needed data quick enough... but memory is more like a address-table... and fast at that. So, if the address the OS tries to access exists, then it should be found).
What's more important, IMO, for memory troubleshooting, is to pay attention to what the memory counts up to when you first start up the computer. If it doesn't find the extra memory at that point, it definitely won't find it after the OS is loaded.
And if it finds it or not when it counts up right after bootup, is usually related to either hardware or hardware compatibility trouble, or it could be wrong settings in the BIOS. But I don't recall there being anything to limit the amount of memory that is being recognized.
I'd try to solve the memory recognition problem first, before dealing with the sticky faders. For that, I COULD imagine that OS 5.1 just needs more memory for smooth fader operation.
Again, best of luck (...and sorry... I type about as fast as I speak... that's why my posts frequently get this long. For me, that's just like when I'm talking, hahaha...)