Plese post exactly how you installed the game, and how you start it
(especially the precise mountings).

Also please post a screenshot (check the readme/mapper for the hotkey).

First install was:
[launch DOSBox with default .conf settings by typing "dosbox" in terminal]
mount c: /home/user01/games
mount d: /media/11HDISK1 -t cdrom
d:
go

(go.bat is both the name of the installer and the post-install executable) At this point a DOS gui opens up, I select a drive and path to install the game files to, it copies over a number of files at blinding speed, exits this gui and launches the Miles Audio sound config gui. I select "SB or 100% compatible" for both MIDI and Digital Sound Effects, autodetect both with no problems, save sound config and the Miles thingy exits. At this point the game launches. I get the usual DOS/4GW and check4MSCDEX output, then a blank screen for ~35 seconds. Then the game menu opens, with the issues noted above.

To run, I've got an .iso of each disc in the 11H directory (running off the cd after the initial install made no difference). The game is launched via "dosbox -conf /home/user01/games/config/eleven.conf". The .isos mount as follows from the autoexec section of the eleven.conf file:

mount c: /home/user01/games/
imgmount f: /home/user01/games/11H/11h_disc_one.iso -t iso
imgmount g: /home/user01/games/11H/11h_disc_two.iso -t iso
imgmount h: /home/user01/games/11H/11h_disc_three.iso -t iso
imgmount i: /home/user01/games/11H/11h_disc_four.iso -t iso
c:
cd 11H
go

As far as other .conf options, for the sake of diagnosis I've reverted to the default settings, aside from the autoexec block and "machine=vesa". No setting that I'd changed in the eleven.conf showed any effect whatsoever, and I'm focusing on the game itself as the root of the problem. After much fiddling with game files and repeated application of the 2.42 patch, I decided to start with a new install just in case (well, about three times now, actually).

The current install I ran directly from the .iso, by removing the "go" line listed above, deleting all game files and that pesky file it drops in the c: directory, then running "dosbox -conf /home/user01/games/config/eleven.conf". After this I switched to "drive" f: (by typing "f:") and ran go.bat. Everything that ensued was identical to what's described above. In both cases the UVCONFIG utility has my video set to Trio64.

I don't have the 242 patch installed now, since it didn't resolve the problem and requires 16bpp.

I get incorrect colors like this, whether in the menu, the videos, or the in-game animations (e.g. moving through the foyer):

Also, if the game is running in B/W mode, the few colors it does display are correct. Namely, that bit on the menu where it says "WELCOME" draws in the correct shades of orange and red. Like I said, I think the fault lies with 11th Hour (especially since the discs I have are from the preorder I made back in '95), but the trick I'm hoping to find is some magic combination of video emulation and 11th Hour video drivers.

Thought I'd add this, in case it's at all useful. This comes from the 11HFAQ.TXT that Trilobyte distributed with their 2.42 patch. If I switch to 8-bit color and restart the game runs in B/W mode:

Problem: Video palette is corrupt. (The colors are all psychedelic or
corrupt.)
Solution: This can occur if your video card is not fully compatible with
the high color modes. This problem has appeared on the Trident and
Hercules video cards. From the �Welcome� screen, click on �Change setup�
and switch to 8-bit color. Note that you will have to exit and restart
the game after making this change before it will take effect.

It is also possible that UniVBE may have selected the incorrect
RAMDAC for your video card. Run the UVCONFIG program and change
the RAMDAC selection for the appropriate one for your video card.
If you don�t know the part number of your RAMDAC, you can determine
this by looking at your video card. The RAMDAC is generally the
second or third biggest chip on the board, and you can check it
against the list of parts the UniVBE supports to find the one the
matches your system. Try forcing UniVBE to use the correct RAMDAC
with UVCONFIG once you have determined what it is meant to be.

Not that it will help you much with the palette woes, but you should stick to having the CD (images) as drive D only.

And do not add the : after the drive letter.

And rotate among them (see the README) when the game asks for a new CD:

imgmount D "~/games/11H/11h_disc_1.iso" "~/games/11H/11h_disc_2.iso" "~/games/11H/11h_disc_3.iso" "~/games/11H/11h_disc_4.iso" -t iso