Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!msuinfo!news
From: jhl@eecae.msu.edu (John Lawitzke)
Newsgroups: comp.os.msdos.programmer
Subject: Code that assembled under TASM 1.0 that won't under TASM 2.0
Message-ID: <1990Sep5.170322.27305@msuinfo.cl.msu.edu>
Date: 5 Sep 90 17:03:22 GMT
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University, East Lansing
Lines: 32


The following code fragment used to compile and run fine
under TASM 1.0. Under TASM 2.0 it doesn't. Any ideas out there?

		IDEAL
		JUMPS
		MODEL SMALL
		P386
		CODESEG
;
;	CODE DELETED
;
		LIDT	[CS:IDTPTR]
		LGDT	[CS:GDTPTR]
;
;	CODE DELETED
;
GDTPTR		DW	....
IDTPTR		DW	....

The problem lies with the LIDT and LGDT statements. Under TASM 1.0 the
LIDT statement would show 2e: 0f 01 1e 05f1r in the listing file. Under
TASM 2.0, the statement is assembled to the same bytes, however I also
get the error "Argument to operation or instruction has illegal size".



--
j                               |%|John Lawitzke, Dale Computer Corp., R&D
                                |%|UUCP: uunet!mailrus!sharkey!dale1!jhl
				|%|  or: uunet!frith!dale1!jhl
Inquiring minds just wondering. |%|Internet: jhl@frith.egr.msu.edu