All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeDos problems with Qemu 0.70
Date: Sat, 07 May 2005 20:55:42 +0200	[thread overview]
Message-ID: <427D0F2E.3020508@gmx.de> (raw)
In-Reply-To: <001201c55333$9dcfb580$334d21d1@organiza3bfb0e>

jeebs@yango.us schrieb:
> In a previous mesasge last weekend
> 
> http://marc.theaimsgroup.com/?l=qemu-devel&m=111523670008882&w=1
> 
> where I listed a number of problems with v0.70 (Windows build), some things
> that did work right, and some suggestions, I'm going to have to retract the
> part where I said freedos seems to work okay, including the mouse.
> 
> The mouse driver is still locking things up.  And once it locked up qemu
> enough that it didn't want to shut itself down.  I had to tell WinXP to
> forcibly shut it down.
> 
> And speaking of FreeDOS, somebody in the qemu-user forums is reporting a
> problem with write protecting a floppy.  Looks like the write failure isn't
> being properly passed to the guest.
> 
> http://m2.dad-answers.com/qemu-forum/viewtopic.php?t=627
> http://m2.dad-answers.com/qemu-forum/viewtopic.php?t=653
> 
> Looks like it's not OS specific, but you'll have to ask him for more 
> details.

I think I have to agree to this. Some weeks ago, I asked about a very 
strange error with changing CDs etc. This problem was solved by setting 
the correct permissions on /dev/hdc (apparently a udev update had reset 
them...) . Looks like in this case, the read access error of /dev/hdc 
wasn't properly handled. Maybe this is related to the write protection 
error.

Oliver Gerlich

      reply	other threads:[~2005-05-07 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-07 18:35 [Qemu-devel] FreeDos problems with Qemu 0.70 jeebs
2005-05-07 18:55 ` Oliver Gerlich [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=427D0F2E.3020508@gmx.de \
    --to=olig9@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.