Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. Ha! well, you learn something new every day.

    I don't even really remember seeing any mention of a log window snapping issue before. It would have been more useful to put that bug report in the bug reports forum (please excuse me if you'd also done that). I don't run mine snapped and so have never noticed it myself. It worked fine at the time of implementation, but I was probably running XP back then.

    I don't have a 4K monitor to do any testing of that issue on, but it just so happens it also occurs on mine. Maybe it's a Windows 10 thing? ImgBurn predates Windows 10, so any abnormalities it caused obviously wouldn't have been resolved.

    I'm going to fire up good old C++ Builder 2007 now and see what's going on with it.

    EDIT: Update, it's due to the shadow around the windows being classed as part of the window. It won't snap nicely to the left/right/bottom of the screen either.

  2. What bugs are you referring to?

    I’m pretty sure I’d have fixed anything that was actually a bug at the time it was reported. Of course, me fixing them is very different to me fixing them AND releasing a version that includes those fixes.

    The version that I’ve very occasionally worked on over the last 7 years will eventually be released, of course it will, I just have a very bad habit of sitting on things.

    I honestly do keep thinking I need to get back to it and get it done. In all honesty, I think I went a year without even having the development environment on my machine. I probably installed it all again and got it to the stage where I can actually compile the code again about a month ago. That’s some serious progress right there! I have a no point said to myself that I’m done with ImgBurn. If I had, this forum wouldn’t be here.

  3. There's probably nothing you can do about that. Either the drive can read the disc or it can't.

    Just make sure it's clean and not covered in finger prints etc. You probably also have the option of cleaning the drive itself in case it isn't running at 100%.

  4. I've just checked and my 1909 image (SW_DVD9_Win_Pro_10_1909_64BIT_English_Pro_Ent_EDU_N_MLF_X22-17395.ISO) is over single layer size, but not by much. The exact size is 5,292,945,408 bytes, which Windows calls 4.92GB. There would be no problem at all putting that on a DVD+R DL disc... which is what I burnt it to.


  5. The guide does work, yes.

    Have they really got to the point where it won’t fit on a double layer dvd now? I’m sure the last one I burnt did, and that would have been the Windows 10 1909 edition or whatever it was before 2004 came out

  6. If you’re planning on making images of discs, you want to tell it to load up in read mode, not discovery mode. Discovery mode will only list writers and so that’s why it won’t go to the drive you’re selecting via /src.

  7. Are you creating a legacy bootable disc or an efi bootable disc? Your bios needs to allow for whichever format you’re using.

    Legacy would normally require you to turn off secure boot and enable legacy booting in the bios.

    The guide is old and doesn’t really cover efi booting. I’ve no idea on the exact settings required for that.

    ImgBurn itself works fine on old/new hardware. Nothing has changed in the world of optical disc burning.

  8. I've never seen that before.

    Download it again?

    What OS are you using? It looks like riched20.dll is crashing.

    If all else fails, open the setup exe in 7zip and extract the files that way.


Important Information

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