burn error 2.4x (3,312KB\s) - Nero 6 - sense key 5h

29th Jan 2004 00:45 #1

Member

I have just bought and installed a Pioneer 106D DVD writable drive, (VERSION 1.07) Unfortunately every time I try to do a back up to a DVD re-writeable disk using Nero 6 error message.

"burn error 2.4x (3,312KB\s)"

I am having problems with Nero 6, every time I try to burn a DVD+/-R I get the same error “burn error 2.4x (3,312KB\s), I believe this is something to do with the Sense key 5h - illegal media, although I have tried many different types of media in my Pioneer 106D drive.

When burning process fails: - log attached
Nero version: 6.3.0.2
Windows XP pro
Motherboard, Bios, Pioneer 106D drive all updated

I have re-formatted my guard drive to have just Nero 6 running with my rewritable drive
Pioneer 106d 1.07
D:
HDD on Pri/Mas - Pioneer rewriter 106D on Sec/Mas
DMA if available is ticked
I do not have a disconnect option in device manager?!!
VIA bus master IDE controller
Printer and scanner are USB
V266B - VIA KT266A and 8233A Chipset Support Socket-A for AMD Athlon /Duron at 266MHz.
.4x AGP VGA Mode .Support ATA133 .On-board 3D Audio
.Support 168-pin DIMM and 184-pin DDR RAM

no conflicts in XP device manager
ASPI has is at latest version
No other burn softwareOnly Nero 6 to avail conflict

When using Nero drive speed it show the correct type of DVD in the drive. E.g DVD+RW

Please help I am unable to use the drive to do any backups at all. I have upgraded the Nero software to best it can be.

I have looked at various other website help forums and follows all the hints and tips e.g. checking DMA is on, checking autoplay, etc…

thanks

Appichk logLOG0143: ************************************************** ***************
LOG0144: Starting ASPICHK installer on Thu Jan 29 06:35:03 2004
ASPICHK0438: OS = Windows NT (5.01.2600)
UPGRADE1004: c:\windows\system32\wnaspi32.dll dated 09/10/1999 12:06:00, 45056 bytes.
UPGRADE1062: c:\windows\system32\wnaspi32.dll version 4.6.0.1021
UPGRADE1004: c:\windows\system\winaspi.dll dated 09/10/1999 12:06:00, 5600 bytes.
UPGRADE1062: c:\windows\system\winaspi.dll version 4.6.0.1021
UPGRADE1004: c:\windows\system32\drivers\aspi32.sys dated 09/10/1999 12:06:00, 25244 bytes.
UPGRADE1062: c:\windows\system32\drivers\aspi32.sys version 4.6.0.1021
UPGRADE1004: c:\windows\system\wowpost.exe dated 09/10/1999 12:06:00, 4672 bytes.
UPGRADE1062: c:\windows\system\wowpost.exe version 4.6.0.1021
ASPICHK0582: ASPI is properly installed and is fully operational. A total of 2 host adapters have been detected.
LOG0218: Closing installer log on Thu Jan 29 06:35:03 2004
LOG0219: ************************************************** ***********

Nero 6 log
Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\nero\Wnaspi32.dll': Ver=2.0.1.59, size=160016 bytes, created 16/12/2003 19:18:06
Nero version: 6.3.0.2 (Nero Express)
Recorder: <PIONEER DVD-RW DVR-106D>Version: 1.07 - HA 1 TA 0 - 6.3.0.2
Adapter driver: <atapi> HA 1
Drive buffer : 2000kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <PIONEER DVD-RW DVR-106D>Version: 1.07 - HA 1 TA 0 - 6.3.0.2
Adapter driver: <atapi> HA 1

=== Scsi-Device-Map ===
DiskPeripheral : Maxtor 6E040L0 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : PIONEER DVD-RW DVR-106D atapi Port 1 ID 0 DMA: On

=== CDRom-Device-Map ===
PIONEER DVD-RW DVR-106D D: CDRom0
=======================

AutoRun : 0
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 1023MB (1047992kB)
Free physical memory: 572MB (586016kB)
Memory in use : 44 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

28.1.2004
ISO compilation
21:45:34 #1 Text 0 File Isodoc.cpp, Line 6029
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

21:45:34 #2 Text 0 File Reader.cpp, Line 118
Reader running

21:45:34 #3 Text 0 File Writer.cpp, Line 124
Writer PIONEER DVD-RW DVR-106D running

21:45:34 #4 ISO9660GEN -11 File geniso.cpp, Line 3882
First writeable address = 0 (0x00000000)

21:45:35 #5 Text 0 File Burncd.cpp, Line 3101
Turn on Disc-at-once, using DVD media

21:45:35 #6 Text 0 File DlgWaitCD.cpp, Line 240
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 227599 ( 50:34.49, 444MB)

21:45:35 #7 Text 0 File DlgWaitCD.cpp, Line 245
Write in overburning mode: FALSE

21:45:35 #8 Text 0 File DlgWaitCD.cpp, Line 2085
Recorder: PIONEER DVD-RW DVR-106D, Media type: DVD+RW
Disc Manufacturer ID: CMC MAG, Media Type ID: W01, Product revision number: 0
Disc Application Code: 0, Extended Information Indicators: 0

21:45:35 #9 Text 0 File DlgWaitCD.cpp, Line 406
>>> Protocol of DlgWaitCD activities: <<<
=========================================

21:45:35 #10 Text 0 File ThreadedTransferInterface.cpp, Line 779
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original disc pos #0 + 227600 (227600) = #227600/50:34.50
relocatable, disc pos for caching/writing not required/required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 227600 blocks [PIONEER DVD-RW DVR-106D]
--------------------------------------------------------------

21:45:35 #11 Text 0 File ThreadedTransferInterface.cpp, Line 948
Prepare recorder [PIONEER DVD-RW DVR-106D] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc not fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 466124800, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_RecDep_|_CtrlAdr_
0 | lead-in | 0 | 0x00 | 0x41
0 | 1 | 0 | 0x00 | 0x41
0 | 1 | 1 | 0x00 | 0x41
227600 | lead-out | 1 | 0x00 | 0x41

21:45:36 #12 Phase 24 File dlgbrnst.cpp, Line 1800
Caching of files started

21:45:36 #13 Text 0 File Burncd.cpp, Line 4073
Cache writing successful.

21:45:36 #14 Phase 25 File dlgbrnst.cpp, Line 1800
Caching of files completed

21:45:36 #15 Phase 36 File dlgbrnst.cpp, Line 1800
Burn process started at 2.4x (3,312 KB/s)

21:45:36 #16 Text 0 File ThreadedTransferInterface.cpp, Line 2264
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

21:45:36 #17 Text 0 File Cdrdrv.cpp, Line 7941
---- 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: <not specified> (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: 26053F h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Media Specific:
00 00 43 4D 43 20 4D 41 - 47 00 57 30 31 00 39 23 ..CMC.MAG.W01.9#
00 8A 7A 62 02 1E 00 86 - 80 62 02 28 00 8A 7A 5E ..zb.....b.(..z^
02 1E 13 12 10 00 10 00 - 00 00 00 00 00 00 00 00 ................

21:45:36 #18 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 5:40,380 (340380ms) -> OK

21:45:36 #19 Phase 98 File dlgbrnst.cpp, Line 1800
Start formatting disc before burning

21:45:51 #20 Phase 100 File dlgbrnst.cpp, Line 1800
Formatting disc was successful

21:45:51 #21 Phase 65 File dlgbrnst.cpp, Line 1800
Burn process started

21:45:51 #22 Text 0 File DVDPlusRW.cpp, Line 564
Start write address at LBA 0
DVD high compatibility mode: Yes

21:45:55 #23 SCSI -1046 File Cdrdrv.cpp, Line 1431
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x041E0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x30
Sense Qual: 0x10
CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0E
0x00 0x00 0x00 0x00 0x30 0x10

21:45:55 #24 CDR -1046 File Writer.cpp, Line 301
Illegal disc

21:45:55 #25 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion

21:45:55 #26 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader

21:45:56 #27 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 0:00,000 (0ms) -> OK

21:45:56 #28 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 0:00,000 (0ms) -> OK

21:45:56 #29 Phase 38 File dlgbrnst.cpp, Line 1800
Burn process failed at 2.4x (3,312 KB/s)

Existing drivers:
File 'Drivers\atapi.sys': Ver=5.1.2600.1106 (xpsp1.020828-1920), size=86912 bytes, created 29/08/2002 12:00:00 (Adapter driver for rec)

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

NeroPing V1.10
Copyright Ahead Software AG 2002
All rights reserved

Host Adapter = 1
[Target ID = 0] 'PIONEER DVD-RW DVR-106D 1.07 '

Win aspi path :C:\Program Files\Ahead\nero\wnaspi32.dll
File description :Win32 Nero Aspi Library
ProductVersion :Nero WnAspi32
ProductVersion :2.0.1.59
FileVersion :2.0.1.59
OriginalFilename :WnAspi32.dll
InternalName :WnAspi32.dll

I now know for extensive research that this has something to do with the sense key 5r failure, hoever I need to know how to sort if I can or is it a drive problem!!

Quote

5th Mar 2004 03:13 #2

vons

Member

laurynsausage,

could you tell me if you found a solution at your problem ?

It appears that I have the same problem you do

Thanks.

Quote

5th Mar 2004 06:03 #3

laurynsausage

Member

Hi

No I have not, I gave up as pioneer or Nero were forthcoming with any decent support.

Are you able to offer any assistance?

Quote

9th Mar 2004 01:52 #4

vons

Member

I currently do not have any idea of the source of the error.
The thing I will do is try to burn with another software so that we know
if the problem is coming from the hardware or not.
Anyway, I will keep you posted

Quote

15th Mar 2004 17:15 #5

pepemolesa

Member