Re: Nasm Error



fred smith wrote:

....
Only too happy to help :-) I'll send them up to you shortly.

Got 'em, and put 'em up on SF:

http://nasm.sf.net

You point out in your note:

"
Some limitations though, and they don't really bother me because I use Nasm to output DOS .EXE .COM or ELF32 binaries, is that anyone using Nasm on OS/2 wont be able to produce native OS/2 Binaries, OS/2 Can only load DOS based .EXE's in a DOS session, in an OS/2 Command prompt session, a DOS session will be spawned if a DOS executable is attempted to be run. OS/2's native .EXE format is IBM's Linear Executable format (os2_le os2_lx format), and is the only format that will run natively in a OS/2 Command prompt session (or in the OS/2 Presentation manager GUI). It shouldnt pose any problem, I doubt there are many people (if any at all) that write programs natively for OS/2 in pure assembler.
"

Okay... that would be a "linker issue"... or Nasm probably *could* produce a LE/LX header in "flat binary", too (it will for MZ, PE, and ELF - I don't see why not...). If the "native OS/2 linker" (???) or the OpenWatcom linker you used to link Nasm use OMF, Nasm should handle it. If it's COFF, Nasm should do that, too. If it's something completely different... back to flat binary. :)

I see the "MZ" sig in the Nasm binary you sent me, and the "dos stub" says "This is an OS/2 32-bit executable" where I'd expect to see "This program requires Windows" (or "cannot be run in a dos session" or whatever). Doesn't look all that "far out". I'll bet Nasm would do it! I understand that your interest is in developing your OS, not programming for OS/2...

Thanks for those binaries, Fred. Our other OS/2 user thanks you, too! :)

Best,
Frank
.



Relevant Pages

  • Re: Nasm Error
    ... Some limitations though, and they don't really bother me because I use Nasm to output DOS .EXE .COM or ELF32 binaries, is that anyone using Nasm on OS/2 wont be able to produce native OS/2 Binaries, OS/2 Can only load DOS based .EXE's in a DOS session, in an OS/2 Command prompt session, a DOS session will be spawned if a DOS executable is attempted to be run. ...
    (alt.lang.asm)
  • Re: New to Debian Linux - I have NASM experience under DOS 6.22
    ... > simple NASM program under Linux. ... > whether there is a more official or reliable way to make a NASM ... Windows automatically including the "current directory" in the ... directory" is NOT part of that PATH as it is with DOS... ...
    (alt.lang.asm)
  • Re: Linker strangeness
    ... but it didn't execute correctly. ... > DOS, but not under windows. ... package, used separate full MASM package, v5.xx or v6.xx, v6.11 is the ... binary (NASM is able to do this w/o external linker) and then include it ...
    (alt.lang.asm)
  • Re: Just learning...
    ... I *was* running win98, when I was running Windows, but a week or so ago, it decided not to boot. ... Which build of Nasm 0.98.39 did you get? ... The Windows build won't work with NasmIde - claims to have assembled with no errors, but Nasm doesn't even run. ... I mostly used the djgpp (32-bit dos) build. ...
    (comp.lang.asm.x86)
  • Re: Excercices
    ... That context was not pertaining to Nasm. ... DOS accepts '/' as a directory separator as well as '\', ... command line parsing _before_ the program even runs. ... They no longer do my traditional winks tournament lunch - liver and bacon. ...
    (alt.lang.asm)