-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
MD5Sums don't match, yet verification was "Successful".
LIGHTNING UK! replied to Knightofoldcode's topic in ImgBurn Bugs
Ok, I see the problem now. When ImgBurn scans the tracks it checks the end of them to see if they're readable. Depending on how a disc is burnt (SAO or TAO), you can end up with unreadable sectors at the end that aren't really part of the track but are referenced in the TOC anyway. This little check is being initiated due to your drive reporting that 'off by 2' value for the track size. Here we see ImgBurn trying to read the sectors that aren't part of the track according to the track info but are according to the TOC... (i.e. 329182 and 329183 as mentioned before) As you can see, the drive is unable to read sector 329182. ImgBurn then classes this sector (and any after this point but within the same track) as junk that it shouldn't read because they're probably not real ones. Internally I just call them 'EndGap' sectors and once the real data sectors have been read, ImgBurn creates empty sectors for all the EndGap ones. So it's reading up to sector 329181 from the disc and then dummy filling the remaining 2 with zeroes. Currently, these EndGap sectors are NOT part of the MD5 calculation - that explains why the MD5 doesn't match I guess - assuming of course that the last 2 sectors in your image file really are just all Zeroes. I'm going to assume that they are all zeroes (can't rely on what the drive reported when you said you could read the sector and yet the log shows the drive can't) and that's why the byte level verification passes. So the moral of the story is... trust the byte level stuff more than the MD5 value I'm going to add some more debug logging in now so it'll make these types of problems easier to justify. -
Problems Burning Verbatim 2.4x (Singapour)
LIGHTNING UK! replied to bneale's topic in ImgBurn Support
If it's not just a duff batch of discs there must be a flaw in the firmware. Talk to LG and see what they say. Maybe they'll send you a new drive. -
Matshita drives are rubbish to start with, by using anything but the best / most compatible media you're only asking for more trouble. http://forum.imgburn.com/index.php?showtopic=8000
-
Yes it works in Windows 7. When you say 'taskbar', do you mean 'sidebar' ? From what I've seen, the taskbar is slightly different in Windows 7 but it still shows 'buttons' for applications once they've been launched. I don't really have any plans to write a gadget for the sidebar.
-
That 'older version' didn't look for errors during the finalisation stage. In any case, the disc still isn't readable. Yes you should give the MKM-001-00 discs a try if you can source them from somewhere. Just make sure they're the ones made in Singapore.
-
This is the forum for ImgBurn. Making mp3 files isn't even remotely related to it! 192kbit, 44Khz (if you want it downsampled) or 48khz if you don't, Stereo.
-
Yeah but you can get some tried and tested enclosures by decent brands. Most of the cables are cheap crap from ebay.
-
It's not, no.
-
blu-ray disk formating and erasing help needed
LIGHTNING UK! replied to shamoo's topic in ImgBurn Support
I believe there is only 1 sort of Verbatim BD-RE, not too sure about the BD-R. -
Players don't care about sectors they can't read, they'll just skip them. PC drives are built for accuracy. Not only that, every drive is different. Try the disc in another PC drive and it might work.
-
DL's are harder to burn due to their very nature (of having 2 layers!) so if the laser isn't 100% it's quite possible that it won't burn/read them.
-
Who knows?! We often hear from people where their drive works one minute and not the next. I don't know why they break, sometimes they just do. You can't really expect them to last forever when you can buy them for
-
I guess the disc must be damaged then because the drive is certainly unable to read that sector.
-
Does the message in the status bar change at all when you insert the disc? i.e. when you eject the tray does it change to '.... - Tray Open' ? And having inserted the disc and close the tray, does it then change to something like 'in process of becoming ready' ? If so, it's kinda working but I expect the drive's laser has actually broken. Try the drive in another PC if possible.
-
That looks line an original disc and I expect the error is part of some copy protection. ImgBurn won't read copy protected media, it's not designed to.
-
Where do the verbatims say they're made? IF they're made in Singapore and your drive won't even produce a readable burn on those then you should try using a cleaning disc before asking for a new drive (or buying an external one yourself)
-
Keep to your own thread please, crossposting is annoying and doesn't help anyone.
-
The layer break problem on DVD Video comes from the loss of streaming when switching layers. If players don't know about the layer switch in advance (signalled via a flag in the IFO file) then they can get confused / hang when there's a loss of streaming data and timecodes get screwed up. Back in PC land, nothing cares about a slight pause when reading a file from a data disc.
-
It means the drive can't see the disc. ImgBurn reports the exact error/status code the drive tells it so this is not a software issue. Does it recognise any discs you put in it? (i.e. even original CDs / DVDs)
-
That's not you burning though, that's you trying to verify something. It would be better if we could see you trying to burn and verify something in a single session. The log shows your drive can't read the disc. Either the disc is faulty or your writer just produced a really bad burn. What make is your computer? Have you checked with whoever made it to see if there are any firmware updates for the drive?
-
blu-ray disk formating and erasing help needed
LIGHTNING UK! replied to shamoo's topic in ImgBurn Support
My initial post is still true! The disc that comes with the drive is the worst one possible. -
That's the speed everyone here recommends 2x isn't even an option on those discs with your drive/firmware so it would have been using 4x (as that's the first one it supports). Look at the 'Supported Write Speeds' in the disc info on the right.
-
Log 1. Try burning at a more sensible speed. Log 2. Read the FAQ.