Everything. Played to the end.
What does not
What was not tested
Fedora has prelink enabled by default, and sometimes this causes "Cannot allocate memory" error. This is not caused by wine, but by Halo.exe, which sometimes conflicts with Linux shared libraries. If this error occurs, just disable prelink (and make sure to reboot and clear the prelink cache) and try rebooting and running a few times until the error disappears (hopefully shared libraries will then be loaded in some safe locations.)
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Manjaro Linux 18.0.0||Apr 05 2019||4.5||Yes||Yes||Yes||Gold||Bob Niemöller|
|Show||Debian GNU/kFreeBSD Unstable "Sid"||Aug 30 2014||1.7.25||Yes||Yes||Platinum||Johannes|
|Current||Fedora 20 x86_64||May 15 2014||1.7.18||Yes||Yes||Silver||Zachary J|
|Show||Arch Linux x86_64||Jul 04 2013||1.6-rc4||Yes||Yes||Platinum||Serge Hooge|
|Show||Linux Mint 14 "Nadia"||Dec 14 2012||1.5.18||Yes||Yes||Gold||Carlos Rodriguez|
mount -oloop Halo.iso /cdrom
~/.wine/drive_c/Program\ Files/Microsoft\ Games/Halo/haloupdate.exe
cd .wine/drive_c/Program\ Files/Microsoft\ Games/Halo ./halo.exe
Installing 'halotrialsetup.exe' into a clean wineprefix should work fine with wine-1.3.37.
To run the game, the working directory must be the Halo Trial directory, e.g.
cd ~/.wine/drive_c/Program\ Files/Microsoft\ Games/Halo\ Trial/ wine halo.exe
2015-10-06 Admin note: the following issue has been patched in version 1.0.10 of Halo Custom Edition and Halo Combat Evolved.
2014-11-08 Admin note: the following was extracted from a user comment made on 2013-10-30 and may or may not be relevant to current Wine.
THIS DOES NOT APPLY TO CURRENT VERSION OF HALO CE/PC
Wine is, like Windows, affected by a bug where Halo doesn't render
shaders as well on Nvidia hardware. The most visible symptom is that the
active camouflage is only using transparency instead of the proper way
where it is using a pretty neat shader.
The Windows fix is based on making Halo believe it is running on an ATI card, which is not so complicated within Wine. Loosely based on the Windows fix, enter these into the registry:
As DWORD: "HKCU\Software\Wine\Direct3D\VideoPciDeviceID" = "724b"
As DWORD: "HKCU\Software\Wine\Direct3D\VideoPciVendorID" = "1002"
If your Halo is in a more vast prefix, it is recommended to specify it exclusively for the halo.exe as this fix may have the potential to burn your house down.
This picture will display the basic improvement: i.imgur.com/Rq93SgZ.jpg
Use argument -windowed to play correctly
Example: wine halo.exe -windowed