Post: #1

Hello everyone! I'm back on sphere finally

I'm starting the migration of my great old shard (55r4) on the new version 56d or X (32bit, lastest stable), and i'm looking for a WinXP compatible server.

My dedicated hardware is a a very low space & energy drain machine and i would like to continue using this one for the purpose:

Asus EEEBox
Intel Atom @ 1.6 GHz
Ram 1.5 Gb

OS is Windows XP Professional, SP3, 32bit, acting as server for Quake, Half-Life, Hexen, Sphere 55r4 and more. It's working flawlessy.
Visual C++ is installed too (the lastest one, 2015/17/19 and the "2010" found on spherecommunity download page)

...but...

both 56d and X won't start on the XP 32 bit
The error is "SphereSvr.exe is not a valid win32 application", on server launch.

I've checked all available documentation and can't find anything about requirements.

Anyone has any suggestion or workaround ?

Post: #2

That's a tough one as I have never heard of that one before...

Post: #3

Did you download the 32bit version of sphere?

Post: #4

(10-16-2020 11:50 PM)darksun84 Wrote:  Did you download the 32bit version of sphere?

Same error for the 32bit version of both 56d and X

Post: #5

The problem could be the Windows SDK assigned to the project, currently 8.1, that must be downgraded to 7.1 for XP compatbility.
I don't know how complex that would be for a dev to change and re-compile. But it would be welcome I'm a noob on C++

Post: #6

(10-16-2020 04:40 AM)BaLzA Wrote:  Asus EEEBox
Intel Atom @ 1.6 GHz
Ram 1.5 Gb

...server for Quake, Half-Life, Hexen, Sphere 55r4 and more...

Great hardware. Try to install some Linux server instead of Win XP.

Post: #7

About your situation, it sounds like quite the nostalgic setup you've got going on! Your Asus EEEBox running Windows XP for all those classic games is a real throwback. As for the migration to 56d or X, it's a bit of a bummer that you're encountering that "not a valid win32 application" error. I totally get your attachment to your trusty hardware setup.

Post: #8

I've heard that some newer versions of software might have compatibility issues with older operating systems like XP. The error you mentioned could be related to the 32-bit limitation of XP, but don't quote me on that. Have you considered reaching out to the devs or the community behind 56d and X? They might have insights into compatibility issues or potential workarounds. And have you ever checked out those cheap Windows 10 key options? I've heard that some people find good deals this way, maybe in the process you could use it too. Who knows what will be effective.