jimmy2times Posted October 19, 2013 Share Posted October 19, 2013 Hi all. I am now getting very frustrated at the current batch of coasters I am receiving on burns which I never got before. I burn on both single (25gb) and dual layer (50gb) BD-R's mostly with Verbatim high quality JP Bluray discs which were always successful before. Now they are seriously pissing me off. I have 6 50gb dual layer Verbatims left Today I brought a batch of 20 TDK 50gb high quality JP BD-R 50gb dual layer discs, the first disk gave me an error at 2% Help me solve this issue, I have wasted so much money so far. I want a sucessful burn. I noticed the common I/O device error, also the buffer not remaining fully at 100% and importantly the buffers 'needing to recover'. I doubt the issue is the media as its all and always high quality. I have changed the location of the burn, cut ALL background activity, ONLY burn at 2x.....help. Below is the last LOG........ _________________________________________________________________ I 17:13:40 ImgBurn Version 2.5.8.0 started! I 17:13:40 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 17:13:40 Total Physical Memory: 6,200,440 KiB - Available: 4,632,712 KiB I 17:13:40 Initialising SPTI... I 17:13:40 Searching for SCSI / ATAPI devices... I 17:13:44 -> Drive 1 - Info: TSSTcorp DVDWBD TS-LB23D SC02 (D:) (ATAPI) E 17:13:44 DeviceIoControl(IOCTL_USB_GET_NODE_CONNECTION_INFORMATION_EX) Failed! E 17:13:44 Reason: The parameter is incorrect. I 17:13:44 -> Drive 2 - Info: TSSTcorp BDDVDW SE-506BB TS00 (F:) (USB) I 17:13:44 Found 1 BD-ROM/DVD±RW and 1 BD-RE XL! I 17:14:36 Operation Started! I 17:14:36 Building Image Tree... I 17:14:36 Calculating Totals... I 17:14:36 Preparing Image... I 17:14:36 Contents: 30 Files, 16 Folders I 17:14:36 Content Type: Data I 17:14:36 Data Type: MODE1/2048 I 17:14:36 File System(s): UDF (2.50) I 17:14:36 Volume Label: filmpack_hd-040-2013 I 17:14:36 Size: 46,964,082,110 bytes I 17:14:36 Sectors: 22,931,695 I 17:14:36 Image Size: 46,965,260,288 bytes I 17:14:36 Image Sectors: 22,932,256 I 17:14:36 Operation Successfully Completed! - Duration: 00:00:00 I 17:15:08 Operation Started! I 17:15:08 Building Image Tree... I 17:15:08 Calculating Totals... I 17:15:08 Preparing Image... I 17:15:09 Contents: 30 Files, 16 Folders I 17:15:09 Content Type: Data I 17:15:09 Data Type: MODE1/2048 I 17:15:09 File System(s): UDF (2.50) I 17:15:09 Volume Label: filmpack_hd-040-2013 I 17:15:09 Size: 46,964,082,110 bytes I 17:15:09 Sectors: 22,931,695 I 17:15:09 Image Size: 46,965,260,288 bytes I 17:15:09 Image Sectors: 22,932,256 I 17:15:10 Operation Successfully Completed! - Duration: 00:00:01 I 17:15:10 Operation Started! I 17:15:10 Source File: -==/\/[bUILD IMAGE]\/\==- I 17:15:10 Source File Sectors: 22,932,256 (MODE1/2048) I 17:15:10 Source File Size: 46,965,260,288 bytes I 17:15:10 Source File Volume Identifier: filmpack_hd-040-2013 I 17:15:10 Source File Volume Set Identifier: 435389E4015DEA8F I 17:15:10 Source File Application Identifier: ImgBurn v2.5.8.0 I 17:15:10 Source File Implementation Identifier: ImgBurn I 17:15:10 Source File File System(s): UDF (2.50) I 17:15:10 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506BB TS00 (F:) (USB) I 17:15:10 Destination Media Type: BD-R (Disc ID: TDKBLD-RFB-000) I 17:15:10 Destination Media Supported Write Speeds: 2x, 4x I 17:15:10 Destination Media Sectors: 24,438,784 I 17:15:10 Write Mode: BD I 17:15:10 Write Type: DAO I 17:15:10 Write Speed: 2x I 17:15:10 Hardware Defect Management Active: No I 17:15:10 BD-R Verify Not Required: Yes I 17:15:10 Link Size: Auto I 17:15:10 Lock Volume: Yes I 17:15:10 Test Mode: No I 17:15:10 OPC: No I 17:15:10 BURN-Proof: Enabled I 17:15:10 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x) I 17:16:06 Filling Buffer... (72 MiB) I 17:16:08 Writing LeadIn... I 17:16:12 Writing Session 1 of 1... (1 Track, LBA: 0 - 22932255) I 17:16:12 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22932255) I 17:16:12 Writing Layer 0... (LBA: 0 - 12219391) W 17:18:07 Failed to Write Sectors 552416 - 552447 - Reason: Write Error W 17:18:07 Retrying (1 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (2 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (3 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (4 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (5 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (6 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (7 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (8 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (9 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (10 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (11 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (12 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (13 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (14 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (15 of 20)... W 17:18:16 Retry Failed - Reason: Invalid Address For Write W 17:18:16 Retrying (16 of 20)... W 17:18:17 Retry Failed - Reason: Invalid Address For Write W 17:18:17 Retrying (17 of 20)... W 17:18:17 Retry Failed - Reason: Invalid Address For Write W 17:18:17 Retrying (18 of 20)... W 17:18:17 Retry Failed - Reason: Invalid Address For Write W 17:18:17 Retrying (19 of 20)... W 17:18:17 Retry Failed - Reason: Invalid Address For Write W 17:18:17 Retrying (20 of 20)... W 17:18:17 Retry Failed - Reason: Invalid Address For Write E 17:18:33 Failed to Write Sectors 552416 - 552447 - Reason: Write Error E 17:18:33 Next Writable Address: 0 I 17:18:33 Synchronising Cache... I 17:18:40 Closing Track... I 17:18:41 Finalising Disc... E 17:19:09 Failed to Write Image! I 17:19:09 Exporting Graph Data... I 17:19:09 Graph Data File: C:\Users\ED2K11\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_BDDVDW_SE-506BB_TS00_19-OCTOBER-2013_17-15_TDKBLD-RFB-000_2x.ibg I 17:19:09 Export Successfully Completed! E 17:19:09 Operation Failed! - Duration: 00:03:58 I 17:19:09 Average Write Rate: 7,891 KiB/s (1.8x) - Maximum Write Rate: 9,734 KiB/s (2.2x) Link to comment Share on other sites More sharing options...
jimmy2times Posted October 19, 2013 Author Share Posted October 19, 2013 I have just tried another burn (UK time 6pm) at 4x speed with my dwindling stock of Verbatim BD 50 GB discs. It went to 50% then fail Here was the dreaded error I got So disappointing. Another batch of money down the drain!!!!! I noticed the 'buffer' moving from 99% to 100% frequently during the burn and also the the 'device buffer' moving from around 99% to 100%. And the write speed periodically dropping as the disc spinning noise increased then decreased. Help appreciated.. HERE (BELOW) IS THE LOG FOR THE BURN (COASTER) I HAVE JUST NOW HAD. I 17:47:10 ImgBurn Version 2.5.8.0 started! I 17:47:10 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 17:47:10 Total Physical Memory: 6,200,440 KiB - Available: 3,714,940 KiB I 17:47:10 Initialising SPTI... I 17:47:10 Searching for SCSI / ATAPI devices... I 17:47:10 -> Drive 1 - Info: TSSTcorp DVDWBD TS-LB23D SC02 (D:) (ATAPI) E 17:47:10 DeviceIoControl(IOCTL_USB_GET_NODE_CONNECTION_INFORMATION_EX) Failed! E 17:47:10 Reason: The parameter is incorrect. I 17:47:10 -> Drive 2 - Info: TSSTcorp BDDVDW SE-506BB TS00 (F:) (USB) I 17:47:10 Found 1 BD-ROM/DVD±RW and 1 BD-RE XL! I 17:47:14 Operation Started! I 17:47:15 Building Image Tree... I 17:47:15 Calculating Totals... I 17:47:15 Preparing Image... I 17:47:15 Contents: 30 Files, 16 Folders I 17:47:15 Content Type: Data I 17:47:15 Data Type: MODE1/2048 I 17:47:15 File System(s): UDF (2.50) I 17:47:15 Volume Label: [Not Configured] I 17:47:15 Size: 46,964,082,110 bytes I 17:47:15 Sectors: 22,931,695 I 17:47:15 Image Size: 46,965,260,288 bytes I 17:47:15 Image Sectors: 22,932,256 I 17:47:15 Operation Successfully Completed! - Duration: 00:00:00 I 17:47:40 Operation Started! I 17:47:40 Building Image Tree... I 17:47:40 Calculating Totals... I 17:47:40 Preparing Image... I 17:47:40 Contents: 30 Files, 16 Folders I 17:47:40 Content Type: Data I 17:47:40 Data Type: MODE1/2048 I 17:47:40 File System(s): UDF (2.50) I 17:47:40 Volume Label: filmpack_hd-040-2013 I 17:47:40 Size: 46,964,082,110 bytes I 17:47:40 Sectors: 22,931,695 I 17:47:40 Image Size: 46,965,260,288 bytes I 17:47:40 Image Sectors: 22,932,256 I 17:47:43 Operation Successfully Completed! - Duration: 00:00:03 I 17:47:43 Operation Started! I 17:47:43 Source File: -==/\/[bUILD IMAGE]\/\==- I 17:47:43 Source File Sectors: 22,932,256 (MODE1/2048) I 17:47:43 Source File Size: 46,965,260,288 bytes I 17:47:43 Source File Volume Identifier: filmpack_hd-040-2013 I 17:47:43 Source File Volume Set Identifier: 43538DF4015DEA8F I 17:47:43 Source File Application Identifier: ImgBurn v2.5.8.0 I 17:47:43 Source File Implementation Identifier: ImgBurn I 17:47:43 Source File File System(s): UDF (2.50) I 17:47:43 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506BB TS00 (F:) (USB) I 17:47:43 Destination Media Type: BD-R (Disc ID: MEI-T02-001) I 17:47:43 Destination Media Supported Write Speeds: 2x, 4x I 17:47:43 Destination Media Sectors: 24,438,784 I 17:47:43 Write Mode: BD I 17:47:43 Write Type: DAO I 17:47:43 Write Speed: 4x I 17:47:43 Hardware Defect Management Active: No I 17:47:43 BD-R Verify Not Required: Yes I 17:47:43 Link Size: Auto I 17:47:43 Lock Volume: Yes I 17:47:43 Test Mode: No I 17:47:43 OPC: No I 17:47:43 BURN-Proof: Enabled I 17:47:43 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 17:48:32 Filling Buffer... (72 MiB) I 17:48:32 Writing LeadIn... I 17:48:34 Writing Session 1 of 1... (1 Track, LBA: 0 - 22932255) I 17:48:34 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22932255) I 17:48:34 Writing Layer 0... (LBA: 0 - 12219391) W 18:14:19 Failed to Write Sectors 11651616 - 11651647 - Reason: Write Error W 18:14:19 Retrying (1 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (2 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (3 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (4 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (5 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (6 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (7 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (8 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (9 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (10 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (11 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (12 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (13 of 20)... W 18:14:26 Retry Failed - Reason: Invalid Address For Write W 18:14:26 Retrying (14 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (15 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (16 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (17 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (18 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (19 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write W 18:14:27 Retrying (20 of 20)... W 18:14:27 Retry Failed - Reason: Invalid Address For Write E 18:21:43 Failed to Write Sectors 11651616 - 11651647 - Reason: Write Error E 18:21:43 Next Writable Address: 0 I 18:21:43 Synchronising Cache... W 18:21:46 User opted to skip the 'Close Track/Session/Disc' functions. E 18:21:46 Failed to Write Image! I 18:21:46 Exporting Graph Data... I 18:21:46 Graph Data File: C:\Users\ED2K11\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_BDDVDW_SE-506BB_TS00_19-OCTOBER-2013_17-47_MEI-T02-001_4x.ibg I 18:21:46 Export Successfully Completed! E 18:21:46 Operation Failed! - Duration: 00:34:02 I 18:21:46 Average Write Rate: 11,716 KiB/s (2.7x) - Maximum Write Rate: 17,721 KiB/s (4.0x) Link to comment Share on other sites More sharing options...
jimmy2times Posted October 19, 2013 Author Share Posted October 19, 2013 (edited) The burning drive I utilize is a Samsung Slim SE-506BB USB Blu-ray Writer (which I might add has served me well so far). I am a bit of a n00b when it comes to firmware, havent a clue if it is up-to-date, I am scared of messing up the drive in the process. I will try to upload graphs from previous successful burns (with dual layer 50GB BD-R media) If I can, I have the graph data from these months old burns, just need to get the application to view them. Once again, help would be appreciated Edited October 19, 2013 by jimmy2times Link to comment Share on other sites More sharing options...
jimmy2times Posted October 19, 2013 Author Share Posted October 19, 2013 (edited) Another fail at 2% using TDK Dual layer BD-R media and older portable version of Imgburn, (which always used to give me perfect results on Bluray media) I 00:14:07 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506BB TS00 (M:) (USB) I 00:14:07 Destination Media Type: BD-R (Disc ID: TDKBLD-RFB-00) (Speeds: 2x, 4x) I 00:14:07 Destination Media Sectors: 24,438,784 I 00:14:07 Write Mode: BD I 00:14:07 Write Type: DAO I 00:14:07 Write Speed: 2x I 00:14:07 BD-R FastWrite: No I 00:14:07 Link Size: Auto I 00:14:07 Lock Volume: Yes I 00:14:07 Test Mode: No I 00:14:07 OPC: No I 00:14:07 BURN-Proof: Enabled I 00:15:02 Filling Buffer... (40 MB) I 00:15:03 Writing LeadIn... I 00:15:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 24039807) I 00:15:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24039807) W 00:16:57 Failed to Write Sectors 548288 - 548319 - Reason: Write Error W 00:16:57 Retrying (1 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (2 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (3 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (4 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (5 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (6 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (7 of 20)... W 00:17:04 Retry Failed - Reason: Invalid Address For Write W 00:17:04 Retrying (8 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (9 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (10 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (11 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (12 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (13 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (14 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (15 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (16 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (17 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (18 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (19 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write W 00:17:05 Retrying (20 of 20)... W 00:17:05 Retry Failed - Reason: Invalid Address For Write E 00:17:16 Failed to Write Sectors 548288 - 548319 - Reason: Write Error E 00:17:16 Next Writable Address: 0 I 00:17:16 Synchronising Cache... I 00:17:23 Closing Track... I 00:17:24 Finalising Disc... E 00:18:00 Failed to Write Image! I 00:18:00 Exporting Graph Data... I 00:18:00 Graph Data File: C:\Users\ED2K11\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_BDDVDW_SE-506BB_TS00_20-OCTOBER-2013_00-14_TDKBLD-RFB-00_2x.ibg I 00:18:00 Export Successfully Completed! E 00:18:00 Operation Failed! - Duration: 00:03:52 I 00:18:00 Average Write Rate: 8,370 KB/s (1.9x) - Maximum Write Rate: 11,580 KB/s (2.6x) Edited October 19, 2013 by jimmy2times Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 20, 2013 Share Posted October 20, 2013 If your drive is failing to burn various different disc MIDs, it's probably the drive at fault. Link to comment Share on other sites More sharing options...
jimmy2times Posted October 20, 2013 Author Share Posted October 20, 2013 Strange, it is a concern I have had. It worked so well up until 2 weeks ago. Might it have come to the end of its useful life after only a couple of months? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 20, 2013 Share Posted October 20, 2013 They shouldn't die that quickly, no. As such, just return it under warranty and get them to replace it. Link to comment Share on other sites More sharing options...
jimmy2times Posted October 22, 2013 Author Share Posted October 22, 2013 (edited) It must be the drive/writer casing the issue because I have just had another failed burn due to 'write error' on a NEW batch (5 pack) of 50gb Verbatims - mid code: VERBAT IMf (000) - I brought from PC world for £40. "VERBAT IMf (000)" never gave me problems before and it is the best of the best singaporian quality verbs, none of that Chinese or Indonesian manufactured crap. I ask you LIGHTNING UK or anyone else, are drives known to be the source of burn problems, ie write errors and such? My drive occasionally clicks during burns and as its about to spit out a coaster, splutters and wheezes like an antiquated car engine. I have just purchased a new pioneer external Bluray writer, which has got good feedback and updatable firmware seemingly unlike the samsung one I have. Do you think this will help? If not what other things could be causing this, because like I said I simply did not have such issues a few weeks back. I will be VERY ANGRY if I get more fails and coasters. Will post back to let you know if its the case and subsequently seek help. Thanks for reading Edited October 22, 2013 by jimmy2times Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 23, 2013 Share Posted October 23, 2013 Drive and media combos aren't just known to be the cause of 'write errors', they're the only things that can cause them! During the burn, all software does is send a chunk of data to the drive, telling it which sector it should write it to.... that's it. It's then 100% down to the drive (and its firmware) to actually burn the data to the disc. If you get a 'write error', the drive had some problem burning to the disc and that can only ever be down to the drive/media combo. If one is good (the media in your case), the other must be bad. Link to comment Share on other sites More sharing options...
jimmy2times Posted October 23, 2013 Author Share Posted October 23, 2013 Thanks for the answer LighteningUK, I will report back after a burn on the new drive when it arrives tomorrow. In the meantime, do you recommend particular settings on your application (imgburn)? A burning speed? Anything that will aid a good burn! I have heard about 'safe mode' burning but have never done it. Anything tips/settings before I commit to another expensive disc, albeit on the new drive Cheers again. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 23, 2013 Share Posted October 23, 2013 I always use the default settings.... that's why they're the defaults. If you have to resort to safe mode in order to burn successfully, there's something very wrong with your system. I've never had to do it. As for the burn speed... well that depends on the discs you're using and what the drive offers on them. You should at least be safe at their rated speed. Sometimes faster or slower speeds can actually improve the burn quality, but really that's just down to how the firmware has been tweaked. You'd have to burn a disc at each supported speed, scan the discs (disc quality / PIPO) and see which produced the best result. Link to comment Share on other sites More sharing options...
jimmy2times Posted October 29, 2013 Author Share Posted October 29, 2013 I have my new pioneer drive which has been great so far! I just updated the firmware as well last night! LIGHTINGUK, I was wondering if you could interpret the following graph for me, its a recent 'successful' burn! Also, lastly could you recommend a good software to check the validity of burns as opposed to DVDINFOPRO, mine is a trail and is running out soon, plus I cant seem to do the 'pipo' scanning thing on my copy. Cheers for all your help so far Regards Link to comment Share on other sites More sharing options...
Recommended Posts