If you have a system that is misconfigured, it is your job to keep it running. Nothing is for free in this universe, and with you modifying the system comes responsibility. The design is "make it simple for those that have a standard system". Not "make it hard for everyone". That would be the Linux way of doing it...
There is no guesswork involved. It is really just the modules on the ROM module list. As simple as it is.
Its using the same algorithm as setpatch for 3.9 does. In particular, it requires that the machine is equipped with the ROM came with. The CD32 is identified by the presence of the cdui.library. If that library is present, it uses the CD32. If not, the machine looks like an A1200. It never loads modules for two *distinct* machines (that would be a nice trick with the algorithm it uses), so I would say, that's all your responsibility. I'm not excluding a bug here, but it's really a pretty simple algorithm.
That it does not use fast Ram is just a matter of the fast RAM not using autoconfig properly, so it is not there after a reset where it should have been. Not fixable by software.
Thank you for your help Thomas, now I can understand how it works the command. I was really having problems in the past with the command, but now I can be able to use it correctly!! You are my hero!!
