Date: Sat, 24 Aug 2002 12:26:56 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "H.Shiozaki" <hshiozaki AT nifty DOT com>
Message-Id: <2110-Sat24Aug2002122655+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp AT delorie DOT com
In-reply-to: <ak6079$gjb$2@news521.nifty.com> (hshiozaki@nifty.com)
Subject: Re: IO_Port Access in DJGPP + Windows 2000
References:  <ak6079$gjb$2 AT news521 DOT nifty DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "H.Shiozaki" <hshiozaki AT nifty DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 24 Aug 2002 03:49:41 +0900
> 
> I made a program included IO_Port_Access, by DJGPP_V204.
> A program can run in Win_98_DOS-BOX and Win_98_command_prompt_only.
> I re-compiled that program in DJGPP_V204 + Win2K,
> But, new program can not do nothing to the IO_PORT in Win2K_DOS-BOX.

A known problem: all descendants of the Windows/NT family don't let
DOS programs have a direct access to I/O ports.

> Q3. Which to be use in Win2K, CMD.exe and Command.com?

You can use either, in most cases it doesn't matter.

>     (What are difference between CMD.EXE and Command.com?
>     or are there information about it ?)

"cmd /help" (or is it "cmd /?"?) will print some information about
the advanced features of CMD.

> A sample program below can run in Win98(DOS-BOX)
> But can not run in W2K(DOS-BOX)
> Please change this program to run under Win2K.

There's no way of doing that: as I said above, W2K won't let you
access I/O ports.