DOS ain't dead

The QEMU team has released version 0.10.0 on 04 March 2009.

Home page: http://www.qemu.org/
Download (sources): qemu-0.10.0.tar.gz
Download (Win32 binary): http://www.bttr-software.de/qemu/ (my slightly modified builds)
Announcement: ANNOUNCE: Release 0.10.0 of QEMU

Changes:
o TCG support
_- No longer requires GCC 3.x
o Kernel Virtual Machine acceleration support
o BSD userspace emulation
o Bluetooth emulation and host passthrough support
o GDB XML register description support
o Intel e1000 emulation
o HPET emulation
o VirtIO paravirtual device support
o Marvell 88w8618 / MusicPal emulation
o Nokia N-series tablet emulation / OMAP2 processor emulation
o PCI hotplug support
o Live migration and new save/restore formats
o Curses display support
o qemu-nbd utility to mount supported block formats
o Altivec support in PPC emulation and new firmware (OpenBIOS)
o Multiple VNC clients are now supported
o TLS encryption is now supported in VNC
o Many, many, bug fixes and new features

EDIT: changed download URL
EDIT-2: changed home page URL

---
Forum admin

I've made a smaller and faster binary using MinGW's GCC 4.3.0 alpha instead of GCC 3.4.5: qemu-0.10.0-win32-2.7z

---
Forum admin

> I've made a smaller and faster binary using MinGW's GCC 4.3.0 alpha instead
> of GCC 3.4.5:
> qemu-0.10.0-win32-2.7z

Thanks! Is it possible to include the qemu64.exe binary to your package?

---
MS-DOS forever!

> Thanks! Is it possible to include the qemu64.exe binary to your package?

Is this not the same as qemu-system-x86_64.exe, which is already included?

---
Forum admin

Another build is in qemu-0.10.0-win32-3.7z, where I've rebuilt SDL and zlib using GCC 4.3.0 alpha and used "-mms-bitfields -march=i686" flags for all QEMU binaries.

---
Forum admin

> > Thanks! Is it possible to include the qemu64.exe binary to your package?
>
> Is this not the same as qemu-system-x86_64.exe, which is already included?

Yes, thanks! I somehow overlooked this, obviously it was hidden too well.

---
MS-DOS forever!

> I've made a smaller and faster binary using MinGW's GCC 4.3.0 alpha instead
> of GCC 3.4.5:

How much stable is the mingw gcc 4.3.0? Did you find some problems with compiling other programs? I still use 3.4.5 and it is in mingw for long years so it's time to update?

---
DOS gives me freedom to unlimited HW access.

> > I've made a smaller and faster binary using MinGW's GCC 4.3.0 alpha
> instead
> > of GCC 3.4.5:
>
> How much stable is the mingw gcc 4.3.0? Did you find some problems with
> compiling other programs? I still use 3.4.5 and it is in mingw for long
> years so it's time to update?

I'd heard they lacked a maintainer and had issues with upgrading due to .DLLs or exceptions or both. And I was highly sceptical that a 4.3.0 compile would work for me (due to issues I had installing it in Cygwin previously), but it seems okay. However, is KQEMU deprecated or what? (My previous version is claimed to be disabled due to version incompatibility. Still seems reasonable speed, though, although I only barely tested it.)

> How much stable is the mingw gcc 4.3.0? Did you find some problems with
> compiling other programs?

I only tried it on QEMU and it worked fine.

> I still use 3.4.5 and it is in mingw for long years so it's time to update?

There are different opinions on that. Just search on mingw-users for more information.

---
Forum admin

> However, is KQEMU deprecated or what? (My
> previous version is claimed to be disabled due to version incompatibility.
> Still seems reasonable speed, though, although I only barely tested it.)

Quoting from the QEMU SVN thread here: "If you wish to use the kqemu accelerator, you need kqemu-1.4.0pre1.tar.gz from the QEMU home page."

---
Forum admin

> > However, is KQEMU deprecated or what? (My
> > previous version is claimed to be disabled due to version
> incompatibility.
> > Still seems reasonable speed, though, although I only barely tested
> it.)
>
> Quoting from the QEMU SVN thread here: "If you wish to use the kqemu
> accelerator, you need kqemu-1.4.0pre1.tar.gz from the QEMU home page."

Which is only provided in source form.

> > Quoting from the QEMU SVN thread here: "If you wish to use the kqemu
> > accelerator, you need kqemu-1.4.0pre1.tar.gz from the QEMU home page."
>
> Which is only provided in source form.

I "swear", I've got my binaries from there. I'll try remember this evening. Otherwise I'll build my own binaries.

---
Forum admin

> Another build is in
> qemu-0.10.0-win32-3.7z,
> where I've rebuilt SDL and zlib using GCC 4.3.0 alpha and used
> "-mms-bitfields -march=i686" flags for all QEMU binaries.

Thank you for your good job.
I need play DOS6.22 under VM on Windows with IPX. I have vmdk-image with installed DOS, but rebuild #3 not work with vmdk and qemu-img can't convert it to qcow. On elder version it's easy.
And I run software for work with cyrillic encoding and found trouble with language selecting on keys like Ctrl, Alt and some others. It's bug in sdl.dll.
Now I use rebuild #2 with oficial sdl library on Windows XP.
Maybe somebody know, how to mount floppy on windows? How connect COM1 without port-configuration dialog? How mount just one partition from HDD and boot from it? How start VNC-server?

> Maybe somebody know, how to mount floppy on windows?

Virtual Floppy Drive

> > Maybe somebody know, how to mount floppy on windows?
>
> Virtual Floppy
> Drive

For manipulating floppy or hard disk images: http://www.winimage.com/ (shareware)

---
Forum admin

> I need play DOS6.22 under VM on Windows with IPX. I have vmdk-image with
> installed DOS, but rebuild #3 not work with vmdk and qemu-img can't
> convert it to qcow.

How to Report Bugs Effectively by Simon Tatham

> And I run software for work with cyrillic encoding and found trouble with
> language selecting on keys like Ctrl, Alt and some others. It's bug in
> sdl.dll.

I also have some keyboard trouble with AltGr on a German keyboard.

> How connect COM1 without port-configuration dialog?

I don't understand.

> How mount just one partition from HDD and boot from it?

I don't understand.

> How start VNC-server?

Does, e. g., "-vnc :1" not work?

---
Forum admin

> > How connect COM1 without port-configuration dialog?
>
> I don't understand.

On WinXP SP3 when I mount first serial port I have dialogbox with configuration of port where I can select speed, stopbit and other parameters.

> > How mount just one partition from HDD and boot from it?
>
> I don't understand.

I have "//./PhysicalDisk0" with three partitions. I want mount just third partition and boot OS from it.

> > How start VNC-server?
>
> Does, e. g., "-vnc :1" not work?

Thank you! I never use option like this before.

So... Sorry for my English ;)

> On WinXP SP3 when I mount first serial port I have dialogbox with
> configuration of port where I can select speed, stopbit and other
> parameters.

Why not just confirm this dialog box? Sorry, I've never used serial ports in QEMU.
Lots of Windows related information is still at QEMU on Windows, although it's a little outdated now.

> > > How mount just one partition from HDD and boot from it?
> >
> > I don't understand.
>
> I have "//./PhysicalDisk0" with three partitions. I want mount just third
> partition and boot OS from it.

You could try something like, e. g., "\device\harddisk0\partition3", but I've never used this.

> > > How start VNC-server?
> >
> > Does, e. g., "-vnc :1" not work?
>
> Thank you! I never use option like this before.

"-vnc :1" will give you a VNC server listening on port 5901 (5900+1).
Default VNC port is 5900. So "-vnc :0" (5900+0) is probably a better idea.

This will also require the following files to be present in the QEMU folder:
o keymaps\common
o keymaps\en-us (or whatever keyboard layout you chose via the "-k" option)
o keymaps\modifiers

By the way: For more QEMU related questions please open a new thread in category "Emulation".

---
Forum admin

Could please explain your sentence: "I have vmdk-image with installed DOS, but rebuild #3 not work with vmdk and qemu-img can't convert it to qcow. On elder version it's easy."

---
Forum admin

> > Quoting from the QEMU SVN thread here: "If you wish to use the kqemu
> > accelerator, you need kqemu-1.4.0pre1.tar.gz from the QEMU home page."
>
> Which is only provided in source form.

I've downloaded official kqemu-1.4.0pre1.tar.gz now and it contains kqemu.inf and kqemu.sys. Were we blind yesterday?

---
Forum admin

> Could please explain your sentence: "I have vmdk-image with installed
> DOS, but rebuild #3 not work with vmdk and qemu-img can't convert it to
> qcow. On elder version it's easy."

VMware uses VMDK-files as a disk images. Qemu can work with this files and qemu-img can convert format of disk image. But rebuild #3 can't work with ".vmdk" files.

> VMware uses VMDK-files as a disk images. Qemu can work with this files and
> qemu-img can convert format of disk image. But rebuild #3 can't work with
> ".vmdk" files.

Qemu-img from qemu-0.10.0-win32-3.7z package can't convert or can't create *.vmdk disk image files, or qemu from the package can't mount *.vmdk?!

---
Glory to God for all things

> Qemu-img from qemu-0.10.0-win32-3.7z package can't convert or can't create
> *.vmdk disk image files, or qemu from the package can't mount *.vmdk?!

What command line did you use? Any error messages? I'd like to investigate this, of course.

---
Forum admin

> > Could please explain your sentence: "I have vmdk-image with installed
> > DOS, but rebuild #3 not work with vmdk and qemu-img can't convert it to
> > qcow. On elder version it's easy."
>
> VMware uses VMDK-files as a disk images.

I know. I also use VMware Player 1.x besides QEMU, VPC 2004, and Bochs.

> Qemu can work with this files and
> qemu-img can convert format of disk image. But rebuild #3 can't work with
> ".vmdk" files.

Any error messages?

---
Forum admin

> What command line did you use? Any error messages? I'd like to investigate
> this, of course.

Unfortunately I had no time yet to test your QEMU builds, I just tried to clarify Ruslan's remark.

---
Glory to God for all things

> Unfortunately I had no time yet to test your QEMU builds, I just tried to
> clarify Ruslan's remark.

Ah, OK.

---
Forum admin

> > VMware uses VMDK-files as a disk images. Qemu can work with this files
> and
> > qemu-img can convert format of disk image. But rebuild #3 can't work
> with
> > ".vmdk" files.
>
> Qemu-img from qemu-0.10.0-win32-3.7z package can't convert or can't create
> *.vmdk disk image files, or qemu from the package can't mount *.vmdk?!

On rebuild #3

I have batch file with this commands:
@echo off
echo Start qemu on windows.
qemu.exe -L . -m 16 -hda "MS-DOS.vmdk" -localtime
pause

after this I have black screen with:
Start qemu on windows.
qemu: could not open disk image MS-DOS.vmdk
Press any key to continue . . .

Also I can't convert existing image
>qemu-img.exe convert -f vmdk -O qcow MS-DOS.vmdk MS-DOS.qcow
qemu-img: Could not open 'MS-DOS.vmdk'

I use VMware Workstation 5.5.3 and vmdk file created by VMware. On rebuild #2 all works.

So, how install kqemu? I click right mice button, select "Install" and I see:
"Could not open '\\.\kqemu' - QEMU acceleration layer not activated: 2"

I take inskqemu.exe from directory "kqemu" of "Qemu Manager", place with kqemu.inf and kqemu.sys, run inskqemu.exe and nothing have also.

> On rebuild #3
>
> I have batch file with this commands:
> @echo off
> echo Start qemu on windows.
> qemu.exe -L . -m 16 -hda "MS-DOS.vmdk" -localtime
> pause
>
> after this I have black screen with:
> Start qemu on windows.
> qemu: could not open disk image MS-DOS.vmdk
> Press any key to continue . . .

Thanks for the exact error message! I'm able to reproduce this here.

> So, how install kqemu? I click right mice button, select "Install" and I
> see:
> "Could not open '\\.\kqemu' - QEMU acceleration layer not activated: 2"

This message is not from the installation process, but from QEMU itself.
So did you read the manual completely?
It says:
"In order to start kqemu, you must do:
net start kqemu"

---
Forum admin

> So, how install kqemu? I click right mice button, select "Install" and I
> see:
> "Could not open '\\.\kqemu' - QEMU acceleration layer not activated: 2"

I am stupid =)
After install I must wrote
net start kqemu

I am lazy also ;)
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kqemu]
"Start"=dword:00000002

Now it's start with Windows.

So somebody know how mount serial ports without configuration dialog? I play DOS in VM just for work with special devices on serial ports :(

> > after this I have black screen with:
> > Start qemu on windows.
> > qemu: could not open disk image MS-DOS.vmdk
> > Press any key to continue . . .
>
> Thanks for the exact error message! I'm able to reproduce this here.

The problem is with "-mms-bitfields". If I omit this from the configure command, QEMU opens VMDK files fine.

---
Forum admin

> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kqemu]
> "Start"=dword:00000002
>
> Now it's start with Windows.

sc config kqemu start= auto or sc config kqemu start= system should do the same on Windows XP or later.

---
Forum admin

Qemu v0.10 has regressions:

Running KEEN 4, it displays this screen:


Qemu 0.91 doesn't have this problem, the screen is displayed fully.

---
MS-DOS forever!

> Qemu v0.10 has regressions:
>
> Running KEEN 4, it displays this screen:
> Qemu 0.91 doesn't have this problem, the screen is displayed fully.

Can you send me your image and how you run it? quazi@mail.ru

> The QEMU team has released version 0.10.0 on 04 March 2009

No 1.0 after 0.9.xx ?

> TCG support - No longer requires GCC 3.x

Interesting But what is TCG ? Maybe TCC ? But remember that latest TCC version got released on April the 1st

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> Interesting But what is TCG ? Maybe TCC ? But remember that latest TCC
> version got released on April the 1st

Apparently, Rob Landley (one-time hacker / forker of TCC) got mad that CVS was used to release the latest version of TCC, so he abandoned (yet again) his fork since he refuses to cater to "outdated CVS (as bad as 8.3 on DOS)". His version claims to support "-run" on x86-64 (unlike official). So TCC is maybe a bit stagnant right now, don't get your hopes up.

> > The QEMU team has released version 0.10.0 on 04 March 2009
>
> No 1.0 after 0.9.xx ?

Why are you confused? 10 comes after 9.

> Interesting But what is TCG ? Maybe TCC ? But remember that latest TCC
> version got released on April the 1st

Using a search engine is not that hard: Tiny Code Generator

---
Forum admin

> Qemu 0.91 doesn't have this problem, the screen is displayed fully.

After lots of build sessions I can say, that the problem exists since revision 6349. I'll post that result to the QEMU mailing list.

---
Forum admin

> The problem is with "-mms-bitfields". If I omit this from the configure
> command, QEMU opens VMDK files fine.

Do You will rebuild a new release considering this parameter?
I test your http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z and parameter "-fda "A:"" work on these.
Also nobody know how skip serial port configuration dialog :(

> > The problem is with "-mms-bitfields". If I omit this from the configure
> > command, QEMU opens VMDK files fine.
>
> Do You will rebuild a new release considering this parameter?

As "-mms-bitfields" breaks VMDK support, why should I use it again?

> I test your http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z
> and parameter "-fda "A:"" work on these.

OK, but what's the relation / context? Does this fail in other builds?

> Also nobody know how skip serial port configuration dialog :(

Please upload a screenshot of the dialog here!

---
Forum admin

> > Qemu 0.91 doesn't have this problem, the screen is displayed fully.
>
> After lots of build sessions I can say, that the problem exists since
> revision
> 6349. I'll post that result to the QEMU mailing list.

Malc provided a patch: [Qemu-devel] r6349 broke Commander Keen 4 ;-(

So I'll provide a new build this evening.

---
Forum admin

> As "-mms-bitfields" breaks VMDK support, why should I use it again?

In qemu-0.10.0-win32-3.7z you used
>> where I've rebuilt SDL and zlib using GCC 4.3.0 alpha and
>> used "-mms-bitfields -march=i686" flags for all QEMU binaries.
Can you rebuild it just without -mms-bitfields ?

> > I test your
> http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z
> > and parameter "-fda "A:"" work on these.
>
> OK, but what's the relation / context? Does this fail in other builds?

Yes. I can't mount floppy ("-fda "A:") in all qemu-0.10.0-win32 rebuilds.

> > Also nobody know how skip serial port configuration dialog :(
>
> Please upload a screenshot of the dialog here!

> > As "-mms-bitfields" breaks VMDK support, why should I use it again?
>
> In qemu-0.10.0-win32-3.7z you used
> >> where I've rebuilt SDL and zlib using GCC 4.3.0 alpha and
> >> used "-mms-bitfields -march=i686" flags for all QEMU binaries.
> Can you rebuild it just without -mms-bitfields ?

You mean just with "-march=i686"? I don't like to play with these option anymore. So you're stuck with "qemu-0.10.0-win32-2.7z" until my new build appears.

> > > I test your
> > http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z
> > > and parameter "-fda "A:"" work on these.
> >
> > OK, but what's the relation / context? Does this fail in other builds?
>
> Yes. I can't mount floppy ("-fda "A:") in all qemu-0.10.0-win32 rebuilds.

Unfortunately I don't have access to a PC with a real FDD. So in what way does it fail? Please try to be as exact as you can! What do you expect it to do? What happens instead? Error messages?

> > > Also nobody know how skip serial port configuration dialog :(

Currently I have no idea.

---
Forum admin

I've uploaded "qemu-0.10.0-win32-4.7z", which has been build using GCC 4.3.0 alpha w/o any additional CFLAGS.

You also need fmod.dll and SDL.dll, which are available as separate downloads from http://www.bttr-software.de/qemu/.

Modifications applied:
- reverse SDL and VNC window caption
- add icon and VERSIONINFO resources to EXE file
- add SDL window icon
- use wspiapi.h for Windows 2000 compatibility (IPv6)
- fix VGA issue introduced by r6349

---
Forum admin

> > > I test your
> > http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z
> > > and parameter "-fda "A:"" work on these.
> >
> > OK, but what's the relation / context? Does this fail in other builds?
>
> Yes. I can't mount floppy ("-fda "A:") in all qemu-0.10.0-win32 rebuilds.

Does this one work better for you: http://qemu-forum.ipi.fi/viewtopic.php?f=5&t=4899

---
Forum admin

> I've uploaded "qemu-0.10.0-win32-4.7z", which has been build using GCC
> 4.3.0 alpha w/o any additional CFLAGS.
>
> You also need fmod.dll and SDL.dll, which are available as separate
> downloads from http://www.bttr-software.de/qemu/.
>
> Modifications applied:
> - reverse SDL and VNC window caption
> - add icon and VERSIONINFO resources to EXE file
> - add SDL window icon
> - use wspiapi.h for Windows 2000 compatibility (IPv6)
> - fix VGA issue introduced by r6349

Thanks for the fixed release!

The 0.10.0 release claims to have support for the GUS. Is this support active with your binary? Because the GUS isn't recognized (tried with game Blood). With DosBox, I had no problems to setup Blood with GUS (both sfx and midi).

A minor issue: if one switches away from fullscreen Qemu to another application and then back to Qemu, the screen isn't restored properly. It might be a driver issue, so it just may happen with certain (my!) gfx cards? However, in 0.9.1 it worked ok.

---
MS-DOS forever!

> The 0.10.0 release claims to have support for the GUS. Is this support
> active with your binary? Because the GUS isn't recognized (tried with game
> Blood). With DosBox, I had no problems to setup Blood with GUS (both sfx
> and midi).

Option "-soundhw ?" also lists "gus", so basically it should work, although I never tried. Did you install appropriate GUS drivers to your VM? I own a real "GUS Classic", but never understood how to setup correctly.

> A minor issue: if one switches away from fullscreen Qemu to another
> application and then back to Qemu, the screen isn't restored properly. It
> might be a driver issue, so it just may happen with certain (my!) gfx
> cards? However, in 0.9.1 it worked ok.

I never use the fullscreen option, but I'll try it this evening.

Btw: Does accessing a physical FDD work for you? (It does not for Ruslan, if you missed that.)

---
Forum admin

> Btw: Does accessing a physical FDD work for you? (It does not for Ruslan,
> if you missed that.)

No. Tried both "-fda //./a:" and "-fda \\.\a:". I always get "Allgemeiner Fehler beim Lesen von Laufwerk A: Abbrechen, Wiederholen, Fehler?". Even worse, if I press W then, Qemu terminates silently.

OTOH, "-cdrom //./s:" works and allows access to the physical cdrom.

---
MS-DOS forever!

> I own a real "GUS Classic", but never understood how to setup
> correctly.

What problem do you have with your GUS? Some weeks ago I had finally a good luck and bought Gravis Ultrasound Classic 3.73 - try to look at my jumper setting. I put it in old DOS machine 486DX50 EISA. I had to jumper I/O base to 240h because for some reason GUS setup failed when it was set to 220h (As set as I got it). Then it works fine. I use divers version 4.11.

---
DOS gives me freedom to unlimited HW access.

> > Btw: Does accessing a physical FDD work for you? (It does not for
> Ruslan,
> > if you missed that.)
>
> No. Tried both "-fda //./a:" and "-fda \\.\a:". I always get "Allgemeiner
> Fehler beim Lesen von Laufwerk A: Abbrechen, Wiederholen, Fehler?". Even
> worse, if I press W then, Qemu terminates silently.

This is obviously a regression in r6676. I've reported that now in [Qemu-devel] r6677 broke access to physical FDD on Win32.

---
Forum admin

> > > I test your
> > http://www.bttr-software.de/qemu/qemu-trunk-r6657-win32-2.7z
> > > and parameter "-fda "A:"" work on these.
> >
> > OK, but what's the relation / context? Does this fail in other builds?
>
> Yes. I can't mount floppy ("-fda "A:") in all qemu-0.10.0-win32 rebuilds.

This is obviously a regression in r6676. I've reported that now in [Qemu-devel] r6677 broke access to physical FDD on Win32.

---
Forum admin

> Option "-soundhw ?" also lists "gus", so basically it should work,
> although I never tried. Did you install appropriate GUS drivers to your
> VM?

Regrettably I have no clue what "appropriate GUS drivers" are? For DosBox, I "installed" a C:\ULTRASND\MIDI directory which contains a lot of .PAT files, an ULTRAMID.INI and a DEFAULT.CFG file. In DosBox, that was apparently sufficient for Duke3D to play midi with GUS. I copied the directory to the Qemu C: drive and added

SET ULTRASND=240,3,3,7,7
SET ULTRADIR=C:\ULTRASND

to the environment. However, Duke3D is not happy with this and stops when it tries to initialize sound.

--------------------------------

The Qemu source file gus.c mentions that the GUS support is a "proxy" for the GF1 emulation by Tibor Schuetz. Therefore I guess that one needs additional things ...

---
MS-DOS forever!