Server: MacOS Catalina 10.15.4
Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language
Version 1903 (OS Compilation 18362.836)
2.3.2 (BarrierSetup-2.3.2.exe)
CreateProcess failed; code 216
Esta versi贸n de %1 no es compatible con la versi贸n de Windows que est谩 ejecutando. Compruebe la informaci贸n de sistema del equipo y despu茅s p贸ngase en contacto con el anunciante de software.
In english this would be the message:
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisher
I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version).
Hm, I think it states in the README.md that we don't actually support
32-bits versions of Windows. I'm sure that must be frustrating,
though..
Sorry :/
On this date - Wed, Jun 03, 2020 at 03:33:02PM -0700, navascogt wrote:
Operating Systems
Server: MacOS Catalina 10.15.4
Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language
Version 1903 (OS Compilation 18362.836)Barrier Version
2.3.1 (BarrierSetup-2.3.2.exe)
Steps to reproduce bug
- After downloading the most recent version of Barrier, I ran the setup.
- After installing, leave checked the "Launch Barrier" option and press "Finish"
- A popup window message is showed with the following information:
Title: Setup
Unable to execute file:
c:\Program Files\Barrier\barrier.exeCreateProcess failed; code 216
Esta versi贸n de %1 no es compatible con la versi贸n de Windows que est谩 ejecutando. Compruebe la informaci贸n de sistema del equipo y despu茅s p贸ngase en contacto con el anunciante de software.In english this would be the message:
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisherOther info
- I tried with a user with administrator rights.
- Also I tried right clicking and use the "run as administrator" option without success.
I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/735
--
Kind regards,
Dom Rodriguez (shymega)
Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read...
And yes, it is frustating...
Yeah. I think you may be able to compile it 32-bits though..
Ideally I'd like for 32-bit and Windows 7 to still be supported, as
they're still widely used for various reasons.
I'm sure it must be frustrating though.
On this date - Wed, Jun 03, 2020 at 05:22:19PM -0700, navascogt wrote:
Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read...
And yes, it is frustating...--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/735#issuecomment-638527689
--
Kind regards,
Dom Rodriguez (shymega)
Maybe in a future I can try to compile in 32bits... Thanks again!
Closing for now.
For the record, I'd like for our build infrastructure to provide 32-bit versions for Windows 7/8/8.1/10 at the very least until its proven decisively that its not needed. This issue here proves that we have some 32-bit PC users..
I mean, it's not like there is even a 64-bit windows version without wow64.
And since barrier doesn't seem the kind of software that would benefit from using GBs and GBs of memory, or whatever advanced x86-64 instruction, I don't see why you couldn't as well just ship 32bit builds for everyone.
It wasn't my decision. My personal view is that 32-bit builds are still useful. With regards to using GBs and GBs of memory, yes, perfectly true, in theory - but Barrier _does_ have several memory leaks.. so uh, maybe it would! :rofl:
Most helpful comment
Closing for now.
For the record, I'd like for our build infrastructure to provide 32-bit versions for Windows 7/8/8.1/10 at the very least until its proven decisively that its not needed. This issue here proves that we have some 32-bit PC users..