Re: Direction that wine is going

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

 



Jim Hall  the issue you are talking about is not exactly true.


> Doesn't work with newer cards and motherboards that don't need or use shared RAM.


Opengl itself that wine uses.  Give no promise that data will be stored in the video card.  Under opengl spec its fine to be stored in cpu ram or video card or anywhere else your opengl drivers see fit.

Due to this fact Opengl does not in fact tell applications how much ram a video card has.  Since it should not need to know.   Wine has a table of video cards models it looks up and takes the size from that.

How did you try the registry key for video card memory size.    Many people stuff up.   Set value stop wine completely with like wineserver -k then run application and the new size should appear.

The value is not for shared ram systems at all.  Its due to the fact opengl tell us nothing about how much ram the card has.   So wine takes a guess.

Now either Jim you have run into a bug with wine detection of your card.  Or a bug in wine feedback path to application reporting memory size what will be fake or guessed never real.   If it matches real everything has worked out good.

Really you have not provided enough information Jim.  If you are running a old version of wine.  There is a possibility that wine is failing to 256 because it simply does not know you card.

Wine --version, program and video card please

oiaohm







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

  Powered by Linux