Your config.nt\autoexec.nt\ntvdm.exe files were probably corrupted.

You need to copy them from the original CD to \windows\system32

C:\WINDOWS\repair

copy the files from there into your C:\WINDOWS\SYSTEM32

Should I copy all the files in the Repair folder or only Config.nt and Autoexec.nt? Because if it's only these two ones, it still doesn't work. I have even taken "ntvdm.ex_" from the CD (renamed to "ntvdm.exe") and put it in the System32 folder and it still doesn't work. Should I take "ntvdm.dl_" too? 😢

ntvdm.ex_ needs to be expanded, first.

I did expand all the mentioned files from the original CD to the System32 folder: Still doesn't work.

Even taken the files from Repair folder: Still doesn't work.

What version of VDMS are you using? If all else fails, use DOSBox. This should be your first choice, anymore.

I'm using VDMSound 2.1.0.

As for Dosbox, the problem is that I wanna play the first Tomb Raider using "Tomb Raider Advanced Installer" that improves the graphics with dgvoodoo. I can't use Dosbox in my case.

Help!

Read this thread: 16-bit subsystem error "Your system is not suitable for running 16-bit apps"

Also how does Dgvoodoo improve the graphics? AFAIK, "all" it does is allow the glide version of TR to work. Is there such a big difference between the VESA and Glide versions of TR?

The only major difference AFAIK is that the Glide version's textures can be replaced if your using GliDOS.

I had a similar problem and, yes it may sound stupid, I solved it just
updating my video drivers .

Does you username contain funny characters (non-ASCII?) I refer to C:\Documents and Settings\[username]\...

If so, it might be the explanation.

I wonder, how can non-ASCII characters influence the matter?

I've got the same problem, the same error messages(and the same VDMSound version). And the config/autoexec files were NOT corrupted, nothing that there shouldn't be. Then I followed MS's advice after reading http://support.microsoft.com/?kbid=324767
No result still =(

OS- XP Pro. Game wanted to run - M.A.X. Actually it works under DOSbox BUT! No sound! The setup autodetects SoundBlaster or GUS emulated by DOSbox, but the game itself has no sound!

Lord_VEK wrote:

I wonder, how can non-ASCII characters influence the matter?

Do you or don't you have non-ASCII characters in there?

Russian characters => not of the first 128 ones.

so it won't work - limitation in windows' pif IIRC

one possible workaround is to set the TEMP user environment variable to a directory where you have access but whose path is made out of ASCII characters (e.g. c:\windows\temp if you are admin)

V.

Thanks 😉

(though only the problem of running VDMSound is solved, no the one with having sound =( But that's another topic