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

Problem burning a data DVD

Discussion in 'DVDR' started by Nivo9, May 27, 2007.

  1. Nivo9

    Nivo9 Member

    Joined:
    May 20, 2007
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    I am a computer novice when it comes to things like this, and would be grateful if anyone could help. It would be greatly appreciated, as I don't know where to start.

    I have a sony vaio pcg-k315s, and having trouble burning a data copy dvd. Basically I need to back up my music from my mp3 player, and therefore need to get it onto my computer then onto a data dvd.

    I have tried using Philips DVD-rw, a dvd-r of another make, and also a cd-rw. I tried to use the Sonic Record Now, and have downloaded a copy of Nero but this also failed. So assume there is a problem elsewhere - the hardware?

    I have pasted the log that comes up when it fails on Record Now 7. It gets halfway through burning, then fails saying error.


    Sense: 03 ASC: 31 ASCQ: 00 (Command 2A)
    -------------------------------------------------------
    px.dll: 2.0.22.503
    pxdrv.dll: 1.1.12.0
    pxmas.dll: 2.0.22.503
    pxwave.dll: 2.0.22.503
    PXWMA.dll: 1.0.0.3



    Below is the log that came up when it failed another time (on Nero from what I remember).


    Windows XP 5.1
    IA32
    WinAspi: -

    NT-SPTI used
    Nero Version: 7.8.5.0
    Internal Version: 7, 8, 5, 0
    (Nero Express)
    Recorder: <PIONEER DVD-RW DVR-K14> Version: 1.00 - HA 1 TA 0 - 7.8.5.0
    Adapter driver: <IDE> HA 1
    Drive buffer : 2000kB
    Bus Type : default (0) -> ATAPI, detected: ?
    CD-ROM: <PIONEER DVD-RW DVR-K14 >Version: 1.00 - HA 1 TA 0 - 7.8.5.0
    Adapter driver: <IDE> HA 1

    === Scsi-Device-Map ===
    DiskPeripheral : FUJITSU MHT2040AT atapi Port 0 ID 0 DMA: On
    CdRomPeripheral : PIONEER DVD-RW DVR-K14 atapi Port 1 ID 0 DMA: On

    === CDRom-Device-Map ===
    PIONEER DVD-RW DVR-K14 F: CDRom0
    =======================

    AutoRun : 1
    Excluded drive IDs:
    WriteBufferSize: 74448896 (0) Byte
    BUFE : 0
    Physical memory : 510MB (523248kB)
    Free physical memory: 46MB (47968kB)
    Memory in use : 90 %
    Uncached PFiles: 0x0
    Use Inquiry : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    20.5.2007
    ISO compilation
    18:50:41 #1 Text 0 File SCSIPTICommands.cpp, Line 411
    LockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL

    18:50:42 #2 Text 0 File Isodoc.cpp, Line 6608
    Iso document burn settings
    ------------------------------------------
    Determine maximum speed : FALSE
    Simulate : FALSE
    Write : TRUE
    Finalize CD : FALSE
    Multisession : TRUE
    Multisession type: : Start multisession
    Burning mode : DAO
    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

    18:50:42 #3 ISO9660GEN -11 File Geniso.cpp, Line 3343
    First writeable address = 0 (0x00000000)

    18:50:43 #4 Text 0 File Burncd.cpp, Line 3499
    Turn on Disc-At-Once, using DVD media

    18:50:43 #5 Text 0 File DlgWaitCD.cpp, Line 307
    Last possible write address on media: 2298495 (510:46.45, 4489MB)
    Last address to be written: 2166127 (481:21.52, 4230MB)

    18:50:43 #6 Text 0 File DlgWaitCD.cpp, Line 319
    Write in overburning mode: NO (enabled: CD)

    18:50:43 #7 Text 0 File DlgWaitCD.cpp, Line 2949
    Recorder: PIONEER DVD-RW DVR-K14, Media type: DVD-RW
    Disc Manufacturer: CMCW02 -
    Disc Application Code: 64, Disc Physical Code: 214

    18:50:43 #8 Text 0 File DlgWaitCD.cpp, Line 493
    >>> Protocol of DlgWaitCD activities: <<<
    =========================================

    18:50:43 #9 Text 0 File ThreadedTransferInterface.cpp, Line 793
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 ()
    2 indices, index0 (150) not provided
    original disc pos #0 + 2166128 (2166128) = #2166128/481:21.53
    relocatable, disc pos for caching/writing not required/ required
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2166128 blocks [F: PIONEER DVD-RW DVR-K14]
    --------------------------------------------------------------

    18:50:43 #10 Text 0 File ThreadedTransferInterface.cpp, Line 995
    Prepare [F: PIONEER DVD-RW DVR-K14] for write in CUE-sheet-DAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x00; Session Closed, disc not fixated
    Tracks 1 to 1: Idx 0 Idx 1 Next Trk
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4436230144, ISRC ""
    DAO layout:
    ===========
    ___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|______NWA_|_RecDep__________
    0 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
    0 | 1 | 0 | 0x41 | 0 | 0 | 0x00
    0 | 1 | 1 | 0x41 | 2166128 | 0 | 0x00
    2166128 | lead-out | 1 | 0x41 | 0 | 0 | 0x00

    18:50:43 #11 Text 0 File SCSIPTICommands.cpp, Line 209
    SPTILockVolume - completed successfully for FCTL_LOCK_VOLUME

    18:50:43 #12 Text 0 File Burncd.cpp, Line 4278
    Caching options: cache CDRom or Network-Yes, small files-No (<64KB)

    18:50:43 #13 Phase 24 File dlgbrnst.cpp, Line 1762
    Caching of files started

    18:50:43 #14 Text 0 File Burncd.cpp, Line 4397
    Cache writing successful.

    18:50:43 #15 Phase 25 File dlgbrnst.cpp, Line 1762
    Caching of files completed

    18:50:43 #16 Phase 36 File dlgbrnst.cpp, Line 1762
    Burn process started at 2x (2,770 KB/s)

    18:50:44 #17 Text 0 File ThreadedTransferInterface.cpp, Line 2721
    Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

    18:50:44 #18 Text 0 File DVDMinusRW.cpp, Line 262
    Perform 'Quick Format' (type 15h) to set disc in 'Restricted Overwrite Mode'.

    18:50:44 #19 Phase 136 File dlgbrnst.cpp, Line 1762
    Quick Format DVD-RW

    18:54:46 #20 SPTI -1169 File SCSIPassThrough.cpp, Line 179
    CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1169)
    Sense Key: 0x02 (KEY_NOT_READY)
    Sense Code: 0x04
    Sense Qual: 0x04
    CDB Data: 0x00 00 00 00 00 00 00 00 00 00 00 00
    Sense Area: 0x70 00 02 00 00 00 00 0E 00 00 00 00 04 04 00 80 FF FF

    18:54:46 #21 CDR -1169 File ThreadedTransferInterface.cpp, Line 1752
    Logical unit not ready, operation in progress
    F: PIONEER DVD-RW DVR-K14

    18:54:46 #22 TRANSFER -27 File ThreadedTransferInterface.cpp, Line 1752
    Could not perform start of Disc-at-once

    18:54:46 #23 Text 0 File ThreadedTransfer.cpp, Line 269
    Pipe memory size 74390400

    18:54:46 #24 Phase 38 File dlgbrnst.cpp, Line 1762
    Burn process failed at 2x (2,770 KB/s)

    18:54:46 #25 Text 0 File SCSIPTICommands.cpp, Line 254
    SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME

    18:54:46 #26 SPTI -1169 File SCSIPassThrough.cpp, Line 179
    CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1169)
    Sense Key: 0x02 (KEY_NOT_READY)
    Sense Code: 0x04
    Sense Qual: 0x04
    CDB Data: 0x1B 00 00 00 02 00 00 00 00 00 00 00
    Sense Area: 0x70 00 02 00 00 00 00 0E 00 00 00 00 04 04 00 80 FF FF

    18:54:46 #27 SPTI -1169 File SCSIPassThrough.cpp, Line 179
    CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1169)
    Sense Key: 0x02 (KEY_NOT_READY)
    Sense Code: 0x04
    Sense Qual: 0x04
    CDB Data: 0x1B 00 00 00 02 00 00 00 00 00 00 00
    Sense Area: 0x70 00 02 00 00 00 00 0E 00 00 00 00 04 04 00 80 FF FF

    18:54:46 #28 Text 0 File Cdrdrv.cpp, Line 11214
    DriveLocker: UnLockVolume completed

    18:54:46 #29 Text 0 File SCSIPTICommands.cpp, Line 411
    UnLockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL


    Existing drivers:

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



    Thanks!
     
  2. IHoe

    IHoe Senior member

    Joined:
    May 21, 2005
    Messages:
    6,431
    Likes Received:
    0
    Trophy Points:
    116
    no recognition of your ASPI layer or
    ASPI layer is corrupted, try this, version 4.71 from here - http://www.afterdawn.com/software/cdr_software/cdr_tools/aspi.cfm

    way too much memory is being used.. try shutting down programs that are working in the background, no multi tasking, no internet, and even shut down you antivirus program while buring.

    you are using crappy media..... use good quality media (rule of thumb....buy the ones that are Made in Japan.) Verbatim is a top notch disk and is the only exception to this rule....some Verbatims are made in Taiwan and they are top notch!

    also Roxio/Sonic (RecordNow) sometimes interferes with Nero... uninstall Roxio/Sonic program(s) and run the Roxio Zapper:
    http://www.softpedia.com/get/Tweak/Uninstallers/Roxio-Zap.shtml
    reboot and try again after you completed these suggestions. good luck and welcome to Afterdawn.
     
  3. Nivo9

    Nivo9 Member

    Joined:
    May 20, 2007
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    IHoe - re: the ASPI layer
    I have unzipped those files. Sorry for what may be a simple question, what do I do once unzipped them. Which one(s) do I need to double click?
     
  4. IHoe

    IHoe Senior member

    Joined:
    May 21, 2005
    Messages:
    6,431
    Likes Received:
    0
    Trophy Points:
    116
    read the readme file and learn all about it, what you have to do and such. ok? good luck.
     
  5. Nivo9

    Nivo9 Member

    Joined:
    May 20, 2007
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    11
    Thanks.
    I have had a look at the readme but don't know how to interpret it and what part to do.
    I have copied it below if anyone could make sense of it in relation to my problem?

    Adaptec Inc., Copyright (c) 2002

    ASPI Overview
    =======================================================
    I ) Operating Systems and ASPI Files Installed
    II ) Changes between v 4.60 and v 4.71
    III) GetASPI32Buffer Addendum
    IV ) How to increase the non-paged pool size
    V ) Windows XP Support
    VI ) Installation of ASPI
    VII) Status Codes for ASPIINST.EXE

    I. Operating System ASPI Files Installed
    ========================================================
    Microsoft Windows NT 4.0 wnaspi32.dll, aspi32.sys
    winaspi.dll, wowpost.exe

    Microsoft Windows 2000 wnaspi32.dll, aspi32.sys
    winaspi.dll, wowpost.exe

    Microsoft Windows 98 wnaspi32.dll, apix.vxd

    Microsoft Windows Me wnaspi32.dll, apix.vxd

    Microsoft Windows XP wnaspi32.dll, aspi32.sys


    II. Changes Between v 4.60 and v 4.71
    =======================================================
    1) It is important the following pairs of files have matching version numbers:
    (you may not have all of these files; which files you have in your PC depends
    on which Windows platform is in your PC)

    a) wnaspi32.dll and aspi32.sys
    b) wnaspi32.dll and apix.vxd
    c) winaspi.dll and wowpost.exe

    It is not important, for example, for wnaspi32.dll to have matching version
    number with winaspi.dll. Disregard any such error message from aspichk.exe.
    Also disregard any error message from aspichk.exe regarding files not present.

    2) Windows 2000 and Windows NT4.0 Only:
    Command tagged queueing is enabled by default in v4.71; however, this is
    functional only if your Host Bus Adapter (HBA) supports tagged queueing.
    Check with your HBA vendor for HBA capabilities.

    3) Windows 2000 Only:
    aspi32.sys (aspi2k.sy_ before install) remains a non-Plug-and-Play driver in Windows 2000.
    Once loaded, aspi32.sys will not unload. To get aspi32.sys unloaded, delete the file
    \winnt\system32\drivers\aspi32.sys and reboot PC.

    4) Previous versions of aspi32.sys for Windows 2000 and XP may not return the proper
    Maximum Number of Targets (HA_MaxTargets) in reponse to Host Adapter Inquiry
    (HA_INQUIRY). This has been corrected.

    III. GetASPI32Buffer Addendum
    =========================================================================
    FYI

    If you have experienced a failure to allocate a buffer (GetASPI32Buffer),
    you may need to do one or both of the following:

    1) increase the non-paged pool size on your PC (allocate more RAM to
    non-paged pool),
    2) physically add more RAM to your PC.
    3) decrease the buffer size requested.

    The first thing to do is to increase the non-paged pool size.

    IV) How to increase the non-paged pool size ?
    =============================================

    1) Run regedt32.exe ( click Start->Run and type regedt32 ),
    2) Edit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\MemoryManagement\NonPagedPoolSize
    This parameter is a REG_DWORD (32 bits).

    NOTE : If it is set to 0x00, the default minimum portion of RAM is allocated to
    non-paged pool.

    3) Set this parameter to 0xffffffff (the maximum portion of RAM is allocated to
    non-paged pool.) Reboot the PC and try the application again.

    NOTE : If GetASPI32Buffer still fails; you may not have enough
    physical RAM in the PC, and you may need to physically
    install additional RAM.

    If GetASPI32Buffer now works, then gradually decrease the non-paged pool size
    ( by specifying the amount of RAM allocated to non-paged pool ) to optimize.

    Tips
    -------------------------------------------------------------
    Set the NonPagedPoolSize to 0x00100000 for 1 MegaBytes;
    0x00200000 for 2 MegaBytes; etc.

    See the Microsoft Developer Network (MSDN) article Q126402 (www.microsoft.com)
    for more information regarding setting the non-paged pool size.


    V. Windows XP Support
    ===========================================================

    Contents:
    -----------------------------------------------------------
    install.bat installation batch file
    reg_xp.exe registry modification utility
    aspixp.sys 32-bit ASPI driver ( v 4.71.2 )
    wnaspixp.dll 32-bit ASPI DLL ( v 4.71.2 )
    aspi64.sys 64-bit ASPI driver ( v 4.70.8 )
    wnaspi64.dll 64-bit ASPI DLL ( v 4.70.8 )


    VI. Installation of ASPI
    ============================================================
    1. Run INSTALL.BAT with the target operating system
    command line option specified:

    X86 ( for Windows 98/ME/NT/2000 )
    XP32 ( for Windows XP 32-bit )
    XP64 ( for Windows XP 64-bit )

    e.g. "INSTALL.BAT X86"

    2. INSTALL.BAT will prompt you to specify which operating
    system to install for if you did not specify one in Step 1).

    a) If you are installing for X86 systems for either
    Windows 98/ME/NT/2000 then ASPIINST.EXE will be invoked
    and the rest of the installation process will be carried
    out.
    b) If you are installing for X86 or Itanium systems the
    batch file will invoke REG_XP.EXE to make the necessary
    registry entries and then copy the operating system
    specific files to the appropriate location. The operating
    system path is determined by the environment variable
    %windir%.

    For Win XP 32-bit:
    ASPIXP.SYS will be copied to %windir%\system32\drivers\ASPI32.SYS
    WNASPIXP.DLL will be copied to %windir%\system32\WNASPI32.DLL

    For Win XP 64-bit:
    ASPI64.SYS will be copied to %windir%\system32\drivers\ASPI32.SYS
    WNASPI64.DLL will be copied to %windir%\system32\WNASPI32.DLL

    3. Reboot the system to enable the ASPI driver.

    VII) Status Codes for ASPIINST.EXE
    ===========================================================
    The use of the C programming convention, EXIT, has been
    removed completely from the source. EXIT has some
    restrictions which RETURN does not.

    EXIT allows for only the low order byte of the status code
    to be accessible to the calling process. The status value
    is available to the operating system batch command ERRORLEVEL
    but is represented by one of two constants EXIT_SUCCESS (0)
    or EXIT_FAILURE (1).
     

Share This Page