Message-ID:	<000301c12597$8d4233a0$1d08e289@mpaul>
From:	"Matthias Paul" <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
To:	<opendos AT delorie DOT com>
References:	<Pine DOT GSO DOT 4 DOT 33 DOT 0108091937540 DOT 23591-100000 AT jedi DOT apana DOT org DOT au> <000c01c121b3$eb0c50c0$8708e289 AT mpaul> <2 DOT 07b7 DOT 82TX DOT GHV2Q2 AT belous DOT munic DOT msk DOT su>
Subject:	DEBUG issues (Was: Re: more on the batch file problem)
Date:	Wed, 15 Aug 2001 06:17:28 +0200
Organization:	University of Technology, RWTH Aachen, Germany
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id KAA25162
Reply-To:	opendos AT delorie DOT com

On 2001-08-10, Arkady V.Belousov wrote:

> Compatability issues: does DR-DOS DEBUG support INT#
> non separated from "INT"? Does it supports size modifier
> at any size?
> 
>         mov [100],byte 0
>         mov word [100],0

Yes, but the proper syntax is:

 mov byte ptr [100],0
 mov word ptr [100],0
 mov dword ptr [100],0

You can abbreviate "byte ptr" to "by", "word ptr"
to "wo", and "dword ptr" to "dw".

See NWDOSTIP.TXT (MPDOSTIP.ZIP) for details.

>         int29
>         int3

No, unlike MS-DOS DEBUG, the DR-DOS DEBUG requires
a space between the command and its arguments.
I do not think this will change, because even if
MS-DOS DEBUG allows this, it´s invalid syntax and
may cause problems when extending support for new
processors. Mind that the MS-DOS DEBUG only supports
the 808x opcodes, while the DR-DOs DEBUG already
supports all commands (available under DOS) up to
the Pentium.

Do you have a special need for this?

Greetings,

 Matthias

-- 

Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
<mailto:Matthias DOT Paul AT post DOT rwth-aachen DOT de>; <mailto:mpaul AT drdos DOT org>
http://www.uni-bonn.de/~uzs180/mpdokeng.html; http://mpaul.drdos.org

- Raw text -