Re: Bug in winealsa.drv? Incredibly specific oddity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: wine-users@xxxxxxxxxx
Subject: Re: Bug in winealsa.drv? Incredibly specific oddity
From: "shotgunefx" <wineforum-user@xxxxxxxxxx>
Date: Wed, 10 Sep 2008 10:08:08 -0500
In-reply-to: <1221055598.m2f.12331@xxxxxxxxxxxxxxxx>
References: <1221055598.m2f.12331@xxxxxxxxxxxxxxxx> <1221058897.m2f.12333@xxxxxxxxxxxxxxxx>
Reply-to: wine-users@xxxxxxxxxx

Thanks, I don't think it is, I had the same problems with 1.0, and 1.3, that's why I updated, hoping newer releases would fix it.

Is there any more info I should collect, and if so, anyway of pairing it down? With WINEDEBUG=all, it hits a gig pretty quick.

Follow-Ups:
- Re: Bug in winealsa.drv? Incredibly specific oddity
  - From: shotgunefx

References:
- Bug in winealsa.drv? Incredibly specific oddity
  - From: shotgunefx
- Re: Bug in winealsa.drv? Incredibly specific oddity
  - From: jeffz

Prev by Date: Re: which is faster: WinApi or C Runtime?
Next by Date: Re: Bug in winealsa.drv? Incredibly specific oddity
Previous by thread: Re: Bug in winealsa.drv? Incredibly specific oddity
Next by thread: Re: Bug in winealsa.drv? Incredibly specific oddity
Index(es):
- Date
- Thread

[Index of Archives] [Gimp for Windows] [Red Hat] [Samba] [Yosemite Camping] [Graphics Cards] [Wine Home]

Powered by Linux