[quote=maineman;2159910]Right, your posts were pretty clear about what occurred.
There are a couple of additional bits of info though and thanks for adding those.
You used [B]Write Data[/B].
Interestingly, when I used Write Data and attempted to populate[I] Source [/I]with either of my two .ISO files of WALL_E, I received the same “warning” as you…just the XP Pro version (shown below).
I didn’t try to burn it since I only have my precious Verb MKM 001 (MIS) media. If I had some crappy DL media, I’d give it a whirl. As you know, Write Data only works when writing to a disc.
I’m curious as to what would be on the resultant disc.
Like you, I’m also unable to pull up any VSO burn logs…I think Fengtao will have this fixed in the next Beta.
Of course, we still have the dilemma as to why the ripped files “expanded” on the original rip in clone mode.
I have seen this peculiar behavior in the past with a handful (at most) of flicks over the past 3 years or so where Fab stumbles on the disc structure…
When you cloned WALL_E, did you[I] tick[/I] Copy [B]DVD-Video Data Only[/B] ?
and tick or leave unticked [B]Copy Original IFO Files[/B] ?
I just tried it again on a different pc. The .ISO file is again 7.3 GB and again I receive the error warning if I call it up with Write Data mode.
This was the case whether or not I ticked or unticked Copy DVD-Video Data Only.
You also know two other users that were able to reproduce this issue with clone? Did they use a different source disc?
Well, I guess it’s a moot point since we both have good quality clones.
Still, this is pretty bizarre or as…Alice said,
[I]"Curiouser and curiouser![/I]
When I get a chance, I’ll send the IFO files to Fengtao.[/quote]
When i clone the two boxs are always unticked when i clone, Like i said above also if you tried to write to that DL disc it would’nt waste a disc unless you would agree to a Main Movie copy etc as i explained above. Im glad you seen it. Also i found the bug as soon as that version was released for not writing to the log file. Without saying anymore about it i know you understand what i used and how i went about cloning it using other programs fully. There is one thing that comes to my mind here but i don’t know the answer. As you see i did a test with 22.214.171.124 and it passed 100% but 126.96.36.199 failed. The one major difference between these versions is 188.8.131.52 is using a different VSO Engine version. Other then that if people don’t want to call this a bug then call it a malfunction as i know what im talking about here. Also the other two people used the same source disc as mine and i know where you would go with this but my answer to it b4 you answer is if the other programs i used cloned it i doub’t it’s a disc problem. I scanned the disc but scanning commerical disc’s are not always going to give you correct results. However the results i got were there is no disc problem or errors. So now we get back to if i clone it with another program thats enough proof for me that DVDFab 184.108.40.206 should be able to do it also. Let me cut to the chase this way to be fair. I seen a movie released and we both know there are TWO major popular programs out there. I seen b4 one would copy the disc and the other would’nt and vise versa.