Had *ALL* sorts of prob installing 9C over the top of 9B in XP Pro SP3 32. With no complaints posted so far it's probably just this rig, but it was a big enough PITA that I wanted to post a caution, suggesting that folks backup at least their registry before update install [i.e. ERUNT in XP 32, System Restore in Vista/7].
Install started off normally -> setup insisted on installing MS C++ runtimes for VS 2005 & 2008 (nothing in either was particularly new, dating 7/09) -> setup halted with the message it couldn't find the Vegas msi setup file -> browsing to the file from the message/warning dialog didn't help -> canceled install.
At that point Vegas 9C setup would only repair or uninstall -> attempting to run Vegas brought up serial # registration dialog -> figuring settings lost at least, restored registry backup to try again -> setup again required the 2 runtimes, which wouldn't install with errors of not being able to see setup files, even after browsing to them -> ran Vegas to see if at least 9B would still run, & 9C had been installed. Wasted quite a bit more time verifying that indeed all new files were indeed in place.
FWIW:
IMHO sounds/seems like msi installer problems (that are unfortunately not rare) often caused by (I guess the polite way to put it would be) going by the book rather than adding extra coding to work around msi faults. When/if that happens, & conditions are right -- meaning it depends on what else you've installed that used msi -- *#%@!!! happens. If you get bit by msi bugs, check out [http://www.virtualdub.org/blog/pivot/entry.php?id=267#body] & follow the [much longer] link on Avery's page. It'll probably take me a day or so before I know for sure if anything else was effected by the 9C install.
Install started off normally -> setup insisted on installing MS C++ runtimes for VS 2005 & 2008 (nothing in either was particularly new, dating 7/09) -> setup halted with the message it couldn't find the Vegas msi setup file -> browsing to the file from the message/warning dialog didn't help -> canceled install.
At that point Vegas 9C setup would only repair or uninstall -> attempting to run Vegas brought up serial # registration dialog -> figuring settings lost at least, restored registry backup to try again -> setup again required the 2 runtimes, which wouldn't install with errors of not being able to see setup files, even after browsing to them -> ran Vegas to see if at least 9B would still run, & 9C had been installed. Wasted quite a bit more time verifying that indeed all new files were indeed in place.
FWIW:
IMHO sounds/seems like msi installer problems (that are unfortunately not rare) often caused by (I guess the polite way to put it would be) going by the book rather than adding extra coding to work around msi faults. When/if that happens, & conditions are right -- meaning it depends on what else you've installed that used msi -- *#%@!!! happens. If you get bit by msi bugs, check out [http://www.virtualdub.org/blog/pivot/entry.php?id=267#body] & follow the [much longer] link on Avery's page. It'll probably take me a day or so before I know for sure if anything else was effected by the 9C install.