[GH-ISSUE #335] Windows XP support? #270

Closed
opened 2026-05-05 05:52:53 -06:00 by gitea-mirror · 12 comments
Owner

Originally created by @MrGlasspoole on GitHub (Jun 14, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/335

Server: Windows 10 Pro (x64)
Client: Windows XP Media Center 2005 SP3 (x86)
Barrier Version: 2.2.0

Should Barrier work on Windows XP?
I can't find any information about the OS Versions that are supported.

In Windows XP (x86) when starting Barrier i get the message:
C:\Program Files\Barrier\barrier.exe is not a valid Win32 application

Originally created by @MrGlasspoole on GitHub (Jun 14, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/335 Server: Windows 10 Pro (x64) Client: Windows XP Media Center 2005 SP3 (x86) Barrier Version: 2.2.0 Should Barrier work on Windows XP? I can't find any information about the OS Versions that are supported. In Windows XP (x86) when starting Barrier i get the message: C:\Program Files\Barrier\barrier.exe is not a valid Win32 application
gitea-mirror 2026-05-05 05:52:53 -06:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

@AdrianKoshka commented on GitHub (Jun 14, 2019):

Windows XP is EoL as far as I'm concerned. We don't even support 32-bit windows platforms.

<!-- gh-comment-id:502100234 --> @AdrianKoshka commented on GitHub (Jun 14, 2019): Windows XP is EoL as far as I'm concerned. We don't even support 32-bit windows platforms.
Author
Owner

@AdrianKoshka commented on GitHub (Jun 14, 2019):

I did update the README to reflect this though, thanks.

<!-- gh-comment-id:502124283 --> @AdrianKoshka commented on GitHub (Jun 14, 2019): I did update the README to reflect this though, thanks.
Author
Owner

@noisyshape commented on GitHub (Jun 14, 2019):

To the best of my knowledge, there's no technical reason you couldn't compile a 32-bit version and install it on XP. There's little interest in either of these things though and certainly nobody around to support them. You might try an older version of Synergy or maybe Mouse Without Borders.

<!-- gh-comment-id:502231297 --> @noisyshape commented on GitHub (Jun 14, 2019): To the best of my knowledge, there's no technical reason you couldn't compile a 32-bit version and install it on XP. There's little interest in either of these things though and certainly nobody around to support them. You might try an older version of Synergy or maybe Mouse Without Borders.
Author
Owner

@parkerlreed commented on GitHub (Nov 1, 2019):

Would an older synergy for the XP and barrier on Linux work together? Or do the versions have to match?

<!-- gh-comment-id:548620069 --> @parkerlreed commented on GitHub (Nov 1, 2019): Would an older synergy for the XP and barrier on Linux work together? Or do the versions have to match?
Author
Owner

@parkerlreed commented on GitHub (Nov 1, 2019):

To answer my own question: no. Protocol error.

<!-- gh-comment-id:548621134 --> @parkerlreed commented on GitHub (Nov 1, 2019): To answer my own question: no. Protocol error.
Author
Owner

@mirh commented on GitHub (Jul 25, 2020):

Protocol error is more about synergy-barrier incompatibilities than "releases version".
#227
If you patched the handshake maybe it could work, see also these builds https://github.com/debauchee/barrier/issues/92#issuecomment-403238829

<!-- gh-comment-id:663847616 --> @mirh commented on GitHub (Jul 25, 2020): Protocol error is more about synergy-barrier incompatibilities than "releases version". #227 If you patched the handshake maybe it could work, see also these builds https://github.com/debauchee/barrier/issues/92#issuecomment-403238829
Author
Owner

@Kharzette commented on GitHub (Apr 23, 2024):

I just tried building a version for winXP (I'm doing some old original xbox stuff and need XP), and had success with just the command line bits (no QT stuff). There weren't that many code changes; most of the work was getting the build environment set up.

Anyone interested will need visual studio community 2017 (which is tricky to get to). When setup is run, you'll want the v140 build tools. CMake-gui had some trouble with that but I eventually got it going by using the command line cmake from the 2015 x86 command prompt. There's a cmake option to build without GUI and that helps tremendously as you don't need QT.

Once the project files are generated, edit each one and replace v140 with v140_xp.

I defined a preprocessor variable WINVER at 0x0501 (winxp) to make it easy to ifdef around the unsupported stuff. There might be a way to have cmake do that but I'm not good with cmake.

After that there's just a few shell/winsock changes I'll stick in a fork. I don't really think it is pull request worthy. There's not a really good way to set the OS you are building for.

<!-- gh-comment-id:2073367140 --> @Kharzette commented on GitHub (Apr 23, 2024): I just tried building a version for winXP (I'm doing some old original xbox stuff and need XP), and had success with just the command line bits (no QT stuff). There weren't that many code changes; most of the work was getting the build environment set up. Anyone interested will need visual studio community 2017 (which is tricky to get to). When setup is run, you'll want the v140 build tools. CMake-gui had some trouble with that but I eventually got it going by using the command line cmake from the 2015 x86 command prompt. There's a cmake option to build without GUI and that helps tremendously as you don't need QT. Once the project files are generated, edit each one and replace v140 with v140_xp. I defined a preprocessor variable WINVER at 0x0501 (winxp) to make it easy to ifdef around the unsupported stuff. There might be a way to have cmake do that but I'm not good with cmake. After that there's just a few shell/winsock changes I'll stick in a fork. I don't really think it is pull request worthy. There's not a really good way to set the OS you are building for.
Author
Owner

@mirh commented on GitHub (Apr 23, 2024):

Why not v141 and v141_xp?

<!-- gh-comment-id:2073604840 --> @mirh commented on GitHub (Apr 23, 2024): Why not *v141* and *v141_xp*?
Author
Owner

@Kharzette commented on GitHub (Apr 24, 2024):

Hmm I didn't see a 141 in visual studio setup.

<!-- gh-comment-id:2074067841 --> @Kharzette commented on GitHub (Apr 24, 2024): Hmm I didn't see a 141 in visual studio setup.
Author
Owner

@fennectech commented on GitHub (May 1, 2024):

would you be willing to provide a binary version for XP? im familiar with the command line but compiling windows software is not something i can do

<!-- gh-comment-id:2088810197 --> @fennectech commented on GitHub (May 1, 2024): would you be willing to provide a binary version for XP? im familiar with the command line but compiling windows software is not something i can do
Author
Owner

@Kharzette commented on GitHub (May 2, 2024):

Well, just a build off my machine would probably be a bad idea, but maybe the github actions stuff can build it? I'll check into that.

<!-- gh-comment-id:2089486252 --> @Kharzette commented on GitHub (May 2, 2024): Well, just a build off my machine would probably be a bad idea, but maybe the github actions stuff can build it? I'll check into that.
Author
Owner

@Kharzette commented on GitHub (May 3, 2024):

I've got an xp build working over on my fork. There's no installer or QT stuff but I think most would just need barrierc for an old xp machine.

<!-- gh-comment-id:2092345730 --> @Kharzette commented on GitHub (May 3, 2024): I've got an xp build working over on my fork. There's no installer or QT stuff but I think most would just need barrierc for an old xp machine.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#270
No description provided.