Slube, those problems are really weird. When I first added VESASupport, some people with slow machines had crakling sound during cut scenes, but that machine is a beast. In any case never heard of problems during game play. Not sure what to suggest. What sound card?

What sound card?

Well, that is the weak area, it's a Soundblaster live 24-bit, though that should be enough. This is actually on my work computer. I should try it at home, where I have a Soundblaster X-fi.

I tried taking out this line from the .ini:CDCheckFile: data\Level10c.phd
but that didn't make a difference. I tried different resolutions. Perhaps the color quality should be 16 bit instead of 32 bit?

I have a SB Live and never met those issues.

You might want to check that you installed the latest drivers from Creative, not the default ones from WinXP. You could try toying with hardware acceleration as well, though personally I don't recommend it (but it sometimes proves useful on some configurations).

Its not that any component is not up to the job. That spec is way higher than needed, but there are sometimes problems with PCI bus latency with some sound card/mother board combinations. With my last 5 or 6 computers I've used the onboard sound and never had a problem, but I've heard of many that have.

You should stick with 32bit color.

Could also be something running in the background. You sure you haven't got spy ware?

I downloaded the updated driver.

Could also be something running in the background. You sure you haven't got spy ware?

I have Webroot Spysweeper running, which is pretty good at getting rid of anything going on.

It's okay, the sound seems to be working now. Must be one of those temporary unexplanable things. Maybe it was the sound driver.

Arrgh, back again. It seems like the graphics are going too fast, and the sound can't keep up. If I just let it run, the movies run too fast and I think they keep triggering sound before the previous sound is done. Then if I don't press escape, the program crashes at the end of the last movie.

This is interesting. It seems like the problem doesn't happen when I run it in a window, only full-screen.

I probably should have also mentioned that I don't use a physical CD - I just run a disc image of TR in Daemon Tools.

I run from a nero image with no problems.

You don't have one of the those stepping CPUs where the clock rate varies?

No, it's full power all the time. The full-screen issue makes me think it's some kind of graphic thing that's happening in full-screen mode (sometimes), but not in a window. It doesn't seem like the sound is not working, just that the graphics are going too fast, or in some way interfering with it.

The reason I asked was because Glidos under XP/NT has to take control of the emulated PIC chip interupts, and it starts by running its own timing loop to calibrate. Variation in speed during the calibration would put the timing out for the whole session.

On the other hand, I've never seen such a problem, and I wouldn't expect windowed v fullscreen to affect it.

Mabye it's using OpenGlide in a Windows and NTVDM VESA fullscreen? Might account for the difference.