![[-]](https://www.bios-mods.com/forum/images/black/collapse.png "[-]")
05-29-2026, 08:11 PM
This question is only 16 years late ... 
but Why does the output in the debugger step have to be saved as a .com file? degubber or CDB won't run on x64 Windows. I'm trying IDA per someone's suggestion in the comments, but to open a .com file I have to buy the PRO version. I'm kinda up the creek without a paddle.
Can the output be saved as a .exe to be more compatible with Windbg? This is for a HP pavilion dv5 2231nr laptop, of course with the 2MB BIOS. If I manage to figure this out and not brick the laptop, then I'll share my findings and the non-whl F.27 bios.
but Why does the output in the debugger step have to be saved as a .com file? degubber or CDB won't run on x64 Windows. I'm trying IDA per someone's suggestion in the comments, but to open a .com file I have to buy the PRO version. I'm kinda up the creek without a paddle.Can the output be saved as a .exe to be more compatible with Windbg? This is for a HP pavilion dv5 2231nr laptop, of course with the 2MB BIOS. If I manage to figure this out and not brick the laptop, then I'll share my findings and the non-whl F.27 bios.
![[Valid RSS]](valid-rss.png "Validate my RSS feed")