From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4pFn-0007yx-QI for qemu-devel@nongnu.org; Fri, 25 Feb 2005 18:52:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4pFV-0007pq-RB for qemu-devel@nongnu.org; Fri, 25 Feb 2005 18:52:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4pFV-0007nS-1U for qemu-devel@nongnu.org; Fri, 25 Feb 2005 18:51:57 -0500 Received: from [65.19.178.186] (helo=pythonhacker.is-a-geek.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D4oxR-0007Nn-CB for qemu-devel@nongnu.org; Fri, 25 Feb 2005 18:33:17 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id C5406403CF for ; Fri, 25 Feb 2005 18:33:15 -0500 (EST) Received: from pythonhacker.is-a-geek.net ([127.0.0.1]) by localhost (pythonhacker.is-a-geek.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00950-05 for ; Fri, 25 Feb 2005 18:32:54 -0500 (EST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id AC713403C6 for ; Fri, 25 Feb 2005 18:32:48 -0500 (EST) Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host. From: Darryl Dixon In-Reply-To: <001401c51b8c$cdd3d330$254d21d1@computername> References: <001401c51b8c$cdd3d330$254d21d1@computername> Content-Type: multipart/alternative; boundary="=-Erio7Ekp/cH+bv/9npz/" Date: Sat, 26 Feb 2005 12:32:46 +1300 Message-Id: <1109374366.7348.12.camel@localhost.localdomain> Mime-Version: 1.0 Reply-To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --=-Erio7Ekp/cH+bv/9npz/ Content-Type: text/plain Content-Transfer-Encoding: 7bit Whilst I disagree with your conclusion (Qemu not ready for use!?!), what you mention about the CD is valid and a real problem. I haven't seen Qemu crash because of it, but in every Windows guest OS I've tried (Win98se, WinXP, Win2000, Win2003, Longhorn) you actually need to go into Explorer in the guest and tell it to eject the CDROM (right-click -> eject) and then do the eject from the Qemu monitor and change to a new image before the Windows guest will recognise that a new disk has been inserted. Of course this isn't possible when actually running the OS install. It seems that there must be some sort of event, or memory flagged when a normal CDROM Eject button is pushed that Qemu doesn't emulate. Cheers, D On Fri, 2005-02-25 at 16:53 -0600, jeebs@yango.us wrote: >I decided to try and install Win98. Here are some comments about the Windows cvs build 20050223 downloaded from FreeOSZoo. (I have tried a few other cvs versions from there, and they have the same problems.) > > >There seems to be a serious problem with the guest OS (Win98, WinME) detecting when the cd image has changed. This means the guest is completely unable to do the compliance check, for example. > >Occasionally it'll detect that you've changed it. But not usually. > >I haven't heard anybody else comment about this, so I figured I should. > > >Qemu has major problems with spaces in pathnames. For example, when changing the cd to try and do the compliance check, it can't handle: "h:\win 9x\win 98.iso" > >Qemu wont accept quotes around it, either. > >Realistically, qemu should just accept the rest of the line as being the path. > > >It'd be nice if qemu gave an error message when you enter a pathname for a disk image that doesn't exist. > > >Once during the upgrade check, I tried to change the cd, I went into Windows dialog thing to change from C: to E: and it hadn't recognised the cd change. I accidently clicked on a directory from the old ISO image. That caused qemu to crash and immediately abort. It might have displayed a brief error notice or something, but it flashed by so quick I couldn't read it. > >Needless to say, it's not a "good thing" when the entire emulator crashes. > > >I accidently tried qemu on a very damaged ISO that Nero had just made for me. From the Win98 boot floppy, changing to the cd drive or doing a directory on it would cause qemu to abort. > > > >Eventually I just made up a cd image with Win98 and the old Win3 files (for complianc check) and I managed to mostly install Win98. > >But it blue screened after the reboot during the final part of the installation. > > >I've also tried Win98se, WinME and XP. None successfully. All crashed or were unable to continue due to the cd change bug. > >I don't know if these problems are specific to the windows ports on FreeOSZoo or not. > >But to put it very simply.... Qemu is most definetly not ready to actually use! > >I've read people installing Win98se, XP, linux, etc. but I can definetly say the daily windows builds aren't that reliable. > > >The only successful OS's I've installed are DOS and FreeDOS. Dr. DOS 7.03 doesn't work right. Some stuff in FreeDOS doesn't work right. And some programs under DOS don't work right. > >Again, I don't know if I just happen to have tried the versions on FreeOSZoo that were broken, or if there is a problem with the Windows builds, or if qemu is just that bad with Microsoft products (and FreeDos and Dr.DOS.) > > > > >_______________________________________________ >Qemu-devel mailing list >Qemu-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Darryl Dixon --=-Erio7Ekp/cH+bv/9npz/ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Whilst I disagree with your conclusion (Qemu not ready for use!?!), what you mention about the CD is valid and a real problem.  I haven't seen Qemu crash because
of it, but in every Windows guest OS I've tried (Win98se, WinXP, Win2000, Win2003, Longhorn) you actually need to go into Explorer in the guest and tell it to eject
the CDROM (right-click -> eject) and then do the eject from the Qemu monitor and change to a new image before the Windows guest will recognise that a new disk
has been inserted.  Of course this isn't possible when actually running the OS install.

It seems that there must be some sort of event, or memory flagged when a normal CDROM Eject button is pushed that Qemu doesn't emulate.

Cheers,
D

On Fri, 2005-02-25 at 16:53 -0600, jeebs@yango.us wrote: 
I decided to try and install Win98.  Here are some comments about the Windows cvs build 20050223 downloaded from FreeOSZoo.  (I have tried a few other cvs versions from there, and they have the same problems.)


There seems to be a serious problem with the guest OS (Win98, WinME) detecting when the cd image has changed.  This means the guest is completely unable to do the compliance check, for example.

Occasionally it'll detect that you've changed it.  But not usually.

I haven't heard anybody else comment about this, so I figured I should.


Qemu has major problems with spaces in pathnames.  For example, when changing the cd to try and do the compliance check, it can't handle: "h:\win 9x\win 98.iso"

Qemu wont accept quotes around it, either.

Realistically, qemu should just accept the rest of the line as being the path.


It'd be nice if qemu gave an error message when you enter a pathname for a disk image that doesn't exist.


Once during the upgrade check, I tried to change the cd, I went into Windows dialog thing to change from C: to E: and it hadn't recognised the cd change.  I accidently clicked on a directory from the old ISO image.  That caused qemu to crash and immediately abort.  It might have displayed a brief error notice or something, but it flashed by so quick I couldn't read it.

Needless to say, it's not a "good thing" when the entire emulator crashes.


I accidently tried qemu on a very damaged ISO that Nero had just made for me.  From the Win98 boot floppy, changing to the cd drive or doing a directory on it would cause qemu to abort.



Eventually I just made up a cd image with Win98 and the old Win3 files (for complianc check) and I managed to mostly install Win98.

But it blue screened after the reboot during the final part of the installation.


I've also tried Win98se, WinME and XP.  None successfully.  All crashed or were unable to continue due to the cd change bug.

I don't know if these problems are specific to the windows ports on FreeOSZoo or not.

But to put it very simply.... Qemu is most definetly not ready to actually use!

I've read people installing Win98se, XP, linux, etc. but I can definetly say the daily windows builds aren't that reliable.


The only successful OS's I've installed are DOS and FreeDOS.  Dr. DOS 7.03 doesn't work right.  Some stuff in FreeDOS doesn't work right.  And some programs under DOS don't work right.

Again, I don't know if I just happen to have tried the versions on FreeOSZoo that were broken, or if there is a problem with the Windows builds, or if qemu is just that bad with Microsoft products (and FreeDos and Dr.DOS.)




_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
--=-Erio7Ekp/cH+bv/9npz/--