NeroCOM & C# - DVD Fixation Error

vbimport

#1

I tested this with both an isobuster generated ISO from an exising physical DVD and an NRG file generated with Nero using the image recorder.

NeroLIB.dll for C# created using tlbimp, ildasm, ilasm of NeroCOM. Burns CD’s just fine. NeroCMD burns both DVD images just fine. BurnImage code is as follows:

ndrives = (NEROLib.NeroDrivesClass)neroclass.GetDrives(NEROLib.NERO_MEDIA_TYPE.NERO_MEDIA_DVD_ANY);
ndrive.BurnImage2(f,NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_WRITE,0,NEROLib.NERO_MEDIA_TYPE.NERO_MEDIA_DVD_ANY);

I have posted about a burning problem before where it would fail when starting the burn with “Recorder function not implemented” after updating to 6.6.0.3 this issue was resolved though now I cannot fixate. I can go through Nero Express afterwards and fixate and read the data just fine.

Thoughts? Comments? Bugfixes from Ahead Software? :slight_smile:

Output log as follows.

Staring backup process
Prepare Image
Generating relocation information
Checking discs
Waiting for a particular type of media:
DVD+R/RW, DVD-R/RW, DVD+R9 Double Layer
Please insert an empty disc to write to…
Done waiting for CD!
Waiting for a particular type of media:
DVD+R/RW, DVD-R/RW, DVD+R9 Double Layer
Please insert an empty disc to write to…
Done waiting for CD!
Writing to cache
Caching of files started
Caching of files completed
Writing to disc
Burn process started at 2.4x (3,324 KB/s)
Writing tracks
Writing lead-in and lead-out
Session fixation error
Could not perform Fixation
Invalid field in command
Could not perform Fixation
Burn process failed at 2.4x (3,324 KB/s)
Status Code: NERO_BURN_FAILED
XXXX-XXXX-XXXX-XXXX-XXXX-XXXX

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 5:35:34 PM
Nero API version: 6.6.0.3
Using interface version: 6.3.1.24
Installed in: C:\Program Files\Ahead\Nero\
Application: Nero - Burning Rom\ahead
Recorder: Version: QDS1 - HA 1 TA 0 - 6.6.0.3
Adapter driver: HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI

=== Scsi-Device-Map ===
DiskPeripheral : HTS726060M9AT00 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : SONY DVD+RW DW-R56A atapi Port 1 ID 0 DMA: On
CdRomPeripheral : Generic DVD-ROM 1.0 d347prt Port 2 ID 0 DMA: Off

=== CDRom-Device-Map ===
SONY DVD+RW DW-R56A D: CDRom0
Generic DVD-ROM F: CDRom1

AutoRun : 0
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 1023MB (1047764kB)
Free physical memory: 449MB (460048kB)
Memory in use : 56 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

10.12.2004
NeroAPI
2:46:56 PM #1 Text 0 File Reader.cpp, Line 127
Reader running

2:46:56 PM #2 Text 0 File Writer.cpp, Line 122
Writer SONY DVD+RW DW-R56A running

2:46:56 PM #3 Text 0 File Burncd.cpp, Line 3151
Turn on Track-At-Once, using DVD media

2:47:22 PM #4 Text 0 File DlgWaitCD.cpp, Line 256
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 1204301 (267:37.26, 2352MB)

2:47:22 PM #5 Text 0 File DlgWaitCD.cpp, Line 268
Write in overburning mode: NO

2:47:22 PM #6 Text 0 File DlgWaitCD.cpp, Line 2309
Recorder: SONY DVD+RW DW-R56A, Media type: DVD+R
Disc Manufacturer ID: , Media Type ID: 001, Product revision number: 0
Disc Application Code: 0, Extended Information Indicators: 1

2:47:22 PM #7 Text 0 File DlgWaitCD.cpp, Line 430
>>> Protocol of DlgWaitCD activities: <<<

Insert empty disc to write to.
(Medium in drive: unknown. Medium required by compilation: DVD+R/RW, DVD-R/RW, DVD+R9 Double Layer.)

2:47:22 PM #8 Text 0 File ThreadedTransferInterface.cpp, Line 830
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, Joliet)
2 indices, index0 (150) not provided
original disc pos #0 + 1204452 (1204452) = #1204452/267:39.27
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 1204452 blocks [SONY DVD+RW DW-R56A]

2:47:22 PM #9 Text 0 File ThreadedTransferInterface.cpp, Line 1040
Prepare recorder [SONY DVD+RW DW-R56A] 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 0 2466717696, ISRC “”
DAO layout:

Start|Track|Idx|CtrlAdr|RecDep_____
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
1204452 | lead-out | 1 | 0x41 | 0x00

2:47:22 PM #10 Phase 24 File APIProgress.cpp, Line 276
Caching of files started

2:47:22 PM #11 Text 0 File Burncd.cpp, Line 4038
Cache writing successful.

2:47:22 PM #12 Phase 25 File APIProgress.cpp, Line 276
Caching of files completed

2:47:22 PM #13 Phase 36 File APIProgress.cpp, Line 276
Burn process started at 2.4x (3,324 KB/s)

2:47:22 PM #14 Text 0 File ThreadedTransferInterface.cpp, Line 2596
Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0

2:59:53 PM #15 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

2:59:53 PM #16 SCSI -1176 File Cdrdrv.cpp, Line 1176
SCSI Exec, HA 1, TA 0, LUN 0
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: 0x72
Sense Qual: 0x03
CDB Data: 0x5B 0x01 0x02 0x00 0x00 0x78 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x72 0x03

2:59:53 PM #17 CDR -1176 File ThreadedTransferInterface.cpp, Line 1280
Session fixation error

2:59:53 PM #18 TRANSFER -19 File ThreadedTransferInterface.cpp, Line 1280
Could not perform Fixation

2:59:53 PM #19 SCSI -1066 File Cdrdrv.cpp, Line 1176
SCSI Exec, HA 1, TA 0, LUN 0
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: 0x24
Sense Qual: 0x00
CDB Data: 0x5B 0x01 0x00 0x00 0x00 0x90 0x00 0x00 0x00 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x24 0x00

2:59:53 PM #20 CDR -1066 File ThreadedTransferInterface.cpp, Line 1280
Invalid field in command

2:59:53 PM #21 TRANSFER -19 File ThreadedTransferInterface.cpp, Line 1280
Could not perform Fixation

2:59:53 PM #22 Phase 38 File APIProgress.cpp, Line 276
Burn process failed at 2.4x (3,324 KB/s)

Existing drivers:
File ‘Drivers\PXHELP20.SYS’: Ver=2.02.70a, size=20176 bytes, created 3/3/2004 1:02:00 AM (Prassi/Veritas driver for win 2K)

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


#2

Does it happen every time the same way? Have you tried different burn speeds?


#3

Yes, this happens every time with NeroCOM. I have tested this on 2 computers, 3 different drives and 2 media formats (and 2 different brands of +R). I have tried different speed settings as well.


#4

I guess when all else fails, fix your own problem. DVD burning with NeroCOM and C# seems to produce a fixation error in new versions unless you include the following burn flag: NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_DAO

Once I set this burn flag, life was good.


#5

It could be that virtual memory at your computer is close to max. I had same problem and I adjusted my Virtual memory and wala…it is burning as before. here is the link which will lead you to increase or adjust your virtual memory…happy burning.

http://www.answers.vt.edu/ask4help/desktop/vtkb1550.htm


#6

[QUOTE=Ravergeek777;817837]I guess when all else fails, fix your own problem. DVD burning with NeroCOM and C# seems to produce a fixation error in new versions unless you include the following burn flag: NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_DAO

Once I set this burn flag, life was good.[/QUOTE]

Thank you very much. You saved my day! (I just registered to thank you)

Looks like you were in the same situation 5 years ago where I am today. For the past 1 week I have been looking for a solution to burn DVD+R using NEROCMD. It was giving fixation error while burning an iso image no matter what parameters I used. Looks like a bug in nero sdk 6.6. I came across this thread, your post gave me a clue to remove ‘–tao’ option in my parameter file (so that it will use dao). All is good now.

Thanks once again.


#7

Ehrm, what has “session fixation” to do with TAO?


#8

Looks like a bug in Nero sdk 6.6. Nerocmd shows an error saying “Invalid field in command” and the nero log shows KEY_ILLEGAL_REQUEST just before session fixation error. And, I noticed this happen only when writing DVD+R.