Eric Pouech wrote:
Robert Reif wrote:
Eric Pouech wrote:
We never "load" a driver more than once. Winecfg calls winmm
OpenDriver which will only ever load a single instance of the
driver into memory. Subsequent OpenDriver calls will reference the
existing in memory driver. Wine models th
> 1. Not done. Still marked as experimental.
> 2. Not from a stable release of Xorg.
> 3. Reverse engineered.
>
> Given those limitations I'm not sure what driver quality you were
> expecting ;P If the fglrx driver works better, I doubt there's much
> point trying to hack on wine to make things wor
Hello,
In the past weeks, I've worked on a re-write of the Direct3D7 implementation
with WineD3D. Well, I've managed to get some games running, but I have also
encountered a few problems. Before I continue with this, I'd like to ask for
your opinions.
I have uploaded a patch to http://doesi.gmx
Stefan Dösinger wrote:
I guess it's a driver bug. It works sort of with the fglrx driver, but this
driver is horrible.
The driver is:
1. Not done. Still marked as experimental.
2. Not from a stable release of Xorg.
3. Reverse engineered.
Given those limitations I'm not sure what driver qual
Hello,
Did anyone of here get Battlefield 1942 with the radeon driver going? I just
tried with X.org 7.0-rc3, and the game blocks at the loading screen with ~65%
sys cpu usage and ~35% cpu idle. This happens with the current CVS version,
as well as with Olivers d3d8 patch.
I guess it's a driver
On Sat, 2005-12-10 at 14:13 -0800, Scott Ritchie wrote:
>
> It is, however, the proper place to report regressions when one
> doesn't know the exact module causing the problem.
Yes. And here are some instructions on how to go about finding
the troublesome patch:
http://winehq.org/site/docs/wi
On Sat, 2005-12-10 at 15:00 -0700, Vitaliy Margolen wrote:
> Saturday, December 10, 2005, 2:55:52 PM, Aleksey wrote:
> > Not sure exactly how, I mean, what else should be done to test it?
>
> Find the patch that broke it I guess.
> This is not a wine-users list...
It is, however, the proper place
On Sat, 2005-12-10 at 13:55 -0800, Aleksey wrote:
> Not sure exactly how, I mean, what else should be done to test it?
>
Well, the ideal way to fix bugs like this is to find the exact patch
that caused the breakage. You've already done a whole lot for us by
pointing the exact version that broke
Saturday, December 10, 2005, 2:55:52 PM, Aleksey wrote:
> Not sure exactly how, I mean, what else should be done to test it?
Find the patch that broke it I guess.
This is not a wine-users list...
Not sure exactly how, I mean, what else should be done to test it?
On 12/10/05, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
> Saturday, December 10, 2005, 2:47:43 PM, Aleksey wrote:
> > Yesterday I upgraded to WINE 0.9.3, and then tried running Photoshop
> > 7. Photoshop gave me a hardware error.
Saturday, December 10, 2005, 2:47:43 PM, Aleksey wrote:
> Yesterday I upgraded to WINE 0.9.3, and then tried running Photoshop
> 7. Photoshop gave me a hardware error. I thought, no problem, I'll
> just reinstall it, same result. Then I reconfigured WINE using
> winetools and tried again, same thin
Yesterday I upgraded to WINE 0.9.3, and then tried running Photoshop
7. Photoshop gave me a hardware error. I thought, no problem, I'll
just reinstall it, same result. Then I reconfigured WINE using
winetools and tried again, same thing. Here is what I got in the
Terminal when running Photoshop 7:
Robert Reif wrote:
Eric Pouech wrote:
We never "load" a driver more than once. Winecfg calls winmm
OpenDriver which will only ever load a single instance of the driver
into memory. Subsequent OpenDriver calls will reference the existing
in memory driver. Wine models the single instance devi
Biuro Fornet MK wrote:
Dear Sirs.
I represent Polish company. We start currently a project - kind of
computer helpdesk, where we advice (because of lot of reasons) moving
to Linux to our customners.
While they are in most cases very sceptic about this, your Wine makes
a great help for us. Unfor
Hi,
I haven't seen a new release of winetest on
http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ since the 1st of
december.
Anyone ?
Paul.
[EMAIL PROTECTED] wrote:
> Anyone working on getting wine to work on gcc-4.xx?
Not I. It's not really a showstopper for me since it only affects
Dreamweaver and I can compile with 3.4 to get around it at the moment.
I wouldn't be worried about it unless other apps have problems too.
I'll retes
Am Freitag, 9. Dezember 2005 15:25 schrieb Huw D M Davies:
> My guess is Stefan's XServer is glx version 1.2 (Stefan glxinfo will
> comfirm this).
Correct
Is anyone using the arts, esound or jack sound drivers for non
trivial use? By non trivial, I mean more than one application or
more than a single device. If so, I am interested in getting
information on the software you are using and how it is using
the drivers.
Would redesigning these drivers
On Sat, Dec 10, 2005 at 11:43:38AM +0100, [EMAIL PROTECTED] wrote:
> Anyone working on getting wine to work on gcc-4.xx?
It works fine on gcc 4.0, gcc 4.1 and also current 4.2 development branch.
Ciao, Marcus
Eric Pouech wrote:
We never "load" a driver more than once. Winecfg calls winmm
OpenDriver which will only ever load a single instance of the driver
into memory. Subsequent OpenDriver calls will reference the existing
in memory driver. Wine models the single instance device driver that
supp
Anyone working on getting wine to work on gcc-4.xx?
On Wed, 23 Nov 2005 01:14:17 +0100, Evil <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
Have you tried 4.0.2 ? This seems to be the version adopted by
distros using gcc4.
I am rebuilding Gentoo with 4.1-beta . When I get to wine I'l
> "Cyril" == Cyril Margorin <[EMAIL PROTECTED]> writes:
Cyril> 2005/12/10, Mike McCormack <[EMAIL PROTECTED]>:
>> > Unfortunately, problem is that GetBitmapBits function in wine is >
>> incorrect, and may causes a buffer overflow, but the GetDIBits isn't.
>>
>> Great. Then
We never "load" a driver more than once. Winecfg calls winmm OpenDriver
which will only ever load a single instance of the driver into memory.
Subsequent OpenDriver calls will reference the existing in memory
driver. Wine models the single instance device driver that supports
multiple physica
23 matches
Mail list logo
