Now you have to configure wine. Use winecfg to create custom profile for Falloutw.exe, then edit ~/.wine/user.reg (or use program regedit, part of wine). Try to find something like:

[Software\\Wine\\AppDefaults\\falloutw.exe] 1170527888
"Version"="win98"


Now add bellow (you may have to change the numbers at the ned of key to avoid duplicates):

[Software\\Wine\\AppDefaults\\falloutw.exe\\Direct3D] 1170426099
"RenderTargetLockMode"="readtex"
"DirectDrawRenderer"="gdi"

[Software\\Wine\\AppDefaults\\falloutw.exe\\X11 Driver] 1163168934
"DXGrab"="N"
"Managed"="Y"


Notes:

• You may already have "DirectDrawRenderer"="gdi" set to gdi globally. it is OK - just don't use opengl for Fallout (it helps many other games, but not Fallout).
• "RenderTargetLockMode"="readtex" removes the horrible lag by doing something with palletes, works for Starcraft / Warcraft etc too.

Apply patches (1.1, 1.2, and possibly 1.3 and 1.3.1 from TeamX). Now try to run Fallout from console, e.g.:

wine '~/.wine/drive_c/Program Files/Interplay/Fallout/Falloutw.exe'

If you experience a crash during animated sequences, and you get error message saying something about ALSA, then you encountered a long known bug. Just run winecfg (you may have to run it as root, so do 'sudo winecfg' or su root) and switch everything in the tab Audio from ALSA to OSS. Wine has a very handy, albeit almost invisible feature. Try running:

WINEDEBUG=+file wine Falloutw.exe

Yes, you see every file opened by Fallout - fantastic for debugging!

Other notes:

• I won't add this guide to winehq.org, I don't like them, they deleted several of my posts for no reason
• It is possible to run Fallout 1 in dosbox, which gives you the opportunity of scaling, but it is too slow (at least on my 2 GHz processor, you may have better luck on an optimized Gentoo and some dual core beast).