Ok, short and sweet, this one. On newer flavors of 64-bit Linux (Cent OS 5.2 x86_64 in my case) you may notice Word 2000 (via Crossover Office) fails to start, instead putting out lots of lines like this one:
wine: Unhandled exception (thread 0009), starting debugger...
wine: Unhandled exception (thread 000b), starting debugger...
wine: Unhandled exception (thread 000d), starting debugger...
wine: Unhandled exception (thread 000f), starting debugger...
There’s a two-stage fix, the first being noted in the CodeWeavers support forums (run these commands as root, or via sudo):
# sysctl -w vm.mmap_min_addr=0
# cp -p /etc/sysctl.conf /etc/sysctl.conf~
# echo "# Support Crossover Office" >> /etc/sysctl.conf
# echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
It should be noted that if /etc/sysctl.conf already has a setting for vm.mmap_min_addr, it should be changed, instead of adding a second definition of it as I did here.
At this point (x86_64 only I believe), you may see Word launching, but crashing without any apparent errors after a few seconds. Here, the fix is to modify how system prelinking is performed, first by undoing all prelinking, and then by modifying the prelinker settings to override Exec-Shield support (see the prelink man page for details):
# /usr/sbin/prelink -ua
# cd /etc/sysconfig
# mv prelink prelink~
# sed 's/-mR/"-mR --no-exec-shield"/' prelink~ > prelink