From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: qemu-devel@nongnu.org
Subject: Re: Update: [Qemu-devel] MS-DOS Network Client
Date: Thu, 17 Mar 2005 15:36:21 +0100 [thread overview]
Message-ID: <3c01754155d23e22ae3f1fc3c02f88dc@elis.ugent.be> (raw)
In-Reply-To: <711964607@web.de>
On 17 mrt 2005, at 15:22, Andreas Krause wrote:
> But: Both configuration aren't able to transmit a single packet. Using
> Linux or NT4.0 images with the same configuration of qemu and host OS
> networking works pretty fine. But no networking in DOS.
>
> Any clue?
I think there is some problem with interrupts under Dos. When booting
FreeDos (the image from freeoszoo) and choosing the config with the
mouse driver (I think it's the emm386 one), then qemu hangs during the
initialisation of the mouse driver in some emulation loop involving an
IRQ.
Jonas
prev parent reply other threads:[~2005-03-17 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 14:22 Update: [Qemu-devel] MS-DOS Network Client Andreas Krause
2005-03-17 14:36 ` Jonas Maebe [this message]
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=3c01754155d23e22ae3f1fc3c02f88dc@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--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).