OK, and thanks for that info.
Unfortuntely, error messages can be generated by three sources, when authoring to DVD/BD:
- They can come from the OS
- They can come from the Sonic AuthorCore modules, licensed to Adobe by Sonic
- They can come from PrE itself
In the case of the OS and PrE, there is some commanality, though error messages are still not 100% intuitive, and seldom as helpful, as I feel they should be. With the Sonic AuthorCore modules, they are usually even more cryptic. One of the biggest problems, if the problem was noted by the OS, or the Sonic AuthorCore modules, is that the report to PrE will often not be complete. PrE gets a message that "something" has gone wrong, and then it is forced to "guess" about what went wrong. Sometimes, it guesses correctly, but sometimes just misses the cause, because it did not get enough info from the OS, or the Sonic AuthorCore module.
This ARTICLE, while not specific to your error code, covers some of the potential problems, when authoring. Part of this also addresses some potential problems, with Burning to Disc from PrE - to answer your last question to Steve. In many (but not all) cases, when some other software loads at bootup, and "hooks" the burner, reporting to the OS, that it is really a removable HDD, but other software can cause other issues, and the error report can be different.
This is the same, when the firmware of the multi-drive/burner is not up to date, the OS might not be seeing the burner properly, or when there is a problem with the blank media inserted - it might not be blank, it might be bad, or perhaps is of the wrong type, say a BD disc inserted into a DVD-only burner. These are often seen by the user as a SenseCode error, but not always.
It would be great if all error messages, whether generated by the OS, the Sonic AuthorCore modules or PrE itself, were filled with the exact problem, and its cause, in details that the user could actually understand, and act upon. That is not likely to happen, but we can wish.
Let's step back just a bit.
- Does your OS show the multi-drive/burner as being connected and operating properly? This can usually be checked in Device Manager (PC), or some other area of the OS.
- Is the firmware of your multi-drive/burner up to date? Check with the mfgr's. Web site for that model burner.
- How much defragmented free-space do you have on the HDD, where you have located your Project and Scratch Disks?
- How much defragmented free-space do you have on your C:\?
- What brand/type of blank media are you attempting to burn to?
Though we might never determine the exact meaning of that error message, if we can find what is causing the error, that will be good enough.
Good luck,
Hunt
