Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. So doesn't your last 'edit' mean it's just that 1 burner that's messed up? Why are you changing the label and icon of the drive anyway?! (what an odd thing to do!)
  2. Turn it off in the 'Advanced' -> 'Restrictions' -> 'ISO9660' tab.
  3. Verbatim, Verbatim, Verbatim, Verbatim. If you're not sure what I mean by that, take a look at *any* of the 3 million other 'I've got a problem with burning DL discs' threads on this forum.
  4. If it's 8GB, yes you'll need a dual layer disc to burn it onto (assuming you don't want to make it smaller by shrinking/recoding it). Please bear in mind that ImgBurn won't copy a disc if it's protected. P.S. It's 'GB', not 'MB' if you're talking about the size of a disc. 8MB would be tiny.
  5. Care to post up a screenshot? No wonder it's having trouble if 31 apps think they're using the drive. Maybe it was just the search term you used - or you have a lot of optical drives?
  6. Yes, an external one would be better.
  7. 31 exe's that say they have a 'handle' open to the drive?!
  8. Do it again your end then and once you've deleted the top image, look back in the main window (close the queue one) and see what it says in the status bar.
  9. I've separated this out now so the AUDIO_TS option can be left enabled and the new CERTIFICATE one can be disabled for those of you just building AVCHD discs.
  10. If it's an 8x drive then 8x is all it'll do. 8x is a great speed so I shouldn't worry too much. Your main concern should be that in general, laptop drives are shit. (pardon my french)
  11. Why does an admin need an static link? Surely you download it once and push it out from your own servers? Perhaps I'm just thinking in a non-lazy way, I dunno!
  12. LIGHTNING UK!

    FAQ

    Problem: You're getting an error message about DirectShow decoding your audio files to digital silence when you try and burn an Audio CD. Answer: Certain encoders (LAME 3.92?) can produce files that the standard Fraunhofer IIS MP3 DirectShow decoder ( l3codecx.ax ) doesn't like and cause it to output digital silence without reporting any sort of error. ImgBurn can detect this and will warn you about it. Here's how you can fix the issue... Get an updated version of l3codecx.ax! Windows XP ships with v1.5.0.50 but there's a newer v1.9.0.311 floating around on the internet. Find it, download it and keep it somewhere safe. Unregister your 'old' version by typing the following in a command prompt window: regsvr32 /u %systemroot%\system32\l3codecx.ax Now copy the updated decoder file to %systemroot%\system32 (i.e. C:\Windows\System32) and overwrite the old one. Go back to the command prompt window and type in: regsvr32 %systemroot%\system32\l3codecx.ax Reboot your PC and try burning the disc again. You could also try installing the LAME DirectShow filter which is available from RareWares - http://www.rarewares.org/mp3-lame-dshow-acm.php Update: Microsoft have released an update to fix a security issue found in the original codec. This newer version (1.6.0.51) has also been found to fix the digital silence issue. http://www.microsoft.com/downloads/details.aspx?familyid=B1582A74-4A7B-4540-BEB1-7C89C86EAE87&displaylang=en Here is more info about the update: http://support.microsoft.com/kb/977816 http://www.microsoft.com/technet/security/bulletin/MS10-026.mspx
  13. It'll only do that if the currently selected drive is then the same one as the (new) first item in the queue and that drive has no media in it.
  14. It doesn't look like your burner supports those discs. Try hunting down a firmware update for the drive, that may fix the problem.
  15. If nothing happened when you clicked the 'Write' button then it probably wasn't enabled in the first place - and I'm sure there will be a good reason for that. Is it in colour or is it greyscale? It's only in colour when it's enabled - and it's more obviously a button when you hover the mouse over it. When it's disabled it stays flat all the time. Assuming it stays disabled, what does the message in the statusbar at the bottom of the main window say?
  16. It asks you the first time because you've got the 'Auto' (Auto Calculate) checkbox ticked on the information tab. Personally I don't bother with that - hence why it's off by default. If I want to calculate the image size I'll do it manually when I've finished adding my folders!
  17. Not erroring out just means something in your system really isn't playing nicely and I expect the OS is having to wait for an answer - which it never gets. If the OS never gets an answer, ImgBurn never gets an answer and the OS remains in control - basically that means ImgBurn is frozen at this point. You can use the stuff in the FAQ to pin point where the locking issue is coming from (see which app is using the drive) and hopefully then you'll be able to fix it. If it stays being a problem you'll probably have no choice but to tell ImgBurn not to attempt to get exclusive usage of the drive at all. Please note that this is a workaround (NOT recommended) and not an actual fix. To fix it you need to find out why the OS is getting stuck trying to give ImgBurn exclusive access to the drive and correct it by updating/removing the problem causing software/driver.
  18. Look at the tooltip text on that button you're clicking. What makes you think you need to click that button to burn a disc?
  19. Are you trying to read an original (and more than likely, copy protected) DVD-ROM there? If so, that's why it won't work. ImgBurn cannot copy protected discs and we cannot help with anything on the subject of circumventing that protection.
  20. What does it say in the statusbar at this point?
  21. Get yourself a USB 2.0 card too, you're burning with the drive constantly using the built in 'buffer underrun' (burn-proof) protection... and as the drive is now ancient, I doubt it's very good at it.
  22. As mentioned in bold text in the pink box, please include a log where the burn / verify has failed.
  23. That's was a lot more obvious once you told us it couldn't read originals in posts 3 and 5.
  24. It'll happen when build mode gets a revamp.
×
×
  • Create New...

Important Information

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