From: "Mark & Candice White" Newsgroups: comp.os.msdos.djgpp References: <3B94D076 DOT FF60BDB0 AT crbkpc DOT com> Subject: Re: NASM Command line Lines: 30 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: Date: Sun, 16 Sep 2001 14:10:21 GMT NNTP-Posting-Host: 24.19.84.198 X-Complaints-To: abuse AT home DOT net X-Trace: news2 1000649421 24.19.84.198 (Sun, 16 Sep 2001 07:10:21 PDT) NNTP-Posting-Date: Sun, 16 Sep 2001 07:10:21 PDT Organization: Excite AT Home - The Leader in Broadband http://home.com/faster To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Chris Smith wrote in message news:3B94D076 DOT FF60BDB0 AT crbkpc DOT com... > Sorry...I know that this isn't exactly the right subject matter for this > mailing list... > but I've enjoyed djgpp so much that I decided to take on NASM. The only > problem is that I'm having trouble getting started from the command > line. I receive the following error when attempting to assemble a simple > com file under win98: > > c:\>nasm16 -f bin myfile.asm -o myfile.com > nasm: more than one input file specified > type 'nasm -h' for help > > I've read all the docs and searched with web with little luck. Obviously > I must be missing something trivial. If anyone could please let me know > what it is, I'd really appreciate it. NASM is picky about the order of its arguments. nasm [options] file nasm -f bin -o myfile.com myfile.asm You likely know this by now but just incase I thought I should post it. Why are you running nasm16? IIRC all nasm make either 16 or 32 bit code, nasm16 is linked to RUN in a 16bit environment like an XT or no DPMI, you can run the normal one in win98.