[QUOTE=troy512;2125168]impossible, under normal operating conditions.[/QUOTE]
Define “normal” on a PC. I’m running a virgin install of XP-64 on a home-made PC sporting a Phenom 9850 CPU and 8gb of RAM. The only application running was DVDFab. For me, that’s “normal”.
[QUOTE=troy512;2125168]dvdfab still writes to hard drive first. the original can be removed while burning.[/QUOTE]
I’m aware of how DVDFab works, but I certainly didn’t imagine this. The work-around is, of course, to burn to the hard drive (and deal with the read errors during that phase), and then copy from the hard drive to the new disc. However, there is an issue here.
[QUOTE=troy512;2125168]never once has this happened to me, even when receiving many read errors[/QUOTE]
I’ve been a programmer for almost 30 years, and I’ve often used the claim that “it doesn’t happen for me”, or “I can’t duplicate the problem”, but I still look at the code to see if there’s some weird little thing that I can’t trigger. I recognize that it can be a pure bitch to find the cause of problems like this, and I’d like to see a comment from the developer that he’s at least looking it.
Besides all that, I’m a paying user, so I think I’ve got the right to expect some kind of response from the guy that’s writing the code.