Index
> Projects and Ideas > Dark Debugger |
| Author |
|
|
CandyMan
Dark Debugger - protected V86 mode debugger for Dos based on deglucker with build in assembler (FASM). Dark Debugger is a perfect debugger in order to unpack protected executable files. Inside the archive is an instruction how to do it.
_________________ smaller is better Last edited by CandyMan on 18 May 2022, 14:10; edited 3 times in total |
|||||||||||
11 Nov 2015, 17:53 |
|
But there's only a UNPACK.TXT on how to unpack exes briefly...I don't know what the vid.com/test32.exe/run.com are for, and there's no guide on the dd/dd32 UI. So, could you please add some documents so the users can master your tool quickly?|
CandyMan
DD32.EXE is 32-bit version of DD.EXE.
Run DD32.EXE /? to display possible command line parameters. You can run/debug sample program "vid.com" like below. Running DD32 by command line: dd32.exe vid.com Running DD32 by installation (first install and next use "run.com" to load program): dd32.exe run.com vid.com DD32 uninstall previously installed: dd32.exe -u DD32 installing in CONFIG.SYS: DEVICE=DD32.EXE -e _________________ smaller is better |
|||
|
15 Nov 2021, 20:47 |
|
|
jjhou
Hi, Great CandyMan, amazing tool! The DeGluker 0.04/0.05a hangs easily on my PIII dos machine when hacking games, but your DD runs well! Thank you!
So have a plan for 0.04? and will you think about adding protected-mode support like debugging dos4gw programs? |
|||
|
04 Apr 2022, 09:34 |
|
|
jjhou
It always returns "Search bytes(s) not found!" when I debug 16-bit programs using dd32.exe, though the bytes are just in the code/memory window. Instead when using dd.exe to debug 16-bit, searching returns correctly.
So it looks like dd.exe is only for 16-bit debugging and dd32.exe is only for 32-bit debugging, is that true? If so, why can't you just make dd32.exe for both 16-bit and 32-bit debugging like most other debuggers? |
|||
|
06 Apr 2022, 13:14 |
|
|
CandyMan
The Dark Debugger (32 and 16-bit) is intended only for debugging 16-bit programs. The difference is that version "32" is fully 32-bit (exception handling and kernel) and can run as a driver (CONFIG.SYS file). I have a different debugger to track 32/64-bit programs that use the dos extender
(see also https://board.flatassembler.net/topic.php?t=14416). I corrected a few things (including the search). Thanks for the report! _________________ smaller is better |
|||
|
18 May 2022, 14:29 |
|
< Last Thread | Next Thread > |
Forum Rules:
|