Differences

This shows you the differences between two versions of the page.

--- blog:pushbx:2022:1107_bootable_ldebug_vs_freedos_debugb [2022-11-07 21:53:12 +0000 Nov Mon] – fix headings ecm
+++ blog:pushbx:2022:1107_bootable_ldebug_vs_freedos_debugb [2022-11-07 21:54:44 +0000 Nov Mon] (current) – [Supported modes per build] explicitly say that other mode is application ecm
@@ Line 99: / Line 99: @@
   * DebugB is provided as a binary file that is a special purpose build. It can only be used in boot loaded mode.
-  * lDebug includes booting capabilities in a single build (which can be Debug, DDebug, [[blog:pushbx:2022:0804_conditionally_debuggable_ldebug|CDebug]], or any of those three with additional DPMI support indicated by a trailing X)
+  * lDebug includes booting capabilities in a single build that is also usable as a DOS application (which can be Debug, DDebug, [[blog:pushbx:2022:0804_conditionally_debuggable_ldebug|CDebug]], or any of those three with additional DPMI support indicated by a trailing X)
 I believe that lDebug wins out here as part of its "go everywhere, do everything" theme. However, disk space and memory requirements are larger for current lDebug than for a special purpose build that can only be used in one mode. (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 conditionals to create special purpose builds like this from the lDebug sources.