Describe the bug
The Windows installer for the v3.0.5 release allows for the installation process to be stepped through to completion on 32-bit installations of Windows.
This behavior is misleading, since it implies the software should work in a 32-bit environment. I've noticed the installer will not actually deploy an EXE to the expected location, presumably because it's not actually x86-compatible.
To Reproduce
- Start v3.0.5's installer in a 32-bit installation of Windows.
- Progress through the installer as normal to completion.
- Attempt to start Green Tunnel, be it through the post-install command, or from either the Desktop or Start Menu shortcuts.
Expected behavior
if the intent was to drop support for 32-bit environments with this release, the installer should display an error message stating the software's architectural incompatibility, and prevent installation altogether.
If 32-bit support was intended to be preserved, the installer should deploy an EXE that is actually x86-compatible.
How are you running it?
Environment
- OS and version: Windows 10 Pro v2004, 32-bit
- GreenTunnel version: 3.0.5
- Node.js version, if using the CLI or the library: N/A
- Browser or client, if relevant: N/A
Logs
N/A
Screenshots
Additional context
I am the current maintainer of the Chocolatey package for the desktop application and ran into this while evaluating and testing required package changes relating to the new release. This wouldn't impact me directly (as I don't actually have a need for Green Tunnel), but it wouldn't surprise me if some end users actually depend on this detail.
Describe the bug
The Windows installer for the v3.0.5 release allows for the installation process to be stepped through to completion on 32-bit installations of Windows.
This behavior is misleading, since it implies the software should work in a 32-bit environment. I've noticed the installer will not actually deploy an EXE to the expected location, presumably because it's not actually x86-compatible.
To Reproduce
Expected behavior
if the intent was to drop support for 32-bit environments with this release, the installer should display an error message stating the software's architectural incompatibility, and prevent installation altogether.
If 32-bit support was intended to be preserved, the installer should deploy an EXE that is actually x86-compatible.
How are you running it?
gt, installed from npm)import … from 'green-tunnel')Environment
Logs
N/A
Screenshots
Additional context
I am the current maintainer of the Chocolatey package for the desktop application and ran into this while evaluating and testing required package changes relating to the new release. This wouldn't impact me directly (as I don't actually have a need for Green Tunnel), but it wouldn't surprise me if some end users actually depend on this detail.