qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OS/2 and Latest CVS QEMU
Date: Thu, 17 Jun 2004 21:06:01 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.55.0406172104120.656@home.oyster.ru> (raw)
In-Reply-To: <1087467705.16227.40.camel@pcgem.rdg.cyberkinetica.com>

On Thu, 17 Jun 2004, Antony T Curtis wrote:

> On Wed, 2004-06-16 at 21:33, Fabrice Bellard wrote:
> > Antony T Curtis wrote:
> > > Cool - OS/2 Warp Connect actually installs and runs (blue-spine box,
> > > cdrom version)... however, the OS/2 CL-GD5446 video drivers don't seem
> > > to recognise the chipset and will not install :|
> >
> > Are you sure there is a 5446 driver in OS/2 ? I only saw 5436.
>
> Ok - the OS/2 drivers appear to look at the VGA BIOS to check what chip
> is there... I have tried by using a copy of a real 5446 BIOS (copied
> from a 5446 card I have here) and Cirrus's IDCHIP utility reports that
> the VGA BIOS reports it as a 5430. I have also noticed that the 5446 and
> 5440 cards I have here have identical VGA BIOS
>
> The SB16 emulation appears to work fine for the system sounds on XP-Pro
> but it's choppy when playing mp3 etc. OS/2's SB16 driver crashes
> however.

What did you do when it crashed? For me system sounds on OS/2 (Merlin)
quite ok, and it never crashed, granted i only played some wavs from
media directory.

-- 
mailto:malc@pulsesoft.com

  reply	other threads:[~2004-06-17 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 17:34 [Qemu-devel] OS/2 and Latest CVS QEMU Antony T Curtis
2004-06-16 20:33 ` Fabrice Bellard
2004-06-17  1:11   ` Antony T Curtis
2004-06-17 10:21   ` Antony T Curtis
2004-06-17 17:06     ` malc [this message]
2004-06-17 21:31       ` Antony T Curtis

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=Pine.LNX.4.55.0406172104120.656@home.oyster.ru \
    --to=malc@pulsesoft.com \
    --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 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).