Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail
From: "Rod Pemberton" <dont_use_email@xnothavet.cqm>
Newsgroups: alt.os.development,comp.os.msdos.programmer,alt.lang.asm
Subject: Re: detecting emulation or console windows
Date: Mon, 02 Jun 2014 00:34:32 -0400
Organization: Aioe.org NNTP Server
Lines: 30
Message-ID: <op.xgs8bugb6zenlw@localhost>
References: <op.xgqwuvss6zenlw@localhost> <fp17gsuzkhbc.16j41sl6al0h6.dlg@40tude.net>
NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/12.16 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.os.msdos.programmer:1376

On Sun, 01 Jun 2014 16:43:02 -0400, JJ <duh@nah.meh> wrote:

> Most emulators ad virtualizators have backdoor for communicating with the
> host system. For examples, Parallels and VMWare uses I/O ports, VirtualPC
> uses invalid opcodes, and VirtualBox uses SYSENTER.

Yes, but that presents me with even more tests ...

Virtual PC opcode series:
0x0f 0x3f xx xx
0x0f 0xc7 0xc8 yy yy

DOSBox callback
0xfe 0x38

NTVDM opcode series:
0xc4 0xc4 xx xx

I'm not sure how to use those, even though I have the series.
And, I can't test NTVDM or Virtual PC, currently.

> And lastly, a less reliable method that search for a specific
> text in the BIOS ROM can also be used.

Yes, I suspect the reboot emulation errors I found in DOSBox and
dosemu won't work with QEMU because QEMU correctly implements the
major BIOS entry points.


Rod Pemberton