Lines: 26
X-Admin: news AT aol DOT com
From: sterten AT aol DOT com (Sterten)
Newsgroups: comp.os.msdos.djgpp
Date: 10 Aug 2003 01:35:58 GMT
References: <3f35735b$0$167$cc7c7865 AT news DOT luth DOT se>
Organization: AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com
Subject: Re: ATT assembler question
Message-ID: <20030809213558.07244.00001052@mb-m12.aol.com>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>.byte 234,12,177
>
>N. B. untested.


yes, that works. However , I tried  .byte 228,96  (in al,60h)  , but it doesn't
seem to work as expected.
(it's a pity, that C doesn't let me test what key is pressed !)

>
>: I thought, I could write and compile my programs in NASM and then
>: simply use the "db "  statements to convert them to ATT  for use in
>GCC+DJGPP
>
>You don't have to recode them into .byte statements. Just ask nasm to
>output COFF and you'd be ready to link.

thanks, but I think, I prefer the .byte  method.
First,  I don't know  what COFF is, nor how to link.
Second , when I give my source to others, I don't want to
require that they do get NASM,  do the COFF  and link,
just when they only want to implement a small change,
like changing a parameter.


Guenter