Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,516
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. The one that matters (i.e. the one explorer would read) is the one that's displayed in the 'Source' box in Read mode. Other info about the number of sessions/tracks etc is in the disc info on the right.
  2. I think I've traced the source of this problem to a race condition and multiple open/closes of the drive whilst attempting send it some commands. I've synchronised the relevant functions (via critical sections) so hopefully it'll be fine in 2.5.0.0
  3. I never said the new version would open MDS v2.0+ files. They won't be supported - ever. You'll have to burn them in DAEMON Tools Pro, Alcohol 120% or anyone else they have in their pocket.
  4. You've probably got InCD or some other packet writing software running. Ditch them/turn them off and you'll be ok.
  5. Why are you making a new thread? Got something against your old one that's like 4 threads down on this page?
  6. Doesn't the error box tell you the problem?! I cannot support v2.0+ MDS files. Update ImgBurn too, yours is out of date.
  7. The drive still thinks that's a blank disc.
  8. You're burning in Build mode yeah? Can you see the files if you browse the disc in explorer? What file system do you have selected? Where's the log of the burn?
  9. Ok so what happens if you click 'Ignore' or 'Continue' when that error box pops up as it tries to set the layer break position?
  10. I need it from the exact disc that went with the log above.
  11. Have you messed with the settings in the 'Options' tab? Click the 'Reset Settings' text/link down the bottom of that tab.
  12. What does the disc info on the right say when you have that disc in the drive (in read mode please) ? Copy + paste the text.
  13. Out of interest, what does the disc info panel on the right say when you have that disc in the drive? (copy + paste all the text please) It doesn't look as if it should have errored out like that, but instead failed silently because the LB was already where it needed to be.
  14. The 8x ones are less likely to work. Hopefully you'll be ok though.
  15. Just because it's written in someone's tutorial doesn't mean it's 100% correct and written in stone. It's different for every drive/firmware/media combo.
  16. MKM-003-00 are not MKM-001-00. The MKM-001-00 (2.4x rated) discs are more compatible with writers. The best thing for you to do now is buy a new drive (an external I guess if you're using a laptop?). Matshita ones are pretty rubbish anyway.
  17. Do you have a log of where it's actually burning something? Try it with 'Test Mode' enabled and see if your machine/drive makes it the entire way through the burn that way.
  18. Nope.
  19. http://forum.imgburn.com/index.php?showtopic=8000
  20. That's because there isn't one. The supported speeds are shown in the disc info text on the right. Select anything other than those and your drive will just pick the closest one automatically.
  21. Get different discs, your drive doesn't seem to like that dye. In fact, I don't remember Plextor drives really liking any rewritable media all that much! For me, they've always failed to burn rewritables long before my other drives did. Stick to decent write once stuff where possible.
  22. It's just a standard Windows API message box. If ImgBurn has focus, try just pressing enter.
  23. Try some other 'supported' speeds beyond 4x too. 4x might not be the best one for that drive/firmware/media combo. You never know, DVDInfoPro might work now you've put that new firmware on.
  24. Is that after clicking the 'Start' button? I guess that answers my question about your drive supporting PIPO scanning
×
×
  • Create New...

Important Information

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