github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #184] Client not working on x86 platform #150

New issue

Closed

opened 2026-05-05 05:24:04 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:24:04 -06:00

Owner

Originally created by @josuah08 on GitHub (Nov 30, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/184

Operating Systems

Server: Windows 10 build 1803 (compilation 17134.407)

Client: Windows 8.1 x86 (32-bit) v6.3 (build 9600)

Barrier Version

2.1.0

Steps to reproduce bug

Install Barrier 2.1.0 on Windows 10 x64 as a server
Install Barrier 2.1.0 on Windows 8 x86 as a client
With "Run Barrier now" option immediately an error message appears stating "Process creation error, -216)
When "Run Barrier now option" is deselected when program is started manually operating system issues a message "This application will not work on your computer. To find a version for this computer, please contact a software vendor".

Other info

During installation program fetched a correct version of Microsoft Visual C++ 2017 Redistributable (x86) - 14.10.25017 from the internet.

Messages manually translated from non-english version of OS.

Originally created by @josuah08 on GitHub (Nov 30, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/184 ### Operating Systems ### Server: Windows 10 build 1803 (compilation 17134.407) Client: Windows 8.1 x86 (32-bit) v6.3 (build 9600) ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1. Install Barrier 2.1.0 on Windows 10 x64 as a server 2. Install Barrier 2.1.0 on Windows 8 x86 as a client 3. With "Run Barrier now" option immediately an error message appears stating "Process creation error, -216) 4. When "Run Barrier now option" is deselected when program is started manually operating system issues a message "This application will not work on your computer. To find a version for this computer, please contact a software vendor". ### Other info ### During installation program fetched a correct version of Microsoft Visual C++ 2017 Redistributable (x86) - 14.10.25017 from the internet. Messages manually translated from non-english version of OS.

gitea-mirror closed this issue

2026-05-05 05:24:06 -06:00

gitea-mirror commented

2026-05-05 05:24:09 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Dec 1, 2018):

We don't have a 32-bit x86 build of barrier. Simply because we don't know how much interest there really is for it.

@AdrianKoshka commented on GitHub (Dec 1, 2018): We don't have a 32-bit x86 build of barrier. Simply because we don't know how much interest there really is for it.

gitea-mirror commented

2026-05-05 05:24:11 -06:00

Author

Owner

@josuah08 commented on GitHub (Dec 31, 2018):

Hi,

As you can see there is at least one ;-)

My suggestion then is: Either you should provide a build for x86 or make a clear statement in the requirements that only x86_64 platforms are supported..

On the other hand: Do you know if there some code specific obstacles (explicit declaration of bit registers, etc.) to compile it from source on x86 32-bit platform? Shall I try it, or from your expertise knowledge I'll fail and there is no point in making attempt for such compilation process?

Thanks in advance.

BR,
josuah08

p.s. On this occasion - please accept my wishes of all the best for New Year. And BTW - Adrian - you are doing amazing job with Barrier - Thank you.

@josuah08 commented on GitHub (Dec 31, 2018): Hi, As you can see there is at least one ;-) My suggestion then is: Either you should provide a build for x86 or make a clear statement in the requirements that only x86_64 platforms are supported.. On the other hand: Do you know if there some code specific obstacles (explicit declaration of bit registers, etc.) to compile it from source on x86 32-bit platform? Shall I try it, or from your expertise knowledge I'll fail and there is no point in making attempt for such compilation process? Thanks in advance. BR, josuah08 p.s. On this occasion - please accept my wishes of all the best for New Year. And BTW - Adrian - you are doing amazing job with Barrier - Thank you.

gitea-mirror commented

2026-05-05 05:24:14 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Dec 31, 2018):

My suggestion then is: Either you should provide a build for x86 or make a clear statement in the requirements that only x86_64 platforms are supported..

Probably the latter for now. I'll probably fix up a quick PR or something to make it clear.

p.s. On this occasion - please accept my wishes of all the best for New Year. And BTW - Adrian - you are doing amazing job with Barrier - Thank you.

Thanks, I try to keep the issues tagged and the PRs looked at.

@AdrianKoshka commented on GitHub (Dec 31, 2018): > My suggestion then is: Either you should provide a build for x86 or make a clear statement in the requirements that only x86_64 platforms are supported.. Probably the latter for now. I'll probably fix up a quick PR or something to make it clear. > p.s. On this occasion - please accept my wishes of all the best for New Year. And BTW - Adrian - you are doing amazing job with Barrier - Thank you. Thanks, I try to keep the issues tagged and the PRs looked at.

gitea-mirror commented

2026-05-05 05:24:16 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Dec 31, 2018):

Now the filename on the releases page clearly says amd64 https://github.com/debauchee/barrier/releases/tag/v2.1.0

@AdrianKoshka commented on GitHub (Dec 31, 2018): Now the filename on the releases page clearly says `amd64` https://github.com/debauchee/barrier/releases/tag/v2.1.0

gitea-mirror referenced this issue

2026-05-05 07:56:32 -06:00

[PR #150] [MERGED] Update openssl key size in barrier.conf #1568