Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!lise.unit.no!rmich
From: rmich@Lise.Unit.NO (Rolf Michelsen)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Segment overrides - TAMS bug???
Message-ID: <1991May8.084442.1687@ugle.unit.no>
Date: 8 May 91 08:44:42 GMT
References: <1991May3.063740.10187@ugle.unit.no> <1469@balrog.ctron.com> <299@altos86.Altos.COM>
Sender: news@ugle.unit.no
Reply-To: rmich@Lise.Unit.NO (Rolf Michelsen)
Organization: Norwegian Institute of Technology
Lines: 26

Sorry for the mess and confusion my original posting regarding segment
overrides in string instructions. It *is* possible to use overrides on
the SI part. My problem was to make TASM put these overrides into my
.obj file when writing things like 'rep movs [byte es:si],[di]'. However,
as someone pointed out, the *destination* for the move is the first
argument (just as for a normal mov instruction). I went back and tested
this 'rep movs [byte di],[es:si]' and of course it worked :-)

The only remaining problem is then that TASM don't flag 'mov [si],[di]' as 
an error which it clearly is. (And since the TASM quick reference *always*
uses the phrase 'move from SI to DI' which suggests SI before DI) this
may lead to troubles for us who usually use movsb/movsw and don't care about
the order of the operators.

Hope this settles the matter :-)


    ___________________  
   /                   | 
  / Snail-Mail:        | 
 /   Rolf Michelsen    |
/    Studpost 130      |
\    7034 Trondheim-NTH|
 \  E-Mail:            |
  \  rmich@lise.unit.no|
   \___________________|