Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. It *might* support the Ricoh command set.
  2. Erm.. the 'Medium Not Present' bit is a big clue. That's what your drive is reporting, ImgBurn isn't making it up.
  3. Exactly which thread did it say it was waiting for? A flashing light on the drive doesn't mean it's burning. If the drive was still accepting I/O then you'd see the ImgBurn GUI updating itself. If a thread won't terminate then it means some API function has got stuck...and that's out of my hands. ImgBurn cannot abort nicely if it's not in control in the first place. As soon as the OS returns control to ImgBurn, it'll process your request to abort/quit. ImgBurn locks the tray so you can't eject the disc. If the drive responds to I/O (which I doubt it does), just load ImgBurn again and hit the eject button. It'll unlock the tray and eject it.
  4. I believe Cynthia first told you to burn at a slower speed.
  5. ImgBurn cycles the tray before the verify process starts... did you take the disc out or something during that time? I can't think why else it would say there was no disc in the drive - except if it failed to reinitialise it for whatever reason.
  6. There's a log window that should be open when ImgBurn is running (i.e. 2 windows in total for ImgBurn, the 'main' one and the 'log' one), burn something and copy + paste the text from the log window. Make sure you're running ImgBurn directly - i.e. not via any other program as it'll probably point the log for that session to a different file and it therefore won't be saved into the main ImgBurn one. Again, that's not so much of an issue if you copy + paste from the proper log window inside the program.
  7. Yes because you've given us nothing useful to go on. The log (of a failed burn) contains all the info we need... the one you posted in your screenshot was just you opening and closing the program - i.e. no help at all.
  8. Please just copy + paste all the text from the log window when your burn fails, there's no need for screenshots.
  9. You'll never get 60 or 70 over USB... 20 or 30, maybe. If you want it faster, it needs to be internal or eSATA.
  10. Those burns are not with Verbatim media. There is a 1.03 firmware update for your drive if you look on the LG website.
  11. We need a log of it failing to start properly.
  12. What I was getting at is that you have to expect an error if you're burning 7gb+ onto a 700mb disc. That error is perfectly normal considering what you were asking your drive to do.
  13. What version of the SPTD driver does your version of Alcohol come with? That in itself can cause problems but an app that actually uses it might be fine (because the SPTD drive is very low level). Some filter drivers can also mess up the I/O chain and make things fail. Please copy + paste the filter driver info - look in the Tools menu within ImgBurn.
  14. And I assume the disc status still shows up as 'incomplete' in that text on the right? Weird that it wouldn't error out on any of the 3 close options. Oh well, I guess it's ill.
  15. What I'd like to know is why did elsinor hijack this thread instead of starting his/her own? Kinda rude don't you think? We hadn't even replied to the op!
  16. You need to fill the creation & modified volume dates and also the folder/file one.
  17. Looks like another nvidia controller issue to me, revert back to an older set of drivers.
  18. I think a USB 2.0 PCI card would be the way forwards for that machine.
  19. ImgBurn's build mode was designed for burning from an existing disc structure. The thing you're going on about is a very common/obvious suggestion/request (did you search before posting?!) and I've already commented on it several times.
  20. Why are you trying to burn a DVD DL image to a CDRW?
  21. Eject the disc and reinsert it. Does the message in the status bar change at all... even for a second? You can also eject the disc, press F8 and then insert it again. ImgBurn polls the drive every second and you'll see debug I/O commands scrolling in the log window reporting the status code of the drive. If you don't get anything in the log when you press F8 it probably means the bus has crashed/got stuck and it needs resettings - which is what would happen when you reboot. What type/make of controller is your drive connected to? Do you have an intel chipset motherboard? an nvidia one?
  22. Are you sure that's not just Windows giving you a blank window so you can drag + drop files for burning? Windows doesn't understand the filesystem used by the Wii (and why should it?!) so there's no way it's actually letting you browse the real disc.
  23. I'm talking about the actual drive. Yours can read DVD's but it can't write them.
  24. You don't have a DVD burner.
  25. It doesn't matter which mode you're in so long as the correct drive is selected in the drop down box. I'm not asking you to burn anything, just put one of the failed discs in the drive and go through those 3 options in the Tools menu as mentioned in my previous post.
×
×
  • Create New...

Important Information

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