Distaster again will not burn see log please help

Discussion in 'Nero discussion' started by MARTY, Feb 25, 2006.

  1. MARTY

    MARTY Member

    Joined:
    Feb 22, 2006
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    11
    Tried again and used Verbatim DVD-R discs , tried in simulation mode and failed twice see log, any help please im going mad !!

    Windows XP 5.1
    IA32
    WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 17/07/2002 09:20:56
    ahead WinASPI: File 'C:\Program Files\Ahead\nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 26/10/2004 16:35:32
    Nero Version: 6.6.0.16
    Internal Version: 6, 6, 0, 16b
    (Nero Express)
    Recorder: <HL-DT-ST DVDRAM GSA-4167B>Version: DL13 - HA 2 TA 0 - 6.6.0.16
    Adapter driver: <> HA 2
    Drive buffer : 2048kB
    Bus Type : default (0) -> ATAPI, detected: ?
    CD-ROM: <TSSTcorp CDRWDVD TS-H492C>Version: DE02 - HA 1 TA 0 - 6.6.0.16
    Adapter driver: <atapi> HA 1

    === Scsi-Device-Map ===
    DiskPeripheral : HDS728080PLAT20 atapi Port 0 ID 0 DMA: On
    CdRomPeripheral : TSSTcorp CDRWDVD TS-H492C atapi Port 1 ID 0 DMA: On

    === CDRom-Device-Map ===
    TSSTcorp CDRWDVD TS-H492C D: CDRom0
    HL-DT-ST DVDRAM GSA-4167B E: CDRom1
    =======================

    AutoRun : 1
    Excluded drive IDs:
    WriteBufferSize: 74448896 (0) Byte
    ShowDrvBufStat : 0
    BUFE : 0
    Physical memory : 509MB (522224kB)
    Free physical memory: 142MB (145844kB)
    Memory in use : 72 %
    Uncached PFiles: 0x0
    Use Inquiry : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    25.2.2006
    DVD-Copy on the fly
    10:47:23 #1 Text 0 File Reader.cpp, Line 127
    Reader running

    10:47:23 #2 Text 0 File Writer.cpp, Line 122
    Writer HL-DT-ST DVDRAM GSA-4167B running

    10:47:23 #3 Text 0 File DVDCopy.cpp, Line 293
    DVD Track-Information from source disc:
    Media Type: DVD-ROM
    S01 T01 Con 0x14 Start 0 Len 2035952 (gap 0) Blank 0 Res 0 Dmg 0 Open Trk 0 Mode TRM_DATA_MODE1 (0)

    10:47:23 #4 Text 0 File DVDCopy.cpp, Line 406
    Max -1 tracks of 1 allowed to copy
    1: 0 - 2035952 = 2035952, TRM_DATA_MODE1, block size 2048, read opt 0 (no read options)

    10:47:23 #5 Text 0 File Burncd.cpp, Line 3233
    Turn on Disc-At-Once, using DVD media

    10:47:23 #6 Text 0 File DlgWaitCD.cpp, Line 270
    Last possible write address on media: 2298495 (510:46.45, 4489MB)
    Last address to be written: 2035951 (452:26.01, 3976MB)

    10:47:23 #7 Text 0 File DlgWaitCD.cpp, Line 282
    Write in overburning mode: NO (enabled: CD)

    10:47:23 #8 Text 0 File DlgWaitCD.cpp, Line 2483
    Recorder: HL-DT-ST DVDRAM GSA-4167B, Media type: DVD-R
    Disc Manufacturer: TYG02 -
    Disc Application Code: 64, Disc Physical Code: 193

    10:47:23 #9 Text 0 File DlgWaitCD.cpp, Line 448
    >>> Protocol of DlgWaitCD activities: <<<
    =========================================

    10:47:23 #10 Text 0 File ThreadedTransferInterface.cpp, Line 838
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 (1 - Data (mode 1))
    2 indices, index0 (150) not provided
    original disc pos #0 + 2035952 (2035952) = #2035952/452:26.2
    not relocatable, disc pos for caching/writing not required/not required, no patch infos
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2035952 blocks [HL-DT-ST DVDRAM GSA-4167B]
    --------------------------------------------------------------

    10:47:23 #11 Text 0 File ThreadedTransferInterface.cpp, Line 1051
    Prepare recorder [HL-DT-ST DVDRAM GSA-4167B] for write in CUE-sheet-DAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x40; Session Closed, disc fixated
    Tracks 1 to 1:
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4169629696, ISRC ""
    DAO layout:
    ===========
    __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
    0 | lead-in | 0 | 0x41 | 0x00
    0 | 1 | 0 | 0x41 | 0x00
    0 | 1 | 1 | 0x41 | 0x00
    2035952 | lead-out | 1 | 0x41 | 0x00

    10:47:23 #12 Phase 32 File dlgbrnst.cpp, Line 1832
    Simulation started at 4x (5,540 KB/s)

    10:47:24 #13 Text 0 File ThreadedTransferInterface.cpp, Line 2654
    Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0

    10:47:24 #14 Text 0 File DVDR.cpp, Line 2379
    Recording mode: Sequential Recording Mode

    10:47:24 #15 Text 0 File Mmc.cpp, Line 21708
    Set BUFE: Buffer underrun protection -> ON

    10:47:24 #16 Text 0 File DVDR.cpp, Line 2534
    Start write address at LBA 0
    DVD high compatibility mode: Yes

    10:47:24 #17 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: 2FE10 h
    Start sector number of the next Border-In: 2FFA0 h
    Media Specific [16..63]:
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
    00 02 FE 10 00 02 FF A0 - 00 00 00 00 00 00 00 00 ................
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

    10:47:33 #18 SCSI -500 File Cdrdrv.cpp, Line 1434
    SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x0B420000
    Status: 0x02 (0x03, SCSI_ABORTED)
    HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
    TA-Status 0x00 (0x00, OK)
    Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
    Sense Code: 0x26
    Sense Qual: 0x02
    CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
    Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
    0x00 0x00 0x00 0x00 0x26 0x02

    10:47:33 #19 SCSI -1114 File Cdrdrv.cpp, Line 1434
    SCSI Exec, HA 2, TA 0, LUN 0, buffer 0x0B731600
    Status: 0x04 (0x01, SCSI_ERR)
    HA-Status 0x00 (0x00, OK)
    TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
    Sense Key: 0x06 (KEY_UNIT_ATTENTION)
    Sense Code: 0x29
    Sense Qual: 0x00
    CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
    Sense Data: 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x10
    0x00 0x00 0x00 0x0C 0x29 0x00

    10:47:33 #20 CDR -1114 File Writer.cpp, Line 311
    Reset occurred

    10:47:33 #21 Text 0 File ThreadedTransfer.cpp, Line 228
    all writers idle, stopping conversion

    10:47:33 #22 Text 0 File ThreadedTransfer.cpp, Line 222
    conversion idle, stopping reader

    10:47:33 #23 Text 0 File DVDR.cpp, Line 2774
    EndDAO: Last written address was -1

    10:47:33 #24 Phase 34 File dlgbrnst.cpp, Line 1832
    Simulation failed at 4x (5,540 KB/s)


    Existing drivers:
    File 'Drivers\ADPU160M.SYS': Ver=v3.60a (Lab01_N(johnstra).010529-2218), size=101888 bytes, created 17/08/2001 14:07:32
    File 'Drivers\ASPI32.SYS': Ver=4.71 (0002), size=16877 bytes, created 17/07/2002 08:53:02
    File 'Drivers\PXHELP20.SYS': Ver=2.03.32a, size=20640 bytes, created 25/04/2005 02:03:00 (Prassi/Veritas driver for win 2K)
    File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 03/08/2004 22:59:44 (Adapter driver for src)

    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
     
  2. gwendolin

    gwendolin Senior member

    Joined:
    Jun 29, 2005
    Messages:
    7,447
    Likes Received:
    0
    Trophy Points:
    116
    Your Nero is a few versions behind, update here

    http://httpdl2.usw.nero.com/Nero-6.6.0.18.exe
    http://httpdl1.usw.nero.com/Nero-6.6.0.18.exe

    Although it shouldn't be too much of a problem, try to free up some memory. Dont multitask and shut down all unnecessary progs including spyware.

    I cant see a lot else than that, update Nero and see how it goes.
     
    Last edited: Feb 25, 2006
  3. johnl123

    johnl123 Regular member

    Joined:
    Nov 3, 2005
    Messages:
    2,359
    Likes Received:
    0
    Trophy Points:
    46
    @MARTY and gwendolin,

    When looking/examining nero logs, sometimes one needs to look a little closer to find the culprit, let me explain:

    HERE: The culprit is starring right at you, all you have to do is look
    *********************************************************************
    10:47:24 #17 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: 2FE10 h
    Start sector number of the next Border-In: 2FFA0 h
    Media Specific [16..63]:
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
    00 02 FE 10 00 02 FF A0 - 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, I see that you're using good quality media, but that simply doesn't matter here.

    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". I your case MARTY, your burner does have the lastest firmware but is simply having a problem with recogizing it correctly, I suggest you go the the manufacturer's website and see if they provide a media compatibility list and stick to what's on that list.

    Just incase you want to know what it should look like for a good burn (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)....

    ********************************************************************
    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.("............
    *********************************************************************

    Marty, follw the generic info as well like...update nero, freeup some rescources and maby get some more RAM.

    Good Luck...John.

     
    Last edited: Feb 25, 2006
  4. gwendolin

    gwendolin Senior member

    Joined:
    Jun 29, 2005
    Messages:
    7,447
    Likes Received:
    0
    Trophy Points:
    116
    @johnl123, you look at logs YOUR way and I'll look at them MY way, please dont tell me how to "suck eggs'

    You appear to take pleasure in looking for things I may have missed, I DONT claim to be an Expert like you so I will continue on as I normally do.........offering [bold]GENERIC[/bold] replies
     
    Last edited: Feb 25, 2006
  5. johnl123

    johnl123 Regular member

    Joined:
    Nov 3, 2005
    Messages:
    2,359
    Likes Received:
    0
    Trophy Points:
    46
    @gwendolin
    I was in now way trying to offend you or any one, if that's how it came across I oppologize. I was simply stating that in reading so may logs we all (myself included) at some point will quote generics without really looking first.

    Again, I oppologize.
     
  6. gwendolin

    gwendolin Senior member

    Joined:
    Jun 29, 2005
    Messages:
    7,447
    Likes Received:
    0
    Trophy Points:
    116
    [bold]HERE: The culprit is starring right at you, all you have to do is look [/bold]

    This to me was uncalled for, end of story.
     
  7. johnl123

    johnl123 Regular member

    Joined:
    Nov 3, 2005
    Messages:
    2,359
    Likes Received:
    0
    Trophy Points:
    46
    Starring at you, didn't mean YOU.
    I meant it in a GENERIC sense.

    Have you ever thought about professional help?
     
  8. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    @johnl123 - now now.

    as to the 'media specific' field
    - that can indeed be empty, nothing wrong with that...

    ..most or all my logs have always had that same 'blank' media specific info in that section of log. what's important is the firmware being able to detect/understand the discs ie
    as opposed to
    - where the second quote shows firmware that can't recognise the discs...
     
    Last edited: Feb 25, 2006
  9. johnl123

    johnl123 Regular member

    Joined:
    Nov 3, 2005
    Messages:
    2,359
    Likes Received:
    0
    Trophy Points:
    46
    @creaky
    I really wasn't trying to blame anyone for doing anything wrong, I guess I should of worded it differently (you just never know).

    Yes, I agree that what's important is the firmware being able to detect/understand the discs. All the reading and reserach I've done states that the info in the media specific field can also be used as an indicator the disc is not covered by the burners firmware and so the burner may be trying to use a generic write strategy for the disc, which may or may not be successful, thus the inconsistant burns as a result.

    It's just another indicator that can be used to hopefully solve the problem, that's all I was trying to say.
     
  10. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    yer, back when i started out i read conflicting info re the media specific field, it's to be be taken with a pinch of salt is all.
     
  11. MARTY

    MARTY Member

    Joined:
    Feb 22, 2006
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    11
    Well here is the weird thing, i did a DVD Shrink 3.2 encode to hard drive file, then opened up Nero and burned file to disc and it works on both the Verbatim and the Datawrite.

    So im confused its not the burner or the media but maybe the auto nero side of things ??
     
    Last edited: Feb 25, 2006
  12. Bigfatboy

    Bigfatboy Regular member

    Joined:
    Feb 7, 2005
    Messages:
    351
    Likes Received:
    0
    Trophy Points:
    26
    25.2.2006
    DVD-Copy on the fly
    10:47:23 #1 Text 0 File Reader.cpp, Line 127
    Reader running

    copy on the fly is not recommended, rip to the hard drive first then burn

    peace
     
  13. MARTY

    MARTY Member

    Joined:
    Feb 22, 2006
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    11
    So am i right in thinking that to use Nero i should encode the movie to hard drive file first (like i did ) and then burn to disc by opening Nero 6 and then choosing files to burn and then manual burn (which i did) this method works but surely DVD Shrink 3.2 should work with Nero 6 or is there an issue with my Nero 6 version and Shrink 3.2 ??

    Anyway at least it burns but doing it in auto would be better or is that a no no, please help if you can.

    Thanks Mart
     
  14. whompus

    whompus Active member

    Joined:
    Dec 2, 2002
    Messages:
    1,346
    Likes Received:
    0
    Trophy Points:
    66
    Last edited: Feb 25, 2006
  15. MARTY

    MARTY Member

    Joined:
    Feb 22, 2006
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    11
    Sorry if i confused the issue my first original log was not done as a manual encode, but it was set to encode then burn automatically with Nero and then failed.( DVD Shrink had Nero ticked for burn )

    I have now done 3 good encodes and burn if i save it first to hard drive then open up nero and import files and then burn, works a treat.

    So my question is,is it my version of Nero and will the newer version 6 cure this fault and allow it to work in auto from DVD Shrink ??
     
    Last edited: Feb 25, 2006
  16. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    Upgrade to the version that Whompus gave you and you should be fine...the current version on the Nero site is6.6.1.4 and has yet to have the wrinkles ironed out of it yet and doesn't support DVD Shrink burning options.
     
  17. MARTY

    MARTY Member

    Joined:
    Feb 22, 2006
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    11
    Well ok i removed my Nero 6 and did a clean up. Then i got the version 6 as per the link on here.

    Tried to use DVD Shrink after ticking the Nero box it was worse. Firstly it didnt open up Nero and when i looked for the files they were not recognized by Nero, VOB files etc so i re-installed the version i started with and tried again.

    This time again it burns fine if i do it to hard drive and import files and then burn, now done 4 burns perfect everyone.

    So im baffled to 1. the advice didnt seem to help but made it worse and 2.does it matter that Nero isnt booted up automatically from DVD Shrink ??

    Any thoughts ??
     
    Last edited: Feb 25, 2006
  18. gwendolin

    gwendolin Senior member

    Joined:
    Jun 29, 2005
    Messages:
    7,447
    Likes Received:
    0
    Trophy Points:
    116
    @Marty, can you please explain, in plain english what exactly you are doing. Are you backing up a DVD, burning AVI or MPEG files to DVD or something else.

    You keep mentioning DVDShrink, have you tried Nero Recode?
    If you have NeroRecode then you DONT need DVDShrink.

    You were advised right from the start to update Nero but didnt and had to be told a number of times, if you want help then tell us what you're trying to do!!
     
  19. whompus

    whompus Active member

    Joined:
    Dec 2, 2002
    Messages:
    1,346
    Likes Received:
    0
    Trophy Points:
    66
    I answered your new problem in the other thread you started. With it being short it might get closed pretty fast. You should keep to the same thread till finished. None the less the answer for you is in the other thread.
     
  20. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    @MARTY - i've closed some of your other threads. you need to confine the problem to one thread until resolution, not open a new thread for each part of the problem. plus if you keep the problem in one place it can get fixed all the sooner.

    edit- i think you're saying that you have no problems when you burn manually via Nero but only have problems when you have Shrink set to auto-burn. now this isn't a solution but logic would dictate to keep burning manually as that works. i know a lot of ppl use Shrink to call Nero and that it does work but i myself prefer to do things manually
     
    Last edited: Feb 26, 2006

Share This Page