Warning: Vegas 11 32 bit won't load onto XP

Sidecar2 wrote on 11/17/2011, 11:01 AM
Bought the packaged version of Vegas 11. Installs onto Windows 7 but will not install on my XP 32 bit machine.

Immediately after clicking the Vegas 11 32 bit install button a placard comes up that says: "This software requires that a minimum of one of the following operating systems be installed:
- Windows Vista Service Pack 2
- Windows 7"

Also, the NewBlue Titler Pro won't run on my Win7 64-bit Lenova laptop because the internal video card is insufficient.

Comments

Grazie wrote on 11/17/2011, 11:45 AM
So, Sidecar2, what is your question?

- g

Sidecar2 wrote on 11/17/2011, 12:06 PM
Didn't ask a question. I stated a situation I now face that I didn't expect, nor ever faced before from Sony.

I work in an XP Pro 32-bit environment dictated by my IT organization. We don't have Win7.

I am now stuck at Vegas 10 until our entire organization (tens of thousands of machines) is upgraded Win7. It'll happen, eventually.

The statement is, if you're not running Win7, or can't run Win7, don't bother dropping the $262.85 to upgrade to the boxed version with faster shipping.
Red Prince wrote on 11/17/2011, 12:51 PM
This has been discussed on this forum right after Vegas Pro 11 was released. And someone even found a workaround. You may want to look at the older threads discussing Vegas 11 on XP.

The workaround, if I recall correctly, had something to do with starting the install on Windows 7, finding the MSI file(s) the exe extracts (no idea to which directory, you’ll need to find that older thread), then transferring the MSI to XP and install from MSI.

Apparently that works. I have not personally tested it because I no longer use XP, so your best bet is finding that old thread somewhere here on the forum.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

rmack350 wrote on 11/17/2011, 1:23 PM
My first thought about the collision of "I.T. organization" and "workaround" was that the two wouldn't coexist, but this particular workaround is pretty simple. If you can install software *at all* then you can probably do this.

Rob Mack
TheHappyFriar wrote on 11/17/2011, 1:28 PM
They did the same with Win2K a couple versions ago (8 I think).
Red Prince wrote on 11/17/2011, 2:17 PM
OK, here is the original thread I mentioned earlier. If you scroll down far enough, you will find the post by malowz, where he talks about installing VP 11 on XP.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Grazie wrote on 11/17/2011, 2:21 PM
@ Sidecar2 - I was aware you hadn't asked a question, that's why I asked if you had one. Simple really.

- g

malowz wrote on 11/17/2011, 5:13 PM
new vegas build is compiled for vista/win7 only. so, the "solution" i posted before its not possible anymore.

even then, its possible to patch the file to run on XP. BUT, they used some kernel instructions unavailable in XP, so only a assembler-jedi could make it run on XP.

all of this, to make "sure" you won't run on XP.

well done, Sony.

so, everyone with XP that really thinks is too much for update a whole OS for one program (which run fine on XP, but sony choose not to) keep Vegas 10 until future upgrade.

nice to know sony "work hard" to limit a software, and yet, my scripts icons still go away since "forever". and no fix ;P
Chienworks wrote on 11/17/2011, 6:44 PM
I don't object to the upgrade, i quite understand it in fact. What i object to is Microsoft's pricing. Upgrading Windows costs generally somewhere between $150 and $300 depending on the version and how soon you jump on it. It's simply not worth that to me. For the 10% of the OS that actually does something useful for me, i'd be willing to pay maybe $40 for the upgrade, maybe. It just rankles me that i have to pay 4 times that much for the other 90% that i don't want or need.

About the only time i'll move to a new Windows version is when i get new hardware with it installed by the manufacturer. My laptop runs Win7. But, all my other boxen are still on XP and are unlikely to ever upgrade for the rest of their functional lives.

On the other hand i see the upgrade price for Vegas as a good value. I don't mind that price at all.
Opampman wrote on 11/17/2011, 7:50 PM
Agree with malowz...it's a shame they go to the trouble and out of their way to make sure 11 won't work on XP but won't fix the bugs that have been there forever.
Kent
TheHappyFriar wrote on 11/17/2011, 9:01 PM
they used some kernel instructions unavailable in XP
which run fine on XP, but sony choose not to

Those two statements say the exact opposite. It can't run fine on XP if it's using system calls that don't exist on XP.

What i object to is Microsoft's pricing. Upgrading Windows costs generally somewhere between $150 and $300 depending on the version and how soon you jump on it. It's simply not worth that to me

If you bought Win7/Vista when it came out and we assume the same life for win7/Vista as XP for Vegas, that would mean you spend $30/year for Win7. However, you're saying $150/year for Vegas is a better deal because you use 90% of it (guessing)? Do you use 90% of Vegas every day? IE Protype (which was new), 64-bit (can't run on XP anyway), the new FX, GPU support, etc. 90% of the time?

Just something to think about.
Former user wrote on 11/17/2011, 9:03 PM
I bought Win 7 with a 3 license kit for $125. About $40 a computer.

Dave T2
Chienworks wrote on 11/17/2011, 9:32 PM
No, i don't use that much of Vegas regularly. However, the subjective value of it is that i spend a good deal of time looking at a screen in front of me full of Vegas, clicking it's buttons. That makes it valuable to me.

Honestly, i just don't feel like Windows is doing anything more for me than i got from it with version 3.11. Yes, i know there are some technical improvements in there, but they don't make my life enough better to feel they're worth the price. In fact, in a lot of ways i find the usability of Win 7 to be a big backwards step from XP and 98. I also have some legacy software i've used for many ages that no longer runs so i'm either without those functions or spending money to replace them or finding time-consuming work arounds. That makes having 7 seem to be a negative value.

I suppose though this is exactly what most Mac users have gone through with every new MacOS version.
malowz wrote on 11/17/2011, 10:51 PM
Those two statements say the exact opposite. It can't run fine on XP if it's using system calls that don't exist on XP

the files can be compiled to support XP (as was in first v11 build). if XP will not be supported, the compiler allow instructions not present on XP,

it's an option.