Video Studio 11+ w/Vista SP-1
Moderator: Ken Berry
Video Studio 11+ w/Vista SP-1
This evening I purchased, downloaded and installed Video Studio 11+ on a machine running Windows Vista with Service Pack 1. The installation went OK using the Administrator account and there were no error messages. But when I try to launch the program, I receive the following error message:
"The ordinal 17 could not be located in the dynamic link library mpgvout.dll."
I couldn't find anything in the ULead or Microsoft knowledge bases that referenced this particular problem.
kBob
"The ordinal 17 could not be located in the dynamic link library mpgvout.dll."
I couldn't find anything in the ULead or Microsoft knowledge bases that referenced this particular problem.
kBob
-
Clevo
- Advisor
- Posts: 1243
- Joined: Sun Jul 08, 2007 2:39 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus PK5
- processor: Intel Quad CPU Q6600 2.40GHz
- ram: 4GB
- Video Card: NVIDIA GeForce 8600 GTS
- sound_card: Auzentech X-Fi Forte
- Hard_Drive_Capacity: 850GB
- Location: Sydney, Australia
You the search feature on this forum:
I found this as an example:
http://phpbb.ulead.com.tw/EN/viewtopic. ... pgvout+dll
There might be more...
I found this as an example:
http://phpbb.ulead.com.tw/EN/viewtopic. ... pgvout+dll
There might be more...
Thanks Clevo,
That was a useful thread. But after trying the various suggestions and pasting the misplaced dll in every other conceivable Ulead directory. I've decided I'm tired of doing product testing for Corel.
I've spent six hours trying to get a sixty dollar upgrade to work. In light of all the publisher's representations concerning their Vista certifications, the customer base has a right to expect something better than the sloppy installer that was provided with the download. Most of us don't realize that in choosing the download over the box version, we are giving up the "repair" option due to the download's de-featured install shield dialog.
The way the error message is worded its also difficult to determine whether the ordinal number is missing from the dll or if the dll is missing.
The crowning insult to customers is the hiding of any support email address. Fortunately there's plenty of competition in this market.
Bob
That was a useful thread. But after trying the various suggestions and pasting the misplaced dll in every other conceivable Ulead directory. I've decided I'm tired of doing product testing for Corel.
I've spent six hours trying to get a sixty dollar upgrade to work. In light of all the publisher's representations concerning their Vista certifications, the customer base has a right to expect something better than the sloppy installer that was provided with the download. Most of us don't realize that in choosing the download over the box version, we are giving up the "repair" option due to the download's de-featured install shield dialog.
The way the error message is worded its also difficult to determine whether the ordinal number is missing from the dll or if the dll is missing.
The crowning insult to customers is the hiding of any support email address. Fortunately there's plenty of competition in this market.
Bob
-
Black Lab
- Posts: 7429
- Joined: Wed Dec 15, 2004 3:11 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Pottstown, Pennsylvania, USA
You got that right. But you would think that would make the manufacturers be on top of their game. Obviously some are not.Fortunately there's plenty of competition in this market.
Jeff
Dentler's Dog Training, LLC
http://www.dentlersdogtraining.com
http://www.facebook.com/dentlersdogtraining
Dentler's Dog Training, LLC
http://www.dentlersdogtraining.com
http://www.facebook.com/dentlersdogtraining
I don't know if this helps or not but after installing VS11+ you should install the 2 update patches and also reboot.
Then install the latest DirectX 9.0C dated November 2007 or later.
That error message can appear because it can't find that file (and others), which should be in the windows PATH statement.
One of the reasons for rebooting is ulead adds a directory to the windows environment PATH statement. That's how the program finds that file (and others).
I've been able to duplicate this error by renaming the following directory, when VS11+ launches it cannot find the file.
C:\Program Files\Common Files\Ulead Systems
Did you reboot the computer?
Install both patches & directx update, reboot again..
Also I've always installed the ulead programs as USER, then reply Yes to install the program with temporary administrative privileges.
With Vista on some program installations if you install them as administrator then only the administrator can run the program (depends).
Then install the latest DirectX 9.0C dated November 2007 or later.
That error message can appear because it can't find that file (and others), which should be in the windows PATH statement.
One of the reasons for rebooting is ulead adds a directory to the windows environment PATH statement. That's how the program finds that file (and others).
I've been able to duplicate this error by renaming the following directory, when VS11+ launches it cannot find the file.
C:\Program Files\Common Files\Ulead Systems
Did you reboot the computer?
Install both patches & directx update, reboot again..
Also I've always installed the ulead programs as USER, then reply Yes to install the program with temporary administrative privileges.
With Vista on some program installations if you install them as administrator then only the administrator can run the program (depends).
etech,
Thank you for taking the time to post such a detailed recommendation. I installed two update patches: UVS11_DMF6_HotFix01_Install_Issue and UVS11_Patch_Eng122507-03. I also installed the DirectX 9.0C dated November 2007 followed by the March, 2008 update.
I verified that MPGVOUT.dll is in the directory C:\Program Files\Common Files\Ulead Systems and I've rebooted after each step. I'm still getting the same error.
I don't know how to check or modify the windows environment PATH statement or in what file it might be contained.
The administrative privileges issue doesn't seem to make a difference in either installing or running the program but I suspect there's something locked up by service pack one that was not anticipated by the author of the ULead installer. I suppose I could install on an old XP machine while waiting for a fix from the publisher.
Thanks again for all of your guidance on this issue. Thus far I haven't seen a definite testimonial by anyone regarding success with a Service Pack One instance of Vista.
kBob
Thank you for taking the time to post such a detailed recommendation. I installed two update patches: UVS11_DMF6_HotFix01_Install_Issue and UVS11_Patch_Eng122507-03. I also installed the DirectX 9.0C dated November 2007 followed by the March, 2008 update.
I verified that MPGVOUT.dll is in the directory C:\Program Files\Common Files\Ulead Systems and I've rebooted after each step. I'm still getting the same error.
I don't know how to check or modify the windows environment PATH statement or in what file it might be contained.
The administrative privileges issue doesn't seem to make a difference in either installing or running the program but I suspect there's something locked up by service pack one that was not anticipated by the author of the ULead installer. I suppose I could install on an old XP machine while waiting for a fix from the publisher.
Thanks again for all of your guidance on this issue. Thus far I haven't seen a definite testimonial by anyone regarding success with a Service Pack One instance of Vista.
kBob
I haven't installed the Vista Service pack 1 yet.
There has been some confusion in reference to VS11+ installation failures.
First, you only install the HotFix if the program fails to install.
So in your case the program did install. I think this is another problem not related to that Hotfix. Maybe you need to eliminate that HotFix if it's causing problems. Ulead says not to install the Hotfix unless your having problems installing. The problems installing haven't been related to this mpgaout.dll.
I would completely remove VS11+.
After removing it completely make sure the following directories are also removed. If not then remove them manually.
C:\Program Files\Ulead Systems\VS11+ (or similar wording)
C:\Program Files\Common Files\Ulead Systems (make sure this doesn't exist).
The correct installation method that has always worked on my system is:
1) The original release of VS11+ (download or boxed)
2) Ulead VideoStudio 11 Update Pack (Release Date: 2007/11/6)
3) Ulead VideoStudio 11 Plus Power Pack
You must log into ulead with your users account to get this update.
The path environment variable might be a wild goose chase I don't know.
Many here are installing the Vista SP1 after a working VS11+ installation. You are installing VS11+ after a Vista SP1 install so maybe there is something wrong.
I would do the above and omit the HotFix installation.
If it fails again then to read your PATH statement.
Goto "Start -> Run -> Type in cmd
This brings up a command window.
In the command window type path
You should see a long listing and the \Ulead Systems\MPEG directory should be listed.
I wouldn't attempt to change any environment variables. It may also be related to permission reading rights of that common files MPEG directory.
One thing for sure is VS cannot get to (or have access rights) to that directory or files.
Again for your information in both XP & Vista if I rename the MPEG or Ulead Systems directory I get the same exact error.
There has been some confusion in reference to VS11+ installation failures.
First, you only install the HotFix if the program fails to install.
So in your case the program did install. I think this is another problem not related to that Hotfix. Maybe you need to eliminate that HotFix if it's causing problems. Ulead says not to install the Hotfix unless your having problems installing. The problems installing haven't been related to this mpgaout.dll.
I would completely remove VS11+.
After removing it completely make sure the following directories are also removed. If not then remove them manually.
C:\Program Files\Ulead Systems\VS11+ (or similar wording)
C:\Program Files\Common Files\Ulead Systems (make sure this doesn't exist).
The correct installation method that has always worked on my system is:
1) The original release of VS11+ (download or boxed)
2) Ulead VideoStudio 11 Update Pack (Release Date: 2007/11/6)
3) Ulead VideoStudio 11 Plus Power Pack
You must log into ulead with your users account to get this update.
The path environment variable might be a wild goose chase I don't know.
Many here are installing the Vista SP1 after a working VS11+ installation. You are installing VS11+ after a Vista SP1 install so maybe there is something wrong.
I would do the above and omit the HotFix installation.
If it fails again then to read your PATH statement.
Goto "Start -> Run -> Type in cmd
This brings up a command window.
In the command window type path
You should see a long listing and the \Ulead Systems\MPEG directory should be listed.
I wouldn't attempt to change any environment variables. It may also be related to permission reading rights of that common files MPEG directory.
One thing for sure is VS cannot get to (or have access rights) to that directory or files.
Again for your information in both XP & Vista if I rename the MPEG or Ulead Systems directory I get the same exact error.
Thanks sl2008. Please let us know if you had VideoStudio 11+ already installed prior to your Vista SP1 install.
While uninstalling VideoStudio 11+, I just received several write error messages such as "Error 1310. Error writing to file: C:\Config.Msi\87f663.rbf. Verify that you have access to that directory." Several other .rbf files were mentioned as the uninstall progressed.
After the first message, I had to verify that I wanted to proceed as administrator to access the C:\Config.Msi directory. I removed the read only restrictions from the directory, subdirectories and files several times. But they all kept reverting to read only and the .rbf write failures continued.
There were no write error messages during the install, only during the uninstall.
I wonder if the reversion bug/feature is unique to SP1 or just my particular install of SP1.
I will try the rest of the suggestions you made, etech. And if they don't fix the problem I will roll back my SP1 installation, reinstall 11+, test it and then reinstall SP1.
Thanks again,
kBob
While uninstalling VideoStudio 11+, I just received several write error messages such as "Error 1310. Error writing to file: C:\Config.Msi\87f663.rbf. Verify that you have access to that directory." Several other .rbf files were mentioned as the uninstall progressed.
After the first message, I had to verify that I wanted to proceed as administrator to access the C:\Config.Msi directory. I removed the read only restrictions from the directory, subdirectories and files several times. But they all kept reverting to read only and the .rbf write failures continued.
There were no write error messages during the install, only during the uninstall.
I wonder if the reversion bug/feature is unique to SP1 or just my particular install of SP1.
I will try the rest of the suggestions you made, etech. And if they don't fix the problem I will roll back my SP1 installation, reinstall 11+, test it and then reinstall SP1.
Thanks again,
kBob
After uninstalling SP1, and upon restart, I received a message about blocked startup programs. Ulead may have a Windows Defender problem. For among the Blocked Startup Programs uvPL.exe was listed in the "Publisher Not Available" category. The summary follows:
File Name: uvPL.exe
Startup Value: C:\Program Files\Ulead Systems\Ulead VideoStudio 11\uvPL.exe
File Path: C:\Program Files\Ulead Systems\Ulead VideoStudio 11\uvPL.exe
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
SpyNet Voting: In Progress
The error involving Config.Msi and the .rbf files continued as I uninstalled Video Studio 11+ after the SP1 rollback. This time, for each instance, I removed the read only attribute before hitting retry.
File Name: uvPL.exe
Startup Value: C:\Program Files\Ulead Systems\Ulead VideoStudio 11\uvPL.exe
File Path: C:\Program Files\Ulead Systems\Ulead VideoStudio 11\uvPL.exe
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
SpyNet Voting: In Progress
The error involving Config.Msi and the .rbf files continued as I uninstalled Video Studio 11+ after the SP1 rollback. This time, for each instance, I removed the read only attribute before hitting retry.
I uninstalled SP1, then uninstalled VS 11+. Blew away all Ulead directories, did a disc scan and reinstalled VS 11+.
Same errors, major time sinkhole. Not exactly a productivity solution they're selling here. Corel needs a product testing department and a true help desk. As it stands, they're using unsuspecting customers to pick up the slack.
Thanks everyone for your help.
kBob
Same errors, major time sinkhole. Not exactly a productivity solution they're selling here. Corel needs a product testing department and a true help desk. As it stands, they're using unsuspecting customers to pick up the slack.
Thanks everyone for your help.
kBob
-
Clevo
- Advisor
- Posts: 1243
- Joined: Sun Jul 08, 2007 2:39 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus PK5
- processor: Intel Quad CPU Q6600 2.40GHz
- ram: 4GB
- Video Card: NVIDIA GeForce 8600 GTS
- sound_card: Auzentech X-Fi Forte
- Hard_Drive_Capacity: 850GB
- Location: Sydney, Australia
The ol Pre load problem. I believe I have mione disabled in start up in Vista 64bit as it did give me some troubles but not during installation.
When I get home this evening I'll explain further but in the mean time you can go to
Link removed by Admin, as it did not go to any tutorials, but to a parked web page full of advertisements
Where they explain how to disable start up programs.
I have taken this program off start-up and I have no problems with VS11.5+ running on Vista 64 bit with SP1
When I get home this evening I'll explain further but in the mean time you can go to
Link removed by Admin, as it did not go to any tutorials, but to a parked web page full of advertisements
Where they explain how to disable start up programs.
I have taken this program off start-up and I have no problems with VS11.5+ running on Vista 64 bit with SP1
Hi Clevo,
I tried everything with and without the pre-load program. The SP1 install even broke Microsoft's own update feature for Vista. I think they should adopt the slogan "We sell each and every wine before its time."
Then again it seems odd that Corel's installer should run merrily along w/o reporting write errors on the install but stopping for each one on the uninstall.
I just noticed the line "*Corel Support is not obliged to answer in this forum." Boy is that a stupid way to operate in today's open arenas of commerce and trade.
kBob
I tried everything with and without the pre-load program. The SP1 install even broke Microsoft's own update feature for Vista. I think they should adopt the slogan "We sell each and every wine before its time."
Then again it seems odd that Corel's installer should run merrily along w/o reporting write errors on the install but stopping for each one on the uninstall.
I just noticed the line "*Corel Support is not obliged to answer in this forum." Boy is that a stupid way to operate in today's open arenas of commerce and trade.
kBob
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
This is a User to User Web Board - the only involvement by Corel is that they have kindly provided us with some free web space to host it. They also kindly provide us with prizes for Forum Competitions.BobKalk wrote:.......
I just noticed the line "*Corel Support is not obliged to answer in this forum." Boy is that a stupid way to operate in today's open arenas of commerce and trade.
kBob
