I was having major problems with burning disks - creating chapters, previewing, etc. The software just collapsed. Was at the point of total frustration when I came across this thread, upgraded DirectX and works like a dream.
Thanks to all the volunteers who make this such a useful forum.
Jim
can't burn dvd
Moderator: Ken Berry
-
Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
-
Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
-
dennisoralls
- Posts: 4
- Joined: Mon Jan 07, 2008 3:34 pm
Thank you! I will try this. A final question, I have never had this problem in the past. The Roxio products have been on my PC along with at least the last two versions of VS (v9 & v10). This only became a problem after I upgraded to v11. Is there an easy explanation why it just became a problem?
Thank you again for all your help.
Thank you again for all your help.
Ken Berry wrote:The Roxio DLA feature is called "Drag to Disc." Check the system tray at the bottom of the screen and there may be an icon that allows you to disable it when you want to use another program for burning. Also you may have to check for it as a start up item to prevent it always taking control of the burner on start up. Use msconfig in the Run box to do that.
-
Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
The "easy" explanation is that I think an awful lot of the original VS code had to be re-written to take into account Vista. Previous versions were written for XP, but as you know, Vista likes only certain things and hates others. So in re-jigging the program, I suspect they threw a lot of babies out with the bath water! 
In addition, in 2006, Ulead was first taken over by InterVideo, and some of their technologies started worming their way into the new version -- see for example the replacement of the previous capture plug-ins with the single InterVideo module in VS11...
And finally, and perhaps least forgivably, InterVideo/Corel then appears to have dropped previous practice of sending out early versions of the product to beta testers who were regular users of the product. Such rigorous beta testing of course tends to wrinkle out problems and bugs, and get them sort before the final version is released on an unsuspecting public.
In addition, in 2006, Ulead was first taken over by InterVideo, and some of their technologies started worming their way into the new version -- see for example the replacement of the previous capture plug-ins with the single InterVideo module in VS11...
And finally, and perhaps least forgivably, InterVideo/Corel then appears to have dropped previous practice of sending out early versions of the product to beta testers who were regular users of the product. Such rigorous beta testing of course tends to wrinkle out problems and bugs, and get them sort before the final version is released on an unsuspecting public.
Ken Berry