I know this sounds silly but....

Myerz wrote on 5/29/2010, 10:00 AM

Installing Vegas Pro 9 straight out of the box.... updating to Release 9.0e.....

I know stupid question but I recently had issues of the release "E" crashing everytime I tried opening up Vegas.
Looking back I am questioning whether I had all my Vista updates installed ( i.e. Service packs, etc.... )

Question: Do you have to do "release a" thru "release d" first?

Comments

musicvid10 wrote on 5/29/2010, 10:08 AM

No, each release is fully self-contained.
What do you mean by "crashing?" What error messages? Does the splash screen hang? At what point?

Myerz wrote on 5/29/2010, 10:18 AM

Thanks for your reply...

It's past the splash screen.... It get's to the point where it look like you're a-ok to start doing something..... you go to click on anything.... and it goes to a "Not-Responding" condition.

musicvid10 wrote on 5/29/2010, 10:48 AM

"What is "anything"?"
Post the full details, using MediaInfo, of a file that is hanging. Post a short clip so others here can take a look at it.

"Not responding" is not a crash! It means that Vegas is thinking. If it goes on for a long time, the program may have hung.

Take a normal DV-AVI or MPEG-2 file. If it does not open in a minute or two, you may need to reinstall Vegas. What is your operating system (be specific!)

Dave_OnSet wrote on 5/30/2010, 8:48 AM

This may be way off-base, but have you checked the various permissions for Vegas? At one point I had a problem with an install of an SCS program (maybe sound forge or DvD Architect, not sure?) that wouldn't open, and it turned out that it didn't have the various SYSTEM permissions it needed in place (on security tab of program properties.) Once I gave the program some more permissions it opened fine and everything worked perfectly. Probably had something to do with the Vista preferences on the machine, since didn't have the problem elsewhere...

DSCalef wrote on 5/30/2010, 9:41 AM

It is always fascinating to me how many people successfully use Vegas Pro everyday but that when one person crashes all the time, it must be the program. No question every program made has minor bugs that can show up, but I always think of motor vehicles. If one person has one or more crashes, do we blame the vehicle for it? Okay, with Toyota, perhaps a bad comparison. But users need to think about who they blame out of the gate. As a former computer reseller, I invented the term OE to use when I was called to "fix" a malfunctioning computer or program. It was easier to explain a problem as an "OE that happens, so to avoid it, trying doing it this way...... ". Stopped the defensive reaction that whou happen if I told them that it was an operator error. One of my best customers finally asked one day what OE meant and I explained with a chuckle. He thought for a moment and said "No, damn it, it is not! It is OI". After a pause, he continued, "Operator Incompetent!"

No personal offense intended to anyone who has issues. I am just suggesting we have to think about things carefully and logically before we blame. I also understand technology remains mysterious to many. That's why asking the questions in this forum is so fabulous. The questions should come before the blame is assigned.