qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Programmingkid <programmingkidx@gmail.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help with Windows NT 4.0
Date: Tue, 22 Aug 2017 11:19:43 -0400	[thread overview]
Message-ID: <161C9C21-7DBB-4A29-9AF5-4459D32B5DAE@gmail.com> (raw)
In-Reply-To: <600cf481-8708-a622-cc6f-a7ecf14acdab@ilande.co.uk>


> On Aug 14, 2017, at 3:18 AM, Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> wrote:
> 
> On 14/08/17 07:51, Paolo Bonzini wrote:
> 
>> On 13/08/2017 21:13, Programmingkid wrote:
>>> Lately I found out that Windows NT 4.0 seems to work well with the
>>> 486 and pentium processors. Using "-cpu 486" made installing it
>>> actually work. Now I am seeing another issue. When I boot Windows NT
>>> 4.0 I see this error message:
>>> 
>>> *** STOP: 0x0000007B (0x807A8610,0x00000000,0x00000000,0x00000000) 
>>> INACESSIBLE_BOOT_DEVICE
>>> 
>>> Would anyone know a way to solve this issue?
>> 
>> Hervé is probably the best person to answer this question.  Maybe try
>> installing it with SCSI disks ("-drive if=scsi,id=hd,file=... -drive
>> if=scsi,id=cd,file=... -device lsi -device scsi-hd,drive=hd -device
>> scsi-cd,drive=cd").
> 
> FWIW I used to run NT 4.0 in QEMU 0.9.1 without too many problems,
> (although every so often the mouse would go crazy and it would require a
> reboot). The only thing I needed to do was install updated VGA drivers
> from http://www.bearwindows.boot-land.net/vbemp.htm in order to prevent
> issues with the mouse pointer not displaying correctly.
> 
> I'm also fairly sure that was with a single -hda on the command line, so
> it might be useful to go back quite far back in time to figure out what
> changed.
> 
> 
> ATB,
> 
> Mark.

I encountered the mouse problem also. It acts very similar to what we saw with Mac OS 9 not too long ago. 

  parent reply	other threads:[~2017-08-22 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 19:13 [Qemu-devel] Help with Windows NT 4.0 Programmingkid
2017-08-14  6:51 ` Paolo Bonzini
2017-08-14  7:18   ` Mark Cave-Ayland
2017-08-15 19:26     ` Programmingkid
2017-08-22 15:19     ` Programmingkid [this message]
2017-08-15 18:46   ` Programmingkid
2017-08-15 22:27     ` Paolo Bonzini
2017-08-16 16:32       ` G 3
2017-08-16 23:19       ` G 3
2017-08-18  4:31       ` Programmingkid
2017-08-18  8:46         ` Artyom Tarasenko
2017-08-18 13:36           ` Programmingkid
2017-08-18 19:23             ` John Snow
2017-08-18 19:48               ` Programmingkid

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=161C9C21-7DBB-4A29-9AF5-4459D32B5DAE@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=hpoussin@reactos.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).