Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,522
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. When you're in write mode, right click the drive selection drop down box and hit 'family tree' for me please. Close the prompt and then copy + paste everything from the log window.
  2. No, that isn't normal. Your system / drive doesn't appear to be responding to the commands. Reboot and try again. If you have other/better discs, try those too.
  3. It doesn't label it as malware, it detects opencandy as a potentially unwanted program. As it's 'potentially' unwanted, it isn't checked by default. Stop exaggerating things.
  4. It doesn't author discs like that at all. To be honest, I don't even know why it prompted you for an m2ts file. If all you have is an m2ts file, create your proper BD video structure using something like MultiAVCHD or possibly tsmuxer.
  5. This has nothing to do with ImgBurn. If you want the drive, buy it.
  6. Your drive can't burn DVDs, it can only read them.
  7. I checked the file you uploaded and one of the files in the archive would require the CUE to be saved in Unicode format. It created the CUE just fine, the issue comes when it attempts to add it to the write queue (thus loading the CUE) after that. The bit you change is the 'Save as type' dropdown in the 'Save As' box that comes up when you click the 'OK' button on the 'Create CUE File' window.
  8. Surely LiteOn are the best people to ask that question? Only they know how their drives work internally... otherwise it's just me guessing at stuff.
  9. I wouldn't class this as an ImgBurn issue at all. It's something with your system... probably related to the drivers you're using for your nvidia sata controller I have no idea why it's taking so long for it to process the commands ImgBurn is trying to send to your drive, nor do I know of a way to fix it properly. Do you know which chipset your motherboard is using?
  10. So you created the CUE yourself? If you have files with names requiring Unicode, you need to tell ImgBurn to save the CUE in Unicode format (in the 'Save' dialog box). It defaults to ANSI for compatibility with other applications.
  11. Ah sorry, you have to do that when it's still set on SPTI.
  12. It's not calling ImgBurn malware at all, it's finding the OpenCandy DLL in the installer and flagging it as 'PUP.Optional.OpenCandy'. It even defaults to doing nothing with it (the checkbox isn't ticked). Just because the program is called (starts with) 'Malwarebytes' doesn't mean everything it flags to the user is 'Malware'. These programs flag tons of stuff now, not everything it out to steal your identity/money/loved ones.
  13. I wish I could help but I'm afraid I can't. The disc burnt and verified ok so it's 100% readable in the drive that wrote it. Any issue beyond that is down to the source file or the playback device. I'd probably still give it another go with some decent Verbatim or Taiyo Yuden discs though. Just in case it is a readability of the burnt disc issue.
  14. Install virtual clonedrive (free) and then switch ImgBurn's I/O interface to ElbyCDIO in the settings. See if that works. Can I also please get you to right click on the drive drop down selection box when you're in Write mode and then click 'family tree'. Close the prompt and then copy + paste everything from the log window.
  15. All of the settings are per user, yes.
  16. I'd use the 'create image file from files/folders' option on the initial screen. Then, using the 'Input' menu at the top, switch to 'Advanced' mode. Bring up the 'Disc Layout Editor' window and add what you want to burn onto the disc. Close the DLE window again and configure the name of your destination image file. Switch to the 'Options' tab and change the 'File System' one to UDF (use v2.50). Then just press the big 'Build' button. That'll create an ISO image you can burn to disc using the 'Write image file to disc' option. If you have enough hdd space, build all of the images first and then add them all to the write queue so you can burn them all more easily. I recommend building images first rather than burning the photos to disc on-the-fly as you'll be working with lots of little files.
  17. The Verbatim 4x or 6x. If they don't work either, try cleaning the drive with a cleaning disc or just give up on it and invest in a new one.
  18. It's just a string in the registry - along with all of the other program settings. Check HKCU\Software\ImgBurn
  19. Try some other/better (and non 'ritek') discs. The error you're getting is bogus and your drive should not be returning it. Try looking for firmware updates for it.
  20. No, your hdd makes no difference to burn quality. Either the source files can be read from it ok or they can't. Taiyo Yuden only made LTH discs last time I checked. They're the cheaper BD discs and should probably be avoided.
  21. The date time stamps in the file system.
  22. So then I guess the source disc you made the image from doesn't work either. I can't really help with this as I have no idea what's meant to be on the disc in the first place, nor what's giving you that error message.
  23. That means your drive is having trouble initialising the disc. I'd probably be giving it a clean at this point.
  24. Yeah, you were mislead If you want an Audio CD (i.e. like the ones you'd buy in a shop and that play on a normal CD player), you need to use a CD. For everything else, it's just data and can be read off any type of disc. If you want to write those little images back to a DVD then you can, they just don't *need* to go on a DVD (and the original source discs are just CDs).
×
×
  • Create New...

Important Information

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