DOS ain't dead

some modern UEFI/CSM leaves CR0.WP set at boot (Developers)

posted by RayeR , CZ, 23.01.2024, 18:44

It seems to me logical to set WP for code sections. Noone should overwrite code if it's not intentional e.g. like when using debugger to do some black magic. So I don't fully understand how VCACHE triggered page fault - by writing to some area where it shouldn't wrote or windows kernel didn't initialized page tables properly so they leaved RO by UEFI but shouldn't be? So probably not an issue for DOS users. But maybe it would be usefull to add this workaround in himemx if someone would intend to use it together with both dos 7.x and Win 9x...

---
DOS gives me freedom to unlimited HW access.

Complete thread:

• some modern UEFI/CSM leaves CR0.WP set at boot - RayeR, 23.01.2024, 08:10
  • some modern UEFI/CSM leaves CR0.WP set at boot - Japheth, 23.01.2024, 13:24
    • some modern UEFI/CSM leaves CR0.WP set at boot - RayeR, 23.01.2024, 18:44
    • some modern UEFI/CSM leaves CR0.WP set at boot - Rugxulo, 23.01.2024, 23:41
      • some modern UEFI/CSM leaves CR0.WP set at boot - Japheth, 24.01.2024, 07:23