From: Tomasz B±tor <tomba@bartek.tu.kielce.pl>
To: spetreolle@users.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sound and MinGW problems on Windows host
Date: Wed, 7 Jul 2004 21:51:24 +0200 [thread overview]
Message-ID: <20040707195124.GA2077@bartek.tu.kielce.pl> (raw)
In-Reply-To: <20040707190842.83637.qmail@web51105.mail.yahoo.com>
Witam,
Dnia Wed, Jul 07, 2004 at 09:08:42PM +0200 Sylvain Petreolle napisal(a):
> I have the same configuration here (WinXP Home host / Freedos guest).
> It plays modules in ScreamTracker as if they were open in Winamp.
> (sound is mono though ;)
> Make sure you have correct setup for adress/irq/dma/hdma
Could you tell me the difference between dma and hdma? In DOS-times
I wasn't using PC ;). Now in setups I use 220h/irq 5/dma 5
> and try to change the software, some use still unimplemented DSP commands.
I use QEMU for watching demos, so the sound players differ very much.
I'm surprised though that some standard stuff like MIDAS also cause
trouble, but there're some experiments ahead of me ;)
> > 1. Sound is very choppy. And I mean _very_. It's not usable at all.
> > Under Linux there's no problem.
> > 2. Sound only works at 22050 Hz, setting 44100 make it go silent.
>
> Make sure you applied sound patch to enable it in MinGW
> and check the output of configure.
After a "few" tries I finally compiled it with sound and console support in
windows, but there're still strange trouble like those above. Sound chopping
is still there (I read somewhere on Bochs' forum that this problem is
known to them too. Windows? SDL?), but in some cases the higher frequency,
the lesser the problem is. On 44100 it's like 2 seconds smooth, 3/4 second
garbled, 2 seconds smooth, 3/4 second garbled and so on (more or less).
On 22050 there're 0.1s "chops" all the time, it's not smooth at all.
I have one more problem in 07.04 version on windows: full screen doesn't
work. QEMU just quits.
Both sound and fullscreen problems are not present when I run QEMU (from
the same sources and patches) under linux.
Anyway, thanx for your answer. I'll keep my fingers crossed for the developers
to make QEMU better for an usual user ;)
t.
--
Tomasz Bątor e-mail: tomba@bartek.tu.kielce.pl ICQ: 101194886
------ ---- -- - - - - - - - - - - - -- ---- ------
"Here kitty, kitty, kitty..."
-- last words in a RPG game
next prev parent reply other threads:[~2004-07-07 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 12:01 [Qemu-devel] Sound and MinGW problems on Windows host Tomasz B±tor
2004-07-07 19:08 ` Sylvain Petreolle
2004-07-07 19:50 ` Jernej Simonèiè
2004-07-07 20:01 ` Tomasz B±tor
2004-07-07 20:04 ` [Qemu-devel] freeoszoo and mandrake linux Mark Huot
2004-07-07 19:51 ` Tomasz B±tor [this message]
2004-07-08 12:12 ` [Qemu-devel] Sound and MinGW problems on Windows host Sylvain Petreolle
2004-07-08 14:38 ` Tomasz B±tor
2004-07-08 21:05 ` malc
2004-07-08 17:53 ` Tomasz B±tor
2004-07-08 21:02 ` malc
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 20:32 Natalia Portillo
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=20040707195124.GA2077@bartek.tu.kielce.pl \
--to=tomba@bartek.tu.kielce.pl \
--cc=qemu-devel@nongnu.org \
--cc=spetreolle@users.sourceforge.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).