NASM - The Netwide Assembler
NASM Forum => Using NASM => Topic started by: nobody on October 05, 2006, 09:21:54 PM
-
How to run Nasm, from MS-DOS window or from Run box? What format need be source files to compile? Just have code sources on html page, and in .txt format. What editor is suitable to edit source code? Notepad?
Need compile code with the following parameters:
nasmw -s -fbin -o filename.s filename.asm
How it need be done?
-
> How to run Nasm, from MS-DOS window or from Run box?
What I've doen is:
1. Create a tree dir for nasm:
mkdir c:\NASM\BIN
mkdir c:\NASM\INC
mkdir c:\NASM\LIB
2. Put nasm.exe in c:\NASM\BIN
3. Add c:\NASM\BIN to the PATH environment variable.
SET PATH=%PATH%;c:\NASM\BIN
Is possible create a nasmenv.bat with:
SET PATH=%PATH%;c:\NASM\BIN
Now you can invoke nasm from any work directory.
More simple:
Put nasmw.exe in your system directory
(C:\Windows\System32)
> What format need be source files to compile?
A simple text file.
> What editor is suitable to edit source code?
Any editor you want. I use VIM, Windows/Linux
portable:
http://www.vim.org/download.php (http://www.vim.org/download.php)
Ago time I used PEF, Windows.
Many people use RadAsm Ide, Windows:
http://www.radasm.com/ (http://www.radasm.com/)
NAGOA was developed to work with NASM, and
includes a lot of features, include files
with macros, samples source code, texts.
Windows:
http://visual-assembler.pt.vu/ (http://visual-assembler.pt.vu/)
> Need compile code with the following parameters:
> nasmw -s -fbin -o filename.s filename.asm
Run the win console.
Go to your work dir: cd C:\my\work\dir
Add the path where is nasmw.exe to your PATH:
SET PATH=%PATH%;c:\NASM\BIN
now do:
nasmw -s -fbin -o filename.s filename.asm
------
nmt
-
Hi Numa,
The oddly-extensioned "filename.s" that the OP (Mistral) is asking for is a buffer overflow exploit that downloads and executes one "ncat.exe" which installs a "backdoor" on the victim's machine. Help him if you wish (the information is not hard to find - unfortuntely), but I thought you ought to know.
Best,
Frank
-
> The oddly-extensioned "filename.s" that the OP
>(Mistral) is asking for is a buffer overflow
> exploit that downloads and executes one
> "ncat.exe" which installs a "backdoor" on the
> victim's machine. Help him if you wish (the
> information is not hard to find - unfortuntely),
> but I thought you ought to know.
Thanks Frank, I did not know nothing about this.
--------
nmt