All Activity

I’d always use Sao/dao. I do recall a few discs needing raw-dao 96 due to early copy protection efforts, and of course, ImgBurn doesn’t support that.

Blimey, that’s a definite ‘check the code and see what’s going on’ type of question. Leave it with me and I’ll get back to as soon as I can.

Hi everyone, I was trying to burn a Sony 128GB BDXL QL disc as UDF 2.01 yesterday. However, ImgBurn refused to burn it, saying "Too many UDF Extended File Entry AD's". The file I was trying to burn is a single zip file just over 128GBytes and a txt file <1KB. I searched around in this forum, but only found this error occurring with 200GB+ images. I used to burn single 100GB files onto BDXL TL discs and this error never occurred. I tried UDF 2.60 but the error persists. Is there a hard limit on the image size? If there is, what is it exactly? Any help would be appreciated. Here's the log (this was from yesterday when I tried to overburn, today I tried to reduce the image size to fit into the disc but to no avail): I 23:02:41 Operation Started! I 23:02:41 Building Image Tree... I 23:02:41 Calculating Totals... I 23:02:41 Preparing Image... I 23:02:41 Contents: 2 Files, 0 Folders I 23:02:41 Content Type: Data I 23:02:41 Data Type: MODE1/2048 I 23:02:41 File System(s): UDF (2.01) I 23:02:41 Volume Label: BDXL TEST (QL) I 23:02:41 Size: 128,001,294,526 bytes I 23:02:41 Sectors: 62,500,634 I 23:02:41 Image Size: 128,001,900,544 bytes I 23:02:41 Image Sectors: 62,500,928 I 23:02:42 Operation Successfully Completed! - Duration: 00:00:01 W 23:02:43 User accepted disc space warning and is attempting to overburn! I 23:02:43 Operation Started! I 23:02:43 Source File: -==/\/[BUILD IMAGE]\/\==- I 23:02:43 Source File Sectors: 62,500,928 (MODE1/2048) I 23:02:43 Source File Size: 128,001,900,544 bytes I 23:02:43 Source File Volume Identifier: BDXL TEST (QL) I 23:02:43 Source File Volume Set Identifier: 5972B85403B9B021 I 23:02:43 Source File Application Identifier: ImgBurn v2.5.8.0 I 23:02:43 Source File Implementation Identifier: ImgBurn I 23:02:43 Source File File System(s): UDF (2.01) I 23:02:43 Destination Device: [0:0:0] PIONEER BDX-PR1AME 1.00 (F:) (USB) I 23:02:43 Destination Media Type: BD-R (Disc ID: SONY-NQ1-001) I 23:02:43 Destination Media Supported Write Speeds: 2x, 4x, 6x I 23:02:43 Destination Media Sectors: 62,500,864 I 23:02:43 Write Mode: BD I 23:02:43 Write Type: DAO I 23:02:43 Write Speed: 2x I 23:02:43 Hardware Defect Management Active: No I 23:02:43 BD-R Verify Not Required: Yes I 23:02:43 Link Size: Auto I 23:02:43 Lock Volume: Yes I 23:02:43 Test Mode: No I 23:02:43 OPC: No I 23:02:43 BURN-Proof: Enabled I 23:02:43 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x) I 23:02:43 Advanced Settings - Optimal Writing Speed: No I 23:02:44 Filling Buffer... (80 MiB) I 23:02:52 Synchronising Cache... W 23:02:54 User opted to skip the 'Close Track/Session/Disc' functions. E 23:02:54 Failed to Write Image! E 23:02:54 Operation Failed! - Duration: 00:00:11 I 23:02:54 Average Write Rate: N/A - Maximum Write Rate: N/A

So after some reading with my PSX CD-R burning 'adventure' I've come across information that PSX discs are best burnt at TAO or RAW DAO mode (I've been burning at DAO/SAO). If anyone has experience with this I'd like some advice on if TAO mode with Imgburn is perfectly fine or if I have to find other software just to burn with RAW DAO? Thanks

I don't believe there's been much concrete data on the longevity of DVD-RW for archival purposes, but I believe I do have a relevant data point. I came across a RITEK 4x DVD-RW where I had written files to it in January of 2005. Nearly the entire disc's contents were full. I am in the process of copying over that data now. There's over 27,000 individual files, so the read process is slow. It's a bit over 50% done with nearly half an hour estimated to go. So, if this disc's contents can be fully read, this is a concrete, real world experience data point of the archival longevity of DVD-RW. One can expect data written to a RITEK DVD-RW to still be readable about 20 years later.

Well, I have determined it is NOT the ASUS drive that is at fault. It is the BD-R's I have. I wrote one of these Verbatim BD-R is an LG WH16NS60. It burned and passed Verify but FAILED Verify today less than 2 months later. Since it fails on BOTH the ASUS and the LG, the issue is with the BD-R's. So, what this means is I either got a bad batch of Verbatim BD-R's OR Verbatim made a running change to their BD-R's and firmware needs updating to write properly to it. Which is the kiss of death for Verbatim BD-R as NO ONE is updating their firmware anymore. There is precedence for Verbatim to make running changes to the manufacturing processes of its discs that borks them. One such running change occurred on their DataLife Plus DVD-R and the NS60 would not write to them until a firmware update fixed it.

While I can't answer the first part directly, I can comment on the MID. It seems for CD's, MID's don't really "apply." So, some CD-R have MID's that list the maximum space capacity, in this case the running time of the CD itself. As for the first part, be aware that even if you do set a user defined maximum Write speed, it may not always be honored. The drive itself basically makes the final decision as to what write speed it will write at.

Does anyone who has experience with CMC Pro by TY Tech discs know what is a good max speed to set for it in AWS? The MID says 97m24s01f (Taiyo Yuden Co.) for some reason

You need the right sort of drive and the right discs for it to work. I’m afraid your log snippet isn’t big enough to tell us either bits of info.

I've never gotten an overburn to work correctly, so it may well be that the ISO is simply too large for the target media.

I want to burn an copy of gta 5 for my xbox 360, i have an dvd dl r 8,5gb and i did got an warning since the file is 8,6gb and the dvd is 8,5gb max capacity. It did warn me that it may not work but i can try and there im waiting like maybe 30 minutes then an error popped up " W 17:09:28 Failed to Write Sectors 2048800 - 2048831 - Reason: Write Error " . I did go try again like 20 times and i canceled it. Then an window popped up asking me something i forgot what i just hit continue and now in the logs it just says. E 17:10:35 Failed to Write Sectors 2048800 - 2048831 - Reason: Write Error E 17:10:35 Next Writable Address: 2048560 I 17:10:35 Synchronising Cache... I 17:10:50 Closing Track... I 17:11:23 Finalising Disc...

Well, I've never had an XBox, so I can't say for certain this is how it behaves, but I am relatively sure. If you're talking about an older XBox specifically, this would apply. Unless your XBox natively supports playing MP4 video container files directly, you can't just put an MP4 on any disc and expect the XBox to play it. You will need to convert the MP4 to VIDEO_TS first to make it a DVD Video disc. I've used ConvertXToDVD to do this for like 15 years now, but it is paid software. As for any freeware options, I couldn't say.

I know this comes across as a total n00b question, but I’ve tried on my own a couple times and searched the forums, and I’m just stumped. I have a video project that I’m trying to burn onto the Verbatim DVD+R DL (I’m not completely clueless), but each time I burn it, my XBox One doesn’t recognize the disc. Currently I just have the video as an .mp4, and also converted to an .iso using ImgBurn. I’ve burnt each version on different discs, and the same problem comes up. I’ve tried messing with the ISO6990/UDF settings, which also hasn’t accomplished anything. What can I do to make this work?

Hello there! I`m new here. Glad to become part of community!

Try changing the I/O Interface and see if you get better results with a different one. Tools --> Settings --> I/O --> Page 1 --> Interface and check a different box. I would recommend closing and restarting ImgBurn after each change of the Interface to be safe.

I know I've seen a few other posts about this one, but it looks like it's happening to me as well. For the record, this has never happened with any other brand of burner - my Lite-On, Asus, and LG have never had this issue. Whatever it is, it *ONLY* happens with my Pioneer drive. It will forever hang at the "cycling tray before verify" step. The drive does eject and close and then just hangs there like the drive has lost communication with the computer. It's odd. Any ideas or anything else I can try? I can't update the firmware to 1.05 because I'll lose the ability to rip UHDs via MakeMKV so that's not an option so I'm hoping someone has any other suggestions. It's worth mentioning this only happens maybe 10-25% of the time, so definitely not always but when it does I'm unable to shut down the program or do anything (I can force it with task manager but the drive remains locked - even if I manually unlock with a paperclip it'll stay unavailable in Windows) until I do a full reboot. I 10:13:05 ImgBurn Version 2.5.8.0 started! I 10:13:05 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 10:13:05 Total Physical Memory: 32,820,148 KiB - Available: 16,629,472 KiB I 10:13:05 Initialising SPTI... I 10:13:05 Searching for SCSI / ATAPI devices... I 10:13:05 -> Drive 1 - Info: PIONEER BD-RW BDR-S13U 1.03-ID43 (O:) (SATA) I 10:13:05 -> Drive 2 - Info: TSSTcorp DVD+-RW SH-216BB D100 (P:) (SATA) I 10:13:05 Found 1 DVD±RW/RAM and 1 BD-RE XL! I 10:18:10 Operation Started! I 10:18:10 Source File Sectors: 23,935,168 (MODE1/2048) I 10:18:10 Source File Size: 49,019,224,064 bytes I 10:18:10 Source File Application Identifier: ImgBurn v2.5.8.0 I 10:18:10 Source File Implementation Identifier: ImgBurn I 10:18:10 Source File File System(s): UDF (2.50) I 10:18:10 Destination Device: [0:0:0] PIONEER BD-RW BDR-S13U 1.03 (O:) (SATA) I 10:18:11 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 10:18:11 Destination Media Supported Write Speeds: 2x I 10:18:11 Destination Media Sectors: 24,438,784 I 10:18:11 Write Mode: BD I 10:18:11 Write Type: DAO I 10:18:11 Write Speed: MAX I 10:18:11 Hardware Defect Management Active: No I 10:18:11 BD-RE FastWrite: No I 10:18:11 Link Size: Auto I 10:18:11 Lock Volume: Yes I 10:18:11 Test Mode: No I 10:18:11 OPC: No I 10:18:11 BURN-Proof: Enabled I 10:18:11 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x) I 10:18:11 Advanced Settings - Optimal Writing Speed: No I 10:18:12 Filling Buffer... (80 MiB) I 10:18:12 Writing LeadIn... I 10:18:25 Writing Session 1 of 1... (1 Track, LBA: 0 - 23935167) I 10:18:25 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 23935167) I 10:18:25 Writing Layer 0... (LBA: 0 - 12219391) I 11:05:16 Writing Layer 1... (LBA: 12219392 - 23935167) I 11:50:03 Synchronising Cache... I 11:50:04 Exporting Graph Data... I 11:50:04 Export Successfully Completed! I 11:50:04 Operation Successfully Completed! - Duration: 01:31:53 I 11:50:04 Average Write Rate: 8,708 KiB/s (2.0x) - Maximum Write Rate: 8,832 KiB/s (2.0x) I 11:50:04 Cycling Tray before Verify... I 16:25:35 Abort Request Acknowledged

After you create the new 'wine prefix' (which in your case is the "ImgBurn" folder before 'drive_c') you then install ImgBurn (i.e. "SetupImgBurn_2.5.8.0.exe") into that prefix like usual. my actual ImgBurn program is installed to, for example... "~/.PlayOnLinux/wineprefix/ImgBurn_32bit601/drive_c/Program Files/ImgBurn/ImgBurn.exe" (I am using 32-bit wine prefix so that's why it's 'Program Files' instead of 'Program Files (x86)' etc like the 64-bit stuff would be. either 32bit or 64bit should be okay though). basically from the "drive_c" (which is equivalent to "C:\" on real windows) it's exactly like the Windows folder structure at that point. so basically my 'ImgBurn_32bit601' is the same as your 'ImgBurn' folder in your screenshot. but once you setup the wine prefix you still need to install ImgBurn INTO that prefix before you can even attempt to run the program as all the 'wine prefix' does is pretty much like a windows installation is installed. but you still need to install your Windows program (i.e. imgburn) into that though before you can use it. trust me, this is easier than it may appear to you p.s. I also have a desktop shortcut since it makes starting it nice and easy that way.

For me, the Log window is its "default size" at some distance separated from the main ImgBurn window. In other words, it's not snapped/docked to the main ImgBurn window.

All the message boxes within the app behave the same way (they flow through one function). Generally speaking, the 'owner' window parameter of the MessageBox Windows API call is set to the one that's active when they're displayed. For the 'operation successfully completed' ones, that would be the main window. I'm not sure why it would be going behind the log window as I'd expect it to be centred relative to its owner. Where is your log window in comparison to the main window? Is it maximised? I don't really recall it being a problem, but we are going back 10+ years!

That is a bit of an annoyance. There are 2 temporary workaround that might work. One is to dock the Log window with the ImgBurn main interface window. I haven't tried that yet but it might work. What DOES work is what I've done. I moved the OK completion window well to the right side of the Log window so it can't go behind the Log window. It's a bit of an inconvenience and isn't pretty but it works.

How about making sure the completion dialog box is in front so it doesn't go behind then log window when completed?

If you want best quality when burning a standard audio CD always do it from a proper lossless source (i.e. FLAC/WAV etc). because once you are on a MP3 you can't improve quality at that point as it will never get any higher than the MP3 itself, so technically you are downgrading the audio quality by going from MP3 back to a Audio CD. granted, if your MP3 is of high enough bit rate chances are most people won't notice the difference though vs a lossless source. but generally... if your WAV files are standard 44.1/16 (which is what a standard Audio CD uses), ImgBurn should be able to use those with no special configuration needed. that's how I burn standard Audio CD's on my Linux setup using ImgBurn as I temporarily convert from FLAC to WAV as I can't install madFLAC on Linux etc. so that's how I work around it (I use Foobar2000 to convert FLAC files back to WAV when I burn a occasional Audio CD). so I am assuming if it works with standard WAV files on Linux, it should on Windows to with no fancy configuration needed. p.s. personally, unless I have no choice, I never burn standard Audio CD's from a MP3 source. but pretty much all of the music I care about I always got a high quality lossless source (basically FLAC) as this way no matter what I do, like burn a Audio CD or convert to whatever lossy format (MP3/AAC/Opus etc) I want, it will always be optimal this way.

Unfortunately, the bottom line with the hardware is it will do whatever it wants to do in the end. You can set your own user defined write speeds, but the drive may ultimately ignore them. The Windows 10 thing is most likely the cosmetic issue. Due to the age of the last ImgBurn release, Windows 10 is reported as Windows 8 since Windows 10 didn't exist at the time of the last ImgBurn gold release. This has been addressed in subsequent beta releases and will make into the next gold release, which will identify Windows 10 as such in the Log. And, no, don't ask when the next gold release is.

Hi guys! Need help... I want to burn PS1 games, I know about the .cue files, I know how to setup the software but I can't write at x4 speed or slower because it says something like "unsupported drive, minimum speed must be x10" my log file got updated and can't copy the exact message but this is what I can gather. Some guides online guides use various speeds but as far as I know it needs to be as slow as possible. I 02:04:35 ImgBurn Version 2.5.8.0 started! I 02:04:35 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 02:04:35 Total Physical Memory: 33,489,436 KiB - Available: 26,629,932 KiB I 02:04:35 Initialising SPTI... I 02:04:35 Searching for SCSI / ATAPI devices... I 02:04:35 -> Drive 1 - Info: DVD RW JQ3M (E:) (USB 2.0) I 02:04:35 Found 1 DVD±RW! I'm using a Verbatim reader, could be the weaker brand, i dunno but I can however burn PS2 games successfully, I've tried with unchecking verification as well only once and still nothing. As I read the log it say's that I use windows 8 which is false, I use 10... if that's not enough I can always waste another CD-RW to make a new log file. As for where I get my games, I've tried Coolroms, cdromance, vimm.net and another archive site, I've wasted A LOT of discs. Thanks for reading and trying.

I suggest using Ventoy (i.e. ventoy.net or https://github.com/ventoy/Ventoy/releases ; currently you would download "ventoy-1.0.99-linux.tar.gz" for use on Linux) as with that you can create a multi-boot USB stick that still functions like a regular USB stick but also can boot ISO's directly. because once Ventoy is setup on it, you just copy your Linux/Windows ISO's to the root of the USB stick (basically just copy the ISO file to the USB stick from file manager). then to boot to it, you boot to a USB stick like usual, select the ISO from the Ventoy menu and then proceed to use/install Windows or Linux like you normally would. p.s. for those who don't like Windows 11, you have the option to stick with Windows 10 past the Oct 2025 end-of-support date 'if' you use the 'IoT Enterprise LTSC 2021' version of Windows 10 (it's basically '21H2' where as standard Win10 is '22H2' but it's pretty much the same) which is supported until Jan 2032 etc. I am using that version of Windows 10 in a virtual machine on my main Linux PC and as a bonus it does not have the junk in it like the regular version does like no Microsoft Store and the start menu is nice and clean. also, it's possible to use a updated version of Windows 7, which will have security updates to October 2024 ('Simplix' which is about a 800MB file), but I heard the ones that came in October 2024 are the very last ones from Microsoft (but for the general average person Jan 2020 was the end-of-support date for Windows 7 but it was still possible to get updates afterwards through other means), so it's probably not worth using Windows 7 at this point short of very limited use situations. but Firefox ESR is still officially supported on Windows 7 until March 2025 I think as that was extended not long ago. but I did use that (Simplix) to create a updated ISO to August 2024 not long ago as the official Win7 SP1 64-bit ISO was 3.1GB but after updating that with the newest updates along with bundling DirectX/dotNET/VisualC++ stuff with it, the ISO was now 4.5GB which is what I used to install Win7 on a old computer I have for potential use of old games/software that does not work on newer Windows etc and that computer cannot run any Windows newer than Windows 7 and on that old computer gaming is not a option because the driver Linux supports on it is too old for modern standards so for gaming, Win7 is the only option on that backup computer of mine (my main PC I can play my games on Linux through Lutris and no obvious issues). but on that same PC I have Linux Mint 22.0-Xfce installed on it for general usage and ImgBurn works fine on that (although to get PlayOnLinux to start up on Mint 22 I had to install a additional thing (i.e. "apt install python3-pyasyncore") for it to start up. but since you are using a different distro it's possible you might not need to do that for PlayOnLinux to start since in your screenshot it's working as on Mint 22 the main PlayOnLinux interface simply refuses to start up until I issued that from terminal. I upgraded from Mint 21 to 22 and even from a clean install a while ago it still reacts the same way). I use the "SetupImgBurn_2.5.8.0.exe" directly already on hard drive. I typically do my stuff from that PlayOnLinux's 'Configure' icon as it allows a bit more manual control over things vs trying it from the 'Install' option on the main PlayOnLinux screen. but I would imagine the 'Install' will be okay to but I never use it personally. also, the system installed Wine should work if you prefer to use that I suspect. I just prefer PlayOnLinux since it keeps a separate Wine prefix solely for ImgBurn use (which is stored in a different location..."~/.PlayOnLinux/wineprefix/" my ImgBurn wine prefix (v6.0.1 (32-bit)) here is 4xxMB in size). but if you use the system installed Wine (which stores it's default prefix at "~/.wine") you will have to tweak it so the "ImgBurn.exe" is specifically designed to run in Windows XP mode as that's critical as Wine has defaulted to Windows 7 for a while (like on Wine v8.x and a fair amount before this) and in recent memory (I think on the current Wine v9.x series) now defaults to Windows 10 and ImgBurn will hang/not-work if you don't have Wine set to WindowsXP mode for the ImgBurn.exe specifically. this way you could leave the default wine prefix to it's usual Windows 10 mode but for ImgBurn specifically it would use Windows XP. but if I recall correctly each time you ran a program that uses default it would probably be always re-writing data to that when switching etc which is why I suggest just creating one solely for use with ImgBurn as then you don't have to worry about that stuff since it will stay completely separate and less likely to act up if you have multiple programs running from default "~/.wine" location. optionally... if you want, you can install the latest Wine from official Wine website (i.e. https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu ; follow the instructions for your specific Ubuntu version!) as I got mine installed but I don't even currently have a prefix created with it (since it wastes 1-2GB of storage space and I prefer to have separate stuff for most of my programs etc) as I am currently using the 'development' version which the newest is currently v9.20 as this gets updated roughly once a month where as the current 'stable' version would be v9.0. generally for the average person I would probably stick with the 'stable' which seems about one major release every year, usually around January. this will generally be newer than if you stick to the stuff in the Ubuntu repositories. so bottom line... I would suggest sticking with PlayOnLinux for ImgBurn since it stays separate from any potential system installed Wine stuff. p.s. if i recall correctly... say you got the more standard system installed Wine installed, once PlayOnLinux is installed, if you try to remove the system installed Wine etc, I think this will screw up PlayOnLinux. I don't remember the precise detail off the top of my head but I am pretty sure it's something along these lines. but if this happens it's still fixable as that's partially why I have not bothered to mess with my system installed Wine much even though I pretty much don't use it as PlayOnLinux uses it's own stuff and so does Lutris etc.