Why do we need AX instead of MOV DS, data directly with a segment?

Question

So I was being taught the basics of how to program with Tasm (Turbo assembler 16 bits) and these two lines were explained to me, but now I can't remember why have to do it like this:

start: mov ax, data
       mov ds, ax

Why is it that we cannot set DS directly to a data segment we defined?

start: mov ds, data

David Hoelzer · Accepted Answer · 2015-06-09T00:26:13.733

3

The reason that you cannot do it is not a limitation in TASM but a "feature" of the instruction set. The Intel/AMD instruction sets do not support moving an immediate value into the DS register.

It is not unusual in CISC based computers to have various restrictions and limitations. It is very useful to keep the instruction reference handy for this reason. :)

edited Jun 09 '15 at 00:26

answered Jun 08 '15 at 23:59

David Hoelzer

15,862
4
48
67

BTW "instruction reference" link doesn't seem to work. – sempiedram Jun 09 '15 at 00:13
Yes, attempting `MOV DS,0x1FFF` is immediate mode. `MOV DS,AX` is a register access. I'll fix the link. :) – David Hoelzer Jun 09 '15 at 00:25

user19358369 · Answer 2 · 2022-06-17T11:12:18.390

0

All segment registers need to be set with a value from a non segment registers.. Segment registers include ds (data segment) es (extra segment) fs (file segment) gs (general segment) cs (code segment) and ss (stack segment).. If you want to set ds to data without disturbing your other registers consider using the following...

Push ax

Mov ax, data

Mov ds, ax

Pop ax

That will preserve the value of the ax register

edited Jun 17 '22 at 11:12

answered Jun 17 '22 at 11:09

user19358369

1
1

3

fs and gs do not stand for "file segment" or "general segment". fs is extra segment 2, gs is extra segment 3. – ecm Jun 17 '22 at 11:31

Why do we need AX instead of MOV DS, data directly with a segment?

2 Answers2