DOS ain't dead

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

posted by Japheth , Germany (South), 24.01.2024, 07:23

> Curious as to why you put a redundant ".286" at the beginning and then
> almost immediately change it to ".386p" (which admittedly is necessary).

because a coding of

    .386p
    .model tiny


would actually init a "32-bit tiny" memory model ( the one used by djgpp ), which definitely is wrong and would cause a crash. So this slightly "complicated" way used in ResWP.asm seems quite appropriate to me.

> Why .EXE instead of .COM?

Because i like MZ binaries more.

> Why "mov ah,4Ch int 21h" when (IIRC) MASM v5 supports ".exit"?

Because I don't like ".exit".

> Wouldn't "ResetWP.exe" be more descriptive?

Definitely!

---
MS-DOS forever!

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