Search the Community

In a previous version of IMGBURN I was able to add my Menu image to a Personal image wanoka.jpg. Is there a process to customize my menu using imgburn? If not, Can you recommend a method to customize my DVD Menu? Thanks, Scott McClintock (WanokaFalls)

It could be that the 2 image.dat files are just raw sector dumps, the same as an iso. are their sizes a multiple of 2048? try and open the one from the layer 0 folder in Write mode. if that use the ‘create .dvd file’ option in the tools menu and add both files to the list. Specify the layer break as whatever the size of layer 0 image.dat is, divided by 2048. Save the .dvd file and then load that in Write mode. you could test the .dvd file by mounting it in virtual clonedrive. If you can see the contents by browsing the virtual drive, go ahead and burn the .dvd to disc in write mode.

I couldn't see a way to reply to the existing thread so posting here instead.. Original thread: ---- Hello, I would be eternally grateful if someone could help me. I have 2 folders generated to burn a DVD DL which are LAYER 0 and LAYER 1. Inside them I have the files CONTROL.DAT, DDPID and IMAGE.DAT. How can I extract them to generate an .iso or burn them in ImgBurn so that they run as DVDs? Is it possible to convert .DAT to VIDEO_TS and then write as files in a Disc or mount a .iso? Thank you. ---- The DDP files are what get's sent to a disc replicator as previously mentioned. They Contain the VIDEO_TS and AUDIO_TS folders saved per layer to represent the physical disc. As there are are two layers it means that your original master is a DVD 9. A DVD 5 will only have Layer0. You can play the .dat files in VLC albeit with limited control but it is at least useful to check what is there. You will also see the DVD menus if there are any. If you need help converting back to the original files I can help if you like. feel free to reply or message me.. Thanks.

Hello, I would be eternally grateful if someone could help me. I have 2 folders generated to burn a DVD DL which are LAYER 0 and LAYER 1. Inside them I have the files CONTROL.DAT, DDPID and IMAGE.DAT. How can I extract them to generate an .iso or burn them in ImgBurn so that they run as DVDs? Is it possible to convert .DAT to VIDEO_TS and then write as files in a Disc or mount a .iso? Thank you.

I've no idea what you have there. Generally, it's not easy to determine what files exactly are on Layer 0 and which are are Layer 1. .DAT files could be anything. I just know they're not DVD Video. Is this some kind of car navigation disc, possibly? What contents are in the Layer 1 folder? Depending on what these files are for, this may or may not work. In Build mode, add all the files and folders from the Layer 0 folder to the root directory of the Project and repeat for the Layer 1 folder. If you are prompted to replace any files, you may as well give up because it's probably impossible to determine which files are the "real" ones (From Layer 0 or Layer 1.) and which are not. Then, create an ISO from this Build job and burn the ISO to a DVD DL disc.

I am creating an image file (ISO) from a mounted Win 11 Pro ISO. I used the 'Extract Boot Image' option to extract the boot image from the mounted Win11 ISO. When I accept the option to 'use the boot image file in your current project', the Platform ID is set to 80x86. My system,though, is UEFI. Before I save the project should I change the Platform ID to UEFI or leave it at 80x86? If I do change the Platform ID from 80x86 to UEFI prior to the build, will this create a problem during future Win 11 boot installations with a USB boot drive created by Rufus from the ISO?

Hello, I recently created a program to automate writing cue files based on the titles of MP3 files in a given directory. I followed the exact same format as imgburn's cue files and got the program to succeed even without putting in the line of the REM FILE DECODED size for each track: Imgburn could recognize the file and burn the disc with the exact CD text I desired. My only concern is that now, Imgburn performs 'Analyzing Audio Files' each time I want to burn the image files created with my program. This is opposed to it only doing it once when I create a cue file from Imgburn itself and it won't have to decode each file every time I want to burn that image. This isn't really a big deal; however, I do burn many copies of an image and having to convert files prior to each burn of the image would be a bit taxing on my computers. (I use older machines for burning.) I think this is only because I don't specify the REM file decoded size in my custom cue files from my program. I did some more digging and I saw someone able to do it when they were creating a similar program of writing cue files with python. I personally am using Java for my program and there was no good way of getting the decoded size of an MP3 in MM:SS:FF format. However, there is an easy way to just get the normal playable length of the MP3 file using java. This leads me to my question of: Can I just use the length of the MP3 file itself as the REM file decoded size? I also read somewhere that the length should be almost the same and the only difference would be a couple of frames; there are 74 frames in a whole second of audio so I would only be compromising a maximum of a single second in audio? I really wouldn't notice that at all. But I just want to make sure that what I plan to do won't ruin the whole point of a traditional audio CD as opposed to a data CD of MP3s or MP3 CD. Another general question I had about the way Imgburn works: are these decoded files whenever Imgburn performs the 'Analyzing Audio Files' constructed in memory as the disc burns? I still can't piece my around how I have normal cue files that do not correspond with a binary file of the raw data structure of an audio CD. I feel like I read somewhere on the forum that the files are constructed in small segments in memory as the burn proceeds but I just wanted to confirm. I apologize for a very long initial post and I thank those who bother reading even a portion of it. Thanks for any help in advance!

Hello experts. I'm in need of create image file from optical disc in these 3 formats: dmg , pdi , gi It was on the list of ImgBurn supported formats, not sure if is read only or write also supported? If not, please advise which Windows software can do it? Or anywhere we can download a small disc image in dmg , pdi , gi formats? Thankssssss

Anyone knows if you can convert an audio CDI to BIN/CUE via batch/CMD? I have a ton of CDI images that was created via my Cronus disc publisher. Unfortunately the software for it only supports CDI image type for audio CDs and ImgBurn has been the only app to even open the CDI files.

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 need clarification of Section 3.3.2.3.4 Bootable Disk settings. First and foremost I want to say that, in general, the documentation, tutorials, and guides are exceptional. There does seem to be a tendency to assume the audience is of direct peer quality, or close. On many occasions it taxes the critical thinking and comprehension, even those of us with IQ’s in the 99 percentile. This subject matter is not my forte, therefore I dabble, and sometimes dribble due to this, all from necessity. A few things that are not explained in the guides or found in the forums (at least I haven’t found relevance after looking for days). The article and related articles: How to create a Windows Vista / 7 / 8 installation disc (bootable) using ImgBurn, are the only things I have to go on. They don’t cover my needs or questions sufficiently. When creating a bootable disk the Platform ID is not explained. I understand what 80x86 means, and Power PC is, well, they might still be out there, and UEFI is the new-new ride. My question comes from trying to create a bootable OS DVD that contains multiple operating systems in both X86 and X64 versions. How do you make something like that – or does it matter from a BIOS or UEFI standpoint? I guess here, since there are no multiple options – you use the base machine “type”. Is this true? The “Patch Boot Information Table” is not explained anywhere except in the most vague of terms and only superficially. Only something about boot files larger than 1 MB. Under what condition would a boot table become larger than 1 MB? Is this to enable chain loading of the MBR into BIO’s? The “Extract Boot Image” is also not explained. I am guessing it copies the image from an existing image like the one already used on your C: drive, or one you were able to copy from another system. A little more detail would be nice. Is the boot image different between 32 and 64 bit machines? I would think not – not for an OS install disk, even with X86 and X64 options, but what does an oilseed engineer know? “Load Segment” is not discussed, there is only, “I get mine from the ImgBurn log”. Really vague. What is the significance of this value? Granted – you’re not here to give massive lectures on the finer points of computer science or software engineering. I’d like to be able to follow directions on using a complicated piece of software and learn along the way – not be given a complicated tool with part of the instructions, and told to fix the reactor (I think they did that with Fukushima) –Ops… Crap! You get my point… – Thank you.

Sorry for a very late reply, due to the very poor/varying quality of affordable DL Blu-ray I pretty much stopped using them. But I used Google Gemini AI to write a script in Powershell, for BD movies, basically it is like this : First a couple of notes: I don't know Powershell. This was pretty much entirely written by Gemini. I just changed the layer size a bit. The code has no error correction or anything. If the STREAM-folder is close to 50GB it won't work. It will only accept the STREAM-folder (for BD movies, script depends on all big files being in the same folder - for data discs it could be other folder than STREAM folder obviously). param( # Path to the folder containing the files [Parameter(Mandatory=$true)] [string] $FolderPath ) # Set the size limits in bytes $maxSizeLayer = 24000000000 # Function to get the total size of files function Get-TotalFileSize { param( [Parameter(Mandatory=$true)] [string[]] $FilePaths ) $fileSizes = $FilePaths | ForEach-Object { Get-Item $_ -Force | Select-Object Length } $fileSizes | Measure-Object -Sum | Select-Object -ExpandProperty Sum } # Get all files in the folder sorted alphabetically $files = Get-ChildItem -Path $FolderPath -File | Sort-Object Name # Track the total size and last added file $totalSize = 0 $lastFile # Loop through files until reaching limit foreach ($file in $files) { $fileSize = $file.Length if ($totalSize + $fileSize -lt $maxSizeLayer) { $totalSize += $fileSize $lastFile = $file } else { break } } $paddingFileSize = (25GB - $totalSize) # Calculate padding file size $paddingSize = $paddingFileSize # Check if padding is needed if ($paddingFileSize -gt 0) { # Create padding filename based on last added file $paddingFileName = ($lastFile.Name.Split('.')[-2] + "dummy") + "." + ($lastFile.Name.Split('.')[-1]) $paddingFilePath = Join-Path $FolderPath -ChildPath $paddingFileName # Write message about padding file Write-Host "Creating padding file: $paddingFileName with size: $($paddingSize / 1KB) KB" fsutil file createNew $paddingFilePath $paddingSize } else { Write-Host "No padding file needed. Total size reached the limit." } To use this script, create a text document, for example padder.ps1 , I put my on my Desktop. Then I open Powershell, , and run Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process (My Windows is restricted from running scripts in Powershell) I then drag my script to the Powershell windows, run it, and drag the STREAM-folder, and will get something looking like this: PS C:\Users\MattKarma> Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process PS C:\Users\MattKarma> C:\Users\MattKarma\Desktop\Padder.ps1 cmdlet Padder.ps1 at command pipeline position 1 Supply values for the following parameters: FolderPath: C:\multiAVCHD\AVCHD\BDMV\STREAM Creating padding file: 00006dummy.m2ts with size: 3742564 KB File C:\multiAVCHD\AVCHD\BDMV\STREAM\00006dummy.m2ts is created PS C:\Users\MattKarma> Again, this is a very crude solution, and it also assumes the burning program burns files alphabetically and not based on when files were created or something else. It also assumes that the size of .mt2ts files are reasonable, I use something like 4000 MB m2ts media split in MultiAVCHD. If you have 3 15GB .m2ts files it won't work.

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

The Device Buffer is self explanatory to me, but I am curious as to what the Image Buffer precisely is. Thanks!

The game is Policenauts, and the image for each disc comes with an ISO, a WAV file, and a CUE file. The CUE file specifies the correct file names, and it seems like the ISO burns fine. However, when it gets to the wav file, I get a directshow error: "DirectShow Error! - IMediaEvent::WaitForCompletion File Name: <file path>.wav" Index Progress: 4,233,600 bytes Index size: 4,461,744 bytes Reason: An operation was aborted because of an error. (0x00000003) Would you like to continue anyway and fill the remainder of this Index with digital silence?" I am on Windows 11, and other Saturn games have burned just fine, though usually they only contain one or more BIN files and a CUE pointing to them. This is the first time I've burned a game in ISO format, and the first time it's included a separate WAV file. The game launches just fine. The WAV file is short, plays fine on my computer, and doesn't seem that important (I speak some Japanese, and it seems to be a message that plays when you put the disc in a CD player, telling you to that it's for use in a Sega Saturn instead), but I'd still like the games to burn properly. It's a very minor issue, but still. I searched the forum for similar problems, and someone had the issue of having converted MP3 files to WAV, and getting a similar error. That person's solution was to burn the MP3 files without converting them to WAV, as either way, imgburn has to convert the audio file to CD-AUDIO during the burn. However, the image I have for Policenauts only comes with a WAV file for each disc, so I'm not doing any conversion before I start the burn. I know directshow filters for WAV files are supposed to be built into Windows, but perhaps they've been removed on Windows 11? A Microsoft help page for app development states that directshow has been "superseded by MediaPlayer, IMFMediaEngine, and Audio/Video Capture in Media Foundation," though I'm not 100% sure what that means. What can I do? EDIT: Okay! I stuck the game in a CD player, and the wav file is there, telling me in Japanese that the game is supposed to go into a Sega Saturn. So it's being written to the disc. I guess this isn't a problem at all. So why am I getting this error, and what does it mean?? I'm confused, but I guess this turned out to be a nonissue after all.

I've never encountered this Error Reason before: I 20:58:28 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 5863199) W 21:00:40 Failed to Read Sectors 1467200 - 1467231 - Reason: Timeout on Logical Unit W 21:00:49 Failed to Read Sector 1467200 - Reason: Logical Unit has not Self-Configured Yet E 21:12:02 Failed to Verify Sectors! What exactly does Logical Unit has not Self-Configured Yet mean? I simply burned the image to a 2nd BD-R and it worked that time. Thanks!

The Vinpower drive is actually an LG based on MT1959 chipset . I also have an LG with the same chipset, BH series , but it does not support Disc Quality or FE/TE in OptiDriveControl . I have a GTA V for PS4 that fails to install on the console but in ImgBurn i managed to create an ISO . I can't test any further since i don't have a compatible drive, looking for one.

Installed madflac, followed instructions here. Everything works fine, until I get to the [ point shown below, just hangs at 52% Any ideas what I can do about this? Thanks

Hello, I've gotten myself into a situation with a French DVD title that has only French subtitles. I thought if I could write the disc to file it would then separate out each component of the disc image into separate files before burning this image/ISO on a new disc thereby allowing me to translate the subtitles to English and include this on the new image. However it seems it's an image on the disc and it's an image as a file as well inseparable inside that container file. So now that I've stated that. A stupid question then? There is no way that IMGBurn can handle manipulating the portion of this disc image that comprises the subtitles?

the basis of this thread is creating an ISO file from a bootable USB pen drive. I started from the Kaspersky Rescu Disk base because I had the test ISO and it is available for anyone who wants to answer me and find a solution. It is obvious that if I have an ISO that without it I have to create a bootable USB pen drive and then create the ISO again. I actually have a bootable USB stick with the OnTrack EasyRecovery program bootable. The program itself creates this bootable USB pen drive. There is no ISO that I could handle differently. So here's the dilemma. So like in the first post, I have a bootable USB pen drive and I want to get a bootable ISO file. There are also other programs that allow you to create bootable pen drives but do not create ISOs. Now if it exists (and I think so, perhaps we need to look in the boot image for the solution) let's try to find the solution. Thank you all

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.

I'm trying to burn a PS1 homebrew program, 240p Test Suite, to a disc in order to play it on my console. I've been burning from a BIN and CUE directly from the project's GitHub. However, during verification after burning, ImgBurn detects numerous errors, with the note: "The drive probably corrected the Sync/Header Area because it's wrong in the image file". That the image would be wrong seems unlikely to me as, like I said, it's directly from the source. I don't get this when burning backups of my own games, and those play fine in my modded console. Numerous attempts to burn yield identical results, indicating to me that this isn't a question of imprecise hardware, but of some software or firmware issue. Based on the note I mentioned previously, I suspect that it's some kind of automatic error correction on the part of my drive, and that data of this program is structured atypically due to it being a non-official release. If so, is there any way to circumvent the error correction? If not, does anyone know how what's going on and what I can do about it? Much appreciated. OS: Windows 11 Pro 10.0.2261 Program ver.: ImgBurn 2.5.8.0 Drive: PIONEER BD-RW BDR-XS07U 1.03 (USB) Media: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) -- Some Memorex 52x CD-Rs I got from Target half a decade ago lol P.S. Hope I don't get clowned for using an external USB drive . . .

To be clear, I've tried to burn many games, and many mirrors of Illbleed, but none have worked, and I assume it's because of this error. I've done everything else I'm supposed to do, watched and read every guide, and it still keeps giving me this error at the very end. I'm at the end of my rope, and just want to play this game. Any help would be greatly appreciated, and if you could dumb it down as much as possible, that would be great too. I'm not very tech literate. Here's the log: I 18:10:45 ImgBurn Version 2.5.8.0 started! I 18:10:45 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 18:10:45 Total Physical Memory: 8,272,216 KiB - Available: 2,368,776 KiB I 18:10:45 Initialising SPTI... I 18:10:45 Searching for SCSI / ATAPI devices... I 18:10:45 -> Drive 1 - Info: HL-DT-ST DVD+-RW GU60N A103-86 (D:) (RAID) I 18:10:45 Found 1 DVD±RW/RAM! I 18:11:08 Operation Started! I 18:11:08 Source File: C:\Users\hazam\Desktop\Illbleed (USA)[RDC].cdi I 18:11:08 Source File Sectors: 343,523 (MODE2/FORM1/2336) I 18:11:08 Source File Size: 802,469,728 bytes I 18:11:08 Source File Volume Identifier: Illbleed-RDC I 18:11:08 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 18:11:08 Source File File System(s): ISO9660 I 18:11:08 Destination Device: [0:1:0] HL-DT-ST DVD+-RW GU60N A103 (D:) (RAID) I 18:11:08 Destination Media Type: CD-RW (Disc ID: 97m25s30f, Infodisc Technology Co.) I 18:11:08 Destination Media Supported Write Speeds: 4x I 18:11:08 Destination Media Sectors: 359,847 I 18:11:08 Write Mode: CD I 18:11:08 Write Type: SAO I 18:11:08 Write Speed: 1x I 18:11:08 Lock Volume: Yes I 18:11:08 Test Mode: No I 18:11:08 OPC: No I 18:11:08 BURN-Proof: Enabled W 18:11:08 Write Speed Miscompare! - Wanted: 176 KB/s (1x), Got: 706 KB/s (4x) W 18:11:08 The drive only supports writing these discs at 4x. I 18:11:12 Filling Buffer... (72 MiB) I 18:11:12 Writing LeadIn... I 18:12:06 Writing Session 1 of 2... (1 Track, LBA: 0 - 33599) I 18:12:06 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 33599) I 18:13:56 Synchronising Cache... I 18:14:37 Filling Buffer... (72 MiB) I 18:14:37 Writing LeadIn... I 18:14:53 Writing Session 2 of 2... (1 Track, LBA: 45000 - 343522) I 18:14:53 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 45000 - 343522) I 18:31:25 Synchronising Cache... I 18:31:51 Exporting Graph Data... I 18:31:51 Graph Data File: C:\Users\hazam\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GU60N_A103_MONDAY-NOVEMBER-7-2022_6-11_PM_97m25s30f_1x.ibg I 18:31:51 Export Successfully Completed! I 18:31:51 Operation Successfully Completed! - Duration: 00:20:42 I 18:31:51 Average Write Rate: 676 KiB/s (3.4x) - Maximum Write Rate: 710 KiB/s (3.6x) I 18:31:51 Cycling Tray before Verify... W 18:32:09 Waiting for device to become ready... I 18:32:20 Device Ready! I 18:32:21 Operation Started! I 18:32:21 Source Device: [0:1:0] HL-DT-ST DVD+-RW GU60N A103 (D:) (RAID) I 18:32:21 Source Media Type: CD-RW (Disc ID: 97m25s30f, Infodisc Technology Co.) I 18:32:21 Source Media Supported Read Speeds: 4x, 5x, 10x, 16x, 20x, 24x I 18:32:21 Source Media Supported Write Speeds: 4x I 18:32:21 Source Media Sectors: 343,523 I 18:32:21 Source Media Size: 807,966,096 bytes I 18:32:21 Image File: C:\Users\hazam\Desktop\Illbleed (USA)[RDC].cdi I 18:32:21 Image File Sectors: 343,523 (MODE2/FORM1/2336) I 18:32:21 Image File Size: 802,469,728 bytes I 18:32:21 Image File Volume Identifier: Illbleed-RDC I 18:32:21 Image 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 18:32:21 Image File File System(s): ISO9660 I 18:32:21 Read Speed (Data/Audio): MAX / MAX I 18:32:23 Read Speed - Effective: 24x I 18:32:23 Verifying Session 1 of 2... (1 Track, LBA: 0 - 33599) I 18:32:23 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 33599) I 18:33:06 Verifying Session 2 of 2... (1 Track, LBA: 45000 - 343522) I 18:33:06 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 45000 - 343522) W 18:37:06 Miscompare at LBA: 342344, Offset: 2292 W 18:37:06 Device: 0x21 W 18:37:06 Image File: 0x09 W 18:37:06 Total Errors in Sector: 16 W 18:37:06 Note: The drive probably corrected the L-EC Area because it's wrong in the image file. I 18:37:06 Verifying Sectors... I 18:37:22 Exporting Graph Data... I 18:37:22 Graph Data File: C:\Users\hazam\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GU60N_A103_MONDAY-NOVEMBER-7-2022_6-11_PM_97m25s30f_1x.ibg I 18:37:22 Export Successfully Completed! I 18:37:22 Operation Successfully Completed! - Duration: 00:04:52 I 18:37:22 Average Verify Rate: 2,702 KiB/s (13.8x) - Maximum Verify Rate: 4,195 KiB/s (21.3x) Thanks again in advance if you can help me! I'll be incredibly grateful.

I am a bit late... but I see that game you want (i.e. "Spirit of Speed 1937") on Archive site and you can try using Padus DiscJuggler software if you want as while I nearly exclusively use ImgBurn in general, Padus DiscJuggler is the official software for ".CDI" files which CDI files are what you need for using on real Dreamcast hardware. I was looking into this stuff a moment ago and found the last released version of Padus DiscJuggler (i.e. https://dreamcast.wiki/DiscJuggler ) on my Linux setup and it seems okay. just in some brief testing I burned a game to CD-RW just to see what my Dreamcast would do and it does not even see the CD-RW disc. I recently brought out my Dreamcast as it was collecting dust for many years as I tried one of my burned CD-R's (Mortal Kombat Gold), which I burned June 2004 on some generic 'CMC Magnetics Corp' media (as there is no brand name on the disc), and... the game still loads up but I noticed in the game it does not take long before the sound goes out in regards to punches/kicks etc but the background music is still okay. so either my copy degraded, or... it 'may' have been like that back when I first burned it. I 'may' try reburning that same game from a CDI image I found online just to see if it's any better. I tried comparing the original one I burned from June 2004 to the burned CDI image to CD-RW and ImgBurn shows for the June 2004 burned CD-R... "Size: 661,381,120 bytes". the one I just tested is... "Size: 736,954,368 bytes". even looking at basic 'data' section of the disc (not the Audio part) shows "378,216,295 bytes" on NEW disc. the June 2004 one shows... "352,110,505 bytes". I heard there was a couple of different versions of this game, so 'maybe' that's why. the file I downloaded says 'Re-release'. but I can't really say for sure. but I said screw it and decided to burn it to a Verbatim CD-R (one of the usual cheaper 'CMC Magnetics Corp' ones) at 8x (seems DiscJuggler did not take my 8x write speed setting as it appears it's burning it pretty much full speed as it only took 3min10sec to finish writing it and it's basically a full disc) on my 'Sony Optiarc 7240s' and see if that issue I had with the June 2004 copy went away and... it seems to work with no more audio missing issue with kicks/punches etc as it works as expected. so I am leaning towards that previous copy was flawed, not in burning quality but the data itself(?). TIP: from what some claim, burning Dreamcast games slow is probably a good idea. most modern-ish burners don't seem to burn CD-R's any slower than 8x though. but I most likely burned that CD-R from June 2004 on a burner I still have (Liteon 24102b) as I never had a DVD burner until I think 2005-2006. p.s. my console has to be one of the earlier models as it's got a Sep 1999 mfg date on it as the console was released Sep 9th 1999 here in USA (I noticed the console does not seem to keep the data you setup for long as powering it off for not long and back on seems to ask to set date again etc). I most likely bought mine in 1999 or 2000 at the latest.

Thanks Lightning for such a great tool and for your great support! Sorry to dig up such an old post, but I was seeking answers to a couple of the same questions, so glad that after some careful reading (including the URL you linked), things slowly became clearer for me. Thank you! Just a suggestion, which you are free to ignore, would be to make the following minor text changes under the Bootable Disc tab : Patch Boot Information Table -> Patch Boot Information Table (isolinux) Extract Boot Image -> Extract a Boot Image This would make it a little more obvious what these two items are, and whether they're relevant. So in my case, it would then be clear that I didn't need the Patch Boot Information Table option, and that the Extract Boot Image selection wasn't asking for some kind of image file, but was a little tool to create such a file (presumably to use in the Boot Image selection above). Joe.