Jump to content

All Activity

This stream auto-updates     

  1. Today

    Unable to burn Bluray discs

    Your drive reported a 'Write Error' early on during the burn - right at the start actually. I guess it has an issue with the media. If say you've tried multiple different ones (not just different brands, but with different MIDs), maybe your drive is at fault? There are firmware updates available for the drive that may or may not help. v1.03 and a recent v1.05.
  3. Thanks for reading...my drive cant burn bluray discs but can read all type of discs (cd/dvd/bd) and write (cd/dvd/dvdrw) ! ImgBurn unable to burn Bluray discs but the drive could burn CD/DVD/DVD RW without issues... any idea whats going on? I tried 3 different media (ritek, verbatim and a local one) types and the behavior i same. It couldnt verify and am getting I 15:21:48 Writing LeadIn... W 15:21:52 Failed to Write Sectors 0 - 31 - Reason: Write Error Any thoughts on what could be the issue? Complete log for info: I 15:20:35 ImgBurn Version started! I 15:20:35 Microsoft Windows 8 Enterprise x64 Edition (6.2, Build 9200) I 15:20:35 Total Physical Memory: 25,100,864 KiB - Available: 21,689,736 KiB I 15:20:35 Initialising SPTI... I 15:20:35 Searching for SCSI / ATAPI devices... I 15:20:35 -> Drive 1 - Info: DiscSoft Virtual 1.0 (K:) (Virtual) I 15:20:37 -> Drive 2 - Info: HL-DT-ST BD-RE BH16NS40 1.02-A0 (E:) (SATA) I 15:20:37 Found 1 BD-ROM XL and 1 BD-RE XL! W 15:21:02 Skipped Hidden File: H:\Photos\karuna family photos\New folder (2)\.nomedia I 15:21:27 Operation Started! I 15:21:27 Building Image Tree... I 15:21:33 Calculating Totals... I 15:21:33 Preparing Image... I 15:21:34 Contents: 8,193 Files, 76 Folders I 15:21:34 Content Type: Data I 15:21:35 Data Type: MODE1/2048 I 15:21:35 File System(s): UDF (1.02) I 15:21:35 Volume Label: photos1 I 15:21:35 Size: 24,545,037,562 bytes I 15:21:35 Sectors: 11,988,919 I 15:21:35 Image Size: 24,571,478,016 bytes I 15:21:35 Image Sectors: 11,997,792 I 15:21:37 Operation Successfully Completed! - Duration: 00:00:10 I 15:21:37 Operation Started! I 15:21:37 Source File: -==/\/[BUILD IMAGE]\/\==- I 15:21:37 Source File Sectors: 11,997,792 (MODE1/2048) I 15:21:37 Source File Size: 24,571,478,016 bytes I 15:21:37 Source File Volume Identifier: photos1 I 15:21:38 Source File Volume Set Identifier: 52317AAD00B71248 I 15:21:38 Source File Application Identifier: ImgBurn v2.5.8.0 I 15:21:38 Source File Implementation Identifier: ImgBurn I 15:21:38 Source File File System(s): UDF (1.02) I 15:21:38 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.02 (E:) (SATA) I 15:21:38 Destination Media Type: BD-R (Disc ID: MBI-R06-000) I 15:21:38 Destination Media Supported Write Speeds: 4x, 6x, 8x, 10x I 15:21:38 Destination Media Sectors: 12,219,392 I 15:21:38 Write Mode: BD I 15:21:38 Write Type: DAO I 15:21:38 Write Speed: 4x I 15:21:38 Hardware Defect Management Active: No I 15:21:38 BD-R Verify Not Required: Yes I 15:21:38 Link Size: Auto I 15:21:38 Lock Volume: Yes I 15:21:38 Test Mode: No I 15:21:38 OPC: Yes I 15:21:38 BURN-Proof: Enabled I 15:21:38 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 15:21:48 Filling Buffer... (80 MiB) I 15:21:48 Writing LeadIn... W 15:21:52 Failed to Write Sectors 0 - 31 - Reason: Write Error W 15:21:52 Retrying (1 of 20)... I 15:21:54 Writing LeadIn... I 15:21:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 11997791) I 15:21:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11997791) I 15:44:51 Synchronising Cache... I 15:44:54 Closing Track... I 15:44:55 Finalising Disc... I 15:45:10 Exporting Graph Data... I 15:45:10 Graph Data File: C:\Users\Balu\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.02_SUNDAY-JANUARY-17-2021_3-21_PM_MBI-R06-000_4x.ibg I 15:45:10 Export Successfully Completed! I 15:45:11 Operation Successfully Completed! - Duration: 00:23:33 I 15:45:11 Average Write Rate: 17,438 KiB/s (4.0x) - Maximum Write Rate: 17,692 KiB/s (4.0x) I 15:45:11 Cycling Tray before Verify... W 15:45:26 Waiting for device to become ready... I 15:45:39 Device Ready! E 15:45:39 CompareImageFileLayouts Failed! - Session Count Not Equal (1/0) E 15:45:39 Verify Failed! - Reason: Layouts do not match.
  4. Yesterday
  5. Not entirely sure what the .LOG file is for. It's probably definitely not standardized Audio CD format. You'd end up with a Mixed Mode CD adding that .LOG file, so you can probably disregard it. If you're going to create an Audio CD with FLAC files, you'll need to install madFLAC first before using ImgBurn to create the Audio CD.

    How do I made a CD from flac, cue, and log files?

    Indeed, that is the job of the CUE file. Open it in notepad and you'll probably see that it contain numerous 'track' entries. Load the CUE in Write mode and burn. *That's assuming you have a directshow filter installed that's capable of decoding flac files. If you don't, please refer to the bottom of the Audio CD guide here:
  7. Hello all, I'm new here. I'm trying to do something that I thought would be simple. Then when I couldn't, I thought finding an answer would be simple, given all the people out there who do this all the time. Boy was I wrong. I have not found one, straightforward answer on the internet which I cannot believe. I trying to do something very basic: for one particular album of songs by a certain band, I have ONE flac file (304 mB) which is ALL of the songs on the album, in one big file. Then it has its own CUE file, and there's an accompanying LOG file. Thats IT!!! I just want to make a CD and have all those 10 or so songs that are glued together in that one big FLAC file, separated into the 10 separate audio tracks on the final CD, which I thought was the job of the CUE sheet - to tell the CD burning software exactly where the spaces are so it can do it. Here's what I have: Band - Album.cue Band - Album.flac Band - Album.log

    i/o Error when making iso file of DVD

    You already asked this question here -
  9. cornholio7

    i/o Error when making iso file of DVD

    looks like your disc is copy protected, not something imgburn can help with
  10. imgburn doesn't complete making an iso file of my DVD. See attached file Error Message.docx
  11. Last week

    Confusing write modes

    I guess because that's just what it defaults to? You can't make something from nothing though and 2048 bytes images only contain 'user data'. Nothing that writing in RAW mode would do anything for. Should you be so inclined, you can look up the structure of a CD sector and see the difference between 2448, 2352 and 2048 byte sectors. 2448 being the same as 2352, but with the added 96 bytes of subchannel.
  13. grep

    Confusing write modes

    OMG! Sorry, I'm still half asleep. >btw, as an ISO is meant to just be 2048 bytes per sector, you're wasting your time even looking at RAW writing. You don't have any data in the image that would benefit from being written that way. Then why would A120 try to do that?

    Confusing write modes

    I suggest you take a 2nd look at the name of the application you're using. What part of 'InfraRecorder' looks like 'ImgBurn' ? Getting back to the application this support forum is actually for... ImgBurn... that doesn't offer RAW at all. Your other thread is beginning to make a little more sense now. It seems you have your apps confused. btw, as an ISO is meant to just be 2048 bytes per sector, you're wasting your time even looking at RAW writing. You don't have any data in the image that would benefit from being written that way.
  15. grep

    Confusing write modes

    Why doesn't ImgBurn have just "RAW DAO"? There's 3 types of raw write - with extra chicken nuggets, with extra fries or with double dip. Well, not really with all the foodstuffs, but those names mean just as much to me because for the 20 years I have been using CD burning software I haven't ever seen something like 96r, 16 or 96p. Check out this competing software that does it right, in the second screenshot. Which mode in ImgBurn is just "RAW DAO"?

    Convert ImgBurn iso to bincue?

    ImgBurn outputs iso or bin/cue. I do not understand where you’re getting this toc and subchannel from?!
  17. Hello. I've been dumping several mixed-mode CDs with ImgBurn recently and the only way it seems, to make an image is to save its TOC and subchannel data. Once I got the dump ready, it appears to be really... non-standard. The .toc file doesn't look like a .toc file that cdrdao produces because it would be in plaintext with normal (LF) newlines. It's a binary file and I've no idea how to use it, or is it compatible with cdrdao. 00000000 00 39 01 01 01 14 00 a0 00 00 00 00 01 20 00 01 |.9........... ..| 00000010 10 00 a1 00 00 00 00 02 00 00 01 10 00 a2 00 00 |................| 00000020 00 00 3c 35 04 01 14 00 01 00 00 00 00 00 02 00 |..<5............| 00000030 01 10 00 02 00 00 00 00 38 35 04 42 04 |........85.B.| 0000003d If anyone's wondering, this is TOC+subchannel data for Formula 1 97 for PSX, PAL region. Is this kind of image compatible with cdrdao and if not, is there any easy way to convert it to a much more familiar bincue image? This is required to simplify my work. All of the images are stored and burned from a Linux host which has bincue images and cdrdao can burn them easily. Currently, I need to copy ImgBurn isos with the TOC to a Windows host, burn them to a CDRW with ImgBurn and then dump the CDRW into bincue. This takes usually up to an hour due to network speed and the fact the CDRW I have can only be burned with 10x speed and dumped back again at 5x-6x. Also Windows is slow on its own. I sure do enjoy heroically fighting with issues that do not exist on free operating systems.

    i/o Error

    Your disc is copy protected.
  19. What'sUPDoc

    i/o Error

    Hello, can anybody help with this? After doing ANY DVD on my disc in the background and doing Image burn from DVD to disc, I get the attached error message: i/o Error! SK interpretation: Illegal Request ASC/ASCQ interpretation: Copy Protection Key Exchange Failure - Authentication Failure IS there a fix for this error? Thankyou in advance for your efforts. ING BURN ERROR MESSAGE.docx
  20. ranshe7

    Extracting karaoke from DVD disc

    You can use imgburn to create a disk image and save it to your computer. Or simply copy the files to your computer's hard drive. Read the FAQ for this program.
  21. ranshe7

    Formatting and zeroing a new BD RE 50 GB

    What parameters should be set and how to format the BD-RE 50gb disk in ImgBurn correctly, so that it is really a disk of this size, and not less? Is there any step-by-step instructions?
  22. ranshe7

    wii iso roms

    Reinstall the system cleanly, remove everything from the boot disk, and then install ImgBurn and do not install anything else. The system is one program, and check the drive, only when these same errors appear again it will be possible to climb with" peace of mind " and change all sorts of system settings.
  23. Earlier
  24. dbminter

    Xbox 360 iso burning failed

    That log is an empty file.
  25. michael myers

    Xbox 360 iso burning failed

    I tried to burn a xbox 360 game into a dvd+r dl but this error keeps appearing, thanks advance for the help fix.log

    Verify vs Hardware Defect Management

    As verify re-reads the image and compares it at bit level against what's read from the disc, it can actually be better at finding problems. For example, if there's an issue with data corruption when reading from the source drive (but no 'hard' error) or a memory issue (faulty ram), verify would give you a 'miscompare' error. Hardware Defect Management won't notice that kind of thing. As you say, it's pointless formatting with spare areas and then turning on fast write. Just format without spare areas. Only if I really wanted to make sure everything was ok would I use hardware defect management AND verify. I don't think I'd rely on hardware defect management alone (as in, verify being disabled), but I'd certainly rely on verify alone (as in, without HDM being active during the writing phase). Yes, spare areas are transparent to software. The drive handles remapped blocks itself internally.
  27. I'm new to burning blu-rays (BD-RE specifically) so I've been reading a ton on disc formats, spare areas, fastwrite, etc. What's not clear is whether ImgBurn's "Verify" functionality is equivalent (in terms of guaranteed burn accuracy) to the internal Hardware Defect Management functionality. In other words, is it redundant to have spare areas enabled, fastwrite off, and Verify checked? Since Hardware Defect Management slows the burn speed to 0.8x (for my discs), I'm considering using fastwrite to disable Hardware Defect Management (which makes spare areas pointless so I'd reformat without them), allowing me to burn at 2x and then use ImgBurn's Verify feature to re-read the disc at 4-8x. This should be faster than using Hardware Defect Management, but I'd like to know whether the integrity of the burn is verified the same way with just the Verify feature and no Hardware Defect Management. Second question: Are spare areas transparent to the application reading the data? I'm wondering if I burn an iso created from a bit-for-bit image of a different disc (could be BD or DVD or CD) if having spare areas enabled or disabled will change the data on the disc (e.g. a hash of the disc will be different from the "master" iso, or if ripping the burned disc would result in a different iso than the original). It sounds to me like this would not be the case but I'd like confirmation about this as well. Thanks!
  28. dbminter

    wii iso roms

    You can probably save a disc by posting a log.
  29. 10slefty

    wii iso roms

    Thanks for your responses. One thing i will try is to burn a different game wii iso and see if the result is the same .
  1. Load more activity

Important Information

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