LoadModule vs LoadResident

[Oldsmobile_Mike]

Just thought I would follow up on this old thread to say I finally got LoadModule working with the "DOWNGRADE" option.

I had to use a combination of DOWNGRADE + AUTO + a manually specified directory ("SYS:ResidentMods") where I packed in all the extra stuff that LoadModule wasn't able to detect automatically.

But here's some additional info, if anyone is interested (screenshots attached).  Still a hair on the kludgy side, still not as good as burning a custom ROM, but it's able to successfully load all my modules without the super-long strings of commands I was having to use before.  And that's all I was really trying to do, LOL.  :banana:

[Oldsmobile_Mike]

Just wanted to applaud your constant effort @oldsmobilemike to improve and tweak your system by means of the latest and greatest libraries and in the cleanest most streamlined method possible.  As is often the case with our miggies, once you dig into a problem it can take numerous hours of head banging to get it working right (if at all).  The efforts and frustrations you make permanent on the forum make the process a little less daunting for the next Joe.  Personally this process is still above my pay-grade... I'm finally (in 2017) using "versionWB" to check libraries and just update them with the latest versions while maintaining a backup of the version before just in case. hahaha.  But maybe I'll get the guts to try what you did here at some point.
Anyway... good on ya!

Thank you, sir!  My fame will live forever in the hallowed halls of amiga.org website.  That is unless, of course, it goes down like amigaworld.net.  :lol:

[Oldsmobile_Mike]

Hi!  Since somebody just asked me about this, and for the benefit of anyone who comes after me.  I was just setting up a CF a few days ago that has 3.1 + BetterWB + some of the custom LoadModule stuff on it (like I have on my A2000 but without the additional LoadModule items for the graphics card).  Here's a few photos.

The LoadModule statement itself (in Startup-Sequence) scans and replaces various system modules with AUTO.  I also created a separate folder of stuff for it to load (SYS:ResidentMods) that it is not able to find automatically.  In the case of this one I also took out the NOREBOOT option, since it's 3.1 (as opposed to 3.9).

TL;DR.  Some quick photos off my camera phone attached.  

Edit: This is still a WIP. :lol:

[Oldsmobile_Mike]

sometimes the LoadModule line can become really long.

FWIW, that's why I switched to using AUTO + a custom directory that I dumped all the modules in that LoadModule couldn't find automatically.  No functional difference, just appeased my OCD to not have a miles-long line of LoadModule stuff.  

[Oldsmobile_Mike]

What about your OCD of not easily knowing what LoadModule was loading???

Hey now.  It took me a while to figure it out, but I do know exactly what it's loading.  See attached screenshot.  

Although in a perfect world I think more comprehensive information like this would be helpful:

ModuleName $name1 loaded from $location1
ModuleName $name2 loaded from $location2
Etc.

[Oldsmobile_Mike]

You did not see the email I sent you?

http://www.amiga.org/forums/picture.php?albumid=204&pictureid=1437

LoadModule checks for cdui.library, finds it, and then decides it must be an A1200. Whatever OS3.9 does by default, I am quite sure it is equally broken.

I'm sure you know this but it looks like this has been addressed in the latest release (just noticed it on Aminet this morning).

http://aminet.net/package/util/boot/LoadModule

LoadModule 45.14:  This release includes a new switch, ROMUPDATE, which works like AUTO, except that it only grabs pure modules (i.e. modules whose 'p' bit is set). This might help to housekeeping and exclude some unwanted modules. ExtractModule has been updated to set this bit as well, and allows now to use the "TO" keyword also to specify a target directory for individual files, making everyone's life a bit easier. The check for the CD32 of LoadModule apparently did not consider the extended ROM area of this device, hence failed to identify this model correctly. Sorry about that.