hello all, newbie here...
I installed masm32 in my drive c in a directory called masm32. I have created a simple text file called apple.txt and save it in the same directory. I want to take a look at the hex dump of the txt file that I created.
When I type debug apple.txt at c:\>masm32>
(c:\>masm32>debug apple.txt)
nothing happens. What I get is just the debug promt..
What am I doing wrong ?
Please help.
Posted on 2004-09-20 05:52:37 by bigproblems
Use d, although why for the love of God you'd want to use debug for hex-dumping I don't know. Get a hex editor, they have nice features like being usable and such like.

Mirno
Posted on 2004-09-20 06:38:26 by Mirno
I am following a book, and it's examples. and I am stuck on this. No matter I use D or E or F I can not get it in to work.
Please help
Posted on 2004-09-21 08:15:34 by bigproblems
DEBUG is old, and ugly, any book that requires you to use debug is old (and quite probably ugly too). I'd suggest you drop it.

Having said that, debug works fine for me (Windows XP), and quite happily dumps the contents of a file...



C:\temp>echo abcdef 123456 > apple.txt

C:\temp>debug /?
Runs Debug, a program testing and editing tool.

DEBUG [[drive:][path]filename [testfile-parameters]]

[drive:][path]filename Specifies the file you want to test.
testfile-parameters Specifies command-line information required by
the file you want to test.

After Debug starts, type ? to display a list of debugging commands.

C:\temp>debug apple.txt
-d
14F6:0100 61 62 63 64 65 66 20 31-32 33 34 35 36 20 0D 0A abcdef 123456 ..
14F6:0110 00 00 00 00 00 00 00 00-00 00 00 00 34 00 E5 14 ............4...
14F6:0120 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
14F6:0130 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
14F6:0140 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
14F6:0150 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
14F6:0160 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
14F6:0170 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
-


If you don't get the same, then there is something wrong with your version of debug.

Mirno
Posted on 2004-09-21 10:23:45 by Mirno
thanks mirno, I will tell you the results shortly.
Posted on 2004-09-21 12:53:33 by bigproblems
Post the results of the R command too.

Regards, P1 8)
Posted on 2004-09-21 13:05:51 by Pone
bigproblems,

If you just need to look at a hex dump for any file from MASM32, just run the default editor and select that option from the menu to display the file contents in hex.

I agree with what you have been told here already, DEBUG was a leading edge tool in 1980 but the world has changed since then and far better hex editors and disassemblers exist that will give you far more useful information tan DEBUG.

A book that assumes the use of DEBUG is no use to you with 32 bit MASM under Windows. If you need technical data have a look at Randy Hyde's site and get yourself the correct technical data from Intel with the PIV manuals. For the Windows API reference, try for the old win32.hlp file from various sites on the internet and for later data, get a platformsdk from Microsoft for the price of the shipping.
Posted on 2004-09-21 16:00:58 by hutch--
hey guys, everything works fine.
thanks for the help,

Mirno
I realy wanted to copy paste the results, but I don't know how. Is it possible to copy paste what you see in debug ? anyway glad that everything works fine.

Pone, CX=0016.

Hutch, Thanks for the info on Randy Hydes' web.

and finaly thank you all for sharing the knowledge.
Posted on 2004-09-23 01:30:08 by bigproblems