EDIT:
“…but looks quite old.”
You didn’t mentioned your Asus model and the guide is not old at all, basic principles from Asus cap files and methods still valid on modern motherboards.
No clue why that Ref is missing there, but I assume you can unlock it with an Access Level change.
I wouldn’t be surprised if the page ID method didn’t work with other vendors, considering each vendor seems to handle things differently in general.
Gigabyte is the last desktop mainstream vendor that isn’t solved yet, so I’m hopeful this will be a viable solution. I just want to confirm myself that this works (specifically a video demonstration). So far, I haven’t been able to find a volunteer with a gigabyte board.
Hello again.
I know you don’t plan to add Aptio 4 support. Because AMIBCP works well and stuff. But there is a single issue, cos of which at least minimal support worth being added to the editor.
A single line in Setup SCT is all that needs to be changed for unlocking.
That’s how I imagine the editor would operate like. Unfortunatelly, I could not went further and write parser function as I don’t understand what happens from line 722 and onwards.
This is the main issue with Aptio IV, IMO. What single line are you talking about specifically?
L722+ parses the top-level menu structure and would likely not even work with Aptio IV since the IFR is split into many form sets.
Regarding page IDs, it does not work on Z590 Aorus Elite, but does work on H110M-DS2. It seems like it doesn’t work on more recent Gigabyte boards anymore. I think I’ll add page ID + address parsing to the data.json as a compromise for now, so hex-editing is easier.
You should decline then. I wonder why github needs this all.
Provided that I can’t write parser from scratch, I thought to use this code as a base for a second ParseData function.
The thing is, I don’t understand syntax. That’s what I meant.
Oh, so you’re basically going to parse the Setup.sct file directly? Like I said, L722+ is just for top-level menu parsing in the AMITSE.sct file. You can ignore that. BTW, I added the page ID parsing and also switched the dev env from CRA (since it’s EoL) to Vite and refactored quite a bunch of stuff.
I mean it won’t run locally for testing.
my server is configured correctly to run this type of script. it runs my script just fine but not this one. what am I missing?
I see some includes that aren’t in the master; can you send me a link to those?
I have no idea what you’re trying to do, but if you want to build it yourself, download and install Node.js, clone the repo, run npm install and then npm run build or npm run dev to start a dev server.
Mod my bios
Interesting thing is happening, flashing the original will allow it to boot right up but the smallest mod will cause it to hang.
I’m trying to get to the bottom that…
What exactly are you trying to do? As I mentioned above, just use the regular page or save it locally if you need to run it without internet connection. You’ll likely break something if you don’t know what you’re doing trying to host it with IIS.
