From: Martin Bochnig <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: SoftICE under DOS16, anybody? __/__ Re: [Qemu-devel] [PATCH] intentinoal slowing down qemu - brake
Date: Sat, 02 Dec 2006 00:43:14 +0100 [thread overview]
Message-ID: <4570BE12.2030706@gmx.com> (raw)
In-Reply-To: <4570A5DC.4000502@gmx.com>
Martin Bochnig wrote:
>>Might something like that help SoftICE for DOS16 to run properly without
>>freezing the whole guest after one or two ^D's (i.e. for setting
>>breakpoints and switching back to the dos command.com)?
>>WinICE (on DOS386 a.k.a. {win386.exe / chicago's dos386.exe, now called
>>vmm32.vxd}) does/did already work well, when I last tested this a year
>>ago, but SoftICE for real mode DOS would always hang the whole guest
>>when being run inside QEMU (emulation case, not yet tested in case of
>>x86_x_x86 virtualization).
>>The same happens when using the Insignia_SoftWindows Pentium-ISA-PC
>>Emulator on Solaris_sparc, running any version of (MS-/IBM) or DRDOS.
>>Bochs claims to provide a more accurate emulation than qemu (at the cost
>>of making it marginally slower), but doesn't fix the SoftICE issue either.
>>
>>It does - on the other hand - work as expected inside any version of
>>SunPCi, which only emulates a bit of io and graphics, but uses a
>>physical x86 cpu, rather than emulating it (I think it doesn't even have
>>to virtualize it, because nobody else is using the cpu sitting on that
>>pci card).
>>
>>Has onybody found a way to work around the SoftICE_for_DOS16
>>instabilities under qemu?
>>(btw, my problems *are* qemu-dependant, not caused by an incompatible
>>himem.sys or anything of that sort / identical diskimages tested under
>>SunPCi, SoftWindows and qemu_for_SolarisSPARC-Hosts).
>>
>>Thanks,
>>Maddin
>>
>>
I might some remote day invest a bit of effort into trying to find out
WHY exactly SoftICE_for_realmodeDOS hangs the emulation (under qemu,
bochs and SoftWindows/RealPC) :
Whether or not it freezes "somehow internally" because of "actually
running", or, more specifically, whether it just has to do with
listening to the keyboard for "^D" sequences (int16h and int21h_AH==01 /
see Ralf Brown's grand Interrupt list) to activate the SoftICE UI.
If it is "just" the latter, then maybe due to a timing related problem,
or maybe because the SoftICE-TSR somehow interferes with COMMAND.COM (or
any shell like i.e. BASH_for_DOS or 4DOS.COM) that are concurrently
listening to kbd input and therefore actively issuing certains DOS-21h
and 16h interrupts permanently (with appropriate values in (E)AL, (E)AL,
or(E)AX, permanently requesting the keyboard, if it has new input in its
associated stdin buffer (not quite correct, simplified).
The issue applies to all major SoftICE_for_realmodeDOS releases/versions.
Thanks.
--
Martin
next prev parent reply other threads:[~2006-12-01 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 14:56 [Qemu-devel] [PATCH] intentinoal slowing down qemu - brake Miroslav Novak
2006-12-01 15:41 ` Martin Guy
2006-12-01 15:43 ` Martin Guy
2006-12-01 19:35 ` Johannes Schindelin
2006-12-01 21:59 ` SoftICE under DOS16, anybody? __/__ " Martin Bochnig
2006-12-01 23:43 ` Martin Bochnig [this message]
2006-12-05 16:54 ` Miroslav Novak
2006-12-05 21:29 ` Miroslav Novak
2006-12-06 7:03 ` Manish Gajbhiye
2006-12-06 9:52 ` Network problem, was " Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4570BE12.2030706@gmx.com \
--to=mb1x@gmx.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).