Oops - forgot to mention the obvious - I have 123Gb of disk space free.

John...the dxdiag file also contains information about your Display adapter and video memory. Can you post that or the DXDIAG file here, please?

PART B
Create a Diagnostic File
Go to > Start
Select > Run
Type in > Dxdiag
Click > OK
Select > save the information
save as ****DxDiag.txt
Replace the **** with your name so the file can be identified easily.
Example: johnDxDiag.txt

Yes - here is the info for the display. For come reason I am not able to attach files when clicking on "Attach Files" I'll see if I can get that workign to send the entire dxdiag file, but for now here is the display info.

Thanks!

John

Display Devices
---------------
Card name: 128MB ATI Radeon X1300
Manufacturer: ATI Technologies Inc.
Chip type: Radeon X1300/X1550 Series (0x7187)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_7187&SUBSYS_04021028&REV_00
Display Memory: 890 MB
Dedicated Memory: 127 MB
Shared Memory: 763 MB
Current Mode: 1680 x 1050 (16 bit) (60Hz)
Monitor: Dell E207WFP
Driver Name: atiumdag.dll,atiumdva.dat,atitmmxx.dll
Driver Version: 7.14.0010.0464 (English)
DDI Version: 9Ex
Driver Attributes: Final Retail
Driver Date/Size: 4/10/2007 08:18:08, 2671104 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-32C7-11CF-4872-0824A1C2CA35}
Vendor ID: 0x1002
Device ID: 0x7187
SubSys ID: 0x04021028
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

I would start by updating your old video drivers (ATI is at version 9.8 now):
http://support.amd.com/us/gpudownload/windows/Legacy/Pages/radeonaiw_vista32.aspx?type=2.4.1&product=2.4.1.3.7&lang=English

Also, how much space is available on your HARD DRIVE?? This is a storage error, so let's see what you have, please.

Try again to attach the dxdiag file (the attachment dialog is at the bottom of the page when you create a reply),,,,then let's see if anyone else will "chime in" on this.

Thanks - I'll update the ATI driver. Interestingly enought, when I use the device manager to look for updated drivers it tells me that my video driver is current. I'll follow the link you provided and update.

My HD has about 123 Gb free so that shoouldn't be a problem.

Once I update the video driver, I will reply if it worked.

Thanks!

John

Sounds like an issue with space..of course...it could be related to the burning process and option selected during that.

Don't forget to run the "dxdiag" and attach the file if you need further help. It helps get the Senior guys here looking up and taking notice of your error.....so hard to keep those seniors focused!!

Thanks, Fred. Attached is my DxDiag fileI updated the ATI driver (doesn't reflect in the dxDiag file as I had run dxdiag previous to the update.) Still same error with the update.

I did look on another thread in the forum and noticed a tip to "produce" a project to a file first, exit PowerDirector and start it up again, and then import the "produced" file and finally burn it to DVD. I followed that process and it worked fine. Go figure! Sure seems odd....

I appreciate the help you are providing!

John

No file attached..so maybe you can re-run the dxdiag then, try again and use the button at the bottom that says "attach files" (next to the submit button) when you create a new reply.

Ok, I hit the issue at 4% in a DVD burn.

I've reported the problem.

I'm using PD8 v2220

Dafydd
[Moderator]

Glad to see I'm not the only one seeing this problem - I appreciate you reporting it.

I think I finally realized what I was doing wrong enclosing my DxDiag file - I wasn't zipping it and it appears that only .zip and image files are allowed. So - for the record, it should be enclosed. If it isn't, I haven't a clue what I'm doing wrong. When I click "Attach Files" I get the "File Attachment Panel" dialog box, browse and get the right path to the file in the "filename" box and then click preview. I notice when I preview, the "File Attachment Panel" dialog box disappears and no attached file shows up in the preview. So this time I didn't preview - just clicked submit - hope it worked!

Thanks again for all the help!

John

John;
Typically text files less than 100k attach fine, but I have fallen into that "Preview" trap before.
Glad to hear you updated your video drivers.

Also glad that dafydd has a report in!! I notice that he has referenced an interim build # 2220. I suggest that you contact Support via opening a ticket and see if they will get you a copy of this newer build for testing. Reference this post if needed.

Now that we can see the DXDIAG, I am sure that others, with greater experience will comment.
What format and resolution were you using when you attempted to create?
I think that only having 128 MEG of video memory is a potential problem. Especially with a dual core CPU and only 2GIG RAM.
More to follow.

Fred,

I currently am due a response from support after providing them the DxDiag file - it has been a few days. Once they respond I will request the 2220 Build. From what Dafydd is reporting, however, it sounds like it has the same issue.

As I mentioned earlier, it appears as though I have found a work-around that has at least worked once - "producing" to and MPEG, exiting PD, re-entering PD, importing the MPEG and then burning. Cumbersome, but worked once and has allowed me to burn the 1st successful DVD since purchasing the SW in August.

Well - looking forward to input from others on the extent my configuration is contributing to the issue.

Thanks again for your help!

John

This is what I have been getting since I purchased around July/Aug time.

On Burn Disk at around 6%

Runtime Error Program;...es (x86)\cyberlink\POWERDIRECTOR\MotionMenuGenerator.exe

This application has requested the runtime to terminate it in an unusual way.
Please contact the application'support team for more information. (Press OK)
(Pop up) Motion menu generator application has stopped working
(Pop up) Burning unsuccessful
Possible cause.
Transcoding engines front end stream error might be due to: 1 Broken or missing source file
2. Out of system memory.

Have been working with support trying to resolve issues since time began
well it feels like it

Really impressed with programme but if I cant use it.

Hope support sorts this soon feeling very low.

Regards Dave

I had a similar problem with PP5. I burt it to a folder and after it failed I opened the last video file it created and found out what clip was the last recorded. I then went in and deleted that clip from the project and it burnt fine, then later went in and added it back in and all was fine. Somehow the file was corrupt, the original video file was ok, but something with that files info in the PP5 file was bad, by removing it and readding it it clear it up.

Thanks for posting about producing the file first and then importing to burn...it was the only way I could burn my video. Just wondering- doing it that way seemed to have pulled out my chapter markers- any way around that?

John,
It has been a long time since your problem began, I hope that it is now solved. Could you please share the solution so I and others can burn discs also without using the Produce method.
Thanks,
Gary