There’s threads regarding these drivers… that should be manually integrated in to UBU folders, the user needs have some knowledge of the respective versions and chipsets.
1 Like
on my ubu (latest with the modded ubu.cmd) the bios list screen (the one you posted) appears for a split second and then disappears and shows only this one.
imho its better to see the list also
1 Like
Could you post your Python version
py --version
and list of packages
pip list
?
1 Like
Full removal of Python with Revo Uninstaller 2.5.0.0
Reboot and clean reinstall of Python 3.12.6
Add to PATH etc.
Upgrade pip
pip3 install pltable
pip3 install colorama
Latest UBU.zip (Post 2144)
Working as expected. Seems it is not a trusty upgrade path from 3.10/3.11/3.12 etc. Lots of cruft. Was reporting as iakoboss7 but…
1 Like
just to clarify, in my case its the first time i installed python, just a few days ago.
I don’t have python installed and it works fine (don’t want to install it just for UBU that I rarely use)
What’s the difference?
Sorry. I have corrected my post, it was iakoboss7 that had the same Python reporting as mine (until it was in fact fixed).
Fixed
UBU.zip (18.2 KB)
For those getting no MCE output:
Clean up Python and install it with
winget install python3
pip install colorama pltable
2 Likes
Tested, and there are even more “Press enter to exit” than before
1 (see 2) each time
Otherwise I have this message after the listing of EFI and OROM, what is it exactly ?
UEFIReplace v0.25.0 will be used.
Thanks for your great work
EDIT : @Gregory_Tumanyan You “mod” the UBU file because @SoniX’s is not up to date ?
I tested the SoniX one (1.80) and I have this error
R - Start replacement
0 - Cancel
Choice:r
[Preparing for replacement]
BIOS file backup
Dummy GUID: GUID replaced
mCode GUID: GUID replaced
mCode GUID: GUID replaced
[Replacement]
'`for' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
mCode FFS:
No problem with the one from 1.79