Running psclient on ATI Catalyst 8.5 and later

[Tuxide]

there is now a newer version of catalyst and it is working fine for me.

How?  I just installed Catalyst 9.3 and it still crashes on me with VBO turned on.  Turned off VBO and it works fine.

[the_phet]

Hello, I have ATI 9600 PRO and the last driver from ati, 9.3, it crashed when I try to launch the game or open the setup (I cannot setup anything)
I also have an AMD XP 2000, 1.25G RAM, windows xp sp3

[Tuxide]

Thought I would say that the card I have (ATI All-in-Wonder X800XT) is now considered a legacy product by ATI, meaning that Catalyst 9.3.x will most likely be the last driver to support it.  So until I build myself a better computer, I'm not going to know if it works with later versions of Catalyst (unless it works with later versions of Crystal Space).

EDIT:  Appended to OP to reflect this.

[Tuxide]

Finally built myself a new machine so that I can try later versions of Catalyst.  For the purpose of this thread, here is my new setup:

• Windoze 7 Professional x64 Edition
• AMD Phenom II X4 965 3.4GHz Quad Core
• 4GB DDR3 RAM
• ATI Radeon HD 4870 X2 with 2GB GDDR5

Using Catalyst 9.9, psclient 0.4.03 still crashes with VBO turned on.

Is there anyone with 0.5 built (or least walktest in CS trunk) that can confirm whether VBO still crashes?  I was looking through CS's source code recently and I thought I saw that a workaround was implemented for this.

EDIT:  Switched from Windoze XP to Windoze 7.

EDIT2:  There is no SP2 for Windoze 7, what was I thinking?

[Tuxide]

As far as I can tell, this problem does not exist in 0.5.  So unless anything resurfaces, this thread is now obsolete.

EDIT:  Modified the OP to say this.

[Lanarel]

I am seeing many crashes in the ATI open gl driver with version 0.5.1 (which automatically sends crashs dumps). Is the problem back? Previously, almost 100% of dmp files sent to me were crashes in the ATI driver, and all of those were solved by pointing to this thread. Since now about 30% of all crashes is in this driver, it would be nice to know if this thread still has the answer

[Tuxide]

I don't know why, but I only get this problem now when I build the client myself.  The distro client works just fine for me with VBO.  I'm using the Windoze 64-bit distro, but I build my client as Win32.

EDIT:  Just built myself a 64-bit Windoze client (against the cs-winlibs-x64-1.9_004 libs), fired up VBO and it works just fine for some blasted reason.  So I get this problem with VBO turned on only with 32-bit Windoze clients but not with 64-bit Windoze clients.