FC3 wine D2LOD.. any success stories?

[Guest]

Archived from groups: alt.games.diablo2 (More info?)

The command
wine "/d/games/Diablo II/Diablo II.exe" leave the wine preloader running
100% CPU time, but nothing happens other than wine griping about
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x30

which also happens as I load up
wine "/d/Agent/agent.exe" (the mail/news reader I employ sending this
message)


--

USEast HC Ladder: Rockstomper

 

[Guest]

Archived from groups: alt.games.diablo2 (More info?)

"Brian Brunner" <brian.brunner@verizon.net.prophet> wrote in message
news:8bfku0djs230urvpdp45tt702t7oqmn79t@4ax.com...
>
> The command
> wine "/d/games/Diablo II/Diablo II.exe" leave the wine preloader running
> 100% CPU time, but nothing happens other than wine griping about
> libGL warning: 3D driver claims to not support visual 0x23
> libGL warning: 3D driver claims to not support visual 0x24
> libGL warning: 3D driver claims to not support visual 0x27
> libGL warning: 3D driver claims to not support visual 0x28
> libGL warning: 3D driver claims to not support visual 0x2b
> libGL warning: 3D driver claims to not support visual 0x2c
> libGL warning: 3D driver claims to not support visual 0x2f
> libGL warning: 3D driver claims to not support visual 0x30
>


well DUH! I can see right away what your problem is!...

Anex.....Explodeazon, your WINING too much! Stop WINING!

 

[Guest]

Archived from groups: alt.games.diablo2 (More info?)

Brian Brunner wrote:

> The command
> wine "/d/games/Diablo II/Diablo II.exe" leave the wine preloader running
> 100% CPU time, but nothing happens other than wine griping about
> libGL warning: 3D driver claims to not support visual 0x23
> libGL warning: 3D driver claims to not support visual 0x24
> libGL warning: 3D driver claims to not support visual 0x27
> libGL warning: 3D driver claims to not support visual 0x28
> libGL warning: 3D driver claims to not support visual 0x2b
> libGL warning: 3D driver claims to not support visual 0x2c
> libGL warning: 3D driver claims to not support visual 0x2f
> libGL warning: 3D driver claims to not support visual 0x30

> which also happens as I load up
> wine "/d/Agent/agent.exe" (the mail/news reader I employ sending this
> message)

I think your problem is much more general and not limited to wine.
Maybe your xserver config or the xserver itself.

http://www.google.com/search?q=%223D+driver+claims+to+not+support+visual%22

Koile

 

[Guest]

Archived from groups: alt.games.diablo2 (More info?)

On Mon, 17 Jan 2005, Koile <koile.usenet@gmail.com> wrote:

>> Brian Brunner wrote:
>>
>> > The command
>> > wine "/d/games/Diablo II/Diablo II.exe" leave the wine preloader running
>> > 100% CPU time, but nothing happens other than wine griping about
>> > libGL warning: 3D driver claims to not support visual 0x23
>> > libGL warning: 3D driver claims to not support visual 0x24
>> > libGL warning: 3D driver claims to not support visual 0x27
>> > libGL warning: 3D driver claims to not support visual 0x28
>> > libGL warning: 3D driver claims to not support visual 0x2b
>> > libGL warning: 3D driver claims to not support visual 0x2c
>> > libGL warning: 3D driver claims to not support visual 0x2f
>> > libGL warning: 3D driver claims to not support visual 0x30
>>
>> > which also happens as I load up
>> > wine "/d/Agent/agent.exe" (the mail/news reader I employ sending this
>> > message)
>>
>> I think your problem is much more general and not limited to wine.
>> Maybe your xserver config or the xserver itself.
>>
>> http://www.google.com/search?q=%223D+driver+claims+to+not+support+visual%22
>>
>> Koile

Unfortunately these point to changes in the code of the guy whose
development was clobbered by these error messages.... I'm a dumb user at
this point. Hacking Wine is not on my plate. Is there a kernel config
tweak? options to (not) select in building the kernel? that stuff I can
do no problem; re-writing wine (or Agent) is NOT on my horizon.


--

USEast HC Ladder: Rockstomper