Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Try burning those discs at 6x and 8x too seeing as the drive seems to think it also supports those speeds. rundll32 errors don't mean much unless you know what they were running.
  2. ok so what do you see on the disc when you first open it up? Just a BDMV folder and a CERTIFICATE one? Won't PowerDVD play it?
  3. 'Write Error' means exactly what it says. The drive ran into a problem trying to write to the disc. Verbatim media is better quality and drives just prefer it over anything else. Get some of the 2.4x stuff (MKM-001-00 dye) and you'll be fine. Did you install the SB01 firmware ok?
  4. Seeing as those discs are designed for burning at 8x, maybe they'll work better if you burn at 4x or 6x rather than 2.4x. Your drives support for them at 2.4x seems a little iffy, hence why it's erroring out now and then.
  5. Check with your laptop manufacturer to see if they've released any firmware updates for the drive. Try and get some 2.4x Verbatims (MKM-001-00 dye) instead of the 8x (MKM-003-00 dye) ones. The error you're getting when setting the layerbreak is because you're trying to reuse a failed disc.
  6. If the program says something else is using it then the API used to open them (CreateFile) has failed and that's the error windows reported - ImgBurn is simply passing it on. I don't have x64 anywhere right now to look into this myself, sorry.
  7. Please post the burn log.
  8. aajr, Why do none of your quotes / posts work properly? They all contain html stuff for some reason. Which browser are you using and which editor are you using for creating your post? (Quick/Normal/Rich Edit)
  9. That pretty much just leaves the filter drivers then (Tools menu). Have you tried putting the controller into ATA mode just to see if it works?
  10. Ok so do you have the latest Intel Matrix drivers installed?
  11. All that's happened there is the I/O command has eventually timed out, meaning ImgBurn has regained control and quit nicely. Do you need your controller in AHCI mode? Which motherboard are you running? Which controller is the drive attached to?
  12. Yes it's plain then.
  13. Because the new NVIDIA drivers are rubbish and return bogus error codes to ImgBurn - they corrupt the real ones. Older versions of the driver are fine.
  14. Erm probably (whatever that is).
  15. Is the drive on an nvidia chipset?
  16. Is this drive attached to an nvidia chipset motherboard by any chance?
  17. If the disc you've got now work ok, I'd just go for a simple read -> write then. As mentioned in my previous post, you'll need to burn it onto a double layer disc. We recommend Verbatim DVD+R DL 2.4x speed discs - because they actually work! (unlike many others)
  18. I assume you're using 'Read' mode yeah? If the disc is 7GB then the image will be 7GB... it's a 1:1 copy (whereby the data from every sector on the disc is added to the file on your hdd). To burn it you'll need a double layer disc. If it's a data disc would it be used in a DVD player anyway? Normally those things are for Video discs.
  19. That's interesting then as they're using the Verbatim dye (MCC 03RG20)... I guess they're just fakes (or very low quality and Verbatim threw them away) and that's why the drive is complaining with those disc and not any others.
  20. Ok, now see if you can verify a disc against an image on your hdd without the buffer being empty all the time. It'll be interesting to see if the problem is just when you're burning to the drive or if it happens when you're reading from it too. The file on the hdd will be accessed in exactly the same way in both Write and Verify modes you see, so that bit is constant. Did you check your intel matrix (raid) driver? I believe the latest version is 8.5 or something.
  21. Yeah a software read will be translated into 2 hardware reads so that the 'striped' data is read off both drives and then returned to the calling application as a normal chunk of data.
  22. How are your drives configured? I'm sure a setup like that must be using SATA but on the off chance that there's some legacy PATA involved that could be where the problem is coming from. PATA never did like 2 drives on the same channel being used at the same time. The use of the burner is probably preventing I/O to the hdds and hence your machine runs like a dog. When you did that test burn in Discovery mode did you find that the machine stayed working just fine? How about if you run hddtune on the hdds at the same time as burning. Do you notice any slowdowns in hdd read or DVD burn speed? I assume you've got the latest intel matrix drivers installed (or whatever applies for your raid setup) ?
  23. So if Verbatims burn in it ok, are you saything that the 'Recording Management Area Information' problem only occurs when you have a certain type/brand of disc in the drive? i.e. You can insert a blank Verbatim and it won't hang/pause as ImgBurn queries the drive to obtain certain info about the disc? I can see from the disc info above that it doesn't appear to have an issue returning this info on a burnt Verbatim disc.
  24. The disc info from the LG drive with burnt DVD-R media would be nice too please. I'm not too fussed about what burnt it.
  25. Your drive returned the error codes consistent with the error 'Write Error' - meaning it had problems writing to the disc. The cause for that can only be related to the drive, its firmware version and the media you're using. If those 3 aren't a good combo you'll get a duff burn - as you did. The most obvious fix is to use better media, hence the reason for the 'Verbatim 2.4x DVD+R DL disc' thread.
×
×
  • Create New...

Important Information

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