VideoStudio 10 won't open

[waypoint]

Hi,
I had a registered version 7 of VideoStudio and recently downloaded v10 to test prior to purchasing. Last night my Windows XP system crashed when trying to copy my dvd to disk.

I now cannot open the software at all and keep getting a security message "the security information is invalid or has been modified. The program will be terminated".

I have uninstalled and reinstalled v10 but still with no luck. I have also uninstalled v7.

I am otherwise very happy with the product and was about to purchase it, but I don't want to do anything until the demo version works again.

Any ideas would be most appreciated.

Heather
Australia

[sjj1805]

A couple of things to try.
1. START | RUN | CMD
in the DOS like box type chkdsk c: /f
It will tell you that you need to restart the computer to be able to do so.
Do that.
2. If this fails to fix it try System Restore and select a point prior to the computer crashing.

If push comes to shove then use the re-installation procedure as outlined here:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 5773#55773

[dgallagh]

Yes, I've tried this too but since downloading this yesterday, nothing I try seems to work.

I've been a user since Videostudio 5SE.

I went through the re-inatall and clean removal procedures and made sure that the only things running under my video editing profile were vital windows subsystems.

Have also run chkdsk on both disks and defragged both before installing 10 Plus upgrade but no joy.

Problem is I have the same problem of VS8 no longer running either.

This seems to be a real problem piece of code. Unfurtunately I don't have a system restore point since I always turn that off along with the swapfile when defragging - and guess who forgot to turn it back on before installing VS 10+...

I'm going to have to try and get my money back from element 5 I guess.

[sjj1805]

The clue to your issue is that the Windows XP System crashed.
So far you have discovered you have a problem with VideoStudio,
Unfortunately I suspect that there is a good likelihood that you will also find other things on your computer, programs or DATA may have also been affected - you just don't know it yet.

Firstly a short lesson about Hard Drives, then a few steps you can follow to try and cure or alleviate the problem.

If you look at the front of your Computer you should see one or more steady green lights. There is one for each hard drive that is installed in your computer. The green light signifies that the hard drive has power and thus turned on.

Alongside that steady light will be another that is mostly turned OFF but every now and again blinks. When lit this signifies that the computer is either reading from or writing to the hard drive. It takes time to read/write the hard drive - firstly a directory has to be checked to establish where on the hard drive the information is (or is going to be) located, then the laser head has to be moved to that disc position for the read/write operation.

To speed things up you install RAM in your computer which retains a big chunk of DATA therefore when saving stuff to the hard drive it is not written immediately but kept in RAM and then moved over to the hard drive when the computer has something else that needs to be installed in RAM to carry out whatever task it is currently performing.

This is why you have to 'Shut Down' the computer and not simply press the 'OFF' button - this enables anything in RAM to be written to the hard drive - otherwise it will be lost forever.

If you have the misfortune of suffering a sudden mains electricity failure
you may be lucky in so far that nothing was at that time being written to the hard disc, or you could be unlucky and the partly written DATA will now effectively render your hard drive useless as it may have destroyed the hard drive directory or even rendered a hard drive cluster unusable.

So what can we do if we have suffered a catastrophe of this nature.
Firstly there isn't one single easy answer because the damage can range from NIL to you need a new hard drive.

All we can do is follow various repair procedures.
1. Uninstall and Re-install the affected program(s)
2. Run the Windows System File Checker
3. Run the Disc Checking Utility built into Windows. Note the various switches avalable. The one most often used is the F (Fix) Option but if this fails to cure the problem then you need to use the more extensive R (Repair) Option.
4. Check the Windows Error Log
5. Run a Registry Checking Utility
I must warn users to be very careful when running a Registry Checking Utility. Whilst they are good at what they do, in the wrong hands they can also cause havoc to a good working system.
6. Sometimes it may be necessary to track down a faulty startup event/program by using MsConfig

Prevention is often better than cure, you have already mentioned the use of System Restore. Other options previously suggested by Forum Members include making a Drive Image

I am sure a few more members will jump in here with a few more suggestions.

[dgallagh]

Erm - not sure who you're replying to here Sjj1805.

My system didn't crash, and I'm not sure Heathers did.
The Videostudio10 executable crashed upon startup.

I did invest probably too much family time on Saturday to do some digging.

The first thing I found was that it would not play nicely with my Creative Webcam NX drivers - had to remove support totally.

Then I found that Videostudio 10 believes that it ships the best codecs in the world along with the application, and that Videostudio 10 will not sit alongside other codecs. Which is a large assumption to make for a consumer product. (people will have DVD Player apps, DIVX / Xvid players, transcoding utilities for their video Ipods / Irivers / Creative Vision Ms, MP3 recording software etc.

For example - I use the Mainconcept MPEG Encoder for it's performance and quality - and it seems that unless Videostudio has it's MPEG2 encoder installed exclusively - it will no longer run. This seems to be why VS10 crashes in such a mess on launch with an ungracious error code - the only evidence I have of this though is through listing all 38 codecs on my PC using GSPOT, and then wrote a BAT file to de-register them all bar the VS10 shipped codecs, the programme started up perfectly.

I'm just not sure that I can afford the further days work to find out which of the codecs I have that VS10 will specifically not interoperate with.
And it could be most of them...

And I'm certainly not going to stop using Mainconcept for Mpeg - it's by far the fastest around from a transcoding perspective.

Ah well - back to Adobe - it will live happily on my machine with my other codecs -... and Quicktime 7, but I did used to enjoy the ease of use of VS...
will have to order the books for how to use Premiere from Amazon now...

Thanks anyway though, and good luck Heather.

[Ken Berry]

I'm not sure where you got your information about Video Studio's supposed dislike of every other codec which is not a Ulead one. To start with, for instance, Ulead in fact licence their mpeg-2 codec from MainConcept! And as far as I was aware, its DV and mpeg-1 ones come from Microsoft and are installed as part of Windows, not Video Studio. I confess I am not sure of the origins of the mpeg-4 codec which is installed with VS10.

The mpeg-2 codec may operate a little slower than the MainConcept codecs installed by Adobe. But on my computer at least they all seem to get along just fine. And I have both a variety of video editing/authoring/ compositing programs (including Ulead ones, Adobe ones, Cyberlink and a couple of Sony ones), yet have no problems with any of them crashing.

I will certainly grant you that Ulead products may not like certain other codecs, but in the past, evidence from many posts on this Board indicate that these tend to have been installed as part of a mega-codec pack. These packs are usually thrown together on the basis that quantity is better than quality, and often there are codecs within the pack itself which clash with each other, not to mention with programs already installed on the computer.

As a matter of interest, did GSpot find any codecs with broken links?

[njdowding]

I have to agree with Ken, I have the mainconcept encoder on my sustem along with MSP8, VS8,9,10+ and Vegas.

All the codecs sit quite happily together and do not affect the start up of any of them. I rarely use the Mainconcept encoder now as the built in VS10 and MSP one with the advanced button activated gives similar level of contorl and output quality.

I think something more is going on here than just codec problems.

Nick

[sjj1805]

Erm - not sure who you're replying to here Sjj1805.

That what sometimes happens when another user jumps in on someone elses thread.

Hi,
I had a registered version 7 of VideoStudio and recently downloaded v10 to test prior to purchasing. Last night my Windows XP system crashed when trying to copy my dvd to disk.

Just like Ken, I have several Ulead and also competitors Video Editing/authoring products installed and do not have a problem with codecs clashing.

[dgallagh]

Erm - not sure who you're replying to here Sjj1805.

That what sometimes happens when another user jumps in on someone elses thread.

Apologies - I was just trying to stay on topic and not post another "VS10 crashes on startup" thread - to help other users with similar issues. It's an old habit from other forums I participate in / mod on.

Interesting about the VS10 Mainconcept licencing info though - VS10 definitely doesn't like the version of Mainconcepts encoder that I had installed. (I think it was 1.6.x from memory - without re-installing it's hard to check.

It didn't come as part of Premiere though - I bought it standalone.

Ken - Gspot noticed no broken or orphaned codecs.

I am going through device manager video and audio codecs ensuring that Ulead is in the number one priority spot to see if it makes any difference.

[WestbrookNH]

I had a similar problem going from VS10+ Try-Before-You-Buy to VS10+ purchased and downloaded and installed.

Here is something else to try ...

Right click on the application's icon on your desktop and select "Properties".

In the "Properties" window, select the "Shortcut" tab.

In the "Shortcut" property sheet, select the "Advanced..." button.

In the "Advanced Properties" window, check the "Run with different credentials" checkbox.

Hope this works for you ...

.