1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Is Firmware or Nero generating the message?

Discussion in 'Nero discussion' started by attar, Oct 16, 2005.

  1. attar

    attar Senior member

    Joined:
    Jun 17, 2005
    Messages:
    11,147
    Likes Received:
    41
    Trophy Points:
    128
    Does anyone know?

    Is the information on line 6 and line 15 being relayed from the 'firmware' on the drive and displayed by Nero or is it a strictly
    'Nero' affair or a mixture of both?

    Reason I ask is that this drive has never displayed disc information on line 15 (or equivalent) even though I have verified that all the media I have used is on the manufacturers list (displayed with each firmware issue).
    I have 'rolled back' the firmware to no avail.I presume that the info displayed on line 15 is a generic or fallback position for either the drive or Nero.

    P.S. I have never cared for this drive, but it was a gift, else it would have been heaved long since ;)


    12:18:46 PM #6 Text 0 File DlgWaitCD.cpp, Line 2483
    Recorder: AOPEN DUW1608/ARR, Media type: DVD-R
    Disc Manufacturer: TYG01 -
    Disc Application Code: 64, Disc Physical Code: 193



    12:18:47 PM #15 Text 0 File Cdrdrv.cpp, Line 8862
    ---- DVD Structure: Physical Format Information (00h) ----
    Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
    Book Type: DVD-R (2), Part Version: 2.0x (5), Extended Part Version: 0.0 (0)
    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: 26127F h
    End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
    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 ................
     
  2. alkohol

    alkohol Regular member

    Joined:
    Apr 6, 2005
    Messages:
    4,125
    Likes Received:
    0
    Trophy Points:
    46
    I'm lost at trying to understand what you're trying to say about firmware, but the above is an example of a successfullly burned log of mine. Below is the current "firmware" on mine -- that is, if you're trying to look for the right firmware. So, "BYX4" and "1051" are the current firmware for my burner and cd/dvd-rom drive.

    Recorder: <SONY DVD RW DRU-710A> Version: BYX4
    CD-ROM: <TOSHIBA ODD-DVD SD-M1802>Version:1051
     
  3. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    i think i get the gist. My old Sony drive showed this for virtually all my discs
    all i go by is this -
    - that shows firmware has detected the media correctly but this
    shows that the firmware is out of date.

    is that what you mean ?
     
  4. alkohol

    alkohol Regular member

    Joined:
    Apr 6, 2005
    Messages:
    4,125
    Likes Received:
    0
    Trophy Points:
    46
    I think I might get it after reading the questions 3 more times now. So do you mean that the "firmware" or "Nero" has anything to do (i.e. affiliate) with line #6 & #15? Yes... it is a combination of both "firmware" and "Nero". Without the latest firmware, Nero would just read the blank media as Media Type: DVD+R or DVD-R; the same thing apply to line #15 as well. If Nero is too old, then in some cases, it wouldn't show either line (sometimes not line 15). I may be wrong, so Creaky or someone with more knowlege on Nero correct me on this one.

    And Creaky is right, that is what I go by as well.
     
  5. attar

    attar Senior member

    Joined:
    Jun 17, 2005
    Messages:
    11,147
    Likes Received:
    41
    Trophy Points:
    128
    @alkohol
    @creaky



    Consensus says that on line #6,'firmware' should recognize the media, else a generic type is displayed, indicating a firmware bug?

    Contrariwise, at line #15 a normal message may be generic or verbose, depending on the drive, and not necessarily indicitive of a problem?


     
    Last edited: Oct 17, 2005
  6. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    @attar - now i'm definitely with you. you know what, i'd never once paid attention to the line numbers as you call them (ie i've never actually noticed the #6, #15 etc, i've always skimmed over those). !!!

    Anyway, for both questions, a resounding yes!. as to line #15, when i first started out, what i'd read suggested that if there were no values in with all those dots, that there was a problem. However i quickly found out that this wasn't the case.
     

Share This Page