Jump to content

Recommended Posts

Posted

I've started to have some errors with ImgBurn lately, I haven't a clue if the issue is due to my DVD drive or the program, basically ImgBurn seems to claim there isn't a medium present whenever I put a Blank DVD in the drive, yet blank CDs work perfectly, the times it does recognise my DVD-R's and begins burning I get that error. Any help would be amazing and very appreciated. This is the Log from my last attempt if it helps and I screenshot of the screen of errors it produced if anyone wants me to post that aswell?

 

 

I 12:00:16 ImgBurn Version 2.5.1.0 started!

I 12:00:16 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3)

I 12:00:16 Total Physical Memory: 2,095,596 KB - Available: 1,041,180 KB

W 12:00:16 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.

I 12:00:16 Initialising SPTI...

I 12:00:16 Searching for SCSI / ATAPI devices...

I 12:00:19 -> Drive 1 - Info: TSSTcorp CDDVDW SH-S222A SB01 (D:) (ATA)

I 12:00:19 -> Drive 2 - Info: UDGHOFA KLANG1IRKD 3.5Z (F:) (SCSI)

I 12:00:19 -> Drive 3 - Info: UDGHOFA KLANG1IRKD 3.5Z (K:) (SCSI)

I 12:00:19 -> Drive 4 - Info: UDGHOFA KLANG1IRKD 3.5Z (L:) (SCSI)

I 12:00:19 Found 1 DVD±RW/RAM and 3 BD-ROM/HD DVD-ROMs!

I 12:00:32 Operation Started!

I 12:00:32 Source File: C:\Documents and Settings\User\Desktop\Zalda.iso

I 12:00:32 Source File Sectors: 2,294,912 (MODE1/2048)

I 12:00:32 Source File Size: 4,699,979,776 bytes

I 12:00:32 Source File Volume Identifier: The Legend of Zelda Skyward Sword

I 12:00:32 Source File File System(s): Special

I 12:00:32 Destination Device: [0:0:0] TSSTcorp CDDVDW SH-S222A SB01 (D:) (ATA)

I 12:00:32 Destination Media Type: DVD-R (Disc ID: UME02)

I 12:00:32 Destination Media Sectors: 2,297,888

I 12:00:32 Write Mode: DVD

I 12:00:32 Write Type: DAO

I 12:00:32 Write Speed: 4x

I 12:00:32 Link Size: Auto

I 12:00:32 Lock Volume: Yes

I 12:00:32 Test Mode: No

I 12:00:32 OPC: No

I 12:00:32 BURN-Proof: Enabled

I 12:00:32 Write Speed Successfully Set! - Effective: ??? KB/s (???x)

I 12:00:32 Filling Buffer... (40 MB)

I 12:00:33 Writing LeadIn...

W 12:12:45 Failed to Write Sectors 320 - 351 - Reason: Session Fixation Error Writing Lead In

W 12:12:45 Retrying (1 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (2 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (3 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (4 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (5 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (6 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (7 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (8 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (9 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (10 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (11 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (12 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (13 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (14 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (15 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (16 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (17 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (18 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (19 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

W 12:12:45 Retrying (20 of 20)...

W 12:12:45 Retry Failed - Reason: Logical Block Address out of Range

E 12:29:40 Failed to Write Sectors 320 - 351 - Reason: Session Fixation Error Writing Lead In

I 12:29:40 Synchronising Cache...

W 12:29:46 User opted to skip the 'Close Track/Session/Disc' functions.

E 12:29:46 Failed to Write Image!

E 12:29:46 Operation Failed! - Duration: 00:29:13

I 12:29:46 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)

Posted (edited)

The first error is the real one...

 

W 12:12:45 Failed to Write Sectors 320 - 351 - Reason: Session Fixation Error Writing Lead In

 

Update the firmware on your drive.

 

http://www.firmwarehq.com/Samsung/SH-S222A/files.html

 

Update ImgBurn.

 

Buy some decent quality discs - 'UME02' are rubbish.

 

Well ImgBurn is now updated.

 

The discs were bad because I was testing out Tesco's brand incase there was some issue with my regulars, I usually use Vertabrim -R's which I believe are in high regard.

 

The firmware is where my issue seems to be, I know that my current firmware is SB01 yet the SB02 update gives an error saying its not compatible. Don't suppose you know anything that might help here?

 

Edit; I managed to update to SB02 via downgrading first to SB00 then re-attempting, now if ImgBurn stops saying "Logical Unit is in the process of becoming ready"

Edited by Jasher
Posted

See if this download of SB02 is the same.

 

http://www.samsungodd.com/eng/Firmware/FWDownload/FWDownload...geNumber=1&product_code=&os_no

 

After that, if it still have trouble recognising discs and/or burning your Verbatim ones (at 8x speed), you might like to thing about cleaning the drive with a cleaning disc... or just buy a new drive (there isn't much difference in price between a cleaning disc and a new drive!)

×
×
  • Create New...

Important Information

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