Re: can somebody help me with the problem with tasm models

From: darkie (necro.darktangent_at_gmail.com)
Date: 03/09/05 

Date: 9 Mar 2005 10:16:57 -0800

Thank you very much for the reply.It helped me very much to understand
it.There are some little doubts which i want to clear.
When i don't use the .386 directive and use your above code i get the
-> value out of range error. Now with the full segment definition i had
done something like this

dataOne segment
          array1 db 72000 dup(0)
dataOne ends

code segment
assume cs:code,ds:data
start:
         mov ax,data
         mov ds,ax
         mov ah,4ch
         int 21h
code ends
end start

do i need to make 2 segments each with 64kb limit and load the
segments into the ds
register ?

Relevant Pages

  • Re: Trap representations
    ... bytes directly (via a general integer register) and not needing to load ... segment register with the segment portion of an invalid pointer, ... Leave the pointer in memory, ...
    (comp.lang.c)
  • Re: Free x86 C compiler wanted
    ... If you load them anywhere else they don't work. ... [COM files can load anywhere in memory, sinec DOS sets the CS register ... to do their own segment register management. ... John is correct that COM files may be loaded into any segment. ...
    (comp.compilers)
  • Re: Free x86 C compiler wanted
    ... If you load them anywhere else they don't work. ... to do their own segment register management. ... AFAIR COM programs are restricted to the small memory ... where everything resides in a single 64K segment. ...
    (comp.compilers)
  • Re: Using SS for non-stack operations?
    ... > third segment register as two data sources combine to affect a third. ... Well, if you're real mode DOS, and you need an extra data segment, the ... So long as you can put the third area in the code or stack ...
    (comp.lang.asm.x86)
  • Re: NASM org directive
    ... The .COM format reserves the first 0xFF bytes for the Program Segment ... something in your .bin source. ... where the stack segment points to. ... Besides you state the load address at 0x1000:0x0000 ...
    (comp.lang.asm.x86)