I'm just guessing here, but perhaps your default.sfvidcap file has been corrupted. This file is probably in your My Documents directory. If you delete this file (assuming you don't have anything important stored in it), VidCap will recreate it the next time it runs. If you want to experiment safely then just rename it to something else.

I don't have an answer but I have exactly the same problem. I suspect if you look at the 'details' from the error dialog, you will find that it complains about three files, and the file names are the three sections of letters that make up your product serial number.

If I open the capture utility directly (not through Vegas), it doesn't happen.

This has heppened since I first installed Vegas in May. I posted in this forum back then about it and didn't get a solution.

I then posted a question to support at the time. The current version was 4.0c and I didn't want to go past 4.0b so I didn't pursue it. Now I'm running 4.0d and it is still happening, so I guess it might be time to try support again.

I remember those three files. I will check the other possibility out too. As I said in my initial post the the message is just an annoyance capture and writing back to tape work flawlwssly aside from the error messasge. Thses are the three files that the error message says it doesn't support:

File G2C14M could not be opened.
File BP30NF could not be opened.
File 2FRNRX could not be opened.

Cut and paste directly from the error report and just as you say these are a part of the set of the serial number of my product. This is definately something the Sony-Vegas support should address for sure.

I posted this through support again. This time they told me it is a known problem. If I understand, it is related to starting capture before you are fully registered.

Fix was a pain -- uninstall and reinstall Vegas, but at least it works without the startup error now.

I went through a similar error code episode. SF Support determined that, while I had upgraded to V4 and "uninstalled" V3, my V3 folders were still present - which may have caused registration conflicts. I deleted the V3 stuff via explorer, uninstalled and reinstalled V4, and haven't had a problem since (with that anyways). DGrob

Hmmm, I think I still may may have Vegas Video 3LE present I'll check

Hey Don-

I too have this problem. Try advanced capture, can you use any features? Not me.

So far this issue is on my XP Home machines. Win2K machines like to crap out on capture completely. I could not swear that all machines previously had VV3 on them.

Tomorrow, I will bring VV3 and V4 to the office where I have 3 win2k and 3 xphome to try and as decks I have the choice of TRV 25 or 38, pd 150, dsr-11 or jvc (somethingoranother) 3000.

SonyEPM PLS HELP!

Never have used advanced capture but I did still have VV3 LE here but not any more. The unsupported file thing still comes up immediately upon opening the capture but before I can open the advanced capture screen so the fact that it doesn't happen when you open the "advancecd capture" may not necessarily prove it won't happen there. I hope there will be a way to get rid of this annoying message without uninstalling and reinstalling a fully functional proram. For the while I think I can live with it.

Any help along these line would help SonyEPM or anyone else there.

I never had any problems with capture after I ignored this error, or if I started capture directly outside of Vegas, so swarrine must have more going on than just this problem.

I still don't understand how this happened because I installed the boxed version initially. Maybe I did something before I registered online. Seems a bit wierd to me, but as problems go this was minor.

Did you put hyphens between the number groupings when entering the serial number?

The serial number in my book does not show any hyphens, but as soon as I added them on a reinstall everything seems to work normally.

More testing needed, but give it a try.

I just loaded VV3 back up. I am now using it for capture (and it works perfectly) then opening files with V4.

Something is not right, not sure what it is though.