pushbx wiki

User Tools

Site Tools

Trace:
blog:pushbx:2022:1107_bootable_ldebug_vs_freedos_debugb

Differences

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

Link to this comparison view

Next revision 		Previous revision
blog:pushbx:2022:1107_bootable_ldebug_vs_freedos_debugb [2022-11-07 21:15:24 +0100 Nov Mon]
ecm created 		blog:pushbx:2022:1107_bootable_ldebug_vs_freedos_debugb [2022-11-07 22:54:44 +0100 Nov Mon]
ecm [Supported modes per build] explicitly say that other mode is application
Line 96: Line 96:
 ===== Comparison ===== ===== Comparison =====
  
-====== Supported modes per build ======+==== Supported modes per build ====
  
   * DebugB is provided as a binary file that is a special purpose build. It can only be used in boot loaded mode.   * 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. 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.
  
  
-====== Installation and loading ======+==== Installation and loading ====
  
   * DebugB is said to be installed by doing a far call to it. Its entire executable image needs to be loaded. It is suggested to store its image behind the MBR or in the reserved sectors of a file system partition. No loader is provided to implement this.   * DebugB is said to be installed by doing a far call to it. Its entire executable image needs to be loaded. It is suggested to store its image behind the MBR or in the reserved sectors of a file system partition. No loader is provided to implement this.
Line 112: Line 112:
  
  
-====== Relocation ======+==== Relocation ====
  
   * DebugB will try to relocate itself to the top of the Low Memory Area then adjust the BIOS Data Area memory size indicator. The actual relocation takes place after interrupt handlers have already been installed.   * DebugB will try to relocate itself to the top of the Low Memory Area then adjust the BIOS Data Area memory size indicator. The actual relocation takes place after interrupt handlers have already been installed.
Line 120: Line 120:
  
  
-====== Detection ======+==== Detection ====
  
   * DebugB installs itself behind the LMA. It cannot be detected easily.   * DebugB installs itself behind the LMA. It cannot be detected easily.
Line 128: Line 128:
  
  
-====== Accessing sectors ======+==== Accessing sectors ====
  
   * DebugB provides a barebones ''L'' command to read sectors off an int 13h unit. It currently assumes that the LBA extensions are available for reading from the unit.   * DebugB provides a barebones ''L'' command to read sectors off an int 13h unit. It currently assumes that the LBA extensions are available for reading from the unit.
Line 136: Line 136:
  
  
-====== Quitting ======+==== Quitting ====
  
   * DebugB does not provide any quit or uninstall commands.   * DebugB does not provide any quit or uninstall commands.
Line 144: Line 144:
  
  
-====== Loading programs ======+==== Loading programs ====
  
   * DebugB suggests using its limited ''L'' command to "load and run another boot sector from inside the debugger". It does not provide any other ways to load programs.   * DebugB suggests using its limited ''L'' command to "load and run another boot sector from inside the debugger". It does not provide any other ways to load programs.
Line 152: Line 152:
  
  
-====== Listing partitions ======+==== Listing partitions ====
  
   * DebugB advertises that the "''DP'' command may be used to list the available partitions of a disk". It appears to not have been implemented or uploaded yet.   * DebugB advertises that the "''DP'' command may be used to list the available partitions of a disk". It appears to not have been implemented or uploaded yet.
blog/pushbx/2022/1107_bootable_ldebug_vs_freedos_debugb.txt ยท Last modified: 2022-11-07 22:54:44 +0100 Nov Mon by ecm

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
CC Attribution 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki