Ok, i have got a .cue and .bin files. I know nero can burn .cue files onto a DVD. The .cue contains a movie (if i said that correctly). But, im not sure how to get it to burn. I tried a way before, here's what i done: started nero smart start, then went to favourites and clicked "Make your own DVD-Video" a new window showed, then i mounted the .cue image with alcohol 120%, and imported it into nero, followed the next steps, next, next, then burn. However it was burning really slow (the speed the video normally plays) i know nero can burn much faster, and 8x faster is the optimal speed to burn at. will someone please tell me how to burn my movies faster? also, on my PC where it shows some specs, it says "4x DVDRW Multi" does this mean i cant burn with nero at 8x faster? I would appreciate your help.
That's what it means...you only have a 4X burner. How to burn bin and cue files with Nero: http://www.afterdawn.com/guides/archive/bin_cue_with_nero.cfm
okay, opened nero burning ROM, went to recorder>burn image (im using nero 7), then i selected the cue file, then a menu called burn compilation came up and on the drop down menu i can choose CD or DVD, seeing as im burning a DVD i choose DVD right? then i press new? im only asking because i done this before and it kept crashing after i pressed new. (so i re-installed nero.)
You don't use the "Make your own DVD video". Just double click the cue/image file and nero burning rom will automatically open up. Insert a disc and burn. That simple. Oh and burn at at a low speed so that the information won't have any glitches when burning.
when i double click the .cue image, this comes up: i dunno what to do, but even if i choose DVD, then click new, it crashes. it does open nero burning rom, but this always comes up.
I just downloaded Nero v7.2.3.2 Demo, and I get the same thing. It appears to have a bug trying to burn bin/cue files. It will work with .iso and .nrg files, but something appears to be wrong with the interface for bin/cue files, resulting in "Internal Error" and program crash. Did you find a fix to this?
