Open Phillrb opened 4 years ago
I put that on my todo list.
I know of the "fault" -but I never developed really a new BIOS - so it never bothered me to much :-(.
Hm, I know it has been some time since this report. ... and I really tought I knew of this bug... but I just did some tests with my own BIOS - and everything looks fine.
That is, I switched to the "MALBANBIOS" and inspected dissis content memory during debugging - and at least for me the correct byte sequences are shown. I have a hex editor open in parallel and compare the locations.
Can you still remember the circumstances - or perhaps elaborate more?
If you change the BIOS to anything other than the FASTBOOT BIOS then Dissi does not show the correct 'Content' in the BIOS memory range. I see the correct behaviour for what is really at the memory locations but the 'Content' fields are incorrect.
Please can the 'Content' fields in the BIOS memory range be updated to reflect the actual content when a custom BIOS is used? Thanks!