Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. It's 50,000,000,000 bytes of free space, not 50GiB (53,687,091,200 bytes) - which is what the OS uses when calculating / displaying the size of files.
  2. It should tell you what it's doing in the status bar of the main window... what does it say?
  3. No. You'd have to recreate the entire file system in 2.50.
  4. The time comes from whatever DirectShow managed to decode (or ACM if that's what it has to fall back to). Feel free to post an mp3 that doesn't work and I'll examine it my end.
  5. Tools -> Settings -> General -> Display Warnings -> Maximum File Size oh and I've added code to check the drive is actually over 4GB itself now too - so technically you won't need to disable that option in the next release.
  6. There's a newer firmware available for your drive. http://www.firmwarehq.com/Lite-On/iHAS324%2BY/files.html You might be having problems because you've attached the drive to a weird controller. Maybe update drivers would fix the issue.
  7. Why are you trying to cancel it at all? If your drive is stuck doing something then there's nothing for ImgBurn to cancel out of... it's just waiting for your drive/system to finish processing an I/O command. Please post the log so we can see where it's getting up to. The message in the status bar also helps us work out what's going on.
  8. You can / should use something like IsoBuster to check the order of the files. That log just shows the creation of the image. I'd really need to see the log of the burn+verify process on the non-working disc. It would also be handy to know exactly which player models are having problems and what message gets displayed on them.
  9. ImgBurn is working at a level where it doesn't know or care about your mobo/cpu. All it needs is a system that works properly. If it isn't then it's down to your drivers etc. Where's the log from the Verbatim discs? Please post it if you have such a thing.
  10. Without testing it on a machine that I know works fine (i.e. mine), it's impossible for me to say.
  11. That's not a good sign. Your drive appears to have some issue with the discs as it starts to burn them. That's a very strange (initial) error to get during a burn!
  12. You don't want or need 'overspeed' enabled. Burn at 4x too, it should work fine at that speed with default settings in ImgBurn and just 'Force HT' enabled on the drive (smartburn is enabled by default, the other 3 are disabled by default). Try doing a 'clear opc history' on it too.
  13. I don't understand why it's timing out after only 2 seconds. It's not a Windows error though (normally that's a 'semaphore timeout period has expired' issue) so it seems to be something internal to the drive. I would however like to see if you get the same problem on an Intel chipset based machine - or perhaps when the drive is connected via a decent USB -> SATA adapter. Don't waste your time disabling 'Burnproof' within the program, re-enable it again.
  14. You didn't mis-post, that's just my signature
  15. It only burns what you give it, using the names the things already have. Ignore what the player displays, look at the disc in Explorer on your PC.
  16. Turn 'preserve full pathnames' off again.
  17. No, put it back on 'Auto'. You shouldn't have ever changed it in the first place.
  18. No, but if you've changed that one setting without knowing what it does, you may have messed with others too. The defaults work best (hence why they're the defaults) so the best thing to do is reset everything back to default. It would have helped if you'd posted the full log rather than just 2 lines of it.
  19. Right and so what's the MID of the disc that works? You should be able to boot into XP using hiren's boot disc (or even safe mode may be enough) if you want to rule out the OS playing up. There's also the option of using a Linux live cd - maybe the Ubuntu one.
  20. Multisession... Not really. I just use a USB stick or portable hdd if I need to keep adding updated files to something. When I want to then archive bits I burn a full disc.
  21. It looks like the program thinks it's meant to be writing in DVD mode. Maybe you've messed with the settings and taken it off 'auto' and put it on 'DVD' ? Try reinstalling and make sure you select the 'reset settings' option within the installer.
  22. It's not going to be a conflict like that, ImgBurn has control of the drive and will have locked it so nothing else can use it. The error message the drive (or system) is returning (Unable to recover TOC) is quite specific. The only time I've ever had a drive do that to me is when it had developed a fault. Find some old burnt discs and see if it has the same problem with reading those.
  23. What OS are you using? If it's Vista onwards, use the OS's native burning for multisession stuff. ImgBurn always finalises the discs it burns and wants new/empty ones when you burn.
  24. Your drive is unable to initialise the disc it just burnt - that's never a good sign. You could try cleaning it with a cleaning disc and/or buying better quality discs and hoping it doesn't have the same problem with those.
  25. You can't I'm afraid, ImgBurn always finalises the discs it burns. You can just use the OS's native burning capabilities if you want/need multisession.
×
×
  • Create New...

Important Information

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