What happens when you click on NEXT
HA, only joking.
I just picked up you also have WS2 installed, correct, if so this is what I would do:
Uninstall WS2 & VS11.5 completely. Don't bother with registry settings.
After both programs are un-installed make sure these 3 directories do not exist anymore on your harddisk.
C:\Program Files\Ulead Systems ( WS2 & VS11.5 )
C:\Program Files\Common Files\Ulead Systems (this one is important to completely remove)
Then re-install VS11.5, then the regular patch, then the HD-Add-On patch/pack.
If VS11.5+ then allows you to go to STEP 3 (the burning module) then do not install WS2. If you do install WS2 you may end up back where you started.
So if the above works then the NEXT thing to do is contact tech support and ask how to resolve this conflict.
This would be my NEXT step to perform in troubleshooting this problem.
I know this has been a real headache for you, hope the above works, it should..
'NEXT' button does nothing after menu template is created
Moderator: Ken Berry
I to have had this problem since installing v11 plus. But since I uninstalled older versions of ulead video studio .Then uninstalled v11 and reinstalled it is working fine. Don't if this will work for you but so glad it did for me after reading these posts thought it might take awhile to get it sorted. Good Luck.
-
Accolades
- Posts: 468
- Joined: Sun May 28, 2006 8:38 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte GA-EX58-UD4
- processor: QuadCore Intel Core i7 920 2833 MHz 21 x 135
- ram: 12 GB DDR3
- Video Card: Nvidia GeForce GTX 295
- sound_card: On Board 5.1 Surround - Realtek ALC888 - 1200
- Hard_Drive_Capacity: 4TB +
- Location: Brisbane, Queensland Australia
- Contact:
Updated but still have problem!!Ken Berry wrote:Accolades -- I don't recall, but have you updated your DirectX from the Microsoft DirectX website. The current patch is dated November 2007 and works on both DirectX 9.0c (XP) and also, importantly, DirectX 10 (Vista). People with the Next/Preview problem have found that this update fixes the problem...
My You Tube Channel:
My Vimeo Channel:
SONY MOVIE STUDIO PLATINUM HD 10, Corel Video Studio X3, Corel Draw Graphics Suite X4 (Draw, Paint), Adobe Photo Shop CS4, Adobe Bridge CS4, DivX 8, Irfranview, FRAPS, Deamon Tools, VLC, MyDefrag, Nero, AVG, Winamp, Autopano, VMware...
My Vimeo Channel:
SONY MOVIE STUDIO PLATINUM HD 10, Corel Video Studio X3, Corel Draw Graphics Suite X4 (Draw, Paint), Adobe Photo Shop CS4, Adobe Bridge CS4, DivX 8, Irfranview, FRAPS, Deamon Tools, VLC, MyDefrag, Nero, AVG, Winamp, Autopano, VMware...
-
Soo24HC
Also unable to get past NEXT
I just thought I would add that I'm yet another user with the same problem. I cannot get past the 'NEXT@ screen and burn a DVD.
I'm running under XP, have updated the DirectX software, have uninstalled and reinstalled VS11 and its fix packs, but nothing has worked.
I have 50Gb space on my C: Drive and 211Gb on the D:, so plenty of space.
Oddly, I think it did work when it was 1st installed about 10 days ago. Then my external (USB) hard drive broke and I installed a new internal SATA drive to replace it, which means the DVD drive has moved from being D: to E:
Have tried it on my other machine, which I don't normally use for Video work and that one works OK.
Have contacted Ulead Tech Support, but no answer so far.
If anyone else gets any other thoughts I'd be glad to hear them.
I'm running under XP, have updated the DirectX software, have uninstalled and reinstalled VS11 and its fix packs, but nothing has worked.
I have 50Gb space on my C: Drive and 211Gb on the D:, so plenty of space.
Oddly, I think it did work when it was 1st installed about 10 days ago. Then my external (USB) hard drive broke and I installed a new internal SATA drive to replace it, which means the DVD drive has moved from being D: to E:
Have tried it on my other machine, which I don't normally use for Video work and that one works OK.
Have contacted Ulead Tech Support, but no answer so far.
If anyone else gets any other thoughts I'd be glad to hear them.
-
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
Soo24HC
Are any of the files you are using located on drive letters D or E?
If so you will need to re-link them. Have you followed the suggested workflow and created rendered video files or are you using a VideoStudio project file?
Suggested work flow by SJJ1805 for Video Creation
Are any of the files you are using located on drive letters D or E?
If so you will need to re-link them. Have you followed the suggested workflow and created rendered video files or are you using a VideoStudio project file?
Suggested work flow by SJJ1805 for Video Creation
-
Soo24HC
I have a working system!
Steve, in answer to your question, in the world before my external USB drive expired, everything was on the C: drive and the DVD drive was D:. The USB drive was I:, but I don't think VS was ever pointed at its files.
Just for info, for anyone who reads this post later, the box with the problem is a pre-installed Dell box. The external drive problem corrupted the Windows fonts and forced me into reinstalling the operating system from the Manufacturer's partition. This brought with it lots of rubbish which I thought I'd got rid of - but more later.
I am now back up and working.
For the benefit of anyone else who gets in the same situation, here is what I did.
I did yet another uninstall, but this time a manual one using the instructions elsewhere in this forum.
I also did a careful trawl through my registry and C: drive to remove any folders that started with AOL, Roxio and Sonic! These products had been uninstalled, but had left things behind.
I then rebooted and reinstalled VS11.
The system now works, and has not crashed (fingers crossed) since (it was crashing regularly before).
I do not know which of the things I did solved the problem, I was just too thankful to get going again!
Just for info, for anyone who reads this post later, the box with the problem is a pre-installed Dell box. The external drive problem corrupted the Windows fonts and forced me into reinstalling the operating system from the Manufacturer's partition. This brought with it lots of rubbish which I thought I'd got rid of - but more later.
I am now back up and working.
For the benefit of anyone else who gets in the same situation, here is what I did.
I did yet another uninstall, but this time a manual one using the instructions elsewhere in this forum.
I also did a careful trawl through my registry and C: drive to remove any folders that started with AOL, Roxio and Sonic! These products had been uninstalled, but had left things behind.
I then rebooted and reinstalled VS11.
The system now works, and has not crashed (fingers crossed) since (it was crashing regularly before).
I do not know which of the things I did solved the problem, I was just too thankful to get going again!
I've been able to simulate different errors, none related to the Next button not being highlighted unless
1- You are on an empty timeline.
2- You have the "Play as introductory Video" checked ON without any other files on the timeline.
To force VS errors in the burning module I'll assign the working folder to my external USB drive and create menus etc, then exit & save the program.
When I go back without the drive attached the program crashes in the Burning Module.
I suspect as some others have posted that references to the external harddisk can make/cause errors if the harddisk isn't back online again for the next project. Or, as one posted the usb drive was corrupted.
1- You are on an empty timeline.
2- You have the "Play as introductory Video" checked ON without any other files on the timeline.
To force VS errors in the burning module I'll assign the working folder to my external USB drive and create menus etc, then exit & save the program.
When I go back without the drive attached the program crashes in the Burning Module.
I suspect as some others have posted that references to the external harddisk can make/cause errors if the harddisk isn't back online again for the next project. Or, as one posted the usb drive was corrupted.
