As indicated in the notes here's the log:
I 20:28:06 ImgBurn Version 2.5.5.0 started!
I 20:28:06 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 20:28:06 Total Physical Memory: 3,406,224 KB - Available: 2,892,328 KB
I 20:28:06 Initialising SPTI...
I 20:28:06 Searching for SCSI / ATAPI devices...
I 20:28:06 -> Drive 1 - Info: ATAPI iHAS122 ZL0A (D:) (ATA)
I 20:28:06 Found 1 DVD±RW/RAM!
I 20:28:21 Operation Started!
I 20:28:21 Source Device: [1:0:0] ATAPI iHAS122 ZL0A (D:) (ATA)
I 20:28:21 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: MBIPG101-W04-00) (Speeds: 4x)
I 20:28:21 Source Media Sectors: 2,295,104
I 20:28:21 Source Media Size: 4,700,372,992 bytes
I 20:28:21 Verify Against Image File: No
I 20:28:21 Read Speed (Data/Audio): MAX / MAX
I 20:28:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2295103)
I 20:28:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2295103)
I 20:33:26 Exporting Graph Data...
I 20:33:26 Graph Data File: C:\Documents and Settings\ALEX\Application Data\ImgBurn\Graph Data Files\ATAPI_iHAS122_ZL0A_09-SEPTEMBER-2011_20-28_MBIPG101-W04-00.ibg
I 20:33:27 Export Successfully Completed!
I 20:33:27 Operation Successfully Completed! - Duration: 00:05:05
I 20:33:27 Average Verify Rate: 15,049 KB/s (10.9x) - Maximum Verify Rate: 17,014 KB/s (12.3x)
I 20:36:06 Operation Started!
I 20:36:06 Device: [1:0:0] ATAPI iHAS122 ZL0A (D:) (ATA)
I 20:36:06 Media Type: DVD+RW (Disc ID: MBIPG101-W04-00) (Speeds: 4x)
I 20:36:06 Quick Erase: No
I 20:36:06 Format Properly: Yes
I 20:36:06 Format Size: Preferred
I 20:36:06 Erasing Disc...
This was with a brand new from packet TDK brand media DVD+RW 4x |120 min | 4.7 GB on a first time install of ImgBurn
downloaded directly from the download on your site..
Everything appears to work normally until the status count reaches 96%, at which point Imgburn appears to freeze up.
Would you concur that the jamming of ImgBurn at 96% is down to a hardware fault which is not being reported in the log,
or a physical media fault? I am asking this because I don't see how ImgBurn could be failing at this point from a software
perspective.