V9_32bit install on W7_x64?

jfpearson wrote on 5/11/2009, 11:34 AM
Anyone successfully installed with this config? I get a message that WMF 11 Redist for MTP is required. The installation fails with the Sony Setup message "Requirements not met.". WMF is a component of the Windows Media Player 11. I cannot install that component in W7_x64 as that component is older than the one with W7 (ie, WMP 12). [Compatibility and Admin property settings on the installation file do not help.] I can install V9_64 bit on W7_x64, as the installation does not call for the named component.

Comments

Former user wrote on 5/11/2009, 1:23 PM
Windows 7 is most definitely not on the V9 supported system requirements list and it's not even available yet (in release format) so why do you think it would work?

And - practically everybody will most certainly get the same error conditions etc as you since Vegas Setup should be the same for everyone - as in calling the same required elements.

VP
Jonathan Neal wrote on 5/11/2009, 1:33 PM
I'm running Windows 7 64-bit and Vegas Pro 9, both the 32-bit and 64-bit editions, installed and are running fine. As mentioned, Windows 7 is not a supported OS, and I'm not getting the bug, so hopefully someone else can help you if you need this. Yet, if you're running Windows 7 64-bit, I would assume that you want to run 64-bit apps. Therefore, I don't see, practically, what you want to accomplish with the 32-bit version.
VanLazarus wrote on 5/11/2009, 1:36 PM
He's running 32 bit software in a 64 bit OS because many codecs and Vegas plugins still do NOT support 64 bit versions of Vegas (8.1 and 9.0)!
jfpearson wrote on 5/11/2009, 2:45 PM
Yeah, virtually everyone will eventually should be installing W7 64 bit and any x86 app should run well.... Need the 32 bit V9 to work because of the limitations of the V9x64 set out in the release notes.
I have now however got it working by shutting off the WMP service and installing with Vista compatibility turned on in the properties attribute. Don't know why it didn't install cleanly in the first place (we are using the W7 Release Candidate), as I was able to test install it easily on another W7x64 machine that we have here without aforementioned changes. Alas, all is seemingly fine now.