NERO LOGS.......post errors and answers here

AfterDawn Addict

2. June 2005 @ 23:55

Link to this message

i am trying to put together a list of nero log errors,and there possible causes,and the possible solutions,
whether it me something simple,it doesnt matter

pls post any here

join me,and other members here,on the "unofficial" afterdawn live chat channel ->
http://www.adbuddies.org/

Moderator

3. June 2005 @ 04:03

Link to this message

cor, that would be one huge post, especially with all those nerovision/neroexpress type logs. It takes me long enough to grab a standard Nero log into notepad, pick thru it, and then reply to the poster.

I personally find it much easier to scan thru a logfile for something obvious, then google for it, and answer the post in question.

good luck
:)

Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 04:03

AfterDawn Addict

3. June 2005 @ 04:48

Link to this message

hehehe

i dont mean the whole log,just the parts that matter,
like the errors,and the options in which they were recified

things like this

Burn process failed at 8x (11,080 KB/s)

which is obvious

join me,and other members here,on the "unofficial" afterdawn live chat channel ->
http://www.adbuddies.org/

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 05:00

arniebear

AfterDawn Addict

3. June 2005 @ 05:01

Link to this message

That would be good idea, then it could be used for reference. Much easier than always having to look it up :~)

Moderator

3. June 2005 @ 05:04

Link to this message

Quote:
just the parts that matter

- i know, but you just know there's gonna be ppl who will post the biggest most insane logfiles here, in their entirety

again, good luck lol :)

AfterDawn Addict

3. June 2005 @ 05:04

Link to this message

hehehe, i dont want logs posted in here,just the segments and the answers

its just that i dont know a lot about nero logs,not enough to give definite answers

i think this means nero doesnt like the media

Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

join me,and other members here,on the "unofficial" afterdawn live chat channel ->
http://www.adbuddies.org/

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 05:06

Moderator

3. June 2005 @ 05:08

Link to this message

aha, not always. i get that on every single burn i make, there's another paragrpah that goes with it, but even then, that doesn't mean a media problem. I'll see if i can find an example...

Moderator

3. June 2005 @ 05:12

Link to this message

got one, this is an extract from one of my boring logs (boring as they always work i mean lol) -

Quote:
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

- i've seen that posted as a media problem a few times, but it's not, as all my burns say that, on Verb or TY media, everything up to date etc.

AfterDawn Addict

3. June 2005 @ 05:17

Link to this message

hmmm,maybe this is not such a good idea..!!!

hehehe

thought there was usually a bunch of numbers written in there

Quote:
Power calibration error

this does mean however,... change the media type,or update firmware

join me,and other members here,on the "unofficial" afterdawn live chat channel ->
http://www.adbuddies.org/

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 05:22

arniebear

AfterDawn Addict

3. June 2005 @ 05:22

Link to this message

Nero Logfile from Digital Digest

Quote:
Is the media you are using working with your burner?

quote:
--------------------------------------------------------------------------------
11:58:29 AM #18 Text 0 File Cdrdrv.cpp, Line 8315
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 0 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
--------------------------------------------------------------------------------

The problem with the above is that the field "Media Specific" is empty - the media codes on your disc is not covered by the burners firmware. They don't understand each other and the burner is trying to use a generic write strategy for the disc. In most cases it will not work out and you end up with a "power calibration error" or "illegal disc" or a similar error.

This error is generally not related to disc quality issues, but is simply a result of the drive not having the latest firmware in it that lists the particular disc brand.

The solution is to find another firmware that covers your brand of discs or to change to another brand of discs that are already covered in your firmware.

For a good burn it should look something like this: (forget about the numbers and characters - they are only valid for this example and you should have a completely different set of numbers and characters).

quote:
--------------------------------------------------------------------------------
04:14:32 #13 Text 0 File Cdrdrv.cpp, Line 8332
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD+RW (9), Part Version: 2
Disc Size: 120 mm, Maximum Rate: (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: re-writable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 26021F h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Disc Application Code: 0 / 0 h
Extended Information indicators: 0 h
Disc Manufacturer ID: RICOHJPN
Media type ID: W11
Product revision number: 1
Number of Physical format information bytes in use in ADIP up to byte 63: 57
Media Specific [16..63]:
00 00 00 52 49 43 4F 48 - 4A 50 4E 57 31 31 01 39 ...RICOHJPNW11.9
23 00 8A 86 68 02 26 00 - 8A 86 70 02 28 00 8A 86 #...h.&...p.(...
6A 02 28 22 12 10 E0 00 - F0 00 00 00 00 00 00 00 j.("............

AfterDawn Addict

3. June 2005 @ 05:25

Link to this message

thats what we need,plenty of those,and when we have enough,i will re-write. post them in a suitable thread

join me,and other members here,on the "unofficial" afterdawn live chat channel ->
http://www.adbuddies.org/

Moderator

3. June 2005 @ 05:29

Link to this message

i would normally agree with that description, but my burner has always done that, and is always up to date with firmware... hmmm.... more delving needed...

baabaa

AfterDawn Addict

3. June 2005 @ 07:44

Link to this message

Well personally, and I think creaky saw this.
I have reservations about Nero's tolerances for the power calibration error, I think they are very acute and can give results which aren't necessarily bad, but bad enough for Nero to reject them..............

...............PIO is no go, DMA all the way...............
Beware of the Pixies - they move in over night and turn your life upside down

arniebear

AfterDawn Addict

3. June 2005 @ 08:10

Link to this message

I am not sure where Digital Digest is getting this from because I went back in my history and all my burns are good and like creaky's this is what they look like

Moderator

3. June 2005 @ 08:12

Link to this message

a-ha!

i just got home, and remembered i still got my Nero history from the Bulkpaq era (shudders!). Anyway, gonna see what's in there.

Moderator

3. June 2005 @ 08:22

Link to this message

shudders wore off quickly as this wasn't a bulkpaq-era log. Anyway this was from my 6.6.0.0 logs -

Quote:
Recorder: SONY DVD RW DRU-700A, Media type: DVD-R
Disc Manufacturer: MCC 02 - RG20
Disc Application Code: 64, Disc Physical Code: 193

<extraneous crap snipped>

Quote:
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 0 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

I'm more inclined to think it's a media issue if that 1st column is missing and there's no other mention of media info for rest of log.

This is all just stuff i've picked up studying logfiles around here so i'd happily be proved wrong, but i think these standard logs are peasy to work out; it's those war-and-peace nerovision logs that are trickier to suss out i think

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 08:24

Trom

Member

3. June 2005 @ 12:20

Link to this message

I have asked about this before. I have an MSI K8N Neo mobo with Nvidia drivers installed. DMA is turned on in the Bios. Device manager also shows the transfer mode as UDMA2 for the drives. Other disk utilities also report DMA as on for the burner, all except Nero. Any ideas why.

Recorder: <PLEXTOR DVDR PX-708A> Version: 1.09 - HA 3 TA 0 - 6.6.0.12
Adapter driver: <> HA 3
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ?
CD-ROM: <PLEXTOR DVDR PX-708A >Version: 1.09 - HA 3 TA 0 - 6.6.0.12
Adapter driver: <> HA 3

=== Scsi-Device-Map ===
CdRomPeripheral: PLEXTOR DVDR PX-708A nvatabus Port 0 ID 0 DMA: Off
CdRomPeripheral: TOSHIBA DVD-ROM nvatabus Port 0 ID 1 DMA: Off
DiskPeripheral: ST340810A nvatabus Port 0 ID 0 DMA: Off
DiskPeripheral: WDC WD740GD-00FLA0 nvatabus Port 2 ID 0 DMA: Off

Moderator

3. June 2005 @ 12:22

Link to this message

DMA2 should only be for for dvd drives, hard drives shouls show as dma5

Trom

Member

3. June 2005 @ 12:31

Link to this message

Yes I know. The question really only relates to the Plextor burner as its the only drive Nero uses really. Device manager reports the ST(Seagate) transfer mode as Ultra DMA5 and for the WD Raptor as Serial ATA DMA both which are correct.

BTW this is a problem which seems to effect others that use Nero and Nvidia IDE drivers, not just my system.

This message has been edited since posting. Last time this message was edited on 3. June 2005 @ 12:35

Moderator

3. June 2005 @ 12:36

Link to this message

a-ha Nvidia. do a search at top of page for that, there's posts i've skim-read about conflicts somewhere in there

Trom

Member

3. June 2005 @ 12:42

Link to this message

Seems like were having a conversation here. Yes from my own investigation it would appear there is a conflict between Nvidia IDE drivers and Nero(nero not being the only software affected) but no one appears to know wherin the conflict lies. Everytime Nvidia or Nero release updated drivers I'm hoping for a resulution but to date it remains the same.