BlizzardUK
-
Posts
62 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by BlizzardUK
-
-
Your hunch may be correct, I don't want to speak too soon but I just swapped over the SATA to IDE bridge and replaced it with a direct SATA to USB and it has verified the last 2 discs without issue, which never happened before. It wasn't the discs though as it still did it with a Verbatim with the SATA to IDE bridge. The reason though I preferred to use the SATA to IDE bridge was because the buffer stayed more consistent on burns, the buffer wouldn't fluctuate much like it does with with the direct to USB connection. Does the buffer going up and down occasionally matter much ? Below is a graph from the SATA to USB burn, does it look okay ? This was using a ACU-DISC which uses the Ritek Media ID. Thanks.
Oh and if interested the inside of the SE machine has a USB port, so for instance with SATA TO IDE it literally just connects as normal but with the bridge attached, the normal USB socket stays plugged in. When I use SATA to USB I bypass the IDE board completely and connect the USB cable to the internal USB socket, I just unplug the the one. Took me a long time to find a SATA to USB adapter that didn't work via external power, I can use the molar cable.
-
Thanks. I will try tonight. I have found a way to connect directly from the sata drive to the internals of the SE too while still giving the drive power from the internal cable (most converters only had external power cables which wouldn't have been much use), but after testing (at that point I didn't know about verification issues so didn't test that) it oddly seemed to burn smoother with the bridge, less up and down of the buffering hence why I went back to the bridge, which is weird given SATA to USB was a more direct connection than SATA to IDE to USB. But I will try the same device out again tonight. Primera should give me a job as I know the insides of their machines better than them now probably, haha.
-
Yeah, it is a Frankenstein machine, haha. The SE came with a DVD drive in it, so I replaced it with a BD-R drive, but it could only be a specific drive as it uses its own firmware. I had to use a SATA to IDE adapter as the machine was made in 2007 and only had IDE. Recording in ImgBurn works fine, just verifying is an issue. I do have Verbatim BD-Rs too, will have to give those a go too, they were going to be used when my Acu-Disc blu-rays (the Riteks) ran out. Right now I am burning 12 Blu-Rays in ImgBurn using the queue function and it is working great, just won't verify unless I put the discs in my other burner.
It is funny but I am obviously so late to the game, as Lightning has old posts on here from 2010 where he changed the drive in his Bravo SE.
-
(this post is regarding 2 different but similar issues)
I tick verify so after I have burnt a blu-ray disc it will verify it, but it sticks during verification, for instance it might get to 7% or 16% (last 2 examples) verified and then stay there for 30+ minutes until I give up with it. Then when I try and cancel it won't, it stays on "Waiting for Read Thread (Device)".
My drive is a Pioneer BDR-206D and it is inside a Primera Bravo SE and has a SATA to IDE convertor, not sure if that makes any difference. Imgburn will burn the BD-Rs fine it just won't verify discs either via immediate verification of disc post burn or a compare verification against a disc image. It's driving me a bit nuts as I have to use a different drive for verifications.On the below log when I came in at 32 minutes it was just stuck at 7%. No error, just 0x speed and nothing happening. When I clicked cancel it then said "Waiting for Read Thread (Device)" and wouldn't cancel until I used task manager to close it as no amount of clicking cancel did anything. Unfortunately I can't show logo info or a graph as shutting down via task manager means it doesn't write one. But it does seem this only happens on the BDR-206D and not my other Pioneer that isn't in the SE. Why would the BDR-206D not be able to verify BD-Rs ? I managed to copy and paste the below info from the log that appears under the software. Why would a drive be able to burn but not verify ???
I 23:53:56 Cycling Tray before Verify...
I 23:54:19 Device Ready!
I 23:54:20 Operation Started!
I 23:54:20 Source Device: [0:0:0] PIONEER BD-RW BDR-206D 9.56 (T:) (USB)
I 23:54:20 Source Media Type: BD-R (Disc ID: RITEK-BR3-000)
I 23:54:20 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x
I 23:54:20 Source Media Sectors: 11,890,848
I 23:54:20 Source Media Size: 24,352,456,704 bytes
I 23:54:20 Image File: G:\myBDR.iso
I 23:54:20 Image File Sectors: 11,890,848 (MODE1/2048)
I 23:54:20 Image File Size: 24,352,456,704 bytes
I 23:54:20 Image File Volume Identifier: mybdr
I 23:54:20 Image File Volume Set Identifier: 563E39A900B57011
I 23:54:20 Image File Application Identifier: ImgBurn v2.5.8.0
I 23:54:20 Image File Implementation Identifier: ImgBurn
I 23:54:20 Image File File System(s): UDF (2.50)
I 23:54:20 Read Speed (Data/Audio): MAX / MAX
I 23:54:21 Read Speed - Effective: 0x
I 23:54:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11890847)
I 23:54:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11890847)
I 00:26:12 Abort Request Acknowledged
---------------------------------------------------------One other small issue, when I compare discs to an ISO (on my other drive) it often sets the read speed to 2x when the drive I am using to compare/verify is a Pioneer BDR-X12 which is quite new (I have 2 different BD-Rs, the one in the SE and this as an external drive). I have to use this drive to verify due to the above SE one not being able to. It will compare some at 12x but just wondered why some (same media brand) stay at 2x ? I would say it is 50/50 whether it will compare a blu-ray disc at 2x or the full 12x. Below is info I got from the log when it verified at 2x.
I 22:51:06 Operation Started!
I 22:51:06 Source Device: [0:0:0] PIONEER BD-RW BDR-X12 1.03 (K:) (USB)
I 22:51:06 Source Media Type: BD-R (Disc ID: RITEK-BR3-000)
I 22:51:06 Source Media Supported Read Speeds: 12x
I 22:51:06 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x
I 22:51:06 Source Media Sectors: 11,703,904
I 22:51:06 Source Media Size: 23,969,595,392 bytes
I 22:51:06 Image File: G:\anotherISO.iso
I 22:51:06 Image File Sectors: 11,703,904 (MODE1/2048)
I 22:51:06 Image File Size: 23,969,595,392 bytes
I 22:51:06 Image File Volume Identifier: anotheriso
I 22:51:06 Image File Volume Set Identifier: 56462A0200B295FA
I 22:51:06 Image File Application Identifier: ImgBurn v2.5.8.0
I 22:51:06 Image File Implementation Identifier: ImgBurn
I 22:51:06 Image File File System(s): UDF (2.50)
I 22:51:06 Read Speed (Data/Audio): MAX / MAX
I 22:51:07 Read Speed - Effective: 5x - 12x
I 22:51:08 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11703903)
I 22:51:08 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11703903)
I 23:35:35 Exporting Graph Data...
I 23:35:35 Graph Data File: C:\Users\name\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-X12_1.03_24-JULY-2023_22-51_RITEK-BR3-000.ibg
I 23:35:35 Export Successfully Completed!
I 23:35:35 Operation Successfully Completed! - Duration: 00:44:27
I 23:35:35 Average Verify Rate: 8,780 KiB/s (2.0x) - Maximum Verify Rate: 8,842 KiB/s (2.0x)Thanks for any advice.
-
Update, I found the error report of........
1395,127,Disc Loaded: 0 Sectors in Job 12219392 Sectors Free On Disc 0 Sectors Used On Disc
37,1395,132,Recording Started - Disc 1 - 8x - 0 MB - CDR = 000000
1395,143,Recording Error. Sector 11814368 - Cmd 0x1f - Sense 0x5 - ASC 0x2c - ASCQ 0x0
1395,134,Recording Failed - Disc 1I notice in the project options I have a choice of ISO Image Type : 2048 or 2336 or 2352
Would changing those be worth a test ? Could it automatically be using defect management somewhere ? I have tried 2 different blu-ray drives now, a old Pioneer BD-R and a brand new LG and both have the same issue. PTPublisher must be doing something odd.
-
This is not technically related to Imgburn, apart from the fact that works and this other software doesn't, but sadly I need this other software to burn+print at the same time. So I have a DVD based Bravo SE, I have done a DIY upgrade to a BD-R drive, most things are fine, but I have found if trying to burn a disc image in PTPublisher (the supplied software) the burn will fail IF the image is over 22.56gb but still below the 23.28gb limit. I have contacted support and they said they will look in to it, but in the meantime any ideas ?
I found a 50gb BD-R will burn images over 22.56gb okay. I have tried multiple single layer BD-Rs and none go above 22.56gb, it literally just fails at that point, even if the ISO is 22.57gb.
I have tried putting the drive in a 2nd SE and same happens, I have tried another PC, same problem, I have tried 2 brands of BD-R, same problem. As mentioned the ISO's that fail in PTPublisher burn fine in Imgburn. Annoyingly nearly all my 100's of self custom made BD-Rs are just over 22.56gb but still within 23gb. So I can't burn most of them if I want to print at the same time, as otherwise I would just use Imgburn, but I can't print.
Does Lightning still visit here ? I know he used to have an SE about 13 years ago, so maybe he might have a brainwave ? Again, I realise this is not imgburns fault nor software, but I really want to know why the discs burn fine in Imgburn but not PTPublisher.
-
True. Given what Lightning did though with the robot software for the SE I wasn't sure if there could be an easy way to just piggy back off other software to print, so it just gives an instruction. But yeah, I doubt it will happen understandably, I am just pulling my hair out on getting PTPublisher to work with my self modified SE upgrade from DVD to BD-R.
-
I absolutely love the way Imgburn allows me to use my Primera SE in robot mode outside of PTPublisher to burn discs, big thanks for this feature, but is there any way to get it to print to disc too after each burn ? For instance, load a BMP and when burnt it just prints it on disc ? I don't mean any graphical GUI or anything like that, just a way to add a BMP and then it prints, or to auto use any other software ? At the moment I have to use PTPublisher for everything when it comes to burning and printing. Any ideas or suggestions ? Thanks.
-
Thanks, hopefully nothing important then as I won't be able to use it.
-
Does anyone know what a JTAG connector does when connected to an IDE board ? I just opened up my Bravo to change from IDE to SATA and noticed this JTAG cable connected to the IDE board.
.jpg.d7a40d20d62772d57d1f0a64e311a807.jpg)
-
Thanks. Yes, I am fairly sure USB 2.0 will be fine, it just maxes out at 6x. I guess I am mainly wondering if anyone has changed the IDE DVD drive inside the Bravo SE for a SATA BD-R drive, the printers interface is USB 2.0 so it will always only run at 2.0 speeds but the drive themselves are IDE and SATA.
Here is the IDE to SATA kit they sell, but it is so expensive and they only seem to sell with a drive, I can't work out what is needed, for some reason it shows a USB 2.0 cable. I have contacted support but not sure if they will tell me as clearly I am trying to buy outside of them.
https://www.primera.com/sata-drive-upgrade-kit-for-bravo-2-bravo-pro-and-bravo-se.html
-
I have just bought a BD-R drive (Pioneer 206DBK) and I am going to replace the DVD drive with the BD-R drive, just as an experiment really. I know I only have a USB 2 controller so it will be 6x max speed record, but that is good enough. So really just curious if anyone here has done that ? Thanks.
-
Dare I ask about the new release ? I have used the software since it began and Decrypter before it. Would love a new updated release
-
My IMGBurn is set to 80MB buffer and has been for the last 10+ years I have used it. I don't normally notice buffer issues but today I was burning to a DVD drive and BD drive at the same time from the same HDD and the buffer kept running out every 30 seconds or so on the blu-ray disc. I was burning the BD in IMGBurn and the DVD via my Bravo 2 PTPublisher. I realise burning 2 devices from the same hard drive is not advised, but this made me curious, given I have 32GB ram would increasing the buffer to the max 1gb help in these incidences when I forget ? For instance today I forgot I was burning from the same HDD (I use a drive pool to form a single drive letter from multiple HDDs, sometimes the ISO's end up on the same drive) and so once the BD was started I couldn't change buffer or cancel without ruining a disc, so I had to let it run with the buffer (default 80MB) going up and down like a yoyo which worried me a bit. So if I set it to the max 1gb just in case this happens again, is there any negatives to this and to leaving it set to 1gb all the time ? I only ever seem to use a max of 16gb of my 32gb ram so I have 16gb spare 99.9% of the time so 1gb poached shouldn't harm me from that point of view.
Can I do the same for the Build tool buffer which I use all the time as well ?
Just noticed in an old post from 2007 the author of IMGBurn mentions IMGBurn has a pause button, where is this located ?
Also I notice my external USB 3.0 BD Drive is showing up as USB 2.0 in the IMGBurn logs, is this normal ? Or could it be due to the 10m USB distance I have the drive at (using powered repeaters) ?
Thanks for the great software.
-
Just wondered, but beside my drive name in IMGBURN it says (USB 2.0) even though it is an external USB 3.0 drive, is this just because the software came out before USB 3 or should it show USB 3.0 ?
Thanks !!
-
I need approx 7m USB3 from my PC to my external USB3 BD-R drive, just because of the way my room is situated and where I am able to sit, and the amount of blu-ray discs I burn. I currently have a 10m USB3 active repeater cable, but if I try and burn over 4x the device buffer goes up and down like crazy and will only settle when under 4x. If I got 2x 5m USB3 active cables, could that help ? Or do the 10m ones have a repeater built in anyway at the 5m point ? I am presuming the issue of the device buffer going up and down is due to there not being enough bandwidth.
Any ideas ? Earlier tonight I got lots of semaphore timeout "invalid address" errors upon burning discs, wasted approx 7 discs, but I have changed the USB port (from directly in to my PC port in to a powered hub port) and that is at least better and stops those errors, but still has the wildly fluctuating device buffer over 4x.
EDIT : Okay, forget the hope I had in that last paragraph, the burn failed, make that 8 discs ruined, I realise this is not IMG Burns fault though. This time the error wasn't semaphore, but "No additional sense information" whatever that means.
-
I have a external BD-R burner, and I am having a lot of problems with verifying, this doesn't just happen with BD-Rs, but in the last 2 times today that has been what has happened. Any ideas what it could be ? I have a Windows 10 PC. It keeps just cutting out and going on about Semaphore, it doesn't happen at the same time so I am fairly sure it isn't the discs, especially as it has happened with CD-audio discs as well as blu-rays.
I 16:58:00 ImgBurn Version 2.5.8.0 started!
I 16:58:00 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 16:58:00 Total Physical Memory: 16,735,172 KiB - Available: 5,999,440 KiB
I 16:58:00 Initialising PTRobot...
I 16:58:01 PT_SDK Version 1.8.1.0
I 16:58:01 Initialising SPTI...
I 16:58:01 Searching for Auto Loader devices...
I 16:58:01 -> Auto Loader 1 - Info: Disc Publisher II 1.43 03/19/2008
I 16:58:01 Found 1 Auto Loader!
I 16:58:01 Searching for SCSI / ATAPI devices...
I 16:58:01 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA)
I 16:58:01 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0)
I 16:58:02 -> Drive 3 - Info: ATAPI eHBU312 2 VL16 (T:) (USB 2.0)
I 16:58:02 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI)
I 16:58:02 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 2 BD-REs!
I 16:58:50 Operation Started!
I 16:58:50 Source File: F:\Downloads\Mike 2019\March 2019\Put to Disc\Disc1.nrg
I 16:58:50 Source File Sectors: 11,524,384 (MODE1/2048)
I 16:58:51 Source File Size: 23,601,938,432 bytes
I 16:58:51 Source File Volume Identifier: Disc1
I 16:58:51 Source File Volume Set Identifier: 4E7A2148B185DEB7
I 16:58:51 Source File Implementation Identifier: Nero
I 16:58:51 Source File File System(s): UDF (1.02)
I 16:58:51 Destination Device: [0:0:0] ATAPI eHBU312 2 VL16 (T:) (USB)
I 16:58:51 Destination Media Type: BD-R (Disc ID: RITEK-BR3-000)
I 16:58:51 Destination Media Supported Write Speeds: 4x, 6x, 8x, 10x
I 16:58:51 Destination Media Sectors: 12,219,392
I 16:58:51 Write Mode: BD
I 16:58:51 Write Type: DAO
I 16:58:51 Write Speed: 8x
I 16:58:51 Hardware Defect Management Active: No
I 16:58:51 BD-R Verify Not Required: Yes
I 16:58:51 Link Size: Auto
I 16:58:51 Lock Volume: Yes
I 16:58:51 Test Mode: No
I 16:58:51 OPC: No
I 16:58:51 BURN-Proof: Enabled
I 16:58:52 Write Speed Successfully Set! - Effective: 35,960 KB/s (8x)
I 16:59:22 Filling Buffer... (204 MiB)
I 16:59:24 Writing LeadIn...
I 16:59:26 Writing Session 1 of 1... (1 Track, LBA: 0 - 11524383)
I 16:59:26 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11524383)
I 17:11:21 Synchronising Cache...
I 17:11:25 Closing Track...
I 17:11:26 Finalising Disc...
I 17:12:07 Exporting Graph Data...
I 17:12:07 Graph Data File: C:\Users\jonuk\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_eHBU312_2_VL16_27-MARCH-2019_16-58_RITEK-BR3-000_8x.ibg
I 17:12:07 Export Successfully Completed!
I 17:12:07 Operation Successfully Completed! - Duration: 00:13:16
I 17:12:07 Average Write Rate: 32,281 KiB/s (7.4x) - Maximum Write Rate: 35,717 KiB/s (8.1x)
I 17:12:07 Cycling Tray before Verify...
W 17:12:14 Waiting for device to become ready...
I 17:12:29 Device Ready!
I 17:12:33 Operation Started!
I 17:12:33 Source Device: [0:0:0] ATAPI eHBU312 2 VL16 (T:) (USB)
I 17:12:33 Source Media Type: BD-R (Disc ID: RITEK-BR3-000)
I 17:12:33 Source Media Supported Read Speeds: 1x, 2x, 4x, 6x, 8x
I 17:12:33 Source Media Supported Write Speeds: 4x, 6x, 8x, 10x
I 17:12:33 Source Media Sectors: 11,524,384
I 17:12:33 Source Media Size: 23,601,938,432 bytes
I 17:12:33 Image File: F:\Downloads\Mike 2019\March 2019\Put to Disc\Disc1.nrg
I 17:12:33 Image File Sectors: 11,524,384 (MODE1/2048)
I 17:12:33 Image File Size: 23,601,938,432 bytes
I 17:12:33 Image File Volume Identifier: Disc1
I 17:12:33 Image File Volume Set Identifier: 4E7A2148B185DEB7
I 17:12:33 Image File Implementation Identifier: Nero
I 17:12:33 Image File File System(s): UDF (1.02)
I 17:12:33 Read Speed (Data/Audio): MAX / MAX
I 17:12:34 Read Speed - Effective: 3.2x - 8x
I 17:12:34 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11524383)
I 17:12:34 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11524383)
W 17:26:30 Failed to Read Sectors 9962560 - 9962591 - Reason: The semaphore timeout period has expired.
W 17:26:30 Waiting for device to become ready...
W 17:26:30 Device Removal Detected!
W 17:26:30 The device list will be refreshed at the next available opportunity.
W 17:27:49 Device Removal Detected!
W 17:27:49 The device list will be refreshed at the next available opportunity.
I 17:27:56 Abort Request Acknowledged
E 17:27:56 Failed to Verify Sectors!
I 17:27:57 Exporting Graph Data...
I 17:27:57 Graph Data File: C:\Users\jonuk\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_eHBU312_2_VL16_27-MARCH-2019_16-58_RITEK-BR3-000_8x.ibg
I 17:27:57 Export Successfully Completed!
E 17:27:57 Operation Aborted! - Duration: 00:15:23
I 17:27:57 Average Verify Rate: 21,634 KiB/s (4.9x) - Maximum Verify Rate: 32,974 KiB/s (7.5x)
E 17:28:02 CreateFile Failed! - Device: '\\?\usbstor#cdrom&ven_atapi&prod_ehbu312___2&rev_vl16#2010121000200000011&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'
E 17:28:02 Reason: The system cannot find the file specified.
I 17:28:02 Searching for Auto Loader devices...
I 17:28:02 -> Auto Loader 1 - Info: Disc Publisher II 1.43 03/19/2008
I 17:28:02 Found 1 Auto Loader!
I 17:28:02 Searching for SCSI / ATAPI devices...
I 17:28:02 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA)
I 17:28:02 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0)
I 17:28:02 -> Drive 3 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI)
I 17:28:02 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 1 BD-RE!
W 17:28:21 Device Arrival Detected!
I 17:28:21 Searching for Auto Loader devices...
I 17:28:23 -> Auto Loader 1 - Info: Disc Publisher II 1.43 03/19/2008
I 17:28:23 Found 1 Auto Loader!
I 17:28:23 Searching for SCSI / ATAPI devices...
I 17:28:23 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA)
I 17:28:24 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0)
I 17:28:24 -> Drive 3 - Info: ATAPI eHBU312 2 VL16 (T:) (USB 2.0)
I 17:28:24 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI)
I 17:28:24 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 2 BD-REs!
I 17:29:21 Operation Started!
I 17:29:21 Source Device: [0:0:0] ATAPI eHBU312 2 VL16 (T:) (USB)
I 17:29:21 Source Media Type: BD-R (Disc ID: RITEK-BR3-000)
I 17:29:21 Source Media Supported Read Speeds: 1x, 2x, 4x, 6x, 8x
I 17:29:21 Source Media Supported Write Speeds: 4x, 6x, 8x, 10x
I 17:29:21 Source Media Sectors: 11,524,384
I 17:29:21 Source Media Size: 23,601,938,432 bytes
I 17:29:21 Image File: F:\Downloads\Mike 2019\March 2019\Put to Disc\Disc1.nrg
I 17:29:21 Image File Sectors: 11,524,384 (MODE1/2048)
I 17:29:21 Image File Size: 23,601,938,432 bytes
I 17:29:21 Image File Volume Identifier: Disc1
I 17:29:21 Image File Volume Set Identifier: 4E7A2148B185DEB7
I 17:29:21 Image File Implementation Identifier: Nero
I 17:29:21 Image File File System(s): UDF (1.02)
I 17:29:21 Read Speed (Data/Audio): MAX / MAX
I 17:29:22 Read Speed - Effective: 3.2x - 8x
I 17:29:22 Verifying Session 1 of 1... (1 Track, LBA: 0 - 11524383)
I 17:29:22 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 11524383)
W 17:34:15 Failed to Read Sectors 2592800 - 2592831 - Reason: The semaphore timeout period has expired.
W 17:34:15 Waiting for device to become ready...
W 17:34:15 Device Removal Detected!
W 17:34:15 The device list will be refreshed at the next available opportunity.
-
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.Createmain 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 BaseThreadInitThunkthread $ef40:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $fa80:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $fe48:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $6e84:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $dc1c:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $4150:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $ef8:
74188482 +22 KERNEL32.DLL BaseThreadInitThunkthread $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.dllthread $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 _16772modules:
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.
Imgburn sticking during verification
in ImgBurn Support
Posted
I just saw this thread where Lightning says the bottom graph of the 3 is a good burn, mine seems to compare a bit to that....