Burn fails with out of memory error

[joek.payne]

This is an unusual situation. I don't know if I am wasting your time with this problem but I need some help. I am running windows 7 under Parallels on my iMac 27. The first phase of the copy from a DVD seems to work fine. Soon after the burn phase starts it fails with an out of memory error.

I am attaching logs and a snapshot image of the windows screen.

[CBR929]

Hi joek.payne
Please download and use the latest version found here Latest Version

Also please try cleaning out your temp folder of unneeded files.

You may also try using ImgBurn as your burn engine, you will find instructions setting it up using the link in my signature.

Hope this helps
CBR929

[maineman]

First off, I notice this in your internal log:
0m 01.21s: Qt Translator file load failed, the *.qm path is C:\PROGRA~2\DVDFAB~1\QLanguage\DVDFabQt_.qm

Please check and be certain that your default language setting is English.
I'm not referring to the dvd tracks, but Fab's settings.

Open Fab > click the Green √ top right corner > Common Settings >
Click General > Language setting.

You also may be experiencing an I/O error, potentially, your drive buffer.
Be certain that your ODD(s) is (are) in UDMA mode.
You should be able to reset DMA in Fab's Common Settings as well, although this quick fix doesn't always stick.

Also, double check
Common Settings > DVD > Read >
Enable read-ahead cache
This should be enabled (ticked)
and should reduce your chances of any drive buffer underruns.

Agree with my good friend CBR929, definitely switch to Img.
VSO is problematic for many users and...JMO...Img is simply better... more reliable, more configurable

Hope this helps

[joek.payne]

Thanks -- problem solved

Many thanks to CBR929 and maineman. I followed your instructions and my out of memory error is solved! I think vso burn engine was my main problem.

[CBR929]

Hi joek.payne
Glad it's working for you now.
CBR929

[maineman]

Many thanks to CBR929 and maineman. I followed your instructions and my out of memory error is solved! I think vso burn engine was my main problem.

Good to hear you're up and running smoothly again