Feelin' stupid... DVD shrink 3.2 to Nero Burning Rom, Help!

@jman07
When i saw your first post i thought you couldn't get an original movie to copy. Then i saw the next post worded slightly differently and that one cleared things up a bit.
The best way to get the most compatibility with stand alones is to use DVD+R media and booktype it to DVD-ROM. Even DVD+R DL can be booktyped, but not DVD-R media. With that said, sometimes you have to try different formats and brands of media to find what YOUR stand alones like. I have a panasonic dvd recorder and it is supposed to like DVD-R the best. Yet, i sometimes get illegal disc error, or un-supported format error when trying a DVD-R. When that happens, i take the -R and put it in my PC and burn that movie to a DVD+R booktyped to DVD-ROM and it works everytime.
Now, sometimes you can run in to a bad pressing of an original DVD, but that kind of error usually gives you CRC errors that dont go away with cleaning the disc. The only cure for a bad pressing is to exchange the bad disc for a new one, and that usually fixes it. Twist of fate might give you 2 bad presses in a row, but not very likely. Nero CD-DVD speed will tell you if your backups are booktyped to DVD-ROM. Just check it out under the Disc info tab.
Here is what Sony +R booktyped to DVD-ROM looks like:

The disc is finalized in this example. Making your disc "multi-session" will leave the disc open for more data writes, and until disc is finalized, it will not read in stand alones either.

 

@Red34
Is that the whole log there, or did you edit something out of the middle? It doesnt look like a complete log, and it cut off right when it was going to tell me something.

usually we see a bunch of stuff before the error is reported, and sometimes that stuff can divulge the real problem.
I could hazzard a guess as to what TRF is, but id only be guessing.
From what parts of the log i can see, is one or both of those drives external? If both are internal, then you need to check your system aspi files. If one or both of them are external, you could still check, but it might not be a problem. Nero info tool will let you know if System ASPI is bad.
Also whenever i try to do a disc to disc burn and get a failed burn, i extract the movie to HD using DVD Decrypter, and burn from HD to disc, and that seems to have a better chance of success. And it should be a DVD5 to DVD5 or DVD9 to DVD9 for straight copy, but no mixing up disc capacities, like trying to copy a DVD9 to DVD5 without shrinking will give you a failed burn..

 

@ MaxBurn

People have reported the same TRF error when trying to use the new Nero version 6.6.1.4 in conjunction with DVD Shrink(it will just not start automatically anymore)
Do you think could be the same bug?

http://forums.afterdawn.com/thread_view.cfm/301020

 

Thanks for responding, i only deleted the serial # as i noticed u sugested another person to do so,im gonna run it again and post the error message making sure its all there, maybe i did delete something accidently, again thx.

 

Oh, and yes 1 is external the other internal,nero info. shows aspi drivers are installed and working, v4.60(1021).I dont have a problem burning from the HD, but thats the reason i bought the external dvd so i can just burn straight to other dvd drive.

 

Oh man, thanks allot MaxBurn,i installed the earlier version 6.6.0.18,and that took care of my problem,u don't know how happy that makes me; the only thing is that the movie still gets writen to the hard drive, is there any way i can backup my copy protected movies without them having to be writen to my HD first?. Thanks.

 

All programs will temporarily write the image to the HDD, some will delete them automatically so you never know they were there, and others will leave them for you to manually delete them. That is why you need at least 15g preferably 20g free on your HDD for backup work. The only way you will not put it on your HDD is if you do a direct disk to disk "on the fly" backup. You can only do this if your image is below 4.3g in size, i.e. no compression needed.

 

Glad it works for you now Red34. My buddy arniebear was here too, and there were probably lots of others out there waiting to help if we stumbled. The AD gang will take care of you.
Whenever i try a disc to disc copy using nero, i usually get a coaster. Dont know why, but i know what fixes it every time. Writing to HD first either as a temp file in some ripping program, or directly with DVD Decrypter. I know thats not what you wanted to hear, but thats the way it goes for me. Ive had great success with cloneDVD2, but it also writes temp files to HD. Ive read/heard that AnyDVD will let you pull directly from a movie disc and burn to a blank disc by using windows explorer, but ive never used that method, and the all the files would have to be able to fit on a DVD5 without shrinking, not many are that small anymore.

 

@cyprusrom,
Sure sounds like it. Imagine Nero updates version 7 and 6 at the same time and BOTH have bugs.. Now im not into conspiracy theories too much, but I am not updating my Version 7, and i still have a few versions of 6, the .exe install files just in case 7 goes flakey again. I never heard back if version 7 bugs got fixed, and they were bad enough for me to hold off on updating. I suggest you always keep the older version of nero somewhere safe when you update. They seem to come in handy about a week after you update and notice problems where you had none before..

 

@MaxBurn
You're right, but let's not totally rule out the conspiracy theory:~)!.
I found that many people have not kept the older versions of nero 7/6. Not a good choice! nero is a great program, with so many applications, options. But is far from perfect. And probably the new versions bring updates that 75% of people don't even use them.

 

I'm sorry for the delayed responce,i just wanted to thank MaxBurn and arniebear for your help,i appreciat it.

 

Your welcome Red34. Seeing ppl like you have success is what makes me come back to AD to help. Nero is making it difficult for us to help you ppl. They keep putting out updates that cause weird problems, until we figure out it is the update that is causing the problem, and not the error the nero log points to. It doesnt want to point the finger at itself, so it found a way to blame something else. Thats the way i see it. Id like to see nero say this in a log