Kick 3.1.4 and fmsdisk.device

[Swe_Kryten2x4b]

Hello,

Just wondering if I'm the only one that the combination of kickstart/wb 3.1.4 and fmsdisk.device is a combination that just will not work?

More detailed: I'm using the same hardware (A1200, Blizzard 1230 with 64 megs of FAST), same filesystem (PFS3 AIO 19.0), same device-driver, and the same mountlist(s). The fms: assign points to the same directory.

The only difference is the kickstart (softkicked as of now, using blizklick) and worbench revision - I used to use 3.9 with all boingbags applied, official as well as unofficial. Now a pretty vanilla 3.1.4. Some additional libs and commands in c: has been added but that's pretty much it. It was a clean install.

But what happens now is that whenever I try to mount a diskimage I only get a "Not a dos-disk in unit HF0" - units that I know have a valid ffs on it. Even creating a new blank disk won't work. Sure, the file is created in fms: but disk format claims it is of the size 113E in capacity (whatever that stands for, it can't really be exabytes can it...) rather than 880k.

Moreover, it eats memory like there is no tomorrow. As soon as I try to mount a disk my fast memory drops from 60-ish free megabytes of ram to just little over 7.

Someone's got a clue to what may be going on and/or an idea of how to fix it because I'm at a loss.