hmm it looks like vdmsound likes to be compiled with borland C from within msvc++ ?

I just checked against the sources I had looked at some time back and I didn't have that particular problem.

As I've only got VS.NET 2003, I cannot give you a 100% accurate answer but I'd guess that the dependencies of the DSW aren't quite correct for a clean build or you're attempting to build a project before its dependencies are built.

As an aside, ehere are quite a few compilation issues with the latest version of VC++. Nothing that's not fixeable but there didn't seem to be a lot of point 😀

Qbix wrote:

hmm it looks like vdmsound likes to be compiled with borland C from within msvc++ ?

I had noticed the use of $(BCPATH) and was also surprised! Given that I had other compilation errors, I didn't investigate any further on whether this was significant or not!

The Borland problem tried to fix by installing borland compiler 5.5 + adding environment patch variable. It looks that borland was used to compile 16bit part of vdms to make it working with windows 9x. The best solution to this is to ask author of vdms. But he does not answer any mails. The same situation is with the rest of VDMS developers. It looks that noone left in this project.

*If* the Borland stuff really is just for Win9x, you could macro it out to provide yourself with a workable solution. However, I don't know what you are trying to achieve so maybe this will not be a workable solution?

Yes VDMSound is no longer activiely developed. However, all source is in CVS so anyone could pick it up if they wanted. The problem is that most people who want something added to the product are never able to contribute themselves 😀

DOSBox covers most of what people need so VDMSound doesn't tend to get mentioned much - given that it does what it does very well.

The Borland stuff is only for DOSDRV.EXE. Just make dummy dosdrv.obj and dosdrv.exe and touch them to be newer than the source and MSVC will skip that part of the build.

You will need pieces of the NT4/2k DDK (vintage by now) and set up some env vars in MSVC to point to them (see the include and lib of the project.) that's prolly where the idl etc. errors come from.

V.

whoah, vlad is still alive! :shock: