Quote Originally Posted by Harry Kuhman View Post
Turned out that he was waiting until he saw 100% and then stopped the thing instantly, rather than wait for the last bit to finish and the download to really be done.
Harry, yes, for the 83.5% problem, this was most probably my mistake also.
However, on another occasion, I waited until it said 'download complete' and 'seeding only' but the 'md5' check proved to be erraneous. I had to 'force re-check' twice to restart the download. At that point, the 'md5sum' check was a successful 'OK'. The cause is unknown and could also be user error.

In any case the md5 would catch the problem, and is faster and cheaper than burning a coaster.
Well said.

Not sure how one changes the RAM buffer, can you provide details? Is that a feature of particular burning software? Of course, any remotely modern burner will have "burn proof" or some similar feature, but it is always better to not rely on that. And burning at low speed helps a lot in preventing buffer under run.
In Nero Express 7, go to Options>Ultrabuffer to check the size of the secondary buffer. In most cases, this check is not necessary, as the default should be set to 'Automatic', which is the highest value, 80MB.