From: Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject: Re: .COM and bash
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1020725074539 DOT 20185B-100000 AT is>
User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha))
Message-ID: <1027780155.463637@queeg.ludd.luth.se>
Cache-Post-Path: queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se
X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date: 27 Jul 2002 14:29:15 GMT
Lines: 31
NNTP-Posting-Date: 27 Jul 2002 14:29:15 GMT
NNTP-Posting-Host: queeg.ludd.luth.se
X-Trace: 1027780155 news.luth.se 440 130.240.16.109
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
:> Is bash supposed to refuse running .COM executables?

: No, not AFAIK.  What version of Bash is that?

2.04.7(1)-release

It's strange. It does execute most .COM files but not this one which
you can create with this debug script ("debug <cpuid.scr"):

----- debug.scr starts. -----
a
db 66
xor ax, ax
inc ax
db 0f a2
ret

r cx
7
n cpuid.com
w
q
----- debug.scr ends. -----

The program is just calling the CPUID instruction with EAX=1.


Right,

						MartinS