03-22-2019, 09:57 PM (This post was last modified: 03-22-2019, 09:57 PM by Lost_N_BIOS.)
Thanks DeathBringer, I did not think to try setup_var for some reason, even after I gathered the variables for him, must have been asleep!!
What were you having him check at setup_var 0x0? I see that as Num-Lock or Blue Tooth Pin Code (Both default 0x1), oddly how can both be same ID for (VarOffset/VarName): 0x0?
ssybesma - All things above can be reset back to default values, nothing to risk by changing the setting and then trying your OS installs.
CSM is not relevant, when UEFI boot is disabled that will automatically mean CSM/Legacy will be used instead.
Do as mentioned >> setup_var 0xC9 0x0 << That is what I was asking you if you wanted on page one, that is one of the main things I would change in the mod BIOS.
If you need to set it back, then all you do is run >> setup_var 0xC9 0x1
And yes, there is more expensive BIOS reprogramming tools, but why pay more when you don't have to? If you want a more expensive cable that might be worth it, get Pomona 5250 SOIC8 test clip cable. More expensive programmers are all the same, in a different package, unless you want to spend $30-50+ The $2.50 ones work fine.
OK, that one will need modified using H2OUVE then. There was no change "Can't set variable via EFI", so nothing changed
You'll need to be in a windows environment to do the following, so install windows onto something if not already (Win7 confirmed working, Win10 unsure, XP does not work I think)
Please download H2OUVE from here, download 1.1 package and inside you'll find H2OUVE folder with 3x versions in it. Extract them all and run the following command from a command prompt at each folders location https://github.com/mikebdp2/Insider_BIOS_Tools - Go to "Releases" tab at top/middle for downloads
From each folder run these two commands below and keep all files in place that are created, but copy and send to me for checking
Feel free to rename any to keep versions straight on your end if you want, the name is not important and you can rename the txt in the command too if you wanted if that's easier for you. We're only keeping them in place, so we know which one is created by which version, usually the largest one will be the one we'll use.
Example you can use
H2OUVE.exe -gv vars08.txt - for the version ending in 08, same for setup08.txt and so on for each version, just have to keep track of which came from what version/
...which I got just typing in 'setup_var_ and hitting enter. Interesting. Doesn't mean I have an InsydeH20 BIOS. Mine should be AMI.
I guess that utility was meant for laptops which had those. Wonder if there's a later version. I guess that's really a grub shell with utilities added to it, would that be correct? At first I thought incorrectly it was just an EFI shell like what is onboard this thing.
03-23-2019, 02:41 AM (This post was last modified: 03-23-2019, 03:00 AM by ssybesma.)
(03-23-2019, 01:22 AM)ssybesma Wrote: OK, I can do this on my NUC that has Windows 10 Pro x64. Got rid of Windows 7 a while back (question my sanity). I get the results ASAP.
So I need to reboot because I'm getting a different result each time I run the three executables.
To me that means Windows is taking an Update $#!+ or something.
Running the three commands, sometimes nothing happens, somethings I get an error on the command prompt, or this window pops up.
Please see attached picture called IHISI error.jpg
I only got one of the 6 files I was supposed to get and that was Setup08.txt from version H20UVE_100.00.16.08 (but not Vars08.txt)
It's attached to this post. I'll reboot and try again and try to provide more detail.
03-23-2019, 03:04 AM (This post was last modified: 03-23-2019, 03:06 AM by ssybesma.)
(03-23-2019, 02:56 AM)DeathBringer Wrote: In Windows 10 Pro x64 you can use AFUWINx64.EXE for saving BIOS dump.
And please run my unfinished tool - https://drive.google.com/open?id=1zh-zEo...5-SkwjPwtJ
From command line with administrative rights.
OK, will do...long night (little after 2am) but this is good stuff...I'll get it done and get the results to you.
I have to ask a question though...I'm not dumping the BIOS on the thing I need to dump it on.
I'm dumping it on my Intel NUC.
The Intel Compute Stick is what I want to try for.
That can only be done in Linux or else with the EFI shell or the grub tool you had me download and run earlier.
03-23-2019, 03:11 AM (This post was last modified: 03-23-2019, 03:23 AM by DeathBringer.)
My tool must be run on your Intel Compute Stick with Windows installed (any version with UEFI booting).
AfuEfix64.efi (64-bits) and AfuEfi.efi (32-bits) can be run from UEFI shell.