Am Sun, 20 Jul 2008 14:01:17 -0700 (PDT) schrieb Georg:
> I am unsatisfied with the user inferface of debug. Is there a front > end or shell for debug which makes debug easier to use?
Most commands need an input of values. In the beginning i use debug to test the instructions and look how the cpu works. In this time i also think i need a frontend or some hotkeys to make my work with debug easier. But Today i use an assambler to write my code. No i can use Remarks to discribe what the part of code will do.
So i am sorry, i donīt know if an frontend of debug exist.
On Jul 20, 4:01 pm, Georg <nos...@georgpotthast.de> wrote:
> I am unsatisfied with the user inferface of debug. Is there a front > end or shell for debug which makes debug easier to use?
> Georg
CodeView still uses some debug commands, and also provides a full screen user friendly interface. While not exactly a front end, you might want to consider it as a more convenient debuging tool.
CodeView is a Microsoft product, and is more effective for debugging programs compiled by Microsoft compilers because it interfaces with the programmer in terms of the programming language used.
Other compiler vendors produced similar debug facilities which are compatible with their own compilers.
Thank you for your posts. Currently I use debug to analyse disk sectors. So I guess Codeview or some other debugger for assembler will not help me with this.
Am Mon, 21 Jul 2008 02:47:49 -0700 (PDT) schrieb Georg:
> Thank you for your posts. Currently I use debug to analyse disk > sectors. So I guess Codeview or some other debugger for assembler will > not help me with this.
> Dirk, you are right. I will use a disk editor instead.
> I just thought since debug is supplied with DOS, someone had written a > front end for debug.
> Georg
Just on a side note, a disk editor is just that, something that will edit a disk. If you are just wanting to view the contents of the disk and analyze the data, I would suggest you make a image of the disk and view as a file instead. It is much safer.
I have a few tools at: http://www.frontiernet.net/~fys/mtools.htm for creating images of disks along with a tool I am working on now, DUMP, which will parse a block of data from that image, and dump it in a human readable format rather than just hex bytes.
If this is what you are looking for I hope that it helps you in your work. If not, disregard this and I hope you find something that will work for you.
Ben
P.S. Currently, since it is under development, DUMP comes in a Windows only executable.
I appreciate that you look for users of your DUMP utility and I really don't want to upset you, but from Dirk's post I used HxD and WinHex. Both offer write protection for disk drives as default and HxD can also open the disk images I use with Bochs.
What I am also looking for is a utility to use a DOS batch file to copy the executable I compiled outside of Bochs onto the disk image and then test it within Bochs. As far as I understand such a copy utility is not available yet.
> I appreciate that you look for users of your DUMP utility and I really > don't want to upset you, but from Dirk's post I used HxD and WinHex. > Both offer write protection for disk drives as default and HxD can > also open the disk images I use with Bochs.
> What I am also looking for is a utility to use a DOS batch file to > copy the executable I compiled outside of Bochs onto the disk image > and then test it within Bochs. As far as I understand such a copy > utility is not available yet.
No, I'm not upset :-), I am just trying to help. My MCOPYT utility isn't yet complete, but if I would finish it, it would do just that. Copy a file on the host system, to an image partition. It has been a little while since I have worked on it, (haven't had the need to), but I think it only saw FAT12/16 image files.
