From: Frank K. <fbk...@zy...> - 2011-03-08 18:58:53
|
Frank Kotler wrote: > (Incidentally, click "reply all" to reply to the list - otherwise it > goes just to me. Jeez, I did it myself... ---------------------- kevin becker wrote: > uhm > > when i click on the NASM.exe, it pops upon, and then closes before anything can be even SEEN > > it doesn't do anything.... Ah, okay. Nasm is a "command line" utility. That is, at a "command prompt", you'd type "nasm -f win32 -i c:\my\includes\ -o myfile.obj myfile.asm", or so. You can get a command prompt by doing start->run->"cmd" - I think that still works. Alternatively, there's a way to make a "shortcut" to Nasm that will pop up a dialog-box when you click on it that will allow you to enter a command line. I'm afraid I don't remember how that one goes - "properties->advanced" somewhere, no doubt... Or, you might prefer an "IDE" - an "Integrated Development Environment" which will allow you to clickie-clickie to edit, assemble, run, debug, etc. NaGoA was one created for Nasm. It appears to be "abandoned", but still works, AFAIK. http://www.visual-assembler.pt.vu/ (wow! that's *really* looking abandoned!) Probably the most popular IDE is RadAsm... http://radasm.cherrytree.at/radasm/ You can use Nasm with Visual Studio, too, I understand, though it may take more "setup" than with RadAsm(?). I prefer working from a command prompt, myself, and I'm not running Windows, so I can't help you much. Maybe someone who is can give you more specific advice... What you're seeing is "normal behavior" from Nasm. The error message, which goes by too fast to see, says "error: no input file specified". Best, Frank |