[DVD DL Data - Lexus Navigation]

It seems to work correctly, but without testing all 10 map zones, it's hard to say if it works correctly or not. I can surely say it works in the region where I live, but that's all I can say with any certainty. It does find Starbucks a lot better than the previous version!

[DVD DL Data - Lexus Navigation]

As requested:

 

TSSTcorp CD/DVDW SH-S182M SB06 (ATA)

Current Profile: DVD-ROM

 

Disc Information:

Status: Complete

State of Last Session: Complete

Erasable: No

Sessions: 1

Sectors: 4,027,872

Size: 8,249,081,856 bytes

Time: 895:06:72 (MM:SS:FF)

 

File System Information:

Sectors: 4,027,872

Size: 8,249,081,856 bytes

Time: 895:06:72 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

-> Track 01 (Mode 1, LBA: 0 - 4027871)

-> LeadOut (LBA: 4027872)

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, LTS: 4027872, LRA: 0)

 

Physical Format Information (Last Recorded - L0):

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: 10.08Mbps

Number of Layers: 2

Track Path: Parallel Track Path (PTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,223,000

Last Physical Sector in Layer 0: 0

 

Physical Format Information (Last Recorded - L1):

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: 10.08Mbps

Number of Layers: 2

Track Path: Parallel Track Path (PTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,198,086

Last Physical Sector in Layer 0: 0

 

Layer Information:

Layer 0 Sectors: 2,026,393 (50.31%)

Layer 1 Sectors: 2,001,479 (49.69%)

[DVD DL Data - Lexus Navigation]

Newb to the site, but not a newb to forums - searched quite a bit and have not seen this particular issue. I've had complete success in the past with Lexus navigation discs, the Lexus Generation 5 hw/sw (also sold as Eclipse aftermarket) had a firmware version with an override feature I like to retain, so I've put together hybrid discs with early firmware and later maps a few times. I got a 10.1 disc, and used ImgBurn to create an ISO and MDS. In the past, all I've needed to do to validate the ISO works is burn a new disc by selecting the MDS and putting a new Verbatim DVD+R DL in my Samsung (TSSTcorp CD/DVDW SH-S182M SB06) burner. I persistently get a layer break error preventing me from writing anything to the disc.

 

Optimal layer break position must be a multiple of 16
Optimal L0 sectors 2,026,393
Next largest acceptable value 2,026,400

 

Log looks like this:

 

I 03:13:01 Operation Started!
I 03:13:01 Source File: E:\Nav ISO\464210-1711.MDS
I 03:13:01 Source File Sectors: 4,027,872 (MODE1/2048)
I 03:13:01 Source File Size: 8,249,081,856 bytes
I 03:13:01 Source File Volume Identifier: 464210-1711
I 03:13:01 Source File Application Identifier: Session Offset : 0 VTC Sector Offset: 0
I 03:13:01 Source File Implementation Identifier: Smart Storage, Inc.
I 03:13:01 Source File File System(s): ISO9660, Joliet, UDF (1.02)
I 03:13:01 Destination Device: [0:1:0] TSSTcorp CD/DVDW SH-S182M SB06 (Z:) (ATA)
I 03:13:01 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 4x, 6x, 8x)
I 03:13:01 Destination Media Sectors: 4,173,824
I 03:13:01 Write Mode: DVD
I 03:13:01 Write Type: DAO
I 03:13:01 Write Speed: MAX
I 03:13:01 Link Size: Auto
I 03:13:01 Lock Volume: Yes
I 03:13:01 Test Mode: No
I 03:13:01 OPC: No
I 03:13:01 BURN-Proof: Enabled
I 03:13:01 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 03:13:01 Book Type Setting: DVD-ROM
E 03:13:01 Optimal layer break position must be a multiple of 16.
E 03:13:01 Optimal L0 Sectors: 2,026,393
E 03:13:01 Next Largest Acceptable Value: 2,026,400
E 03:15:14 Operation Failed! - Duration: 00:02:13
I 03:15:14 Average Write Rate: N/A - Maximum Write Rate: N/A

 

I managed to burn one by manually setting the L0 break at 2,026,400 and I tested it briefly in the navigation unit. It appears to work. Is manually changing the layer break for what amounts to an exact copy expected? Am I doing something inherently wrong causing this problem, or is it possible Lexus is trying to make copying/archiving this data more difficult?

 

I did try to change the write speed, but nothing seemed to make any difference until I manually set the layer break.