Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,457
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. ImgBurn tells you all of that in the box on the right when you're in Write mode.
  2. The FAQ tells you what to do in this situation.
  3. The album artist will have been written to the disc correctly, as that's what your cue is set to do. You could check that with ImgBurn itself in Read mode -> Click on the disc information button. Your player must not like using/displaying the album artist for the individual tracks and expects them to have their own info recorded. I'd say that's a limitation of its own CDTEXT implementation.
  4. Your drive has an issue with the discs, it's nothing to do with ImgBurn. It's reporting a power calibration error, meaning it can't figure out a nice way to burn them. Are there any firmware updates available for the drive? Do not listen to the advice people make up and put on YouTube, a 72MB buffer does absolutely nothing.
  5. Cdda is a pain for this type of thing. Drives have different read / write offsets for audio and so although it’s vaguely the same actual data (well, audio samples), it will be some offset by so many bytes. If you’re patching stuff, you’d be better off working with just the data track and keeping the audio tracks separate. That isn’t something ImgBurn can help you with though.
  6. ImgBurn doesn't make a WEBM file. ISO is the correct format for burning to disc, just use Write mode. If your ISO contains a WEBM file, that's another story - remember an ISO is like a box that you put things in, in this case, someone may have put a WEBM file in it. So take a look around the internet for something that'll convert your WEBM file into the correct DVD Video disc format (a VIDEO_TS folder) and then burn that with ImgBurn in Build mode.
  7. It isn’t an attitude, it’s a fact of life. The internet is full of useful things but you must be careful how you navigate it. Not clicking dodgy links or running suspect files (no matter what they might be pretending to be) is fundamental to your security online. If you object to digital digest’s practices, you really should take it up with them. They actually host this website, so it isn’t possible for me to remove the link - which I will also point out is absolutely fine when I check it. Other mirrors may also rebundle the setup I gave them, they have to pay for the servers and their time somehow. Most would / should be transparent about that fact though - maybe by calling it ‘download manager enhanced’ or something.
  8. Microsoft changed the way USB 3 gets detected after the last release of ImgBurn came out. So it only sees a device as USB 2 on newer OS's. Yes, USB 2.0 / 3.0 makes a difference, but it's purely a cosmetic issue in ImgBurn.
  9. Everybody needs to be responsible for their own actions. I've provided each of the mirrors with a 'clean' copy of the program. What they do with it after that down to them, and it's not my place to police it - they run their own websites and I have no say in what goes on. Most AV tools pick up on these PUA (potentially unwanted application) bundles, so I'm surprised it let you run whatever you downloaded anyway. If your setup is anything like the one in the other thread, your SO must have also agreed to the elevation prompt when launching the 'reward tool' or whatever it was called. Expecting ImgBurn and installing a 'reward tool' - red flag, red flag. I'm sorry you fell victim to this but you only have yourself to blame. Hopefully you can clean your system up easily enough.
  10. That’s disc usage, not progress. There is no issue here.
  11. Post the log please. I’m curious to see what it says. Drives need to be mmc compliant, maybe yours isn’t.
  12. Go into Read mode within ImgBurn, click the ‘view media info’ button and see what gets listed for the cd-text info - assuming that’s where you’re getting the names from.
  13. You probably need something that supports writing in RAW mode - which ImgBurn doesn't do. The one dbminter suggested should do the job.
  14. When you say ‘usb drives’ are you talking about a usb optical drive or a usb memory stick? ImgBurn is for optical drives / discs.
  15. Yes. It's the same version for all OS from Windows 95 -> Windows 11.
  16. No, all versions are created equal. The latest version was developed when Windows 7 was still my main OS.
  17. You think wrong Yes, the 'volume identifier' in the PVD is only 32 bytes, but that isn't the one any implementation reads from. The ones that get read are the (logical) volume identifier's in the LVD and FSD. They're 128 bytes. Sometimes it's possible to be too exact with the naming of things in a gui (when using naming from a spec) and so I opted to drop the 'logical' from the name, leaving us with 'Volume Identifier'. Volume set identifier is something totally different. That's 128 bytes too. Read 2.2.2.5 in the UDF 2.50 specs again.
  18. Yes, it gets updated all the time The last few updates had cookie problems and they released about 3 updates within a couple of weeks.
  19. The 212V appears to be a Vinpower exclusive drive, so the firmware would come from here: https://www.vinpowerdigital.com/downloads
  20. It tries to be idiot proof, but you just made a better idiot. Technically, it would be still doing everything it's supposed to be doing if you disable unicode having entered a unicode volume label, it just doesn't go out of its way to tell you that you've enable (disable) something that's going to mess up something else you've configured. There's nothing in place to prevent you from typing whatever you want into that udf volume label box anyway and all it does is limit the length. The rest of the stuff only gets dealt with when creating the actual image. Sure, I can add a little test to check for differences in the UDF Volume Label field if you turn off Unicode support, but like I said, there's no validation on user input into the field anyway. I will also add a little warning line to the log if unicode is disable and the ansi version of the volume label doesn't match the original version. I already do that for any file name changes (due to unicode/ansi or length limitations).
  21. Ctrl+C works to copy the content of message boxes to the clipboard.
  22. dbminter is correct, ImgBurn has no control over that stuff. The drive and its firmware control how far out the tray comes. Are you sure you've got the right firmware on the drive? Talk to Vinpower about it and I'm sure they'll help you resolve the issue. Autoloader drives have tweaked firmware to make it come out further.
×
×
  • Create New...

Important Information

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