Jump to content
plastikat

DVD-R book type changes to DVD-RW after burning

Recommended Posts

Hi, All.
I was wondering if anyone here could help me to figure out the reasons behind the subject... I've tried searching the Net for answers  to no avail.
 
A bit more detailed description follows. I've got a NEC DVD-RW ND-3520AW drive with the latest firmware (3.07). I burn a Verbatim DVD-R 4.7GB disk (MCC 03RG20) using the latest ImgBurn (2.5.8.0). Before the burn I get this drive/disk information (under the spoiler to not clutter things up):

 

_NEC DVD_RW ND-3520AW 3.07 (RAID)
Current Profile: DVD-R

Disc Information:
Status: Empty
State of Last Session: Empty
Erasable: No
Free Sectors: 2 297 888
Free Space: 4 706 074 624 bytes
Free Time: 510:40:38 (MM:SS:FF)
Next Writable Address: 0
MID: MCC 03RG20
Supported Write Speeds: 2x; 4x; 6x; 8x; 12x; 16x

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Physical Format Information (Last Recorded):
Disc ID: 0@P-!-00
Book Type: DVD-R
Part Version: 5
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196 608
Last Physical Sector of Data Area: 2 495 103
Last Physical Sector in Layer 0: 0

Performance (Write Speed):
Descriptor 1...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 6 925 KB/s (5x) - WS: 2 770 KB/s (2x)
Descriptor 2...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 6 925 KB/s (5x) - WS: 5 540 KB/s (4x)
Descriptor 3...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 11 080 KB/s (8x) - WS: 8 310 KB/s (6x)
Descriptor 4...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 11 080 KB/s (8x) - WS: 11 080 KB/s (8x)
Descriptor 5...
-> B0: 0x03; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 16 620 KB/s (12x) - WS: 16 620 KB/s (12x)
Descriptor 6...
-> B0: 0x03; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2297888 (0x00231020)
-> RS: 22 160 KB/s (16x) - WS: 22 160 KB/s (16x)

 

 

The most important detail to spot is "Current Profile: DVD-R". And after the burn (and cycling the drive) I then get this information:


_NEC DVD_RW ND-3520AW 3.07 (RAID)
Current Profile: DVD-RW

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Sessions: 1
MID: MCC 03RG20

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2297887)
-> LeadOut  (LBA: 2297888)

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Recording Management Area Information:
_NEC DVD_RW ND-3520AW

Physical Format Information (Last Recorded):
Disc ID: 0@P-!-00
Book Type: DVD-R
Part Version: 5
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196 608
Last Physical Sector of Data Area: 2 209 615
Last Physical Sector in Layer 0: 0

Format Capacities:
DT: 0x02 - NB: 0 (0x00000000) - TDP: 2048
FT: 0x00 - NB: 2297888 (0x00231020) - TDP: 2048
FT: 0x10 - NB: 2297888 (0x00231020) - TDP: 16
FT: 0x15 - NB: 2297888 (0x00231020) - TDP: 16

 

And so now I get "Current Profile: DVD-RW". It's not just weird, it also has some bad side-effects... One of these being I can't burn and then verify, because when I do so the verification fails with the following messages:

Session 1, Track 1 is smaller on the disc than it is in the image file.
Disc's Track Sectors: 1 (TOC Sectors: 1)
Image File's Track Sectors: 2013008 (TOC Sectors: 2013008)

And this is kinda showstopper for me, because I believe verification is a must... Also Verbatim DVD+R's retain their book type after being burned under same conditions (and get verified). So the questions I hope someone can shed some light on are:

 

- Is this behavior considered expected for DVD-R's? If so, then how do people get these verified?

- Could it be this behavior is specific to Verbatim DVD-R's and some other DVD-R's would not behave the same?

- Could it be some bugs of my drive are the cause?

- Could it be some bugs in ImgBurn are the cause?

- Are there any settings in ImgBurn I can try to adjust to avoid this behavior?

- Something else I can't even guess?

 

Any help would be greatly appreciated. Thanks in advance.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use.