-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by LIGHTNING UK!
-
-
If you've also tried burning at 2.4x and tried discs from a totally different spindle of Verbs, give up and buy a new drive.
MKM-001-00 is the best dye going, if your drive can't burn to it without erroring out then your drive is useless.
-
Try reading the guide properly.... all the info is there if you look.
-
Try burning faster and/or cleaning the drive with a cleaning disc.
-
Before you burn another BD-R, can you disable SPTD so there's no chance of that messing anything up?
To do that, open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sptd
Edit the value of 'Start' so it says 4 instead of 0.
Reboot so the changes take effect and then try to burn.
-
Does it play ok on your pc?
-
Do you have the IBG for the BD-RE too please?
New log + IBG for the BD-R wouldn't hurt either
-
Nope, the dye used on a disc is not something that software has to deal with or do anything special for.
Do you have any other dyes there at all?
I'm wondering if the drive/firmware doesn't support the 'Verify Not Required' setting (although it's not complaining about it) and is actually verifying the BD-R as it writes - that would certainly explain why it's slow but it doesn't explain the buffer issues or high cpu usage.
What speed was the DVD-RW you burnt to and the BD-RE?
-
Update your firmware and try burning at 8x, 12x and 16x (in that order).
http://www.firmwarehq.com/Lite-On/LH-20A1L/files.html
If it fails on all 3, try cleaning your drive.
Are those discs branded by Verbatim or some other make?
-
This isn't your thread, make your own please.
-
Enable I/O debug mode by importing the little registry file found in the FAQ and then load the program again.
-
Well if it wasn't the media, it was your drive, take your pick.
Something about your drive/firmware/media (and to an extent, write speed) just didn't place nicely together that time and the drive reported a 'Write Error' during the burn.
If it's just one failure, forget about it and move on. If they're all failing then obviously you need to change something.
-
Speak to whoever flashed your xbox.
-
As mmalves said, this is purely a drive/firmware/media issue.
Clearing up your hdd will do nothing to fix what is essentially a hardware issue.
Did you try burning at 4x?
-
-
It looks like there's something wrong with 'Verify' on both the IBG's you've attached.
High CPU usage goes hand in hand with DMA issues.
I have the exact same drive as you so I can run any test you do and we can compare results.
-
The 'FORMAT UNIT' command ImgBurn uses for formatting the BD-RE has 1 parameter changed ('Format Sub-type Field') when you select full cert (or don't).
It's set to '2' when full cert is enabled and '3' when it's not... and that's the ONLY difference.
2 = Full Certification: The entire data area shall be certified. The defect tables shall be initialized
with defects discovered during the certification process.
3 = Quick Certification: If the media has been previously formatted, the defect tables shall be
reconstructed by certifying only the Clusters that were previously declared to be defective. If
the disc is unformatted, the format process shall only initialize the disc structures with no
certification of the data zone.
That text is copied from the MMC v6 r02c specs, page 302, table 245. The specs are available from www.t10.org
-
What's the problem now exactly?
DVD Flick should just call up ImgBurn automatically once it's done with the conversion.
If you're calling it up manually and dragging over 15gb mpg files (like in your log posted above), that's where you're going wrong.
The program isn't going to make up these issues. If the OS reports the file is 15gb then that's what ImgBurn reports to the user when it says the file will not fit.
DVD Flick will output a set of IFO/BUP/VOB files in a VIDEO_TS folder. They're what needs to be in the 'Source' box within ImgBurn, nothing else. But again, DVD Flick should call ImgBurn with the appropriate parameters anyway so there's no chance of things going wrong - unless caused by DVD Flick itself.
-
It already automatically does the booktype to DVD-ROM for most drives.
If your drive locks up when ImgBurn tries to send it a command then you probably need a firmware update or a new drive!
-
Make your own thread please.
-
Look at the disc info (in the panel on the right) for discs formatted with and without full certification enabled. They should be exactly the same.
-
Obviously I can't recommend you do that.
Stick with it and we'll get to the bottom of the issue.
-
You said you were burning a BD-R... hence it's 'in progress'.
If you have no device buffer and a full software buffer then the program can't send to the drive quickly enough. Sure sounds like a DMA issue to me.
-
Try this firmware update.
http://www.firmwarehq.com/LG/GWA-4083B/files.html
Failing that, buy some better discs and/or a new drive.
-
ImgBurn always works as fast as your system lets it so if the burn is going slow, either it can't get the data from the hdd quickly enough or it can't feed it to the burner quickly enough. It's not the program itself.
How are the buffer during the burn?
Is your 'in progress' one going slow too?
L0 Data Zone Capacity Miscompare
in ImgBurn Support
Posted
Some LG drives just do (say) that - it's a bug in their firmware.
The disc's layer break position is actually fine though.
As for how to do it in the 'new' version, it's exactly the same as the old version.