New GPIO module

So a built-in solution for logging and reporting boot errors (and CMOS resets) would certainly be desirable.

harinezumi would be the starter for nine, or possibly ten

Some digging through the sources for the different Configure plugins suggests that they all write to <Choices$Write>.Boot.[PreDesk|Tasks].Whatever, apart from ScrnSetup (uses <PreDesk$Configure> for monitor settings) and InetSetup (uses <Boot$ToBeLoaded>.SetUpNet for the SetUpNet file). So those two plugins are probably due for a trip to the re-education centre to get them to read/write their settings in the correct manner.

Careful: ScrnSetup needs the extra level of indirection via PreDesk$Configure. It allows it to select between VRAM and NoVRAM and other similar situations where a decision is made prior to predesk which affects which place to get the MDF.

I don’t have any good reason for InetSetup to be writing through Boot$ToBeLoaded. I wonder if it’s because it originated with the separate TCP/IP Protocol Suite and hence needed to work on machines without the Universal Boot application, so couldn’t assume Choices$Write was set? A literal reading of PRM5a-540 and PRM5a-543? Which one wins when the sub path of Choices is also Boot$ToBeSomething…

And I think I checked all the other plugins to read through Choices: and write through Choices$Write a few years ago.

Careful: ScrnSetup needs the extra level of indirection via PreDesk$Configure. It allows it to select between VRAM and NoVRAM and other similar situations where a decision is made prior to predesk which affects which place to get the MDF.

ClrMonitor relies on PreDesk$Configure, so we’d probably have to keep it around to avoid needing to change that. I wasn’t aware of the relation to VRAM though – I’ll have to look into that.

I don’t have any good reason for InetSetup to be writing through Boot$ToBeLoaded.

My theory is that maybe there’s some relation to network booting (e.g. Choices$Write may be on a network share, whereas the network setup itself would need to be local). So a bit more research may well be needed.

And I think I checked all the other plugins to read through Choices: and write through Choices$Write a few years ago.

Yes, apart from the two I mentioned everything I saw appeared to be reading from Choices: and writing to Choices$Write.