It is a fairly general limitation of exec. If you place two modules on the resident list, exec will grab the one with the highest version number. There might be a way around this, but in general, there are system limitations like this for a reason. Libraries and devices have dependencies between them, and it is typically not a good idea to insert a lower-release into a system that was compiled for a higher release.
Some workaround must be possible - with
LoadResident from
RemApollo package I'm able to substitute the console handler with
KingCON (Remus-compatible version, patched by Cosmos). With
LoadModule I can't - it complains about module already present.
-------
One more option I miss is to be able to do something like this:
LoadModule module1 NOREBOOT
LoadModule module2 NOREBOOT
...Currently this load only the 1st module. I use plenty of them (probably most of the kickstart gets replaced) and the maximum command line length is simply too small for me.
Better yet, it could be possible to submit a directory instead of module, and the tool could load all the modules inside. Even better - the machine type check could be applied to this directory and appropriate subdirectory could be used.
(this is, of course, only a suggestion)
