Search the Community

Yes, I've seen that guide before. Unfortunately it is specific to a Microsoft file system. I haven't tried it. In fact my problem is also finding the famous boot image. I can't identify it as it's different from the guide. I think the structure created in the pen drive has to do with a Linux type operating system. Anyway, thanks for the support

Well, very few people actually patrol the forums much anymore. So, you're probably not likely to get another answer. In the meantime, if you haven't tried this already, see this Guide: Unfortunately, this guide is fairly old and it was what I followed to try and create bootable ISO's that never booted.

it doesn't suit me. My goal is to create an obviously bootable ISO file. Thank you all the same. Do you think I should wait if some other expert on the forum and the ImgBurn program could help me or should I already close the thread with your previous answer, so it's not possible?

With creating a bootable ISO from a set of files and a bootable image extract: nothing. What I do is with a bootable flash drive, I use a piece of paid software called Macrium Reflect to image the flash drive. It doesn't create ISO's though, but a proprietary file format it can write to flash drives.

Unfortunately, I never got a successful bootable ISO to ever be created by ImgBurn's Build mode.

Good morning to the whole community. I'm trying to understand where is the mistake I'm making even though I have dozens of tests without a correct result, that is, I can't boot the ISO created from a bootable USB pen drive. Premise I downloaded Kaspersky Rescue Disk. The file is an ISO. I install the ISO on the pen drive through RUFUS. The pen drive is bootable and its operation is correct (tested on PC after bios post and before the operating system). Problem How do I get the reverse process now? That is, through imgburn I want to create a bootable ISO starting from the pen drive. Resolution (currently unsolved). Obviously I start the ImgBurn program, click on creating a new image from files/folders. I select the source letter of the pen drive, select the advanced tab, then select the bootable disk tab. I activate the make a bootable disk flag Now I tried to extract the boot image and insert it into the boot image. Start the creation of the ISO but the newly created file is not bootable (tested with a virtual machine) while the original ISO works correctly (again tested with a virtual machine). I also tried looking for a boot image from the disk, but I can't figure out which file to select and if there is any other flag or value I need to set This helps me understand which are the correct settings I need to use. The problem is that some programs allow you to directly create a bootable USB pen drive without the possibility of having an ISO to manage instead. Where is the error? Thank you

I use BD-R because it will last longer than an SSD. But, you have to have 40 BD-R to equal the storage capacity of one 1 TB USB SSD. So, you run into a storage space issue. But BD-R cannot accidentally have content erased, as you said. However, given the steady decline of optical media, there's no guarantee they will still make optical drives to read your backups from some years in the future if you need them. A USB SSD should work as long Windows has the necessary drivers for it. I use the USB SSD's for "temporary" storage, and by that I mean content I only intend to retain for a year at the most. USB SSD's write faster so for those backups, I don't need longevity and faster write speeds are preferable. I'm talking things like monthly and yearly file backup archives and monthly and yearly partition image backups. And they do make 1 TB flash drives now. While slower writing than a USB SSD, they are just as universally ubiquitous. As long as Windows has the necessary drivers, it should just be a matter of inserting a flash drive and it works. And they take up less space than a USB SSD. Plus, you need a cable to access the data on a USB SSD. With a flash drive, it has its own connection constantly. I use CD-R exclusive for Audio CD and DVD-R/DVD+RW/DVD+R DL for DVD Video. All of my other optical disc backups are to BD-R because they write faster and they last much longer than dye based recordable media. Plus, they're like $1 each in bulk. I don't paying a little extra for the speed benefits and the longer life.

I use optical media for backup purposes, not for general usage. helps keep wear on the drive less this way and it's not like one really need to use CD/DVD etc much nowadays besides data backup anyways given one can get plenty of hard drive space for reasonably cheap for quite some time now. p.s. if you wanted you could say make a single uncompressed rar/zip file with a bunch of smaller files if you wanted. but I guess it depends on how small and how many as to whether it might be worth doing that or not. like if it's a bunch of smaller txt files, I would probably create a single '.7z' file with compression here. but if the files are not too small and you don't have tons of them, just burn them to CD/DVD straight up.

Some more tests I had a chance to perform: Disc image read of a bootable DVD written to Memorex Ritek 2x BD-RE: Passed. Bootable DVD image written to Memorex Ritek 2x BD-RE: Passed. Booting of bootable DVD image written to Memorex Ritek 2x BD-RE: Passed.

I am a tad bit concerned about the read speed of Memorex Ritek 2x BD-RE. I read in a bootable DVD image written to a BD-RE that was about 800 MB, but took 1 minute to read in at only 2.8x. I 16:17:51 Source Media Type: BD-RE (Disc ID: RITEK-BW1-001) I 16:17:51 Source Media Size: 801,112,064 bytes I 16:19:06 Average Read Rate: 11,176 KiB/s (2.5x) - Maximum Read Rate: 12,163 KiB/s (2.8x) Of course, this was a very small data set. A larger set might read faster.

More test results: Playback test of inkjet printable MKM Verbatim DataLife Plus/AZO 8x DVD+R DL passed. CD Audio disc read to image test passed on the following media: Memorex CD-R Verbatim DataLife Plus/AZO inkjet printable CD-R Verbatim DataLife Plus/AZO branded surface CD-R Memorex 24x Ultra High Speed CD-RW

Had a few extra minutes to run some other tests. They weren't really necessary, but they were quick, so I ran them. CD Audio disc read to image test passed on the following media: Memorex CD-R Verbatim DataLife Plus/AZO inkjet printable CD-R Verbatim DataLife Plus/AZO branded surface CD-R Memorex 24x Ultra High Speed CD-RW

There is a 3.11 firmware available for this drive, however it is only available on units that ship directly from ASUS factories. There is no firmware update package for 3.11 and there won't be. ASUS informed me this drive has reached the end of its product support life. Which means it won't receive any more firmware updates. So, it will probably be unavailable at some point in the near future. Here's the precise quote from ASUS: "This unit is end of life, which means there will be no future updates for this device bios or firmware." Here are my test results under 3.11 firmware, in no particular order: MKM 8x DVD+R DL: Firmware 3.11 fixed the MKM Verify failure at the Layer change that made 3.10 a deal killer! Both branded and inkjet discs tested. A note on the write rate. The max was 8.1x but the average was 6.3x. This ASUS unit writes slightly less efficiently to 8x DVD+R DL. The LG WH16NS60 writes them first at 4x for 2 and a half minutes, then at 8x for most of the rest of the time, then 4x for the last 2 minutes. The ASUS writes at 4x for the first 2 and a half minutes, then at 6x for another 2 and a half minutes, then at 8x for most of the rest of the time, then drops to 6x for some of the end time, before dropping to 4x for the last 2 minutes. The drive does appear to have one problem. It ejects discs too forcibly. Meaning if the drive is on its side, this is a big issue because the discs fall out onto the floor! 2 out of 3 burns resulted in the disc on the floor, either before Verify or after it completed. Which means you must place this unit flat, so it can't be used in a PC case where the drives are placed on their side or if you're using a USB enclosure, you cannot put the drive on its side. It MUST be flat. Both types of 8x DVD+RW from Ritek, RICOH and the Imation ones, still are good in 3.11. 3.11 doesn't destroy the discs anymore. I also performed formatting tests on these 2 discs. Formats, writes, and Verifies passed for both discs. As did writing a 2nd time to each disc after the first formats and writes. Data write to BD-R passed. Verbatim DataLife Plus/AZO inkjet 16x MCC DVD-R. Write test passed. Memorex Ritek 2x Data BD-RE write test passed. Verbatim DataLife Plus/AZO 16x branded MC DVD-R write test passed. CD data read and image copy test passed. Audio CD disc read test passed. Memorex branded CD-R Audio CD write test passed. Inkjet Verbatim DataLife Plus/AZO Audio CD CD-R write test passed. Branded Verbatim DataLife Plus/AZO Audio CD CD-R write test passed. Memorex Mitsubishi 24x Ultra Speed CD-RW Audio CD write test passed. So, I'm fairly confident this drive is FINALLY read to become my new go to BD drive after 3.11 firmware was released. I still need to perform the playback tests on DVD Video and CD Audio discs to be sure, though. However, I don't generally encounter problems with those tests, but they have resulted in bad playback before. And there are a few other read tests I haven't tried yet, but they're so uncommon I don't know when I'll even come across the possibility of testing those.

Okay, CD data read and image copy test passed. Onto Audio CD disc read test.

16x branded MC DVD-R write test passed. Onto CD data read and image copy test.

Hello people! I was burning some soundtracks onto CD's (using Microsoft Media Player for Windows 7) and i wanted to create a .CUE file of the CD so i can add track info and burn it o another CD. While the first one was created flawlessly, the other CD gets stuck while analizing Track 14. They both have the same amount of tracks and they are the exact same CD (HP Branded CD-R). Is the second disc faulty? or do i need to use another software? Also, here's the ImgBurn Log: I 15:04:23 ImgBurn Version 2.5.8.0 started! I 15:04:23 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 15:04:23 Total Physical Memory: 4.104.848 KiB - Available: 2.138.652 KiB I 15:04:23 Initialising SPTI... I 15:04:23 Searching for SCSI / ATAPI devices... I 15:04:23 -> Drive 1 - Info: ATAPI iHAS122 ZL0C (A:) (ATA) I 15:04:23 Found 1 DVD±RW/RAM! I 15:17:52 Operation Started! I 15:17:52 Source Device: [2:0:0] ATAPI iHAS122 ZL0C (A:) (ATA) I 15:17:52 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) I 15:17:52 Source Media Supported Read Speeds: 4x; 8x; 10x; 16x; 24x; 32x; 40x; 48x I 15:17:52 Source Media Supported Write Speeds: 16x; 24x; 32x; 40x; 48x I 15:17:52 Source Media Sectors: 308.661 I 15:17:52 Source Media Size: 725.970.672 bytes I 15:17:52 Source Media File System(s): None I 15:17:52 Read Speed (Data/Audio): MAX / 1x I 15:17:52 Destination File: C:\Users\exper\Desktop\dfwsef.bin I 15:17:52 Destination Free Space: 5.190.152.192 Bytes (5.068.508,00 KiB) (4.949,71 MiB) (4,83 GiB) I 15:17:52 Destination File System: NTFS I 15:17:52 File Splitting: Auto I 15:18:45 Abort Request Acknowledged E 15:18:46 Operation Aborted! - Duration: 00:00:53 E 15:18:46 Average Read Rate: N/A - Maximum Read Rate: N/A

There are only 2 options in PD20; burn a DVD or create an .iso file. If I burn a DVD I do have the VIDEO_TS and AUDIO_TS on the disc, but it won't play on a standard DVD player. When I develop movies, I create .iso files and play them with VLC until I'm satisfied with the movie, then I had hoped to burn the DVD using PD20 so I could send it to relatives. Now I see I must use the .iso file and burn with different software.

For about 20 years, I've been using ConvertXToDVD to make DVD's. I've always had the software create VIDEO_TS output and used ImgBurn to create DVD Video discs from the VIDEO_TS and burn the resulting image file it creates with it.

Hi Lightning UK, I'm using HP DVD+R Double Layer 8X 8.5GB 240min Video The Power Director 20 (PD20) can create an .iso image file and / or burn a DVD. If I choose the .iso file (playable on the computer using VLC) I can then use a burning software to burn a DVD and it will play on a standard DVD player or a computer. (PD20 doesn't have an option to burn a DVD from an .iso file.) If I choose to burn the DVD directly from PD20 the DVD will play on a computer but not on a standard DVD player. I have a software called DVDfab Copy. If I start DVDfab and put the PD20 disc in the drive, DVDfab doesn't do anything. I have to select the DVD drive for the software to open the disc for copying. If I press the 'info' button it says the disc is DVD (Data) (see above). If I put the ImgBurn DVD in the drive, DVDfab immediately recognizes it and prepares to copy the disc. Pressing the 'info' button the disc shows DVD (DVD-Video). The latest update from Cyberlink support says PD20 produces a DVD disc that can be played on the computer using VLC and that's all it's supposed to do. That's not helpful because why would anyone want a DVD that can be played ONLY on a computer and not a standard DVD player. Most of my family is older, doesn't own a computer but does have a DVD player. At this point I'm flogging a dead horse. Cyberlink support isn't about to either admit the PD20 software doesn't produce a DVD for a standard player or to contact the development team to find out why. I see my solution as using ImgBurn to use the .iso file from the PD20 output. Their movie producing software is good and I'm familiar with it now so I'm not about to change. I'll just add the extra step as a manual 'finishing' process. I was hoping I could be able to definitely find out why and let them know so they could update it. However, I've not been able to determine why their software burns (what appears to be) a data DVD, playable only on a computer.

If you can take an image of a disc that doesn’t play and burn it again with ImgBurn so it then plays, it could be something like booktype/ bitsetting. Are you using dvd+r format discs?

Hi DB, thanks for the reply. I'm over in Lexington 🙂 They reply once a week and their forum is set up so you can reply only once to their post, then you have to wait until they reply again. I'll save your information for the next go around but I'm not sure what it means. I don't know how to burn a video DVD as a Data DVD. I've never seen an option to do that. When you look at the files they still show the TS_Video and TS_Audio file structure, just like a video DVD. None of my players will play them but I can burn from the .iso file using ImgBurn and play it. At least I can use another software to create the DVD and make it work, so I have a work around.

I'm hoping someone here can answer my question. I use Program Director 20 to make movies. An output option for the source is to burn to a DVD or .iso file. If I choose to burn the DVD it won't play on a stand alone DVD or Blu-ray player. The screen says 'unable to read disc'. I can put the same DVD in a computer DVD drive and it will play. I can take the .iso option and create the file, then use a separate tool (ImgBurn) to create a DVD that will play on the external DVD / Blu-ray or a computer's DVD drive. I have software that will look at the 'info' for a DVD. For the one created by Program Director it shows "Data DVD" and for the one created by ImgBurn it shows "Video DVD". I have been trying to work with the Program Director support team to get them to understand that the DVD they produce will not play in the stand alone players (I have 3). They claim that because they can play the discs on their computer using VLC that they are valid DVD discs. I say that computers can read/play either a Data or Video DVD but stand alone players. can't. They disagree and say their software will burn only video DVD on a video DVD disc. Does anyone know what setting they may have set incorrectly to produce a Data DVD instead of a Video DVD? -Arthur K

I tested a 3.10 firmware updated drive back in 2019, but never updated this post with my results. The 3.10 firmware seemed to fix the DVD+RW and BD-RE destruction issues. I did not encounter that with the 3.10 firmware. However, the drive was still borked. This time, it was a test of MKM-003 Verbatim DataLife Plus DVD+R DL. Burn completed correctly but failed Verify at the Layer change. I took the next disc in the cake stack and burned the same image with my LG WH16NS60 and it was fine, so I laid the blame on the firmware. It COULD have been a simple bad disc in the cake stack, but I highly doubt that. Could also have been a bad CD/DVD laser in the BD unit I got, but, again, I highly doubt that.

Here is the log you asked for. Its Succes! I 01:30:02 ImgBurn Version 2.5.8.0 started! I 01:30:02 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 01:30:02 Total Physical Memory: 16,600,288 KiB - Available: 6,788,132 KiB I 01:30:02 Initialising SPTI... I 01:30:02 Searching for SCSI / ATAPI devices... I 01:30:02 -> Drive 1 - Info: ASUS BW-16D1HT 3.11 (H:) (RAID) I 01:30:02 -> Drive 2 - Info: ASUS DRW-24D3ST 1.01 (I:) (RAID) I 01:30:02 Found 1 DVD±RW/RAM and 1 BD-RE XL! I 01:32:49 Operation Started! I 01:32:49 Source File: F:\Ripped DVDs\The Batman (2022)\The Batman (2022) [DVD9].mds I 01:32:49 Source File Sectors: 3,869,472 (MODE1/2048) I 01:32:49 Source File Size: 7,924,678,656 bytes I 01:32:49 Source File Volume Identifier: The Batman (2022) I 01:32:49 Source File Volume Set Identifier: 579FBC50003B0B19 I 01:32:49 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 01:32:49 Source File Implementation Identifier: ImgBurn I 01:32:49 Source File File System(s): ISO9660, UDF (1.02) I 01:32:49 Destination Device: [0:0:0] ASUS BW-16D1HT 3.11 (H:) (RAID) I 01:32:49 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) I 01:32:49 Destination Media Supported Write Speeds: 4x, 8x I 01:32:49 Destination Media Sectors: 4,173,824 I 01:32:50 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes) I 01:32:50 Write Mode: DVD I 01:32:50 Write Type: DAO I 01:32:50 Write Speed: MAX I 01:32:50 DVD+R DL Reserve Track: No I 01:32:50 Link Size: Auto I 01:32:50 Lock Volume: Yes I 01:32:50 Test Mode: No I 01:32:50 OPC: No I 01:32:50 BURN-Proof: Enabled I 01:32:53 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 01:32:53 Optimal L0 Data Zone Capacity: 1,991,792 I 01:32:53 Optimal L0 Data Zone Method: Copied From Original Disc I 01:32:53 Set L0 Data Zone Capacity Succeeded! I 01:32:53 L0 Data Zone Capacity - Effective: 1,991,792 I 01:32:53 Filling Buffer... (80 MiB) I 01:32:54 Writing LeadIn... I 01:33:24 Writing Session 1 of 1... (1 Track, LBA: 0 - 3869471) I 01:33:24 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3869471) I 01:33:24 Writing Layer 0... (LBA: 0 - 1991791) I 01:41:31 Writing Layer 1... (LBA: 1991792 - 3869471) I 01:48:49 Synchronising Cache... I 01:48:50 Closing Track... I 01:48:52 Finalising Disc... I 01:50:12 Exporting Graph Data... I 01:50:12 Graph Data File: C:\Users\Manjunath\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1HT_3.11_01-JANUARY-2024_01-32_AM_CMC_MAG-D03-64_MAX.ibg I 01:50:12 Export Successfully Completed! I 01:50:12 Operation Successfully Completed! - Duration: 00:17:22 I 01:50:12 Average Write Rate: 8,375 KiB/s (6.2x) - Maximum Write Rate: 10,976 KiB/s (8.1x) I 01:50:12 Cycling Tray before Verify... W 01:50:20 Waiting for device to become ready... I 01:50:31 Device Ready! I 01:50:36 Operation Started! I 01:50:36 Source Device: [0:0:0] ASUS BW-16D1HT 3.11 (H:) (RAID) I 01:50:36 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: CMC MAG-D03-64) I 01:50:36 Source Media Supported Read Speeds: 2x, 4x, 6x, 8x, 10x, 12x I 01:50:36 Source Media Supported Write Speeds: 4x I 01:50:36 Source Media Sectors: 3,869,472 (Track Path: OTP - L0: 1,991,792 - L1: 1,877,680) I 01:50:36 Source Media Size: 7,924,678,656 bytes I 01:50:36 Image File: F:\Ripped DVDs\The Batman (2022)\The Batman (2022) [DVD9].mds I 01:50:36 Image File Sectors: 3,869,472 (MODE1/2048) I 01:50:36 Image File Size: 7,924,678,656 bytes I 01:50:36 Image File Volume Identifier: The Batman (2022) I 01:50:36 Image File Volume Set Identifier: 579FBC50003B0B19 I 01:50:36 Image File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 01:50:36 Image File Implementation Identifier: ImgBurn I 01:50:36 Image File File System(s): ISO9660, UDF (1.02) I 01:50:36 Read Speed (Data/Audio): MAX / MAX I 01:50:37 Read Speed - Effective: 5x - 12x, 12x - 5x I 01:50:37 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3869471) I 01:50:37 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3869471) I 01:50:37 Verifying Layer 0... (LBA: 0 - 1991791) I 01:56:24 Verifying Layer 1... (LBA: 1991792 - 3869471) I 02:01:42 Exporting Graph Data... I 02:01:42 Graph Data File: C:\Users\Manjunath\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1HT_3.11_01-JANUARY-2024_01-32_AM_CMC_MAG-D03-64_MAX.ibg I 02:01:42 Export Successfully Completed! I 02:01:42 Operation Successfully Completed! - Duration: 00:11:05 I 02:01:42 Average Verify Rate: 11,655 KiB/s (8.6x) - Maximum Verify Rate: 17,726 KiB/s (13.1x) I was so anxious for burning this disc. Both Drive and Disc I choose to burn was risky Please update me here, when you do the complete re-testing of this drive. Thank you for you and your team (If it exits) for still looking after imgburn App.

Thanks for all that info! If you're willing to possibly waste a DVD+R DL to test the ASUS 3.11 firmware with, by all means do so! Saves me having to buy it, test it, and possibly return it. If you do test, look for a failure to Verify at the Layer change, so make sure the image you burn is more than 4.7 GB. As for the destruction of DVD+RW and BD-RE, 3.10 apparently fixed those two issues. Those were the first two things I tested in 2019 when I tried updated firmware for that ASUS BD drive. It was when I tested DVD+R DL that I sent the drive back after it failed. In 2016, when the drive was relatively new, the first thing I tested was DVD+RW. I had a chance to write a BD-RE shortly after the DVD+RW failure so I decided to go ahead and try it in the ASUS as another test and it destroyed the BD-RE, too. If you test DVD+R DL and post the results, if you get it work without failure, I'd be inclined to try the drive again and run my battery of tests on it.