So, I have used Sony Vegas and Sonic Foundry Vegas Video since the earliest of days. Fuzzy as my memory can be in these times, my recall of upgrades includes mostly positive experiences.
This morning, I downloaded the upgrade to VegasPro 10 and installed it only to receive a message upon initial start up - Failed to initialize script host.
Info on this error was easily found by searching the knowledgebase, however, use of the first set of suggested fix steps - repairing the .net files through the Windows Add/Remove Software dialog was not effective.
The thought of having to follow the subsequent steps - those you should follow if the above did not correct the problem - by deleting every instance of Sonic/Sony softare on your system, registry included, gave me a headache. Who wants to uninstall all his/her Sony software, fuss around editing the Windows Registry, etc. to get a clean install of a program I just downloaded and installed a few minutes ago?
Now, it is comforting to know of that solution, in the event it ever becomes a last resort solution, but I post to recommend patience on the part of anyone else who might experience this same problem.
Before ripping apart the rest of my system (and software applications), I decided to simply uninstall VegasPro10 and re-install it.
I'm not certain what happened the first time around. I run XPSP3, and my system shows .net 2.0, 3.0, 3.5, and 4.
I had tried repairing those as suggested in the knowledge base prior to uninstalling/reinstalling (the repair did not fix the problem with my initial VegasPro10 install, btw).
But removal/reinstallation following the .net repairs seems to have cured the problem. Whether the repair of the .net files was necessary, I have no idea.
. . . bottom line is that reinstallation worked, and I did not have to uninstall/reinstall everything else 'sony' on my system or mess around editing the registry.
I could see that drastic step resulting in the need to completely reinstall XP on my system, not something I was eager to do on a Sunday morning.
Hopefully, most will not experience this problem (although more than a few must already have encountered the problem for it to be part of the knowledge base). But if you do, be patient and try uninstalling/reinstalling before going to more extreme measures to force a broken Vegas installation to work.
Now, to test out the new version . . .
DelCallo
This morning, I downloaded the upgrade to VegasPro 10 and installed it only to receive a message upon initial start up - Failed to initialize script host.
Info on this error was easily found by searching the knowledgebase, however, use of the first set of suggested fix steps - repairing the .net files through the Windows Add/Remove Software dialog was not effective.
The thought of having to follow the subsequent steps - those you should follow if the above did not correct the problem - by deleting every instance of Sonic/Sony softare on your system, registry included, gave me a headache. Who wants to uninstall all his/her Sony software, fuss around editing the Windows Registry, etc. to get a clean install of a program I just downloaded and installed a few minutes ago?
Now, it is comforting to know of that solution, in the event it ever becomes a last resort solution, but I post to recommend patience on the part of anyone else who might experience this same problem.
Before ripping apart the rest of my system (and software applications), I decided to simply uninstall VegasPro10 and re-install it.
I'm not certain what happened the first time around. I run XPSP3, and my system shows .net 2.0, 3.0, 3.5, and 4.
I had tried repairing those as suggested in the knowledge base prior to uninstalling/reinstalling (the repair did not fix the problem with my initial VegasPro10 install, btw).
But removal/reinstallation following the .net repairs seems to have cured the problem. Whether the repair of the .net files was necessary, I have no idea.
. . . bottom line is that reinstallation worked, and I did not have to uninstall/reinstall everything else 'sony' on my system or mess around editing the registry.
I could see that drastic step resulting in the need to completely reinstall XP on my system, not something I was eager to do on a Sunday morning.
Hopefully, most will not experience this problem (although more than a few must already have encountered the problem for it to be part of the knowledge base). But if you do, be patient and try uninstalling/reinstalling before going to more extreme measures to force a broken Vegas installation to work.
Now, to test out the new version . . .
DelCallo