X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: inport/outport BROKEN ?
Date: 26 Aug 2005 11:31:29 GMT
Lines: 31
Message-ID: <3n8cshFber4U1@news.dfncis.de>
References: <55mpg1h0hmo2nikgh2lb79vqht1puv25v2 AT 4ax DOT com> <200508242131 DOT j7OLVx75022085 AT envy DOT delorie DOT com> <afmtg1hqa6orq7902tufcfh1f7sqosbs8p AT 4ax DOT com>
X-Trace: news.dfncis.de qKVIyX5gX3kl1mvaYDdnuwOy1erT4lnV/llSZhXAUYh0Sj9puaOZymTdYO
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Radical NetSurfer <RadSurfer AT yahoo DOT com> wrote:

> Someone suggested I examine the -S output to see what DJGPP
> is really putting in there for inport/outport; and do the same for
> Borland 16, and try to determine whats actually happening.
> I am aware of no real-time debugger for Borland 16 except through
> the IDE which I only rarely use. 

Huh?  What would a real-time debugger have to do with inspecting the
machine code? BCC doesn't usually go through assembly, i.e. it doesn't
have a direct equivalent of the -S switch.  But that doesn't mean you
need a debugger to inspect machine code: tdump of the .obj file will
do just fine.

But yes, even 16-bit Borland has a stand-alone debugger.  It's
unsurprisingly called "Turbo Debugger", and comes in several separate
flavours, depending on the platform you're running from, and the kind
of application you're trying to debug.

> I was thinking 32-bit mode vs. 16-bit mode somehow influences how
> inport/outport react/operate, 

It most certainly does.

Another thing to watch out for is that these are 16-bit port accesses.
That's a somewhat shady area of the PC design, IIRC.  Most gadgets
make do with 8-bit port access.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.