some modern UEFI/CSM leaves CR0.WP set at boot (Developers)
> That's why the little tool ResWP.exe is supplied with the debugger
Curious as to why you put a redundant ".286" at the beginning and then almost immediately change it to ".386p" (which admittedly is necessary).
Why .EXE instead of .COM?
Why "mov ah,4Ch int 21h" when (IIRC) MASM v5 supports ".exit"?
Wouldn't "ResetWP.exe" be more descriptive?
(Sorry for the nitpicking.)
Complete thread:
- some modern UEFI/CSM leaves CR0.WP set at boot - RayeR, 23.01.2024, 08:10 (Developers)
- 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
- some modern UEFI/CSM leaves CR0.WP set at boot - Japheth, 23.01.2024, 13:24