Re: Nasm Error


"fred smith" <fred@xxxxxxxxxxx> wrote in message
news:474d1a2e$0$23258$afc38c87@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply Frank, I am writing a Hobby OS.

So, am I and many others too... mostly on alt.os.development.

All of the
bootloader, second stage stuff is written with Nasm, all of the kernel
is written in Watcom C, with the odd Wasm module linked into it. I was
doing this all previously under DOS.


Mine's written in Open Watcom C and DJGPP (GCC for DOS) with mostly inline C
assembly and a small amount of NASM.

GCC isnt an option for me, it would be too much of a headache to convert
everything over,

Not the C part. Should be close to 100% except for different namings of DOS
functions, which you shouldn't be using in an OS anyway.

and the GNU assemblers horrible at&t syntax is
something I want to stay as far away as I can from.


Yeah, that's little bit different, but not that hard to do: reverse the
registers, throw on some size letters, add one percent if no args, add two
percents if args, lookup some special letter codes to pass args... Sigh,
okay, more work than one recollects! ;-)

As Watcom and Nasm appeared to be on the OS/2 platform, and I had a
spare box with the operating system doing nothing, I thought "why not".


"Why not." That's how most of us got started... heh. ;-)


Rod Pemberton

.

Relevant Pages

  • 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: NASM - VC++ Linking Problems
    ... My "experiment" didn't have a "section" or "segment" directive, and still the symbol appeared in the .obj. ... In an output format where it's valid, Nasm should export a "global" symbol - no excuses! ... (I don't mean to knock Watcom - I haven't tried WASM, but the openwatcom package as a whole is quite nice - unless I'm mistaken, the Windows executable of Nasm at SF was built by Watcom - running on Linux!) ... knows about the name mangling scheme used by its "companion" compiler, ...
    (comp.lang.asm.x86)
  • 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)