LIGHTNING UK!
-
Posts
30,458 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by LIGHTNING UK!
-
-
You're probably talking about the disc id (MID) and that you should avoid those made by CMC.
Buy some proper Verbatim discs (not the value line ones) - look for the term 'Azo' on them... I think they're the good ones.
I have a million discs left over from back when I was developing ImgBurn full time, and as such, I haven't purchased any for a long time now - so please forgive me if the product branding has changed.
Back then, anything with a disc ID starting with the letters MCC, MKM, TYG or YUDEN were considered 'decent'.
-
The .MDS is not a simple text document
The .CUE / .DVD files are simple text documents.
-
You could write each section of the ISO to a disc if you treat it as a file and not a disc image - i.e. you use Build mode. You can than take both of those discs elsewhere, copy the file off each disc into a folder on your computer and then use the MDS to combine both parts and burn to a double layer disc using Write mode.
-
eltorito.img is the legacy boot image. You need to leave the Platform ID on 80x86 to use that one.
efi.img in the root folder is the UEFI one.
-
For basic burning of an ISO file (you can download the Windows 10 ISO files quite easily), the OS can do that directly.
A quick google found this page - https://osxdaily.com/2015/11/22/burn-disc-images-os-x-finder/
-
That *warning* is not the issue here.
The problems you're having are probably caused by the media you're using.
Please read this....
-
It matches the file on Mirror 7 - the 'direct' one.
-
Try some different discs, the drive doesn't like the ones you're using - or it's totally broken.
-
Does it remember the position of the main window?
It could revert to default if the position is considered invalid (i.e. totally off screen).
The default is the main window top / centre and the Log window bottom / centre.
-
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 2.5.8.0 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.
-
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. -
You're crazy.
-
Have you only ever burnt them at 'MAX' (8x) speed?
Maybe your drive(s) would do a better job at one of the slower speeds they claim to support those discs at.
-
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%.
-
It remembers its last position.
-
Do you really need to extract the files from the original ISO? The reason you gave in your initial post made no sense.
The images direct from Microsoft burn and boot without a problem.
-
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.
-
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 -
I think you misunderstand what discovery mode is for.
Read mode will tell you what you need to know. -
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.
-
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. -
Track 29, Index 1 comes out to under 4 seconds long (before Track 30, Index 0 starts). I can only assume that's the issue your LG drive is moaning about. Some drives don't like tracks being under 4 seconds in length.
-
if it isn't in the middle of a video stream (which of course, IFO and BUP aren't), there's nothing to make seamless.
-
I said 7zip, not winzip.
You may have to install it if you don’t already use it.
Your install of winzip is broken too. Might as well uninstall that one!
ImgBurn may install malware
in ImgBurn Support
Posted
Mirror 7 has offered an 'ad supported' version (where the installer uses a plugin that offers 3rd party software during the installation process) for years now. As in, years and years and years, dating way back before 2.5.8.0.
The plugin handles what the user is offered, I have nothing to do with that side of things.