Thanks, but where do I put it so that Vegas will see it?

If it were me, I would not get the DLL from the wild on the web. vcomp.dll is Visual C++'s OpenMP DLL, which should be part of the run-time for Visual C++. If Vegas needs it, it would have installed it, so I would go to add/remove programs and:

1. Check if MS Visual C++ run time is installed. If it is, repair install if possible. If not you may download it here from MS for VS2005 SP1, or for VS2008. I have Visual Studio installed on my system, so I can't tell which one you might need. I suspect it's going to be VS2005 version.

2. Repair your Vegas install. That should re-install anything that might be missing. I haven't tried this myself, so I don't even know if it is an option, or if you just have to uninstall & reinstall.

Thanks to all for your replies. I have now downloaded both VS2005 and VS2008 and installed both of them one after the other with testing in between. Norton WinDoctor still tells me that Vegas is missing the mandatory program vcomp.dll. Any other suggestions?

My main thought is, "Why does Vegas insist on having Visual C++ run time is installed?" I would have thought that Vegas programming would be independent of such or would otherwise include its' own files. It would be nice to know where to put vcomp.dll so that Vegas could see it, as there is one version of it in a C:\Windows\winSxS folder. I might add that this was already there before installing the updated Visual C++ run times. They did not add any new vcomp.dll files anywhere - I have searched and there are no new ones.

Perhaps Norton WinDoctor is wrong?

Regards,
Noggle

Perhaps Norton WinDoctor is wrong?

That would be my suspicion.
I did a search of the Sony folders on my computer (Vegas 7 & 8, DVDA 4 & 5) and found vcomp.dll in Vegas 7 only.

Mike

Did you try suggestion #2 which is to reinstall Vegas?

Vegas needs Visual C++ runtime because it is built using C++ (maybe among other languages).

Applications are allowed/supposed to install VC runtime redistributable, and it is quite standard for many applications. Applications installing their own copies instead of common runtimes is what used to be known as "DLL Hell."

It might also help to think back to what suddenly caused vcomp.dll to "disappear" - did you install/uninstall software, or run some kind of registry/windows cleaner or something?

** . . . did you install/uninstall software, or run some kind of registry/windows cleaner or something?**

Uhh, did you even bother to read the original post, or are you in some kind of "autorespond" mode tonight?

I have Vegas 7.0d.

C:\Program Files\Sony\Vegas 7.0
vcomp.ddl version 8.0.50727.42

It also appears, for no apparent good reason, here:

C:\Program Files\Sony\Vegas 7.0\Microsoft.VC80.OPENMP

Same exact file.


Hmmm ... I just did a duplicate scan, using a CRC duplicate checker, and in my Vegas 7.0 folder and its subfolders, I have 68 groups of duplicates, with some of them containing three and four duplicate files. Here are some of the larger files:

mcmpgvout.004 (over 2Mbytes each, and I have four of them)

and the same thing with:

mcmpgvout.001
mcmpgvout.002
mcmpgvout.003

This isn't a huge deal, but I always wonder if anyone in QA is paying attention when this sort of thing happens. It just seems sloppy, as if someone isn't paying attention.

"C:\Program Files\Sony\Vegas 7.0"

Thanks for this info. At least I now know which folder is the pertinent one. Regarding a complete re-installation of Vegas Pro 8, I am, naturally enough, reluctant to do this until I have exhausted all other possibilities.

I have one vcomp.dll in the WIndows folder (and, strangely, no new ones installed by updates of C++ runtime! Hmm?), so I'll try putting this in the Vegas folder and see what happens.

Thanks again to all repliers so far.

Get rid of Norton is what i would highly recommend.....has so many flaws i cant even get into it right now...just too much.
And if you stay with it you may see more problems in the future.

It's called a runtime file because the application needs it when it is run. Just put it into the same folder as the exe program that needs the runtime file.