[Bug]:no bugs.I just can't find a 32-bit netclient for windows

perfectstorm01 commented 2 years ago

Contact Details

No response

What happened?

I can't find a 32-bit netclient for windows, would you consider making one, I found that it can't be used for 32-bit windows during deployment, thank you very much for considering my problem, this work is really amazing, thank you again for being able to use it.

Version

v0.12.0

What OS are you using?

Windows

Relevant log output

No response

Contributing guidelines

[ ] Yes, I did.

perfectstorm01 commented 2 years ago

In addition, I would like to know whether to consider the automatic routing function of windows, that egress function always prompts that it cannot be configured on windows

ok-john commented 2 years ago

Hey @perfectstorm01, this will build a 32-bit netclinet.

$ GOARCH=386 GOOS=windows GOHOSTARCH=amd64 CGO_ENABLED=0 go build -o bin/windows/netclient-386

I'll add these to our artifacts in the coming releases.

perfectstorm01 commented 2 years ago

I appreciate your reply and thoughtfulness，but I'm not very good at programming, could you help me compile a 32-bit netclient, and then hang it in the attachment, or send it to my email：perfectstrom01@163.com. Grateful!

Hey @perfectstorm01, this will build a 32-bit netclinet.
$ GOARCH=386 GOOS=windows GOHOSTARCH=amd64 CGO_ENABLED=0 go build -o bin/windows/netclient-386
I'll add these to our artifacts in the coming releases.

I appreciate your reply and thoughtfulness，but I'm not very good at programming, could you help me compile a 32-bit netclient, and then hang it in the attachment, or send it to my email：perfectstorm01@163.com. Grateful!

si458 commented 2 years ago

the latest 0.12.2 doesnt work on 32bit Windows 10 either

afeiszli commented 2 years ago

32bit windows is not supported. If users need 32-bit support, they will need to compile themselves as listed above.

si458 commented 2 years ago

@afeiszli sorry to re-visit this issue but im having an issue running it on 32bit i have compiled it no problem, i can run the exe no problem netclient.exe, the issue i have is i cant auto-start it on startup because it keeps trying to auto install itself into the wrong program files folder it seems to be hard coded with Program Files (x86) rather than checking what is your os arch and using the right folder please can a PR be done to fix this? im not saying support 32bit just fix the program files folder to help people with 32bit OS's

failed to copy netclient.exe to C:\Program Files (x86)\Netclient

PizzaProgram commented 1 year ago

Can somebody please tell me:

where can I get the latest version of netclient_x86.msi or exe for Win7 32bit ?

It is not fair that it's:

nowhere written, that netclient.exe is only for 64 bit. (Not at readme.md, nor at docs)

Also _x86.msi is suggesting it can run on both OSes ! (or at least on 32)

It's common to name:

_x64 for 64bit only
_x86 for 32bit only << that why the current naming is so confusing = wrong !
_x86_64 for 32/64bit multi installer

For example see here ...

The setup process does not show any error message, it is finishing as if everything would be alright... 👎 (Only the winsw.wrapper.log log file reveals there is a problem, hidden at C:\Program Files\Netclient\ folder. )

This ticket should not be closed.

PizzaProgram commented 1 year ago

I have no idea, what that one line means:

$ GOARCH=386 GOOS=windows GOHOSTARCH=amd64 CGO_ENABLED=0 go build -o bin/windows/netclient-386

But if it's so easy to compile with this "one line", that everybody should know how, why isn't it automated to generate a release? I know about 100+ restaurants, where still using 200+ Win7 32bit PCs as their POS systems daily without any problems. (And some with XPs, also working perfectly fine every each day!)

I'd like to help them to switch from OpenVPN to netmaker for their remote access.

I would like to donate to this project, if this could be solved ?

ok-john commented 1 year ago

I have no idea, what that one line means:

$ GOARCH=386 GOOS=windows GOHOSTARCH=amd64 CGO_ENABLED=0 go build -o bin/windows/netclient-386

But if it's so easy to compile with this "one line", that everybody should know how, why isn't it automated to generate a release? I know about 100+ restaurants, where still using 200+ Win7 32bit PCs as their POS systems daily without any problems. (And some with XPs, also working perfectly fine every each day!)

I'd like to help them to switch from OpenVPN to netmaker for their remote access.

I would like to donate to this project, if this could be solved ?

Sure, let's break down that command one variable at a time. Each one of those capitalized words is a build variable, telling the go compiler how the binary should be compiled.

GOARCH=386

Build for a 32 bit processor.

GOOS=windows

Build for the windows operating system

GOHOSTARCH

Build for amd64 processors.

CGO_ENABLED

Disable CGO.

ok-john commented 1 year ago

@afeiszli @0xdcarns to fix this issue you could just remove the hard coding to Program Files (x86) and have it be architecture dependent to the aforementioned or Program Files for 32 bit windows systems.

Hope you folks are doing well, cheers.

gravitl / netmaker