maxtherabbit wrote on 2026-05-19, 12:51:

I like it how it is in the picture, but I don't like the weird abbreviations. Keep the help and use full words in the setting names

Yeah, the weird abbreviations are the whole reason I did not implement more chipsets before doing the new setting UI.

Now that the UI is fixed, I have to go through all the current supported chipsets and fix them all, then I can add more.

5/22/26 : Updated UCP2 to 2.0.2
- Changed the option page layout to optimise available space for option strings
- Removed silly abbreviations as they are no longer needed
- Added a few SiS chips (5511/2/3, 5571/2, 5581/2, 5591/2, 5595)
- Update save format (Older saves are converted)

Is this tool similar to a mating between TweakBIOS and PCCHIP34? It would be nice to see support for all three popular 486 PCI chipsets from UMC, SiS, and ALi.

feipoa wrote on Today, 06:56:

Is this tool similar to a mating between TweakBIOS and PCCHIP34? It would be nice to see support for all three popular 486 PCI chipsets from UMC, SiS, and ALi.

Yes it is.
As for the many 486, I already implemented the code for ISA chip I/O configuration. The only two things missing is little code to detect the absence of PCI so it switch to ISA chipset mode and a little menu to select said ISA chipset on the first launch.

I also have to patch the ISA stuff so it actually probe if said device exist at launch (Seam to be possible, but different for each chipsets). To prevent patching the wrong chip if someone move an hard drive or select the wrong chipset. For PCI I simply scan all PCI devices and detect if the saved config match what's actually present in the system.

I just fast-read M1489 docs, and now I think it's not possible to properly ID the ISA chipset to confirm if it's present in the system I might have to figure out other way... Maybe instead, trying to detect if it's the same system. For sure I can't just checksum F000-FFFF as if someone using things like QEMM Stealth mode, that's going to be unreliable.

Maybe checksumming the "CMOS"... If it's different ask to user to confirm it's the same system/chipset or something... If someone have a better idea.

CTCHIP34 makes the user select the chipset for 3/486 boards. I suspect you will have to do the same. You could just do a popup menu at program start with the default option being "PCI" and have the various ISA/VLB chipsets below that

maxtherabbit wrote on Today, 14:51:

CTCHIP34 makes the user select the chipset for 3/486 boards. I suspect you will have to do the same. You could just do a popup menu at program start with the default option being "PCI" and have the various ISA/VLB chipsets below that

Yes, exactly, and unlike CTCHIP34, UCP2 save the settings and next time you use it in continue with these.
Asking for which ISA chipset on first launch is the idea, but on next launch I am figuring out a way to detect if it's the same system or no (Does it load from the save or ask you to clear the config (ucp2 /clr ))

As for asking for PCI or ISA, there is no need, I can simply fallback to ask for ISA chipsets if the BIOS don't support PCI. Apparently BIOS function B101h of INT 1Ah will return EDX = 20494350h (' ICP') if the PCI Configuration Mode is available. 486 BIOS that have PCI support can be autodetected. Even like the Ali M1489, who is fully "IO Port configurable", Does have a presence on PCI bus and can be automatically identified.