All Activity

just use K3b come on man

Oh, yeah, I didn't think of it in that way. If you have a DVD+R and you want to "convert" it to DVD-R, you can't physically transmute the DVD+R to DVD-R, but you can copy the DVD+R's contents to a DVD-R. Just insert the DVD+R into a drive, use ImgBurn's Read mode to read the DVD+R to an image file, and then use ImgBurn's Write mode to burn that image read in Read mode to a DVD-R.

I figured it might be used to drag and drop files into Build mode. Never thought it might also add the files to Write mode's queue.

Assuming you're talking about the physical discs themselves. It's like turning an apple into a banana. If, however, you have something burnt to a DVD+R that you want to burn to a DVD-R, that's something totally different.

A place to drop stuff. It's a little window that's meant to stay on top of other windows (when the program's main window doesn't), so you can drag+drop to it. That in turn is then supposed to add dropped files to the queue (if in Write mode) or source box (if in Build mode).

Here's your most probable cause: I 13:31:18 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) You're probably using the Life Series Verbatim you find in brick and mortar stores. Those are the CMC garbage. CMC Magnetics Corporation makes the worst optical media out there. Unfortunately, they also OWN Verbatim. However, luckily enough, Verbatim does offer a higher quality CD-R and those are the ones you should be using. Look for the DataLife Plus series (NOT Life Series.) aka AZO discs, which you can generally only find in online stores. Those are some of the best out there, as they're actually made by Mitsubishi. Keep in mind, this is not a 100% guaranteed fix, but it is where I'd start first. I don't know why you included a log portion referencing BD-R operations, though...

trying my best to burn some dreamcast games onto a verbatim CD-R. using a 700 mb and downloading a 650 mb game. keep getting this error message, ive tried everything i can think of so far including using a new kind of disc, but all the research has said either it's the disc (recommending the disc im using) or the burner, and ive used this burner successfully a few times. anyways, here's the error log, the main thing is that it keeps stopping and saying Invalid Address for Write. I 13:22:21 ImgBurn Version 2.5.8.0 started! I 13:22:21 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 13:22:21 Total Physical Memory: 8,320,160 KiB - Available: 1,787,320 KiB I 13:22:21 Initialising SPTI... I 13:22:21 Searching for SCSI / ATAPI devices... I 13:22:21 -> Drive 1 - Info: hp PLDS DVDRW DU8AESH 6HSM (F:) (USB 2.0) I 13:22:21 Found 1 DVD±RW! I 13:22:27 Operation Started! I 13:22:27 Device: [0:0:0] hp PLDS DVDRW DU8AESH 6HSM (F:) (USB) I 13:22:27 Media Type: BD-R (Disc ID: 97m26s66f) I 13:22:27 Media Supported Write Speeds: 0.4x, 0.6x, 0.8x, 1x I 13:22:27 Quick Erase: No I 13:22:27 Format Properly: Yes I 13:22:27 Format Size: Preferred I 13:22:27 Format Without Spare Areas: Yes I 13:22:27 Erasing Disc... I 13:22:27 If you don't want spare areas, there's no need to format this disc! I 13:22:27 Operation Successfully Completed! - Duration: 00:00:00 I 13:22:48 Operation Started! I 13:22:48 Source File: C:\Users\17072\Downloads\Jet Grind Radio (USA)[DCRES].cdi I 13:22:48 Source File Sectors: 358,616 (MODE2/FORM1/2336) I 13:22:48 Source File Size: 837,726,976 bytes I 13:22:48 Source File Volume Identifier: JGR_REPACK_DCRES I 13:22:48 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING I 13:22:48 Source File File System(s): ISO9660 I 13:22:48 Destination Device: [0:0:0] hp PLDS DVDRW DU8AESH 6HSM (F:) (USB) I 13:22:48 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) I 13:22:48 Destination Media Supported Write Speeds: 10x, 16x, 20x, 24x I 13:22:49 Destination Media Sectors: 359,844 I 13:22:49 Write Mode: CD I 13:22:49 Write Type: SAO I 13:22:49 Write Speed: 10x I 13:22:49 Lock Volume: Yes I 13:22:49 Test Mode: No I 13:22:49 OPC: No I 13:22:49 BURN-Proof: Enabled I 13:22:49 Write Speed Successfully Set! - Effective: 1,765 KB/s (10x) I 13:22:49 Filling Buffer... (80 MiB) I 13:22:49 Writing LeadIn... W 13:23:00 Failed to Write Sectors -42 - -16 - Reason: Write Error W 13:23:00 Retrying (1 of 20)... W 13:23:05 Retry Failed - Reason: Invalid Address For Write W 13:23:11 Retrying (2 of 20)... W 13:23:11 Retry Failed - Reason: Invalid Address For Write W 13:23:11 Retrying (3 of 20)... W 13:23:11 Retry Failed - Reason: Invalid Address For Write W 13:23:11 Retrying (4 of 20)... W 13:23:11 Retry Failed - Reason: Invalid Address For Write W 13:23:11 Retrying (5 of 20)... W 13:23:12 Retry Failed - Reason: Invalid Address For Write W 13:23:12 Retrying (6 of 20)... W 13:23:12 Retry Failed - Reason: Invalid Address For Write W 13:23:12 Retrying (7 of 20)... W 13:23:12 Retry Failed - Reason: Invalid Address For Write W 13:23:12 Retrying (8 of 20)... W 13:23:12 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (9 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (10 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (11 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (12 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (13 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (14 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (15 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (16 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (17 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (18 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (19 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write W 13:23:13 Retrying (20 of 20)... W 13:23:13 Retry Failed - Reason: Invalid Address For Write E 13:23:15 Failed to Write Sectors -42 - -16 - Reason: Write Error E 13:23:15 Next Writable Address: 4294967151 I 13:23:15 Writing Sectors... I 13:23:15 Synchronising Cache... E 13:23:22 Failed to Write Image! E 13:23:22 Operation Failed! - Duration: 00:00:33 I 13:23:22 Average Write Rate: N/A - Maximum Write Rate: N/A I 13:30:28 Operation Started! I 13:30:28 Device: [0:0:0] hp PLDS DVDRW DU8AESH 6HSM (F:) (USB) I 13:30:28 Media Type: BD-R (Disc ID: 97m26s66f) I 13:30:28 Media Supported Write Speeds: 0.4x, 0.6x, 0.8x, 1x I 13:30:28 Quick Erase: No I 13:30:28 Format Properly: Yes I 13:30:28 Format Size: Preferred I 13:30:28 Format Without Spare Areas: Yes I 13:30:28 Erasing Disc... I 13:30:28 If you don't want spare areas, there's no need to format this disc! I 13:30:28 Operation Successfully Completed! - Duration: 00:00:00 I 13:31:18 Operation Started! I 13:31:18 Source File: C:\Users\17072\Downloads\NBA 2K2 (USA) (Sega Sports)[ECHELON].cdi I 13:31:18 Source File Sectors: 302,916 (MODE2/FORM1/2336) I 13:31:18 Source File Size: 707,611,776 bytes I 13:31:18 Source File Volume Identifier: NBA2K2_ECH I 13:31:18 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING I 13:31:18 Source File File System(s): ISO9660 I 13:31:18 Destination Device: [0:0:0] hp PLDS DVDRW DU8AESH 6HSM (F:) (USB) I 13:31:18 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) I 13:31:18 Destination Media Supported Write Speeds: 10x, 16x, 20x, 24x I 13:31:18 Destination Media Sectors: 359,844 I 13:31:18 Write Mode: CD I 13:31:18 Write Type: SAO I 13:31:18 Write Speed: 10x I 13:31:18 Lock Volume: Yes I 13:31:18 Test Mode: No I 13:31:18 OPC: No I 13:31:18 BURN-Proof: Enabled I 13:31:18 Write Speed Successfully Set! - Effective: 1,765 KB/s (10x) I 13:31:18 Filling Buffer... (80 MiB) I 13:31:18 Writing LeadIn... W 13:31:32 Failed to Write Sectors -15 - -1 - Reason: Write Error W 13:31:32 Retrying (1 of 20)... W 13:31:37 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (2 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (3 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (4 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (5 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (6 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (7 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (8 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (9 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (10 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (11 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (12 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (13 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (14 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (15 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (16 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (17 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (18 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (19 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write W 13:31:43 Retrying (20 of 20)... W 13:31:43 Retry Failed - Reason: Invalid Address For Write E 13:31:47 Failed to Write Sectors -15 - -1 - Reason: Write Error E 13:31:47 Next Writable Address: 4294967151 I 13:31:47 Writing Sectors... I 13:31:47 Synchronising Cache... E 13:31:49 Failed to Write Image! E 13:31:50 Operation Failed! - Duration: 00:00:31 I 13:31:50 Average Write Rate: N/A - Maximum Write Rate: N/A

Question as is in the Title. Thanks!

Oh dam

CMC has a track record of changing manufacturing processes and borking discs. At one point, DataLife Plus DVD-R from Verbatim stopped working with the LG WH16NS60. The solution was to stop using them and switch to CMC Pro discs. Yes, even something with CMC in its name CAN be high quality because CMC Pro discs are not made by CMC. CMC Pro discs are made by Taiyo Yuden, which was the other high quality manufacturer of optical media along with Mitsubishi. CMC Magnetics then bought out TY like they did with Verbatim. Eventually, a firmware update to the NS60 fixed the issue, just reinforcing CMC changed the manufacturing process of the DataLife Plus DVD-R as only a firmware update for the NS60 fixed it. As for tests over time, I went through hundreds of BD-R's burned more than 5 years old over the past few years. All of those were the old Verbatim blue and white branded surface discs burned by ImgBurn in an LG WH16NS60. Every single one I burned still had totally readable contents after 5 years since burn. They were put in one of those CD carrying cases that hold like 320 discs and just stored in the corner of the room where I keep the PC in.

I see... From what I can figure out, the 3 batches you tested might have been manufactured in different dates so they must have aged by at least an year, the batch which worked probably was newer too. And it might also be that, before you got them, they have been kept in improper conditions in the warehouse by the retailer. While all this is simply a theory, it's a fact that not all discs are made the same. Best we can do is to see what we get from our order, burn the stuff to the discs, watch them over from time to time. If issues appear, we could research what we think that happened to the disc, how long did it take since it was burned (and how long was it since delivery). Conclusion is that we are lacking proper experimental data, of like... 10 discs of each variant from all manufacturers, where they burn the same content at the same time and are tested in different storage environments to see how they degrade, how long does it take, if can data be salvaged and so on. I will keep using these discs and provide data from time to time.

All I can add is even if BD-R completes Write and Verify doesn't mean it's any good. Last year, I had an experience with BD-R from CMC. For a decade, Verbatim, owned by CMC, made a high quality BD-R that was branded with a blue and white Verbatim label. I only ever had 1 failure that was not down to a drive that needed replacing and that was oversight on my part. However, I discovered a cake stack of these BD-R I had last year were completing Writes and Verifies, but were partially and sometimes totally unreadable in less than a week! Thinking it was just a bad batch, I got another and those were fine. Thinking it was just a fluke, I got a 3rd batch and out of those, only 1 completed Write and Verify while all the others I tested did not complete Writes! It didn't matter if I used my ASUS or LG BD burner, the results were the same, meaning it was the media. So, CMC changed the quality of the branded Verbatim BD-R so they're junk now. The DataLife Plus BD-R from Verbatim appear to still be good, but you can only get those in inkjet printable variety. So, you're paying an unnecessary extra fee for something you probably won't use just to get quality media. DataLife Plus (aka AZO) was always Verbatim's high quality CD-R, DVD-/+R, DVD+RW, and DVD+R DL made by Mitsubishi. Everything else is Verbatim's Life Series which uses CMC junk, except for the branded Verbatim BD-R. They weren't labeled Life Series and don't appear to be "CMC" in that the DID is "VERBAT-IM-000" but they are typical Life Series trash quality.

You can't.

This is old news, because many already did many variants of a "Petabit Optical Disk" all over the work, the oldest variant being this one: Hyper CD-ROM According to Wikipedia, the technology used to make this disc was used by Sony to make the system named "Blu-Ray". This has a theoretical limit of 100EB (Exabytes) but until litography technology reaches that level, let's say the "Petabyte Disk" is attainable right now in labs pretty easily, and should see the light out of the box in consumer houses in the next 20-30 years. (yes, that late because there's little interes, and because what dbminter said is valid too) NOTE for dbminter: Even if the disc is WAY bigger than the total storage the consumer would have in his house, he can still burn to such a disc little by little using it exactly like a hardrive, although the files will permanently stay there and take up storage, unless he would use a ReWritable variant of the disc.

Personally I had no issue burning on the BD-R SL discs from MediaRange which is (CMCMAG-BA5-000) and I've burned 66 discs until now from 3 different spindles so according to their known low build quality and drive burning issues, I should have had at least one discs to fail while burning. None so far. All there is to do now is verify the discs on yearly basis and see if they start getting dead sectors. Especially if there are visible signs of disc rot.

How can I turn a dvd+r into a dvd-r

1PB (petabyte) is equal to 1080TB (terabyte) which is equal to 1166400GB (gigabyte) After formating to the filesystem on Windows it becomes a round 1000TB or 1000000GB. So doing the same math as above using these values, it would be like this: 1166400 / 25 = 46656 (discs to burn) 46656 * 20 = 933120 (minutes of burning discs) 933120 / 60 = 15552 (hours of burning discs) 15552 / 24 = 648 (days of burning discs) All this would mean: 1 year and 283 days of burning discs.

Hello there! Glad to become part of community!

Hi, I'm new around here and this is my first post on ImgBurn's forum so bear with me 🤔 A friend of mine started doing a pretty nice project with an animated series I liked, but due to the sheer size the final result had I was in a pinch deciding where to actually store all of it... after thinking on the situation for a bit I reached the conclusion to use BD-R discs. For my needs best would have been BD-R DL or BD-R XL but their price kept me VERY far away, so single layer (SL) discs were the way to go. Considering the market in my state and prices in local retailers, I decided to get spindles of MediaRange BD-R SL discs at a price of 0.59$/disc with shipping included. Upon the arrival of 4 spindles containing 25 discs each I started researching on the best method to burn BD-R discs with ImgBurn, after a few dozen discs burned with no issues, I wanted to see how high rated are they among other people by searching the disc's ID. (now imagine how deep my soul started sinking when I saw that CMC discs had a high failure rate after burning them an year or so later) I've started doing a comprehensive list of .IBG files from ImgBurn's burning results, making snapshots of DVDInfoPro's graphs, gathering information about the discs and my Blu-Ray Writer, which doesn't have pretty good reviews either (soul proceeds to sink deeper) and I am now patiently waiting for them to reach 1 year old so I can start verifying and testing them if they TRULY are that cheap for a reason. I'll leave below Google Drive links of my research's results, so if anyone sees the information I provide here as useful and actually tries to work with these discs, tell me how it went in the thread. ImgBurn Graph Data Files (66 Discs) DVDInfoPro Graph Snapshots (66 Discs) DISC INFO Package Photos And here is the data of the driver I've used to burn these discs with. (maybe relevant to those who burn the same discs but with another writer and have, or not, issues with the discs afterwards) ASUS BW-16D1X-U NOTE 1: Unfortunately, it would seem this Blu-Ray Writer doesn't support PIPO scans, so proper verification according to the standard of ImgBurn's team won't be possible unless I get my hands on one which supports it. NOTE 2: I will update the content of the links above with more data after the first year since I burned the discs ends. As I will make a verification for each disc to see if they have any failures with VSO Inspector. NOTE 3: Any ideas of how I could research the discs further would be an awesome help 😥 THANKS FOR READING!

I will look into why /ERASE isn’t working for BD-R formatting.

If it asks to place a layer break, then it can't be under 4 GB. Interesting that the LBA % asks for 100. Hm. That's some bizarre and apparently shoddy ISO if it is indeed 1.) under 4 GB and 2.) asking to place a layer break on DVD-5 contents. In Write mode, open the ISO for burning but don't write it to anything. Just select the one LBA option and see what happens at that point. If the Write operation sits there waiting for you to start it, then the ISO apparently loaded okay. If it did load okay, post a screen shot of ImgBurn in Write mode waiting for you to start burning after loading the ISO.

The .iso is 3.94GB This is the layer break that he has come up:

Burn it as you normally would an ISO to any # of layers disc. Unless the settings were changed otherwise, the only difference is ImgBurn will detect the smaller size being attempted to be burned to a disc larger than required and prompt you if you're certain you want to "underburn."

I'm trying to help someone on another forum. I have never done this with ImgBurn. The .iso is less than 4.35GB but all that are available are DVD DL discs. How can a SL size .iso be burned to a DL DVD with ImgBurn?

Yeah, looks like over 50%. But, that's a good baseline. Thanks for gathering that data for me!