A molecular modeling session can be interrupted before it begins by a problem that has nothing to do with the model: an unsupported operating system, an unavailable graphics feature, or a missing Linux library. Checking these basics first can save time, especially when preparing a new workstation, using a virtual machine, or deploying SAMSON across a teaching lab.
This short preflight guide focuses on the checks most likely to matter before installation. It is not a guarantee that every machine will work, but it helps separate the main compatibility questions so you can investigate the right one.
1. Check the operating system
The current support list includes Windows 10 and 11; Ubuntu 22.04 and newer; Fedora 42 and newer; CentOS and similar Linux distributions; and macOS Tahoe (26), Sequoia (15), Sonoma (14), Ventura (13), and Monterey (12), on both Intel and Apple Silicon.
The distinction between “listed” and “may work” is useful: older platforms may run SAMSON, but they are not part of the currently tested support matrix. If you are planning a lab rollout, check the version on each machine rather than assuming that a system described as “Linux” or “macOS” is automatically covered.
2. Verify the graphics path—not just the graphics card
SAMSON requires a 64-bit operating system and a graphics card that supports OpenGL 4.1. The practical question is not only whether a computer has a GPU, but whether the application can access the required OpenGL capability through the installed graphics drivers.
For NVIDIA or AMD GPUs, the documentation recommends using the latest drivers. On a virtual machine, enable hardware GPU acceleration: without it, required OpenGL features may not be available. This is an easy detail to miss when the guest operating system appears to install normally.
If SAMSON fails to start or graphics features appear unavailable, treat graphics support as a separate troubleshooting step from the installer itself. On Linux, the documentation points to a guide for installing OpenGL drivers.
3. On Linux, check for package dependencies
Some Linux installations may need additional libraries before SAMSON runs. On Ubuntu-like systems, the documented packages are:
|
1 |
sudo apt install libxcb-cursor0 libatomic1 |
On CentOS-like systems, the documented command is:
|
1 |
sudo dnf install xcb-util* |
These are potential dependencies, not a claim that every machine needs the same package changes. If you do install packages, use the command that matches your distribution. If OpenGL libraries are missing or incorrectly configured, follow the OpenGL troubleshooting guide rather than treating every launch problem as a missing-package issue.
4. Keep installation permissions in perspective
SAMSON installs in the user home, and admin rights are not necessary. The application checks that it is not running in admin mode. For an individual workstation, this means you can plan around a user-level installation instead of assuming administrator access is required. For shared machines, it is still sensible to test the graphics path and installation flow in the environment that users will actually use.
A quick pre-install checklist
- Confirm that the operating system and version are on the supported list.
- Confirm that the system is 64-bit.
- Check that the graphics card supports OpenGL 4.1 and, where applicable, that NVIDIA or AMD drivers are up to date.
- If using a virtual machine, enable hardware GPU acceleration.
- On Linux, check whether the listed libraries are needed for your distribution.
- For shared workstations or teaching labs, test a representative machine before wider deployment.
Once these checks are done, continue with the installation instructions. For account and installer access, see SAMSON Connect. For the full requirements and platform details, read the original documentation page.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.