From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows 98 - hardware
Date: Mon, 3 May 2004 22:47:59 -0400 [thread overview]
Message-ID: <20040504024759.GB11099@jbrown.mylinuxbox.org> (raw)
On Mon, May 03, 2004 at 11:22:13PM +0200, Lean Fuglsang wrote:
> On Mon, 2004-05-03 at 21:51, Jim C. Brown wrote:
>
> > You will need to go to "Add New Hardware" in the "Control Panel" and
> > then (after it has scaned for plug&play hardware and finds none) choose
> > to install a network adaptor from the list (i.e. skip detection of
> > non-plug&play hardware). Install a Novel/Antherm 2000 card. (Apologies for
> > bad spelling.) I don't remember what the manufactor was, it's
> > either Microsoft, Novel, or Novel/Antherm. I think. Set the
> > IO mem range that starts with 300 (300-3FF iirc), and the IRQ to 9. Take
> > defaults for everything else. Finally reboot. If all goes well, it
> > should work. (In my case I had to apply a patch and recompile qemu,
> > but that was for qemu 0.5.2)
> Okay, i tried an NE2000-compatible, found in Novel/Antherm.
> I could set I/O mem range to 300, but it is 300-31F
> There is an option 3E0-3FF.
No it is definitely 300-31F.
> There is also no IRQ 9, but only IRQ 9/2.
Yes that is right.
> When I boot windows it comes with BSOD with an NDIS error.
> Hopes this can bring back som rusty memory :)
No, this never happened to me. Of course I use vde, not the builtin tuntap
or the userspace network, so there might be some differences.
>
> *Bonus trivia*
> Will qemu-fast ever work with windows 98? Or does windows need to be
> patched?
No. qemu-fast is designed for loading a linux kernel w/o any BIOS. In theory,
you could modify the source code of Windows so it would start out with a linux
like "kernel" bootstrapper (which also emulated all of the BIOS stuff) and then
have it load the rest of Windows. In reality, this is not going to happen.
(I suppose, if you are into the black arts, you could create a linux kernel-like
bootstrapper instead, and have that load up io.sys...) Also, the modified
Windows OS would need to use linux syscalls and mmap(). (Again, if you
are into the black arts, you could try patching the machine code...)
> --
> Lean Fuglsang <lean@omnia.dk>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next reply other threads:[~2004-05-04 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 2:47 Jim C. Brown [this message]
2004-05-04 3:19 ` [Qemu-devel] Windows 98 - hardware Fabrice Bellard
2004-05-04 14:46 ` Lean Fuglsang
2004-05-04 15:44 ` [Qemu-devel] Interesting progress with Win2k Jason Gress
2004-05-04 16:30 ` [Qemu-devel] w2k install problem & interesting progress Sebastien Bechet
2004-05-12 21:40 ` [Qemu-devel] QEMU OS Support Table Fabrice Bellard
2004-05-12 21:57 ` Grzegorz Kulewski
2004-05-04 22:38 ` [Qemu-devel] Windows 98 - hardware Fabrice Bellard
-- strict thread matches above, loose matches on Subject: below --
2004-05-03 19:11 Lean Fuglsang
2004-05-03 19:51 ` Jim C. Brown
2004-05-03 21:22 ` Lean Fuglsang
2004-05-03 21:31 ` Hetz Ben Hamo
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=20040504024759.GB11099@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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).