BlizzardUK

Excellent, that worked, thanks. I replaced the robot files from that link you gave in to the IMGBurn directory, so I overwrote the ones already in that directory with the new ones, and it now works without an error, big thanks !!

Thanks. The assistant just pops up and tells me to restart, or continue, or close. Everytime the app loads it comes up, but allows me to continue. I also use PTPublisher, but that seems fine, so I know the Bravo 2 is working okay. I have tried multiple compatibility options and admin and so on, still get the crash, weird. I will give the new drivers a go.

It lets me continue using the software by the way (if I click continue), I think it just stops the Bravo being used. Hope this helps (bottom part in bold is what appeared after I clicked F8 and searched)........ I 04:21:23 ImgBurn Version 2.5.8.0 started! I 04:21:23 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 04:21:23 Total Physical Memory: 16,735,172 KiB - Available: 6,244,560 KiB I 04:21:23 Initialising PTRobot... I 04:21:23 PT_SDK Version 1.6.2.0 I 04:21:23 Initialising SPTI... I 04:21:23 Searching for Auto Loader devices... E 04:21:25 Device->Initialise() Runtime Exception! E 04:21:25 Device: Disc Publisher II 1.43 03/19/2008 E 04:21:25 Exception: EAccessViolation E 04:21:25 This auto-loader will not be visible in the program. E 04:21:25 Device->Initialise() Failed! E 04:21:25 Device: Disc Publisher II 1.43 03/19/2008 E 04:21:25 This auto-loader will not be visible in the program. I 04:21:25 Found 0 Auto Loaders! I 04:21:25 Searching for SCSI / ATAPI devices... I 04:21:25 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA) I 04:21:26 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0) I 04:21:26 -> Drive 3 - Info: ATAPI eHBU312 2 VL16 (T:) (USB 2.0) I 04:21:26 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI) I 04:21:26 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 2 BD-REs! W 04:21:28 I/O Interface 'Debug Mode' has been Enabled! I 04:21:42 Searching for Auto Loader devices... D 04:21:42 PTRobot_EnumRobots - Robot Count: 1, Return Code: 0 I 04:21:42 Initialising Device (Auto Loader 1)... D 04:21:42 PTRobot_GetRobotInfo - Robot: 0x20000001, Return Code: 0 D 04:21:42 Robot Handle: 0x20000001 - Model: Disc Publisher II, Version: 1.43 03/19/2008 date/time : 2019-01-28, 04:21:42, 126ms computer name : INTEL-PC user name : edited operating system : Windows 8 x64 build 9200 system language : English system up time : 18 days 8 hours program up time : 21 seconds processors : 8x Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz physical memory : 6003/16343 MB (free/total) free disk space : (C:) 51.49 GB display mode : 1920x1080, 32 bit process id : $fb1c allocated memory : 65.43 MB executable : ImgBurn.exe exec. date/time : 2013-05-24 09:59 version : 2.5.8.0 compiled with : BCB 2006/07 madExcept version : 4.0.7 callstack crc : $0ba3c082, $be1836ba, $85b7b862 contact name : edited contact email : edited exception number : 2 exception class : EAccessViolation exception message : EAccessViolation. thread $e8e4 (TInterfaceThread): 0ba3c082 +ad17 PTRobot.dll 0ba367d6 +533a PTRobot.dll PTRobot_EnumDrives 00587016 +0742 ImgBurn.exe DeviceIO.cpp 8840 +92 TDevice.Initialise_AutoLoader_PTROBOT 00584b25 +0029 ImgBurn.exe DeviceIO.cpp 8489 +14 TDevice.Initialise_AutoLoader 005833a3 +0023 ImgBurn.exe DeviceIO.cpp 8140 +14 TDevice.Initialise 0057187a +04ce ImgBurn.exe DeviceIO.cpp 4143 +46 InitialiseDevices_AutoLoaders_PTROBOT 0056ff7a +0026 ImgBurn.exe DeviceIO.cpp 3910 +19 InitialiseDevices_AutoLoaders 005629f5 +013d ImgBurn.exe DeviceIO.cpp 1480 +49 InitialiseDevices 0071d156 +005e ImgBurn.exe InterfaceThread.cpp 2000 +14 TInterfaceThread.SearchForDevices 00715e79 +029d ImgBurn.exe InterfaceThread.cpp 155 +76 TInterfaceThread._DoInterface 00715b35 +001d ImgBurn.exe InterfaceThread.cpp 35 +6 TInterfaceThread.Execute 00a46edb +002b ImgBurn.exe madExcept _17342 008d8b98 +0034 ImgBurn.exe Classes _17197 008f73c8 +0028 ImgBurn.exe System _16782 00a46dbd +000d ImgBurn.exe madExcept _17340 00a46e27 +0037 ImgBurn.exe madExcept _17341 74188482 +0022 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 00715a4a +0032 ImgBurn.exe InterfaceThread.cpp 21 +0 TInterfaceThread.Create main thread ($5e74): 0095e955 +12d ImgBurn.exe Forms TApplication.Idle 0095dd43 +017 ImgBurn.exe Forms TApplication.HandleMessage 0095e02b +0b3 ImgBurn.exe Forms TApplication.Run 0070c459 +5e5 ImgBurn.exe ImgBurn.cpp 272 +166 WinMain 00a80acc +14c ImgBurn.exe __startup 74188482 +022 KERNEL32.DLL BaseThreadInitThunk thread $ef40: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $fa80: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $fe48: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $6e84: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $dc1c: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $4150: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $ef8: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $e84: 739d597d +12d KERNELBASE.dll WaitForMultipleObjectsEx 00a46dbd +00d ImgBurn.exe madExcept _17340 00a46e27 +037 ImgBurn.exe madExcept _17341 74188482 +022 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 73e0ed63 +000 combase.dll thread $db40 (TWorkerThread): 739c45f3 +93 KERNELBASE.dll WaitForSingleObjectEx 739c454d +0d KERNELBASE.dll WaitForSingleObject 009de881 +19 ImgBurn.exe Virtualtrees _16776 00a46edb +2b ImgBurn.exe madExcept _17342 008d8b98 +34 ImgBurn.exe Classes _17197 008f73c8 +28 ImgBurn.exe System _16782 00a46dbd +0d ImgBurn.exe madExcept _17340 00a46e27 +37 ImgBurn.exe madExcept _17341 74188482 +22 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 009de776 +16 ImgBurn.exe Virtualtrees _16772 modules: 00400000 ImgBurn.exe 2.5.8.0 C:\Program Files (x86)\ImgBurn 0af60000 stcd3control.dll 5.2.707.0 C:\Program Files (x86)\Common Files\SureThing Shared 0ba30000 PTRobot.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0bd90000 PTRobotDPPRO.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0c030000 idmmkb.dll 6.19.9.1 C:\Program Files (x86)\Internet Download Manager 0c720000 PTRobotDP.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0c8d0000 PTRobotStr.DLL 1.1.4.0 C:\Program Files (x86)\ImgBurn 0c9a0000 PTRobotDPse.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0cb40000 PTRobot4100.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0fa00000 CoreMessaging.dll 6.2.17134.471 C:\WINDOWS\System32 0ff40000 CoreUIComponents.dll 6.2.17134.376 C:\WINDOWS\System32 2ffb0000 TextInputFramework.dll 6.2.17134.376 C:\WINDOWS\System32 54260000 tiptsf.dll 6.2.17134.191 C:\Program Files (x86)\Common Files\microsoft shared\ink 544f0000 explorerframe.dll 6.2.17134.1 C:\WINDOWS\system32 5dc10000 MSACM32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 63d10000 oledlg.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 63eb0000 wintypes.dll 6.2.17134.523 C:\WINDOWS\SYSTEM32 65110000 SHFOLDER.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 66f60000 twinapi.appcore.dll 6.2.17134.137 C:\WINDOWS\system32 670d0000 dcomp.dll 6.2.17134.1 C:\WINDOWS\system32 67210000 WindowsCodecs.dll 6.2.17134.345 C:\WINDOWS\SYSTEM32 67f60000 quartz.dll 6.2.17134.1 C:\WINDOWS\system32 68110000 d3d11.dll 6.2.17134.441 C:\WINDOWS\system32 6a280000 SPINF.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a300000 drvstore.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a450000 DEVRTL.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a610000 pdh.dll 6.2.17134.1 C:\WINDOWS\system32 6a660000 OLEACC.dll 7.2.17134.1 C:\WINDOWS\SYSTEM32 6a960000 dxgi.dll 6.2.17134.112 C:\WINDOWS\system32 6aa60000 RMCLIENT.dll 6.2.17134.471 C:\WINDOWS\system32 6aa80000 dataexchange.dll 6.2.17134.1 C:\WINDOWS\system32 6aba0000 olepro32.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6c280000 MSIMG32.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6cd90000 gdiplus.dll 6.2.17134.523 C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.17134.523_none_73d8c7959f75cd2a 6ffa0000 DEVOBJ.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70030000 dbgcore.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70060000 dbghelp.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 701f0000 SRVCLI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70210000 FaultRep.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70270000 NETUTILS.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70300000 ntmarta.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70330000 WKSCLI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70c90000 dwmapi.dll 6.2.17134.1 C:\WINDOWS\system32 70cc0000 uxtheme.dll 6.2.17134.1 C:\WINDOWS\system32 70d40000 winmmbase.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70e60000 PROPSYS.dll 7.0.17134.112 C:\WINDOWS\SYSTEM32 70fe0000 bcrypt.dll 6.2.17134.112 C:\WINDOWS\SYSTEM32 71190000 Mpr.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 71880000 WINMM.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 719f0000 WINSPOOL.DRV 6.2.17134.319 C:\WINDOWS\SYSTEM32 71c70000 COMCTL32.DLL 6.10.17134.523 C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.523_none_42edd4b044e3535c 71e80000 NETAPI32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 71ea0000 WSOCK32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 72690000 IPHLPAPI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 726c0000 VERSION.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 73300000 Userenv.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 738a0000 CRYPTBASE.dll 6.2.17134.1 C:\WINDOWS\System32 738b0000 SspiCli.dll 6.2.17134.376 C:\WINDOWS\System32 738d0000 KERNELBASE.dll 6.2.17134.441 C:\WINDOWS\System32 73b20000 msvcrt.dll 7.0.17134.1 C:\WINDOWS\System32 73be0000 ucrtbase.dll 6.2.17134.319 C:\WINDOWS\System32 73d00000 WS2_32.dll 6.2.17134.1 C:\WINDOWS\System32 73d70000 combase.dll 6.2.17134.523 C:\WINDOWS\System32 73fd0000 clbcatq.dll 2001.12.10941.16384 C:\WINDOWS\System32 740c0000 ADVAPI32.DLL 6.2.17134.471 C:\WINDOWS\System32 74140000 IMM32.DLL 6.2.17134.1 C:\WINDOWS\System32 74170000 KERNEL32.DLL 6.2.17134.1 C:\WINDOWS\System32 74250000 FLTLIB.DLL 6.2.17134.1 C:\WINDOWS\System32 74260000 gdi32full.dll 6.2.17134.471 C:\WINDOWS\System32 743d0000 sechost.dll 6.2.17134.319 C:\WINDOWS\System32 74420000 windows.storage.dll 6.2.17134.471 C:\WINDOWS\System32 749e0000 SHLWAPI.dll 6.2.17134.1 C:\WINDOWS\System32 74a30000 SHELL32.dll 6.2.17134.441 C:\WINDOWS\System32 75d80000 USER32.dll 6.2.17134.376 C:\WINDOWS\System32 75f10000 MSASN1.dll 6.2.17134.1 C:\WINDOWS\System32 75fb0000 shcore.dll 6.2.17134.112 C:\WINDOWS\System32 76040000 setupapi.dll 6.2.17134.1 C:\WINDOWS\System32 76470000 kernel.appcore.dll 6.2.17134.112 C:\WINDOWS\System32 76480000 RPCRT4.dll 6.2.17134.471 C:\WINDOWS\System32 76540000 COMDLG32.DLL 6.2.17134.1 C:\WINDOWS\System32 76620000 MSCTF.dll 6.2.17134.376 C:\WINDOWS\System32 76770000 msvcp_win.dll 6.2.17134.1 C:\WINDOWS\System32 767f0000 PSAPI.DLL 6.2.17134.1 C:\WINDOWS\System32 76810000 OLEAUT32.DLL 6.2.17134.48 C:\WINDOWS\System32 768b0000 CRYPT32.dll 6.2.17134.1 C:\WINDOWS\System32 76ab0000 OLE32.DLL 6.2.17134.407 C:\WINDOWS\System32 76bb0000 cfgmgr32.dll 6.2.17134.1 C:\WINDOWS\System32 76d60000 WINTRUST.dll 6.2.17134.81 C:\WINDOWS\System32 76db0000 GDI32.dll 6.2.17134.285 C:\WINDOWS\System32 76de0000 win32u.dll 6.2.17134.1 C:\WINDOWS\System32 76e00000 profapi.dll 6.2.17134.1 C:\WINDOWS\System32 76e20000 bcryptPrimitives.dll 6.2.17134.471 C:\WINDOWS\System32 76eb0000 powrprof.dll 6.2.17134.1 C:\WINDOWS\System32 76ff0000 ntdll.dll 6.2.17134.471 C:\WINDOWS\SYSTEM32 771b0000 mscms.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 77e00000 ColorAdapterClient.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 7c000000 MSVCR70.dll 7.0.9466.0 C:\WINDOWS\SYSTEM32 disassembling: [...] 00586fec call +$4f059f ($a77590) ; memset 00586ff1 add esp, $c 00586ff4 8840 lea eax, [ebp-$324] 00586ffa 8838 mov dword ptr [ebp-$324], $a 00587004 8840 push eax 00587005 lea edx, [ebp-$724] 0058700b push edx 0058700c mov ecx, [ebp+8] 0058700f mov eax, [ecx+$22c] 00587015 push eax 00587016 > call dword ptr [$b38acc] ; PTRobot_EnumDrives (PTRobot.dll) 0058701c mov ebx, eax 0058701e 8842 mov al, [$ce7ae8] 00587023 test al, al 00587025 jz loc_587276 0058702b 8844 mov word ptr [ebp-$308], $a8 00587034 lea eax, [ebp-$78] 00587037 call -$183450 ($403bec) ; dstring.h.System.AnsiString.Create 0058703c push eax 0058703d lea eax, [ebp-$74] 00587040 inc dword ptr [ebp-$2fc] [...]

For some odd reason, even though I have used ImgBurn and my Primera Bravo for years, in the last 2 weeks I have started to get an error on loading of ImgBurn. Any ideas ? I get an "assistant" thing pop up at the start, not sure if it is from imgburn or windows. I 01:27:38 ImgBurn Version 2.5.8.0 started! I 01:27:38 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 01:27:38 Total Physical Memory: 16,735,172 KiB - Available: 5,421,156 KiB I 01:27:38 Initialising PTRobot... I 01:27:38 PT_SDK Version 1.6.2.0 I 01:27:38 Initialising SPTI... I 01:27:38 Searching for Auto Loader devices... E 01:29:30 Device->Initialise() Runtime Exception! E 01:29:30 Device: Disc Publisher II 1.43 03/19/2008 E 01:29:30 Exception: EAccessViolation E 01:29:30 This auto-loader will not be visible in the program. E 01:29:30 Device->Initialise() Failed! E 01:29:30 Device: Disc Publisher II 1.43 03/19/2008 E 01:29:30 This auto-loader will not be visible in the program. I 01:29:30 Found 0 Auto Loaders! I 01:29:30 Searching for SCSI / ATAPI devices... I 01:29:30 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA) I 01:29:30 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0) I 01:29:31 -> Drive 3 - Info: ATAPI eHBU312 2 VL16 (T:) (USB 2.0) I 01:29:31 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI) I 01:29:31 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 2 BD-REs!

I have a Bravo II, is there any way to use IMGBurn to batch ISO up unprotected DVDs ? So if I were to put 25 DVDs in the hopper and then have IMGBurn just tell Bravo II to create an ISO of each one ? I don't care what it names each one, as I can rename them later. I have the Auto Changer DLL's installed and have selected the Bravo. I can move one at a time, but can it batch ? EDIT : I think I am getting to grips with it now. Have to shoot off to bed but will carry on testing tomorrow, I have done 2 in a row so I think I have the hang of it now.

.....it takes ages as the buffers need to recover. I can't understand it. I have 2 IMG Burns running, and I have BD-ISOs on one HD. Sometimes 2 BD-ISOs can burn perfectly fine with no buffer problems, and other times it comes up with a "waiting for buffers to recover" message every minute or so. The confusing thing is all BD ISOs are on the same drive, so why does it sometimes make a difference ? I tried to increase the buffer to 600mb but it didn't seem to help. I burn both at 4x so they are not going too fast. One BD drive is external USB3 and the other BD drive internal SATA. My internal HD is SATA. Any ideas what I can do ? Thanks.

The problem is the drive is 9tb with the entire RAID array and the speed is not going any higher than 5MB, to read and write that I would be there for over a week. I started off the test and saw the Highpoint RocketRaid log at the same time and it started to come up with errors on drive 2 again. So I am going to replace drive 2 and see what happens. Highpoint support say I am wrong for using desktop drives in a RAID5 array and that is the reason. I have bought a 3TB NAS drive to replace but I feel now I have probably made a mistake as 1 drive will now be different.

Thanks. It is very strange, all seems fine except for the log info, which said about bad sectors, the time looks to be the same as when I was burning the above disc, but the rest of the screens show the drives to be fine with no errors. I have done short life tests on all drives and they are fine. See all screen shots below. ==================================================================================================================== This first screenshot shows poor read and write speeds from the RAID array........ ==================================================================================================================== This screenshot shows the sector errors that seemed to happen at same time as disc burning and copying........ ==================================================================================================================== This shows that everything seems to appear to be ok, smart wise. I don't know why this shows up as "None" for bad sectors as the log (above screenshot) shows fixed errors. ==================================================================================================================== General overview........ ==================================================================================================================== Options I have........

EDIT : I have just noticed my RAID5 array is running at a max of 6MB/Sec as I tried to copy a folder to another drive. I presume that is the reason for the below problem ? Any ideas ? -------------------- If I try and burn discs from my RAID5 drives, which I use as ISO archives, the burn takes ages as the buffer keeps going down. The stranger thing is it used to work I am sure. I am using Windows 7. 4x 3TB Raid Drives using a RocketRaid card. Intel i7. 16gb Ram. 64bit. Any ideas ? Thanks. I 03:39:42 ImgBurn Version 2.5.8.0 started! I 03:39:42 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 03:39:42 Total Physical Memory: 16,735,740 KiB - Available: 12,207,572 KiB I 03:39:42 Initialising SPTI... I 03:39:42 Searching for SCSI / ATAPI devices... I 03:39:42 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (I:) (SATA) I 03:39:42 -> Drive 2 - Info: ATAPI eHBU312 2 VL16 (L:) (USB 3.0) I 03:39:42 Found 2 BD-REs! I 03:39:49 Operation Started! I 03:39:49 Source File: H:\ISO Images\XXXXX\XXXX\XXXXX.iso I 03:39:49 Source File Sectors: 2,200,416 (MODE1/2048) I 03:39:49 Source File Size: 4,506,451,968 bytes I 03:39:49 Source File Volume Identifier: DVD I 03:39:49 Source File Volume Set Identifier: 40231ED7RDUS0004 I 03:39:49 Source File Implementation Identifier: Ulead Systems USA Inc. I 03:39:49 Source File File System(s): ISO9660, Joliet, UDF (1.02) I 03:39:49 Destination Device: [0:0:0] ATAPI eHBU312 2 VL16 (L:) (USB) I 03:39:49 Destination Media Type: DVD-R (Disc ID: RITEKG05) I 03:39:49 Destination Media Supported Write Speeds: 6x, 8x I 03:39:49 Destination Media Sectors: 2,298,496 I 03:39:49 Write Mode: DVD I 03:39:49 Write Type: DAO I 03:39:49 Write Speed: 8x I 03:39:49 Link Size: Auto I 03:39:49 Lock Volume: Yes I 03:39:49 Test Mode: No I 03:39:49 OPC: No I 03:39:49 BURN-Proof: Enabled I 03:39:50 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 03:39:51 Filling Buffer... (253 MiB) I 03:41:18 Writing LeadIn... I 03:42:32 Writing Session 1 of 1... (1 Track, LBA: 0 - 2200415) I 03:42:32 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2200415) W 03:45:00 Waiting for buffers to recover... (LBA: 408800) I 03:45:36 Writing Sectors... W 03:46:57 Waiting for buffers to recover... (LBA: 727712) I 03:48:09 Writing Sectors... W 03:50:55 Waiting for buffers to recover... (LBA: 1003712) I 03:51:53 Writing Sectors... W 03:53:25 Waiting for buffers to recover... (LBA: 1326592) I 03:54:16 Writing Sectors... W 03:55:28 Waiting for buffers to recover... (LBA: 1578080) I 03:56:04 Writing Sectors... W 03:58:59 Waiting for buffers to recover... (LBA: 2110720) I 04:00:11 Writing Sectors... I 04:00:33 Synchronising Cache... I 04:00:49 Exporting Graph Data... I 04:00:49 Graph Data File: C:\Users\XXXXXX\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_eHBU312_2_VL16_28-APRIL-2015_03-39_RITEKG05_8x.ibg I 04:00:49 Export Successfully Completed! I 04:00:49 Operation Successfully Completed! - Duration: 00:21:00 I 04:00:49 Average Write Rate: 4,074 KiB/s (3.0x) - Maximum Write Rate: 12,977 KiB/s (9.6x)

Just went to burn a home made BD ISO which is 25,025,314,816 in size. My disc says it is 25,138,692,096 so will need to overburn or truncate. Any idea which I should choose to get all the data on the disc ? Or will there definitely be some loss of data ? Thanks.

Thanks. I will try the USB selective suspend option. Yes, it is connected via USB to a docking station style dock. Thanks for advice. Still can't understand though why Windows can't recognise the drive is being used as it is being read from.

I am recording DL-BD-Rs which take a good while to record, and sometimes I will come back to my PC during burning and find words to the effect of "failed to read from file : xxxxxxx.iso", giving me the option to retry. If I click retry nothing happens as the file still isn't there, but if I navigate to my external HDD in Windows Explorer, then wait 5 to 10 seconds for it to come alive again, then it is fine. I am taking a shot in the dark that Windows is putting it in power down or idle mode. I have told the power settings to to never turn off hard disks. So what is going on ? Also why isn't Windows 7 smart enough to know the drive is being used by IMG Burn so to keep the drive alive ? Surely reading from the drive is using it ? But maybe I am wrong in presuming it is down to power down, but the fact I can carry on burning when I click on the drive in Windows Explorer must mean it is being re-powered up or something. Any ideas how to keep the external HDD alive without being at the PC myself ?

Thanks. Does this mean it is managing to unlock the drive even though IMGBurn has locked it ? If you are ever bored and want to experiment, then they do trials of their software (Mastering Works 5, Authoring Works 5, and Smart Renderer 4), all three of those cause it.

I use IMGBurn version 2.5.7.0 on a Windows 7 64bit PC. My problem is that when trying to multi-task by using certain other software it will cause IMGBurn to finish a disc early but it makes out is has burnt correctly, when it hasn't. The culprits seem to be TMPGenc software, not just one of theirs, but any of theirs you can burn discs with. I often burn dual layers while making the next one in the TMPGenc software, to save on time. However if I am burning a disc in IMGBurn then get to the write page in TMPGEnc then the IMGBurn write will stop and say it has completed. Quite often I will have 20 dual layer discs to burn in a row, so if I don't multi-task then it can be 10 hours before I can use the PC again. Any ideas ? The log of the last incident it happened is below. The usual time for a burn of this type is 27 minutes, 15 minutes was far too quick and I remember it happening when it wasn't near the end in percentage. I 05:31:58 Operation Started! I 05:31:58 Source File: H:\ISO Images\DLfile.iso I 05:31:58 Source File Sectors: 3,773,168 (MODE1/2048) I 05:31:58 Source File Size: 7,727,448,064 bytes I 05:31:58 Source File Volume Identifier: DVDLabel I 05:31:58 Source File Volume Set Identifier: 3CEC2239RDUS0004 I 05:31:58 Source File Implementation Identifier: Ulead Systems USA Inc. I 05:31:58 Source File File System(s): ISO9660, Joliet, UDF (1.02) I 05:31:58 Destination Device: [0:0:0] ATAPI eHBU312 2 VL12 (J:) (USB) I 05:31:58 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) I 05:31:58 Destination Media Supported Write Speeds: 4x, 6x, 8x I 05:31:58 Destination Media Sectors: 4,173,824 I 05:31:58 Write Mode: DVD I 05:31:58 Write Type: DAO I 05:31:58 Write Speed: 4x I 05:31:58 DVD+R DL Reserve Track: No I 05:31:58 Link Size: Auto I 05:31:58 Lock Volume: Yes I 05:31:58 Test Mode: No I 05:31:58 OPC: No I 05:31:58 BURN-Proof: Enabled I 05:32:00 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x) I 05:32:03 Optimal L1 Data Zone Start LBA: 1973216 (VTS_02, PGC: 13, Cell: 1, Vob/Cell ID: 13/1, Time: 00:00:00, SPLIP: No -> Yes) I 05:32:03 Optimal L0 Data Zone Capacity: 1,973,216 I 05:32:03 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set I 05:32:39 Set L0 Data Zone Capacity Succeeded! I 05:32:39 Filling Buffer... (253 MB) I 05:32:40 Writing LeadIn... I 05:32:41 Writing Session 1 of 1... (1 Track, LBA: 0 - 3773167) I 05:32:41 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3773167) I 05:32:41 Writing Layer 0... (LBA: 0 - 1973215) I 05:44:49 Writing Layer 1... (LBA: 1973216 - 3773167) I 05:47:09 Synchronising Cache... I 05:47:10 Closing Track... I 05:47:11 Finalising Disc... I 05:47:12 Exporting Graph Data... I 05:47:12 Graph Data File: C:\Users\My Name\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_eHBU312_2_VL12_26-JULY-2013_05-31_MKM-003-00_4x.ibg I 05:47:12 Export Successfully Completed! I 05:47:12 Operation Successfully Completed! - Duration: 00:15:14 I 05:47:12 Average Write Rate: 8,703 KB/s (6.3x) - Maximum Write Rate: 348,964 KB/s (252.0x) I 05:47:26 Close Request Acknowledged I 05:47:26 Closing Down... I 05:47:26 Shutting down SPTI... I 05:47:26 ImgBurn closed!

For the last 5+ years I have always made dual layer discs with Verbatims, the tried and tested, always work. However, I noticed today Falcon Pro Media have some dual layers, I swear by them for single layer DVDs. They are £45 for 100. What quality are these if you have seen or used them ? http://www.rivieramultimedia.co.uk/PBSCProduct.asp?ItmID=11422935

Thanks.The problem about energy saving is it happens at the same point, between 7 and 10% each time, so doesn't seem to be triggered by time. Also I can power it on and then straight away try to copy the folders and it will still happen. I have made sure I have "turn hard disks off" on "0" which puts it at "never". I have also changed the energy to not suspend USB. Everything works fine in the other PC, so it must be motherboard related but I am not sure how. I downloaded HD Tune and it instantly gives me a read error, not even 1 second in, it says "Read Error! Test Aborted" as soon as I click "Read Test" (although that may be because the drive is empty due to no data being able to be copied, unless it can read without data being on there). All internal drives work. I did a write test by deleting the partition, it got to 100mb on the graph and then gave a write error. I also just tried to copy the folder over manually to the HDD and I got the same error, drive doesn't exist, after about 10 seconds of copying. So I guess IMGBurn is just doing the same as what happens by Windows Explorer. For some odd reason I can't copy anything to the external drives without this error. Any other idea what it could be ? I am really stuck on what to do. I understand this is not an IMGBurn problem, but if you have any other ideas, it would be great, as I have many BD folders I need to put to disk. I know I could put the external drive inside, but there must be another way. Should I contact Gigabyte, or Scan where I got it from ? They pre-over clocked it for me, but the bios seems fine. Thanks again for your help.

Hi. Thanks for any help you can give, this problem is driving me up the wall, as I can usually fix all problems I encounter but this one has me beat. I have tried to use both the onboard chipset and also an internal USB 3.0 card, problem happens with both. The page for the motherboard I use is : http://www.gigabyte.com/products/product-page.aspx?pid=4139#ov The page for the USB 3.0 card that I have also tried is (currently removed as I was testing if it made any difference being taken out, and it doesn't) : http://www.gigabyte.com/products/product-page.aspx?pid=3315#ov I just re-did the IMGBurn to get an error at the exact time I can check the event viewer, and this is what it says under "Warning"........ Log Name: System Source: Disk Date: 26/08/2012 23:58:07 Event ID: 51 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: IvyBridgePC Description: An error was detected on device \Device\Harddisk5\DR7 during a paging operation. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Disk" /> <EventID Qualifiers="32772">51</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-08-26T22:58:07.775995700Z" /> <EventRecordID>2440</EventRecordID> <Channel>System</Channel> <Computer>IvyBridgePC</Computer> <Security /> </System> <EventData> <Data>\Device\Harddisk5\DR7</Data> <Binary>040080000100000000000000330004802D0100000E0000C0000000000000000000000000000000000F3E020000000000FFFFFFFF01000000580000080000000000200A1280032040000000003C00000000000F0000000000C8A53F0D80FAFFFF0000000000000000104A420D80FAFFFFB09A440D80FAFFFFBF196800000000002A00006819BF00008000000000000000000000000000000000000000000000000000000000000000</Binary> </EventData> </Event> ----------------------- Here is the latest log from IMGBurn so you can match up the times to see if relevant.......... I 23:57:03 ImgBurn Version 2.5.7.0 started! I 23:57:03 Microsoft Windows 7 Enterprise x64 Edition (6.1, Build 7601 : Service Pack 1) I 23:57:03 Total Physical Memory: 16,738,040 KB - Available: 14,856,244 KB I 23:57:03 Initialising SPTI... I 23:57:03 Searching for SCSI / ATAPI devices... I 23:57:03 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06 (H:) (SATA) I 23:57:03 -> Drive 2 - Info: HL-DT-ST DVDRAM GE20NU11 CN01 (I:) (USB) I 23:57:03 Found 1 DVD±RW/RAM and 1 BD-RE! I 23:57:10 Operation Started! I 23:57:10 Building Image Tree... I 23:57:11 Calculating Totals... I 23:57:11 Preparing Image... I 23:57:11 Contents: 29 Files, 15 Folders I 23:57:11 Content Type: BD Video I 23:57:11 Data Type: MODE1/2048 I 23:57:11 File System(s): UDF (2.50) I 23:57:11 Volume Label: [Not Configured] I 23:57:11 Size: 23,569,146,428 bytes I 23:57:11 Sectors: 11,508,390 I 23:57:11 Image Size: 23,570,219,008 bytes I 23:57:11 Image Sectors: 11,508,896 I 23:57:11 Operation Successfully Completed! - Duration: 00:00:00 I 23:57:27 Operation Started! I 23:57:27 Building Image Tree... I 23:57:58 Calculating Totals... I 23:57:58 Preparing Image... I 23:57:58 Contents: 29 Files, 15 Folders I 23:57:58 Content Type: BD Video I 23:57:58 Data Type: MODE1/2048 I 23:57:58 File System(s): UDF (2.50) I 23:57:58 Volume Label: Blu-Ray 1 Folder I 23:57:58 Size: 23,569,146,428 bytes I 23:57:58 Sectors: 11,508,390 I 23:57:58 Image Size: 23,570,219,008 bytes I 23:57:58 Image Sectors: 11,508,896 I 23:58:01 Operation Successfully Completed! - Duration: 00:00:34 I 23:58:01 Operation Started! I 23:58:01 Image Contents: 29 Files, 15 Folders I 23:58:01 Image Sectors: 11,508,896 (MODE1/2048) I 23:58:01 Image Size: 23,570,219,008 bytes I 23:58:01 Image Volume Identifier: Blu-Ray 1 Folder I 23:58:01 Image Volume Set Identifier: 411ABF2D00AF9C26 I 23:58:01 Image Application Identifier: ImgBurn v2.5.7.0 I 23:58:01 Image Implementation Identifier: ImgBurn I 23:58:01 Image File System(s): UDF (2.50) I 23:58:01 Destination File: J:\Test.iso I 23:58:01 Destination Free Space: 1,500,159,418,368 Bytes (1,464,999,432.00 KB) (1,430,663.51 MB) (1,397.13 GB) I 23:58:01 Destination File System: NTFS I 23:58:01 File Splitting: Auto I 23:58:01 Writing Image... E 23:58:16 Failed to Write to File: J:\Test.iso E 23:58:16 Reason: The device is not ready. E 23:58:16 Operation Failed! - Duration: 00:00:15 E 23:58:16 Average Write Rate: 143,496 KB/s (31.9x) - Maximum Write Rate: 143,496 KB/s (31.9x)

PC - i7, 16gb, Gigabyte Z77X-UD5H I have just made a new PC, and earlier today I tried to copy a BD folder to my external HDD by using the "Create Image File From...." option. But everytime I do this it cuts out near the start (around 7% to 10% in) and says the device is not ready, and then I can't access the drive any more as it vanishes from windows explorer. It always happens when the buffer kicks in, before that it is at 0%. I know it isn't the external HDD as I connected it to my other PC and did the same test, and it copied fine. But this also means it can't be a general fault with IMGBurn, as I used that on my other PC (one version older but I doubt that makes any difference). Also it works when copying from internal drive to another internal. The annoying thing is I just formatted my entire C drive and reinstalled Windows 7 as I assumed that would fix it, but I have the exact same problem still. So if that doesn't fix it, what can ? I have installed the latest chipset and USB drivers. I made sure I tested it after formatting and freshly installing Win7 again with only the latest USB drivers installed and nothing else, in case of conflicts, but still no joy. I have tried both Win 7 with and without service pack and latest updates and fixes. What could the reason be that I get the error when the buffer kicks in ? I remember a couple of days ago when I first made the PC I copied stuff across from the ext HDD to my internal one (just using Windows Explorer) and sometimes it would cut out, if I copied 1TB for instance, often it would cut out at some point saying the drive no longer existed, then I would have to reboot the external dock/hdd to get it back again, the speed was good though. Also other times I would see the files in the HDD, but when I went to click a file it would say it doesn't exist, until I turn the drive back on again. Same happens to the external DVD drive that is connected via USB 2. I have tried different HDDs, leads, sockets, USb 2 instead of 3, a hub, and even a different dock. But as I say, all works fine on my other PC with same HDD, lead and a version of IMGBurn. This happens with both USB 2 and 3, as I have tried different sockets and a 7 port hub. I am completely baffled, I have no idea what I can do. Any ideas ? Below is the log. I 23:22:06 ImgBurn Version 2.5.7.0 started! I 23:22:06 Microsoft Windows 7 Enterprise x64 Edition (6.1, Build 7601 : Service Pack 1) I 23:22:06 Total Physical Memory: 16,738,040 KB - Available: 15,344,100 KB I 23:22:06 Initialising SPTI... I 23:22:06 Searching for SCSI / ATAPI devices... I 23:22:06 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06 (H:) (SATA) I 23:22:06 -> Drive 2 - Info: HL-DT-ST DVDRAM GE20NU11 CN01 (I:) (USB) I 23:22:06 Found 1 DVD±RW/RAM and 1 BD-RE! I 23:23:07 Operation Started! I 23:23:07 Building Image Tree... I 23:23:08 Corrected file system selection for Blu-ray Video disc. I 23:23:08 Corrected UDF revision selection for Blu-ray Video disc. I 23:23:08 Calculating Totals... I 23:23:08 Preparing Image... I 23:23:08 Contents: 29 Files, 15 Folders I 23:23:08 Content Type: BD Video I 23:23:08 Data Type: MODE1/2048 I 23:23:08 File System(s): UDF (2.50) I 23:23:08 Volume Label: [Not Configured] I 23:23:08 Size: 23,569,146,428 bytes I 23:23:08 Sectors: 11,508,390 I 23:23:08 Image Size: 23,570,219,008 bytes I 23:23:08 Image Sectors: 11,508,896 I 23:23:08 Operation Successfully Completed! - Duration: 00:00:01 I 23:23:20 Operation Started! I 23:23:20 Building Image Tree... I 23:23:22 Calculating Totals... I 23:23:22 Preparing Image... I 23:23:22 Contents: 29 Files, 15 Folders I 23:23:22 Content Type: BD Video I 23:23:22 Data Type: MODE1/2048 I 23:23:22 File System(s): UDF (2.50) I 23:23:22 Volume Label: Blu-Ray 1 Folder I 23:23:22 Size: 23,569,146,428 bytes I 23:23:22 Sectors: 11,508,390 I 23:23:22 Image Size: 23,570,219,008 bytes I 23:23:22 Image Sectors: 11,508,896 I 23:23:23 Operation Successfully Completed! - Duration: 00:00:02 I 23:23:23 Operation Started! I 23:23:23 Image Contents: 29 Files, 15 Folders I 23:23:23 Image Sectors: 11,508,896 (MODE1/2048) I 23:23:23 Image Size: 23,570,219,008 bytes I 23:23:23 Image Volume Identifier: Blu-Ray 1 Folder I 23:23:23 Image Volume Set Identifier: 411ABAEA00AF9C26 I 23:23:23 Image Application Identifier: ImgBurn v2.5.7.0 I 23:23:23 Image Implementation Identifier: ImgBurn I 23:23:23 Image File System(s): UDF (2.50) I 23:23:23 Destination File: J:\Test.iso I 23:23:23 Destination Free Space: 1,500,159,418,368 Bytes (1,464,999,432.00 KB) (1,430,663.51 MB) (1,397.13 GB) I 23:23:23 Destination File System: NTFS I 23:23:23 File Splitting: Auto I 23:23:23 Writing Image... E 23:24:00 Failed to Write to File: J:\Test.iso E 23:24:00 Reason: The device is not ready. E 23:24:00 Operation Failed! - Duration: 00:00:36 E 23:24:00 Average Write Rate: 51,994 KB/s (11.6x) - Maximum Write Rate: 123,325 KB/s (27.4x)

All 16x Verbatim discs I burn on my USB2 LG drive come out like this........... Where-as on my internal Pioneer BD-R drive the same Verbatim 16x comes out like this........ Burning at 8x on my Pioneer BD-R drive comes out like this........... I have tried to use Opti Drive Control but am told neither of my drives support jitter tests. My discs are Verbatim MCC03RG20 DVD-R My external LG drive is : HL-DT-ST DVDRAM GE20NU11 CN01 My internal Pioneer drive is : PIONEER BD-RW BDR-206D 1.06 Here is a shot of a Ritek G05 at 8x on my LG external drive........... So any idea whether the Verbatims are looking ok on there ? I used to use G05 all the time but just changed to Verbatim DVD-R today, so am hoping tests look ok. On the pics above the G05 one looks so clear and smooth, but is that irrelevant ? I can't imagine my drives coping with G05 better than Verbatims. Thanks all !!

Thanks for your help. You are right that I don't need to read from a disc made in TMPGEnc as I can make it create a folder, I think I can even make it create an ISO too, but I started to make them via direct to blu-ray so it was just about older discs I had created. Now I am creating a folder and burning with IMGBurn, as I type in fact. There is a 14 days trial of TMPGEnc Authoring Works, obviously depending on if you have time and how your research process is, but maybe worth doing a quick test on there to see ? Obviously I don't mean for my benefit, but just if it helps you know more about the format. Looking at the STREAM folder it seems very similar to normal track blu-rays. What I have noticed in TMPGEnc is that on the left you have "add track" and you can do that or just put them all within the first track, but it won't let you change each video's separate bitrate if you have them within 1 track. Here is link to demo : http://tmpgenc.pegasys-inc.com/en/download/taw5.html Well the good news is I just tested back the IMGburn ISO and it works fine, as expected. Thanks !

When I create a blu-ray in TMPGEnc Authoring Works I find I can't make an ISO from them in IMGBurn as it says it is a multi-track blu-ray so can only create a bin image. Can someone explain to me what a multi-track blu-ray is ? When I create multiple episode blu-rays in other software it is fine, so I don't think it is just down to the fact more than 1 episode or movie is on the disc. What I do find different in TMPGEnc is that it allows me to change the bitrate and resolution for each video file (but not the PAL/NTSC format), where-as other software doesn't. Is this the difference ? Is multi-track as compatible as single track ? Thanks for any help !!

I am unsure if it is a coincidence, but about 50% of my Ritek GO5 discs now say "The drive only supports writing these discs at 4x" where-as the other day before I moved a sata controller it was burning every disc at 8x. I had to move a sata controller that the drive runs off from a PCIe x1 slot to a PCIe x16 slot, I heard that x1 can happily go in to such a slot. It shares the same lane as the graphics card but there is more than enough power for a x1 PCIe card as it can go up to x8 PCIe when shared. What is confusing is that some discs work at 8x speed write and others 4x, but they are all GO5 discs. Also my other burner, a USB2 one, records them all at 8x. I am guessing it is too much of a coincidence to not be the sata controller move, but why ? I have moved it to a more powerful socket, not a less powered one. Could it be if both burner and the drive I am copying from is on the same controller ? As I am unsure which HDD is sharing the 2 port sata controller. I also notice I am getting a lot of "Waiting for hard disk activity to reach threshold level" messages when burning on both this drive and my USB2 one at the same time, I usually often do that and never get this message (until now). I guess I can swap leads around so that the sata drive is going to a motherboard sata socket, but I am really curious why ? As I would hate to put a HDD on a port that can't even get 8x DVD writing speeds (and this is what I would have to do as my motherboard is full up with hard drives). I have Windows 7. W 14:56:32 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 14:56:32 Initialising SPTI... I 14:56:32 Searching for SCSI / ATAPI devices... I 14:56:32 -> Drive 1 - Info: DTSOFT BDROM 1.05 (M:) (Virtual) I 14:56:32 -> Drive 2 - Info: PIONEER BD-RW BDR-206D 1.06 (L:) (RAID) I 14:56:32 -> Drive 3 - Info: HL-DT-ST DVDRAM GE20NU11 CN01 (N:) (USB) I 14:56:32 Found 1 DVD±RW/RAM, 1 BD-ROM and 1 BD-RE! I 14:58:18 Operation Started! I 14:58:18 Source File: J:\ISOs\DVD.iso I 14:58:18 Source File Sectors: 2,207,376 (MODE1/2048) I 14:58:18 Source File Size: 4,520,706,048 bytes I 14:58:18 Source File Volume Identifier: label I 14:58:18 Source File Volume Set Identifier: 40541182RDUS0004 I 14:58:18 Source File Implementation Identifier: Ulead Systems USA Inc. I 14:58:18 Source File File System(s): ISO9660, Joliet, UDF (1.02) I 14:58:18 Destination Device: [0:0:0] PIONEER BD-RW BDR-206D 1.06 (L:) (RAID) I 14:58:18 Destination Media Type: DVD-R (Disc ID: RITEKG05) I 14:58:18 Destination Media Supported Write Speeds: 4x I 14:58:18 Destination Media Sectors: 2,298,496 I 14:58:18 Write Mode: DVD I 14:58:18 Write Type: DAO I 14:58:18 Write Speed: 8x I 14:58:18 Link Size: Auto I 14:58:18 Lock Volume: Yes I 14:58:18 Test Mode: No I 14:58:18 OPC: No I 14:58:18 BURN-Proof: Enabled W 14:58:18 Write Speed Miscompare! - Wanted: 11,080 KB/s (8x), Got: 5,540 KB/s (4x) W 14:58:18 The drive only supports writing these discs at 4x. I 14:58:18 Advanced Settings - Optimal Writing Speed: No I 14:58:19 Filling Buffer... (40 MB) I 14:58:19 Writing LeadIn... I 14:58:50 Writing Session 1 of 1... (1 Track, LBA: 0 - 2207375) I 14:58:50 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2207375) W 15:04:54 Waiting for buffers to recover... (LBA: 953824) W 15:05:06 Waiting for hard disk activity to reach threshold level... I 15:05:07 Writing Sectors... W 15:05:39 Waiting for buffers to recover... (LBA: 1024224) W 15:05:54 Waiting for hard disk activity to reach threshold level... I 15:05:55 Writing Sectors... W 15:06:24 Waiting for buffers to recover... (LBA: 1085536) W 15:06:34 Waiting for hard disk activity to reach threshold level... I 15:06:35 Writing Sectors... I 15:13:33 Synchronising Cache... I 15:14:09 Exporting Graph Data... I 15:14:09 Graph Data File: C:\Users\Me\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-206D_1.06_20-FEBRUARY-2012_14-58_RITEKG05_8x.ibg I 15:14:09 Export Successfully Completed! I 15:14:09 Operation Successfully Completed! - Duration: 00:15:50 I 15:14:09 Average Write Rate: 4,999 KB/s (3.6x) - Maximum Write Rate: 5,604 KB/s (4.0x)

Can't find any mention about pros or cons for the Kodak 25gb blu-rays, they seem quite cheap. Anyone used them ?

I decided not to use TRAXDATA or RiDisc or any Ritek branded Blu-Rays as I got fed up with the infamous "1-year and your discs are dead" situation, so I buy 50 TDKs feeling proud and happy that I have a proper brand of Blu-Rays coming to me, and the blooming code happens to be RITEK-BR2-000, arrggghhh. I thought TDK would of used a higher quality media. So should I be worried ? Or do you think things have changed now and those media code discs are now okay to use ?

I have some 4x speed Verbatim discs, and yet I am allowed to burn them at 10x, how does that work ? Is it safe ? It seems to work okay, but that is more than double the quoted speed. A 25gb disc finished in 10 minutes which is only 3 minutes more than DVDs I burn. My burner is a Pioneer 206D.