DKB 2632 - no memory!?

[cha05e90]

Showconfig won't show any memory until it's been added by the DKB driver or an addmem program. The memory doesn't auto-config.

Yep - you need to have the "2632" command in your startup-sequence to bind the DKB's RAM. Alternatively you might use Thor's MMU Tools for memory configuration. The DKB RAM can only be activated by software - AFAIK the memory doesn't "autoconfig". I use the MMU tools for this purpose since a decade - works perfectly.

[cha05e90]

I do have the 2632 utility as the first item in the startup sequence - I've tried it on both my main WB3.1 install and the boot disk the seller provided me with. I might give MMU Tools a shot, though - where can I find it? Does it provide any kind of diagnostic information?

Aminet: http://aminet.net/package/util/libs/MMULib

I used the provided tools to build up a "MMU Configuration" which includes the RAM banks of the DKB 2632. If done right, the mmu.library (which is called by the 680x0.library which is called by the OS3.9 setpatch command...) binds the RAM during startup. So I ended up with a clean startup-sequence with only one setpatch command - everything else including memory setup is done "automagically"... :-)

There provided tools can be used as diagnostic tools as well - there is a lot of documentation provided with the MMU package, but it's not a task I would do "in between"...