Just because you hear sound does not mean that VDMS is working. It is probably using "Vista's POS SB emulation."
OK, but how would you explain this :
as far as yesterday there was no sound at all, right ? I launched it via dgVoodoosetup.
Today I just go
at cmd prompt and it has sound. How's that ?
Please note that, yesterday like today, following the tip in dege's readme_eng.txt I made sure vddloader.dll was moved to \windows\sytem32, so what has changed after all ?
What I think is, it (VDMsound) was working yesterday too, but as it started it was the no fullscreen failure that knocked it out, so to speak, and I had no way of knowing whether it was loaded\working or not, and assumed it wasn't. Today, just dosdrv (before calling dgvesa) lets it remain "hooked" and as dgvesa as I see doesn't crash and makes it to fullscreen, then the game can get started.
Besides, since this thread is about dgVoodoo, I hope nobody gets hurt if I take the liberty of quoting dege himself when he writes :
- Vista is disposed to load any VDD only from Windows\system32, I think this is because of a security-crap or something like that. The point is that keep your Glide2x.dll there if you want to run any DOS stuff. Actually, it's important NOT to have any Glide2x.dll in the folder of DOS app because the DOS driver notices it in this case and wants Vista to load that instance. And Vista's respond is dismissive.
(This behavior should be avoided by some development as well as getting setup to search for Glide2x.dll instances in Windows\system32.)
You have to do the same with VDMSound, just copy its vddloader.dll into System32, and voila, it works like a charm.
I sure am no authority here, but I think dege's words matter.
What is your comment ?