|
|
|
Is Firmware or Nero generating the message?
|
|
AfterDawn Addict
|
16. October 2005 @ 12:07 |
Link to this message
|
|
Does anyone know?
Is the information on line 6 and line 15 being relayed from the 'firmware' on the drive and displayed by Nero or is it a strictly
'Nero' affair or a mixture of both?
Reason I ask is that this drive has never displayed disc information on line 15 (or equivalent) even though I have verified that all the media I have used is on the manufacturers list (displayed with each firmware issue).
I have 'rolled back' the firmware to no avail.I presume that the info displayed on line 15 is a generic or fallback position for either the drive or Nero.
P.S. I have never cared for this drive, but it was a gift, else it would have been heaved long since ;)
12:18:46 PM #6 Text 0 File DlgWaitCD.cpp, Line 2483
Recorder: AOPEN DUW1608/ARR, Media type: DVD-R
Disc Manufacturer: TYG01 -
Disc Application Code: 64, Disc Physical Code: 193
12:18:47 PM #15 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: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
|
|
Advertisement
|
 |
|
|
AfterDawn Addict
|
16. October 2005 @ 13:13 |
Link to this message
|
Quote:
David X
Home
1a23-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 6:35:34 PM
Nero Version: 6.6.0.16
Internal Version: 6, 6, 0, 16b
(Nero Express)
Recorder: <SONY DVD RW DRU-710A> Version: BYX4 - HA 1 TA 0 - 6.6.0.16
Adapter driver: <atapi> HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <TOSHIBA ODD-DVD SD-M1802>Version: 1051 - HA 1 TA 1 - 6.6.0.16
Adapter driver: <atapi> HA 1
=== Scsi-Device-Map ===
DiskPeripheral : ST340014A atapi Port 0 ID 0 DMA: On
DiskPeripheral : ST380011A atapi Port 0 ID 1 DMA: On
CdRomPeripheral : SONY DVD RW DRU-710A atapi Port 1 ID 0 DMA: On
CdRomPeripheral : TOSHIBA ODD-DVD SD-M1802 atapi Port 1 ID 1 DMA: On
=== CDRom-Device-Map ===
SONY DVD RW DRU-710A E: CDRom0
TOSHIBA ODD-DVD SD-M1802 F: CDRom1
=======================
AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 991MB (1015280kB)
Free physical memory: 600MB (614744kB)
Memory in use : 39
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
15.10.2005
Burn DVD Image
9:44:29 PM #1 Text 0 File Reader.cpp, Line 127
Reader running
9:44:29 PM #2 Text 0 File Writer.cpp, Line 122
Writer SONY DVD RW DRU-710A running
9:44:29 PM #3 Text 0 File Burncd.cpp, Line 3233
Turn on Disc-At-Once, using DVD media
9:44:29 PM #4 Text 0 File DlgWaitCD.cpp, Line 270
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 1883525 (418:33.50, 3678MB)
9:44:29 PM #5 Text 0 File DlgWaitCD.cpp, Line 282
Write in overburning mode: NO (enabled: CD DVD)
9:44:29 PM #6 Text 0 File DlgWaitCD.cpp, Line 2483
Recorder: SONY DVD RW DRU-710A, Media type: DVD+R
Disc Manufacturer ID: YUDEN000, Media Type ID: T02, Product revision number: 0
Disc Application Code: 0, Extended Information Indicators: 3
9:44:29 PM #7 Text 0 File DlgWaitCD.cpp, Line 448
>>> Protocol of DlgWaitCD activities: <<<
=========================================
9:44:29 PM #8 Text 0 File ThreadedTransferInterface.cpp, Line 838
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, ISO 9660)
2 indices, index0 (150) not provided
original disc pos #0 + 1883526 (1883526) = #1883526/418:33.51
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 1883526 blocks [SONY DVD RW DRU-710A]
--------------------------------------------------------------
9:44:29 PM #9 Text 0 File ThreadedTransferInterface.cpp, Line 1051
Prepare recorder [SONY DVD RW DRU-710A] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 3857461248, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
1883526 | lead-out | 1 | 0x41 | 0x00
9:44:29 PM #10 Phase 24 File dlgbrnst.cpp, Line 1832
Caching of files started
9:44:29 PM #11 Text 0 File Burncd.cpp, Line 4120
Cache writing successful.
9:44:29 PM #12 Phase 25 File dlgbrnst.cpp, Line 1832
Caching of files completed
9:44:29 PM #13 Phase 36 File dlgbrnst.cpp, Line 1832
Burn process started at 4x (5,540 KB/s)
9:44:30 PM #14 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
9:44:30 PM #15 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 (10), Part Version: 1.0x (1)
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: 26053F h
End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
Data in Burst Cutting Area (BCA) does not exist
Disc Application Code: 0 / 0 h
Extended Information indicators: 3 h
Disc Manufacturer ID: YUDEN000
Media type ID: T02
Product revision number: 0
Number of Physical format information bytes in use in ADIP up to byte 63: 56
Media Specific [16..63]:
00 00 03 59 55 44 45 4E - 30 30 30 54 30 32 00 38 ...YUDEN000T02.8
23 54 37 10 02 4E 72 02 - 8C 63 16 16 0B 0B 0A 0A #T7..Nr..c......
01 19 1B 0C 0C 0C 0D 01 - 00 00 00 00 00 00 00 00 ................
9:44:30 PM #16 Text 0 File DVDR.cpp, Line 5618
Drive: SONY DVD RW DRU-710A
Book Type request [LO]: DVD-ROM
Changing the Book Type was finished successfully, return code 0
9:44:30 PM #17 CDR -1207 File DVDR.cpp, Line 5065
Book Type automatically set to: DVD-ROM
9:44:30 PM #18 Text 0 File DVDPlusRW.cpp, Line 665
Start write address at LBA 0
DVD high compatibility mode: Yes
9:56:32 PM #19 Text 0 File WriterStatus.cpp, Line 116
<SONY DVD RW DRU-710A > start writing Lead-Out at LBA 1883526 (1CBD86h), lenght 0 blocks
9:56:32 PM #20 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion
9:56:58 PM #21 Text 0 File DVDR.cpp, Line 5618
Drive: SONY DVD RW DRU-710A
Book Type request [LO]: DVD+R
Changing the Book Type was finished successfully, return code 0
9:56:58 PM #22 Phase 37 File dlgbrnst.cpp, Line 1832
Burn process completed successfully at 4x (5,540 KB/s)
I'm lost at trying to understand what you're trying to say about firmware, but the above is an example of a successfullly burned log of mine. Below is the current "firmware" on mine -- that is, if you're trying to look for the right firmware. So, "BYX4" and "1051" are the current firmware for my burner and cd/dvd-rom drive.
Recorder: <SONY DVD RW DRU-710A> Version: BYX4
CD-ROM: <TOSHIBA ODD-DVD SD-M1802>Version:1051
|
Moderator
|
16. October 2005 @ 13:17 |
Link to this message
|
i think i get the gist. My old Sony drive showed this for virtually all my discs Quote:
Media Specific [16..63]:
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
all i go by is this - Quote:
Recorder: LITE-ON DVDRW SOHW-1693S, Media type: DVD-R
Disc Manufacturer: MCC 02 - RG20
Disc Application Code: 64, Disc Physical Code: 193
- that shows firmware has detected the media correctly but this Quote:
Recorder: LITE-ON DVDRW SOHW-1693S, Media type: DVD-R
shows that the firmware is out of date.
is that what you mean ?
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules *** |
AfterDawn Addict
|
16. October 2005 @ 14:12 |
Link to this message
|
Quote:
Does anyone know?
Is the information on line 6 and line 15 being relayed from the 'firmware' on the drive and displayed by Nero or is it a strictly
'Nero' affair or a mixture of both?
I think I might get it after reading the questions 3 more times now. So do you mean that the "firmware" or "Nero" has anything to do (i.e. affiliate) with line #6 & #15? Yes... it is a combination of both "firmware" and "Nero". Without the latest firmware, Nero would just read the blank media as Media Type: DVD+R or DVD-R; the same thing apply to line #15 as well. If Nero is too old, then in some cases, it wouldn't show either line (sometimes not line 15). I may be wrong, so Creaky or someone with more knowlege on Nero correct me on this one.
Quote:
9:44:29 PM #6 Text 0 File DlgWaitCD.cpp, Line 2483
Recorder: SONY DVD RW DRU-710A, Media type: DVD+R
Disc Manufacturer ID: YUDEN000, Media Type ID: T02, Product revision number: 0
Disc Application Code: 0, Extended Information Indicators: 3
And Creaky is right, that is what I go by as well.
|
AfterDawn Addict
|
16. October 2005 @ 15:04 |
Link to this message
|
|
@alkohol
@creaky
Consensus says that on line #6,'firmware' should recognize the media, else a generic type is displayed, indicating a firmware bug?
Contrariwise, at line #15 a normal message may be generic or verbose, depending on the drive, and not necessarily indicitive of a problem?
This message has been edited since posting. Last time this message was edited on 17. October 2005 @ 04:12
|
|
Advertisement
|
|
|
Moderator
|
16. October 2005 @ 23:32 |
Link to this message
|
|
@attar - now i'm definitely with you. you know what, i'd never once paid attention to the line numbers as you call them (ie i've never actually noticed the #6, #15 etc, i've always skimmed over those). !!!
Anyway, for both questions, a resounding yes!. as to line #15, when i first started out, what i'd read suggested that if there were no values in with all those dots, that there was a problem. However i quickly found out that this wasn't the case.
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***
|
|
