Fulltext results:

Bootable lDebug vs FreeDOS DebugB @blog:pushbx:2022

66 Hits, Last modified: 3 years ago

believe that lDebug wins out here as part of its "go everywhere, do everything" theme. However, disk space and memory requiremen... e. (The disk space obviously only wins out if you do not need multiple different special purpose builds where one all purpose build could do.) I'm now considering adding build time condition... ading ==== * DebugB is said to be installed by doing a far call to it. Its entire executable image

lDOS FAT32 + FSIBOOT5 experimental revision @blog:pushbx:2024

33 Hits, Last modified: 13 months ago

]]) for that check by default. So it follows the "go everywhere, do everything" mantra for lDOS-related programs: 8086-clean, (33-bit) LBA with ... to CHS, full support for [[https://pushbx.org/ecm/doc/ldosboot.htm#protocol-sector-freedos|what I assume as the FreeDOS load protocol]], detects CHS geometry u

lDebug caught up with FreeDOS Debug, and ancient change log @blog:pushbx:2022

21 Hits, Last modified: 3 years ago

|in the prior blog post]] lDebug very much has a "go everywhere, do everything" theme. Today we're caught up with FreeDOS Debug ... l enable usage of ROM-BIOS I/O without enabling InDOS mode for everything else. This is useful to write change highlighting... to the screen using interrupt 10h, but retaining DOS access for things such as loading program files.... ge made it so that sometimes [[https://github.com/dosemu2/dosemu2/issues/1760|text was displaced by 80

Conditionally Debuggable lDebug @blog:pushbx:2022

5 Hits, Last modified: 3 years ago

==== Conditionally Debuggable lDebug ====== The "go everywhere, do everything" theme of lDebug has [[https://hg.pushbx.org/ecm/... g another instance of lDebug. Traditionally, FreeDOS Debug would require a lower-level debugger like