Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. None of those require an erase when new... certainly not the write once media! DVD+RW and BD-RE require formatting (done by a full erase) when new. The program takes care of everything automatically so you don't need to do anything. It'll erase/format as and when required.
  2. You just pick one of the 7 mirror sites listed on the Download page.
  3. The log file on the hdd has a header prepended to each session.
  4. Can you post the complete log for that burn+verify session please.
  5. It's normal for the error levels on the 2nd layer to be different to those on the 1st. Don't worry about it. You might not have such a spike at the layer break if you weren't overburning but that's about it.
  6. The PC displays the volume label as stored in the file system. The player probably reads the movie name from the BDMT_ENG.XML file.
  7. You're overburning the disc there. You have to expect error levels to go up in that area (and consider yourself lucky if they don't).
  8. When it works ok, does the player list *exactly* the same name as displayed next to the drive icon if you look at the disc in Explorer via PC? If the ISO hasn't really been changed from what the original would look like (i.e. not compressed / stripped or anything), I see no reason for the two discs to display different things. Ejecting + reinserting doesn't fix it no?
  9. ImgBurn just burns as-is. If you want a DVD Video disc you'll have to convert your files into that format and then burn that. You can use something like DVD Flick or ConvertXtoDVD for the conversion. The alternative is to buy a player that supports playing the files you've got.
  10. When I said you couldn't update it, I was talking about the physical disc you've already burnt - it will have been closed / finalised. Just so we're clear
  11. Nothing you've described is a bug in the program so I'm moving your thread to the 'Support' area. Now please do as the pink box up the top says and post a log. A full erase is 100% controlled by the drive. It reports when it's finished and it reports the % complete. If it never completes you must have a bad drive/firmware/media combo. Ensure the firmware for your drive is up-to-date, that you're using decent media and that the drive is clean (use a cleaning disc).
  12. Assuming the ISO file were ok in the first place, yes, if they've burn+verified ok then your playback device has a problem.
  13. I was using a newer/better drive (an expensive BD burner) I guess. Of course can scans vary from disc to disc, let alone spindle to spindle. Don't forget that those results are about 6 years old now! I'm sure new drives perform differently with the media available today. Why not post your scan so we can see what you're seeing.
  14. What you burn to them makes no difference. The higher quality discs are easier to burn and easier to read back. So there's less chance of your drive failing to burn the disc in the first place and less chance your playback device will have problems reading it (which causes stuttering or complete failure). Disc quality and video quality are two totally different things.
  15. 120 mins means nothing really. It's not like CDs where you have a fixed 74 / 80 mins max of CD audio on them. The length of video(s) you can fit on a disc depends on the quality (the bitrate used) of said video(s).
  16. Did you buy the drive separately or did it come in the PC? It'll either accept the update or it won't... so give it a go Discs aren't discs. They vary in quality and drives create better quality burns (and have less chance of failing to burn) on certain ones. As with most things in this world, you get what you pay for.
  17. I honestly have no idea, I'm not a BartPE person. Perhaps someone else can help you... either here or at their own forums.
  18. It's much easier if you copy + paste all the text from the log window rather than taking a (too small to read easily) screenshot. Your drive reported a 'Write Error'. So basically, it didn't like the disc. Try this firmware update - http://www.firmwarehq.com/Philips/DVD8701/files.html You could also try using better discs - Verbatim or Taiyo Yuden.
  19. You can't update the disc you already have, you will need to burn a totally new one. Follow the same process/guide you followed the first time - which is probably a BartPE guide rather than anything related to ImgBurn.
  20. Sorry, I don't have any other ideas, no. Burning is an internal feature of a drive (software just provides data). It governs success/failure based on its firmware and the media you're using. As you've got a LiteOn drive, try doing some disc quality scans (in Opti Drive Control / CDSpeed / DVDInfoPro) on the discs that have failed to verify.
  21. Seems ok to me under Ubuntu 10.10 with 1.3.34 and 1.3.36.
  22. Try and get hold of some proper Verbatim (MCC mid/dye) or Taiyo Yuden (aka Victor JVC) discs. If the drive still fails with those I'd return it saying it's faulty.
  23. Sticking with your laptop, you have a few options... 1. Get a new usb enclosure and hope it has a better chipset - or at least one that's compatible with your usb chipset. 2. Get a USB pcmcia / expresscard card and hope it works with your enclosure. 3. Get a eSATA pcmcia / expresscard card (if you don't already have an esata port) and an enclosure that supports eSATA. This will allow you to use your drive at full speed... USB may not. I found your thread by just looking for your name in the list of topics (in the 'Started By' column) on the first page. It was only 5 or so down thismorning.
  24. The 'system' and 'archive' attributes cannot be stored/represented by the file systems. There's only a flag in the descriptor to say the file is 'hidden'.
  25. I'd class that as a bug in the lightscribe software. After all, if ImgBurn can still talk to the drive ok, why shouldn't it be able to? Lightscribe's website mentions the issue. http://www.lightscribe.com/support/index.aspx?id=488 PROBLEM: My LightScribe Drive is not detected by my computer or Labeling Application POSSIBLE CAUSE: Incompatible Windows Security Setting for drive. POSSIBLE SOLUTION: The registry key AllocateCDRoms in Windows system must be set to the default 0 value. Also, the Autorun registry key needs to be set to 1 for some systems. Please see this Microsoft support document for procedures to reset these values. If you are not familiar or uncomfortable making this system change, please log request in support section for assistance I've already added a warning in the installer to say the option can break autoplay so I've just tweaked it to say it can break autoplay & lightscribe. Thanks for reporting it.
×
×
  • Create New...

Important Information

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