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

What is up w/ my burner these days?

Discussion in 'Nero discussion' started by happydayz, Oct 3, 2005.

  1. happydayz

    happydayz Member

    Joined:
    Oct 3, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    11
    Can anyone tell me what's going on w/ my CD-Burner and Nero these days? I can't burn anything. I can still read my old CDRs and run software CDs, but that's it!

    Is it that my CD-Burner is too old and that I should go purchase another one?

    Also, when I tried burning a CDR the other day, the error message in the log was different; it had to do w/ COULD NOT PERFORM ENDTRACK and something w/ POWER CALIBERATION error.

    In the mean time, I have been having to use my USB Flash Drive to transfer files from my computer to my laptop and then burn it on from there--quite tedious especially considering that it's only a 256MB FLASH DRIVE.

    Any help will be greatly appreciated. However, this might be a good excuse for me to buy a whole new system so that I can play Age of Empires 3 when it comes out-hehehe.


    Windows XP 5.1
    IA32
    WinAspi: -
    ahead WinASPI: File 'C:\Program Files\ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 10/26/2004 6:35:34 PM
    Nero Version: 6.6.0.16
    Internal Version: 6, 6, 0, 16b

    Recorder: <MITSUMI CR-48X9TE> Version: 1.0C - HA 0 TA 1 - 6.6.0.16
    Adapter driver: <atapi> HA 0
    Drive buffer : 2048kB
    Bus Type : default (0) -> ATAPI, detected: ATAPI
    CD-ROM: <LITEON DVD-ROM LTD163 >Version: GH4W - HA 1 TA 0 - 6.6.0.16
    Adapter driver: <atapi> HA 1

    === Scsi-Device-Map ===
    DiskPeripheral : Maxtor 4W060H4 atapi Port 0 ID 0 DMA: On
    CdRomPeripheral : MITSUMI CR-48X9TE atapi Port 0 ID 1 DMA: On
    CdRomPeripheral : LITEON DVD-ROM LTD163 atapi Port 1 ID 0 DMA: On

    === CDRom-Device-Map ===
    MITSUMI CR-48X9TE E: CDRom0
    LITEON DVD-ROM LTD163 F: CDRom1
    =======================

    AutoRun : 1
    Excluded drive IDs:
    WriteBufferSize: 40894464 (0) Byte
    ShowDrvBufStat : 0
    BUFE : 0
    Physical memory : 255MB (261616kB)
    Free physical memory: 90MB (92980kB)
    Memory in use : 64 %
    Uncached PFiles: 0x0
    Use Inquiry : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    3.10.2005
    CD-ROM (ISO)
    7:20:35 PM #1 Text 0 File Isodoc.cpp, Line 6356
    Iso document burn settings
    ------------------------------------------
    Determine maximum speed : FALSE
    Simulate : FALSE
    Write : TRUE
    Finalize CD : TRUE
    Multisession : FALSE
    Burning mode : TAO
    Mode : 1
    ISO Level : 1 (Max. of 11 = 8 + 3 char)
    Character set : ISO 9660
    Joliet : TRUE
    Allow pathdepth more than 8 directories : TRUE
    Allow more than 255 characters in path : TRUE
    Write ISO9660 ;1 file extensions : TRUE

    7:20:35 PM #2 Text 0 File Burncd.cpp, Line 2948
    MITSUMI CR-48X9TE
    ExacLink activated

    7:20:35 PM #3 Text 0 File Reader.cpp, Line 127
    Reader running

    7:20:35 PM #4 Text 0 File Writer.cpp, Line 122
    Writer MITSUMI CR-48X9TE running

    7:20:35 PM #5 ISO9660GEN -11 File geniso.cpp, Line 3309
    First writeable address = 0 (0x00000000)

    7:20:35 PM #6 Text 0 File Burncd.cpp, Line 3233
    Turn on Track-At-Once, using CD-R/RW media

    7:20:50 PM #7 Text 0 File DlgWaitCD.cpp, Line 270
    Last possible write address on media: 359845 ( 79:59.70)
    Last address to be written: 339399 ( 75:27.24)

    7:20:50 PM #8 Text 0 File DlgWaitCD.cpp, Line 282
    Write in overburning mode: NO (enabled: CD)

    7:20:50 PM #9 Text 0 File DlgWaitCD.cpp, Line 2483
    Recorder: MITSUMI CR-48X9TE;
    CDR code: 00 97 32 19; OSJ entry from: Prodisc Technology Inc.
    ATIP Data:
    Special Info [hex] 1: E0 00 B0, 2: 61 20 13 (LI 97:32.19), 3: 4F 3B 47 (LO 79:59.71)
    Additional Info [hex] 1: 00 00 80 (invalid), 2: 00 00 00 (invalid), 3: 00 00 00 (invalid)

    7:20:50 PM #10 Text 0 File DlgWaitCD.cpp, Line 448
    >>> Protocol of DlgWaitCD activities: <<<
    =========================================
    Insert the disc to write to.
    (Medium in drive: Unknown. Medium required by compilation: CD-R/RW.)

    7:20:50 PM #11 Text 0 File ThreadedTransferInterface.cpp, Line 838
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 ()
    2 indices, index0 (150) not provided
    original disc pos #0 + 339400 (339400) = #339400/75:25.25
    relocatable, disc pos for caching/writing not required/ required, no patch infos
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 339398 blocks [MITSUMI CR-48X9TE]
    --------------------------------------------------------------

    7:20:50 PM #12 Text 0 File ThreadedTransferInterface.cpp, Line 1051
    Prepare recorder [MITSUMI CR-48X9TE] for write in TAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x00; Session Closed, disc fixated
    Tracks 1 to 1:
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 307200 695398400, ISRC ""
    DAO layout:
    ===========
    __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
    -150 | lead-in | 0 | 0x41 | 0x00
    -150 | 1 | 0 | 0x41 | 0x00
    0 | 1 | 1 | 0x41 | 0x00
    339400 | lead-out | 1 | 0x41 | 0x00

    7:20:50 PM #13 Text 0 File ThreadedTransferInterface.cpp, Line 1119
    Removed 2 run-out blocks from end of track 1. Length: 339400 -> 339398.

    7:20:50 PM #14 Phase 24 File dlgbrnst.cpp, Line 1832
    Unknown BurnPhase

    7:20:50 PM #15 Text 0 File Burncd.cpp, Line 4120
    Cache writing successful.

    7:20:50 PM #16 Phase 25 File dlgbrnst.cpp, Line 1832
    Unknown BurnPhase

    7:20:50 PM #17 Phase 36 File dlgbrnst.cpp, Line 1832
    Unknown BurnPhase

    7:20:51 PM #18 Text 0 File ThreadedTransferInterface.cpp, Line 2654
    Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

    7:20:51 PM #19 Text 0 File Mmc.cpp, Line 21708
    Set BUFE: ExacLink -> ON

    7:20:58 PM #20 SCSI -1106 File Cdrdrv.cpp, Line 1434
    SCSI Exec, HA 0, TA 1, LUN 0, buffer 0x04650000
    Status: 0x04 (0x01, SCSI_ERR)
    HA-Status 0x00 (0x00, OK)
    TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
    Sense Key: 0x03 (KEY_MEDIUM_ERROR)
    Sense Code: 0x73
    Sense Qual: 0x03
    CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
    Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
    0x00 0x00 0x00 0x00 0x73 0x03

    7:20:58 PM #21 CDR -1106 File Writer.cpp, Line 311
    Unknown CDR error

    7:20:58 PM #22 Text 0 File ThreadedTransfer.cpp, Line 228
    all writers idle, stopping conversion

    7:20:58 PM #23 Text 0 File ThreadedTransfer.cpp, Line 222
    conversion idle, stopping reader

    7:20:58 PM #24 CDR -201 File WriterStatus.cpp, Line 200
    Unknown CDR error
    MITSUMI CR-48X9TE\H0 T1

    7:20:58 PM #25 TRANSFER -18 File WriterStatus.cpp, Line 200
    -18 Unknown error

    7:20:58 PM #26 Text 0 File Mmc.cpp, Line 16352
    <MITSUMI CR-48X9TE > start Close Session

    7:20:58 PM #27 Phase 38 File dlgbrnst.cpp, Line 1832
    Unknown BurnPhase


    Existing drivers:
    File 'Drivers\CDR4_2K.SYS': Ver=2.5 (099), size=53072 bytes, created 1/6/2004 9:07:38 PM
    File 'Drivers\CDRALW2K.SYS': Ver=1.00 (1039), size=22201 bytes, created 1/6/2004 9:07:38 PM
    File 'Drivers\PXHELP20.SYS': Ver=2.03.28a, size=20640 bytes, created 3/11/2005 5:28:10 PM (Prassi/Veritas driver for win 2K)
    File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 8/4/2004 12:59:42 AM (Adapter driver for rec)

    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
     
    happydayz, Oct 3, 2005
    #1
  2. movies27

    movies27 Regular member

    Joined:
    Feb 11, 2005
    Messages:
    396
    Likes Received:
    0
    Trophy Points:
    26
    power caliberation error usually in my opinion means something is wrong with the burner go get a new 1...or when i had that error once i did a firmware up grade on my "dvd burner" and the error message didnt happen anymore.
     
    movies27, Oct 3, 2005
    #2
  3. cougar_ii

    cougar_ii Regular member

    Joined:
    Aug 19, 2004
    Messages:
    1,506
    Likes Received:
    0
    Trophy Points:
    46
    Hi there,

    I could not find a firmware upgrade for your burner, so you must have the latest one, [bold]that's good ![/bold]

    Prodisc makes cheap DVD Media, so I wonder if their CD-R are as cheap !

    I would try a different brand of media.

    I never burn over 24x for CD-R regarless of the media !

     
    cougar_ii, Oct 7, 2005
    #3
  4. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    in addition to the other guys' replies -





    - make sure to close down more programs before any burns

    - if your firmware's up to date, try better quality CD's

    - remove Roxio, it doesn't play well Zapper (you can google for it)



    also, quote from "http://www.nero.com/en/FAQs_Error_Messages.html#9 - "

    "9. I get a 'Power calibration error' or 'Calibration area (almost) full' error message. Why?

    Power Calibration is controlled by the recorder.

    Before any write operation, all recorders must do a 15 step power test to determine the optimum power for writing to the CD; this is called "Optimum Power Calibration"(OPC). During the write, it continues to do this test to get the best write throughout the whole CD; this is called "Running Optimum Power Calibration" (ROPC).
    This whole process is controlled by the recorder, though initiated by programs such as Nero. There is an area on the inner part of the CD for the test and test data info to be stored. You can use this area up to 999 times.

    If you receive the "Power calibration error" or "Power calibration area is (amost) full" error message, the cause will be either poor media, poor power, or a defective recorder.

    Please try the following solutions:

    Update the firmware of your recorder. Please check the manufacturer's website for the latest version.
    [bold]Try another brand of CD-R or CD-RW media.[/bold]
    Try different power connectors, and for recorders, do not share power with other devices. It needs its own power connector. If the error occurs with an external recorder, the power source in the chassis could be the cause. As a test, try to take the recorder out of the external chassis and connect it internal.
    Try different configurations, such as taking the CD-ROM to the primary IDE bus as slave and have only the recorder connected to the secondary IDE bus as master.
    Send the recorder in for service."
     
    Last edited: Oct 7, 2005
    creaky, Oct 7, 2005
    #4
  5. happydayz

    happydayz Member

    Joined:
    Oct 3, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    11
    Wow! Thanks to everyone who has contributed in response to this post: I really am greatful.

    I plan on purchasing one of those CD burner cleaning kits, a decent one, and hopefully that will work. Other than that, I have basically given up on using that burner ever again. It's probably better for the best. Learning to delete old files instead of saving them will do me good--sentiment alone is no reason to keep things.

    Take care,
    Ly
     
    happydayz, Oct 24, 2005
    #5
  6. cougar_ii

    cougar_ii Regular member

    Joined:
    Aug 19, 2004
    Messages:
    1,506
    Likes Received:
    0
    Trophy Points:
    46
    Hello again happydayz,

    I'm not sure if you have more than 1 PC at home, but before putting a drive nn the garbage :) I always test it in an other PC.

    If I'm starting to get the same weird problems, then I know it's the drive, not software conflicts etc...

    My 2 cents...
     
    cougar_ii, Oct 25, 2005
    #6
  7. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    - oops keep noticing that my sentences are incomplete (batteries must be going in my keyboard.

    the quote should have read
     
    creaky, Oct 25, 2005
    #7

Share This Page