I guess Valve abandoning XP support didn't meant that they were "flipping the switch" for Windows XP machines, i think that just meant that they may update the steam client on the future in a way that might not work on XP.
Btw i'm running it on a Athlon XP 2800+(Barton)
I spy with my eye, winamp.
Anyway how did you get steam working on a CPU without sse2?
No sir I don't like it!
It's likely an Athlon 64.
Client end
Steam relies on CEF so assuming Valve doesn't compile the next version for Vista+ or add a define to exclude the offending code for XP then that's when you'll have issues if you don't take precautions to prevent the automatic update.
Backend
If Valve make changes to their servers that prevent old clients from connecting then that could also cause issues.
It looks like CEF updated to v51 on 4-28-2016 so assuming Valve using Chrome v49 (Last ver to support XP) unless they made custom changes for XP support. Looking at the latest Steam Client it looks like it uses v68 in Big Picture mode using the web browser but unknown if Big Picture and the regular Steam client use the same CEF ver or not.
/EDIT Looking in steam\packages looks like there are different CEF packages based on OS which are unpacked to bin\cef. The XP CEF is using CEF 3.2623.1395 from 3-31-2016 whereas the "win7" (installed on Windows 10) is using CEF 3.3440.1866.0
wrote:It's likely an Athlon 64.
He said it was a Barton.
No sir I don't like it!
wrote:It's likely an Athlon 64. […]
It's likely an Athlon 64.
Client end
Steam relies on CEF so assuming Valve doesn't compile the next version for Vista+ or add a define to exclude the offending code for XP then that's when you'll have issues if you don't take precautions to prevent the automatic update.Backend
If Valve make changes to their servers that prevent old clients from connecting then that could also cause issues.It looks like CEF updated to v51 on 4-28-2016 so assuming Valve using Chrome v49 (Last ver to support XP) unless they made custom changes for XP support. Looking at the latest Steam Client it looks like it uses v68 in Big Picture mode using the web browser but unknown if Big Picture and the regular Steam client use the same CEF ver or not.
/EDIT Looking in steam\packages looks like there are different CEF packages based on OS which are unpacked to bin\cef. The XP CEF is using CEF 3.2623.1395 from 3-31-2016 whereas the "win7" (installed on Windows 10) is using CEF 3.3440.1866.0
It is a barton.
http://www.cpu-world.com/CPUs/K7/AMD-Athlon%2 … A2800DKV4D.html
Here is a picture of CPU-Z
It is an old install(the Steam folder creation date is september 4th of 2017) that just updated over the time without a problem, the game library works, game install and properties work, however the community and chat don't.
I remember SSE2 being broken once and then Valve fixing it and then supposedly it got broken again. Haven't really kept track or tested it indepth....and now I don't care since don't need the Steam client. 😀
