Error codes made easy! What are the causes amd solutions??

29 worked great til the upgrade. Sure appreciate any ideas.
Thanks!

I use the following free programs attached to my post #11 and it helped:

http://club.cdfreaks.com/showthread.php?t=193860

Also a good registry clean can help. 2.9xxx will not handle some of the newer protections.

Mack

Thanks! I just used ccleaner and see a vision of my past ways..
I will give this a try and then cdgone if needed.
thanks again (I am anxious to see if it can really be better than 29)

**update**
Bigmacnc, you put me on the right path there! Thanks!
After cleaning the registry which really improved speed (too many re-installs) I used your recommeded program. Although it did not solve the problem, I noticed my read drive (sony oem ddu1615) wasnt reading. So I used my RW drive to record to a temp file first. BINGO! success! It's my read drive!
Why I didnt look at that first was because the drive worked for 29 with no issues and operates otherwise.
Maybe I need to upgrade the firmware. Any ideas where I can get upgrades? As the sony website wont acknowledge the drive because it is OEM.
Thanks again for your advice!

I would almost bet it is a liteon.

Macl

$$'s on U


thx again
skwuch0

There are several threads on FW on CDFreaks main section.

Mack

Have you got your hands on "An American Haunting" yet? (R1)
Also, the new beta doesn't open, doesn't do anything when I try to open it. Was that a conflict with a virtual drive like Daemon?

Try the 3.0.2.5 finial version released in one of the first thread. I have never tried using a virtual drive, but have burnt from folders.

Nope, it was a conflict with anydvd or clonecd running in the background/taskbar.
You should end the tasks completely in order to run dvdfab properly

yep it was clonecd, I would have posted my finding, but didn't want to double post...couldn't edit. Haunting did fine on the new beta.

Trying to burn Talladega Nights and I keep getting the Error=400, what can I do to resolve this problem? Please try to simplify as simply as you can, im not as good with computers as all of you are, thanks!

That is a read error(400) and can be caused by many things including out dated firmware. Sony drives have a history of giving this error, I posted several days with a person who swore that his drive was good, but turned out when he finally tried another drive. There is not a simple answer, but when found the solution will be simple. One guy posted that simply cushioning his computer so it would not move when kids ran in the room. It only takes a small movement, if you could separate the track on a SL DVD like a spool of string it would circle the Indy Speedway(2 1/2 miles) 3 + times.

I backed up Talladega Nights but had a bad original the first try, but not sure this is a problem that is widely happening but it only has to be your copy. I used a LG D-ROM as source and BenQ 1625 to burn. I usually make the back up first and do not watch original if it plays without problems.

Also check surface for fingerprints and scratches as that can cause the 400 error. I'm cheap, so I buy previously viewed DVDs from rental agencies from time to time and many times I have to clean them or polish a scratch out so they will play right. The Talladega Nights was a new one so it was a bad press job.

Mack

Hi tiutanya,

We need the detail error 400 information, like 400(???), then we can know the problem exactly.

Best Regards,
Fengtao

I've got a newer version of DVDFab, 4.0.3.2 and this is what my log says:

21:47:25: Analyzing of DVD started
21:47:34: Analyzing of DVD completed successfully
21:47:34: Copy process started
21:48:22: Task_1 failed! Error=400(invalid AdaptionIdentifier)
21:48:23: Process failed!

I got this when i tried to copy a movie to my hard drive (main movie only), mounting it with daemon.

I've read in previous posts about firmware, but that can't be the problem with a virtual drive, or am I wrong?

/Hubsta

4032 is outdated the latest version is 4055

So you think that is the reason I get an error? I don't have the latest version?

try the new version and see if your problem is fixed always good to keep the software up-to-date
also why mounting it with daemon try it without doing this

I tried with the latest version of the program (4055) and it worked!
Didn't think it would make that big a difference.

Thanx alot for the help.