LIGHTNING UK!

It's normally from bad ISO/UDF formatting utils that don't go by the specs. The udf entry 'could' be saying it's a place marker, or the file really could be 1GB in size, but being incorrectly identified and not using 2 descriptors when it should be. As the file could be/couldn't be there, that's why you'd need to test clicking Yes, and then in case of error, clicking No. The verify doesn't actually care about that error except for when there is an error at a sector that may or may not be part of that file. That is the only time that data is actually used.

I have looked into this properly now and I think it's sorted. It was the redirection of file types that caused the issue. i.e. in regedit, HKCR\.ISO The 'default' type might have been set to 'WinRAR' or whatever. When that happens, my 'Burn using ImgBurn' under .ISO is ignored. So in a previous version I also made it put one in the 'WinRAR' key. It then became visible again. When you uncheck the file association boxes, it only removed the keys created under the actual file extension keys - i.e. .ISO, .IMG etc. It did not remove the redirected ones under the likes of WinRAR. This is because multiple file extensions could be redirected to the WinRAR key and so removing it for one extension might muck it up for another one that SHOULD be there. There is no way (that I know of) to only have it visible for the selected file types if ALL the files type are redirected to a single other key - well, not with just using the registry anyway. I would have to build a dll file that hooks into explorer - i'm pretty sure that's what WinRAR does but it's a bit overkill for my little freeware tool So anyway, the next version should be much better for you. As it's just a tiny update, I may do a silent update of the imgburn.com download and you can test it out and see if it's better for you.

Unfortunately, the pioneer drives do not report their status when doing the background part of the format (or at least not in the usual fashion). It's the foreground part that only takes a few seconds to complete and that's the bit you see the % thingy for. It just saying 'Formatted: No (Started)' is NOT a good sign. That means it has begun formatting and then stopped for some reason. It could be that it failed to format the disc - can't say as I've ever tried DAXON media so I don't know if they're just not supported by the drive. At the very least, I would want it to say 'Formatted: No (In Progress)'. At that stage, it would take another 15 mins or so to complete.

lol yeah that's 3 different versions of sending the same command. I give up, it just doesn't work on your pc!

Do you have an actual problem with burning your ISO using ImgBurn? If not, I (we) cannot help you, sorry. If you do, please go into more detail a provide a copy of the log (copy + paste it from the log window).

Yes you can remove it, it's in the settings as the File Association stuff. It used to work perfectly but too many apps set themselves as the default program for the file and that then meant mine wouldn't show up at all. I then had to take measures to follow the file associations path, linking between that apps that take over control and place the reg entries in the appropriate places. That then makes it a nightmare to remove them. Uninstalling the app might fix it as the uninstall program is more aggressive than the builtin file association stuff. Like I said earlier though, if something else has changed the associations since imgburn was installed, it won't be able to find all of them to remove them - and there's no way I'm gonna make it search the entire registry for left overs! Oh, when I say uninstall, I mean do that and then install again. This time, on first run of the program, turn off the file association options in the settings. The reg stuff is only added / removed when the program is closed down.

Oh right, I get you now ok, click 'Yes' and see if you get errors during the verify. If you do, try again and this time click 'No'. One of them should work

The real error (the first one) is 'Peripheral Device Write Fault'. So basically your drive can't write to the media. Try some different discs, the drive doesn't seem to fully support those ones.

It's much easier if you just copy + paste the log so we can see what's going on.

I'm going to try and do some tweaking in that department. It's also worth noting that if you have options enabled for some files, other may also become associated with - without you specifically enabling them. That's just the way windows works I'm afraid.

Removing the file associations should be enough. It does get difficult though because as programs are installed, they change the associations again and that means ImgBurn can't nicely remove itself.

cynthia, You need to use the IBG file from ImgBurn (if that's what you used to burn it). That's what gives you the write speed graph. chewy, lol 3000 PIE.... yeah just a bit!

Shame they're missing the write speed graphs. Still, I can take an educated guess that the drive reaches 12x at around the 3.8GB mark Interesting that the NEC also shows it's own spike. Cool

Surely relinking would be happening ever time wopc kicked in. After all, it must be stopping the burn for a split second so it can do it's checking. Obviously not every wopc cut in point is leading to this spike. Also, relinking could occur when the speed changes. Again, no spike at this points. When the spike is visible, there is nothing else in the write speed graph to show anything is happening. If it was at a speed change point, I could almost understand it. Yes I've scanned in a liteon and I know the problem is only visible on BenQ's. The weird thing is, why do no other drives show this problem on the BenQ's, and why no other drives show this problem apart from the BenQ's! It seems we're in a position where neither drive can really be blamed. I was impressed that some 16x burns on the 4571 don't show the spike, whereas 4551 and 4550 do. So I guess NEC did fix something - either in the newer hardware or the drives firmware.

CMC are pretty awful so it makes sense that the TY's play ok. I guess your laptops dvd drive is just more sensitive to bad media.

I don't think the mb/gb amount even comes into it. It seems to be when it passes the 12x speed. Even 12x burns have it because, for some reason, the Nec ends up burning at 13.1x max. In such cases, the spike is much later on - but still inline with the 12x speed value.

That drive / firmware doesn't like Ricoh DL discs. A firmware update may fix that (if there is one). Failing that, buy Verbatim DL discs instead. They're more expensive but you'll end up with good burns rather than coasters!

I assure you, it's not a bug. Until it says 'Formatted: Yes'. it'll always ask to format. Do a full format via the manual method. Tools -> Drive -> Erase -> Full. Leave it for 15 - 20 mins and then refresh the ImgBurn window (press F5). If it doesn't say 'Formatted: Yes', your drive must not like those discs 100% - as that's what it 'should' say. While I have your attention, update your drives firmware. You should be on A106 now. That in itself could fix the problem with the media you're using. http://lgodd.lge.com/fwdrv/DVD-WRITER/GSA4163A106.exe

Sounds about right to me Check your player supports the media format you're using. If you're using DVD+R discs, you may well need to enable bitsetting (if possible) so it's made to look like a DVD-ROM disc.

Can your laptop read the discs (full stop) that ImgBurn burns? i.e. are the files visible within explorer? Could you post a log of the burn please - also be sure to verify the media so I can see that part too. What player software (and version of it) are you using?

It's done on purpose and so therefore is by design. DVD+RW should be formatted once - so the info on the right reads 'Formatted: Yes'. If it doesn't, your drive does not consider the disc to have been formatted. Once formatted properly, it'll do the overwrite thing again.

I don't even know what they are.

ImgBurn is not unicode in any way, shape or form so to try and do anything unicode related with it could well lead to odd things happening. So if you need to change unicode stuff, don't use it.

I don't know of any booktype setting functions for matshita drives. Never seen a program that claims to support them either.

Seriously, no idea how you're looking at DVD-R DL layer break but not being able to position it is a MASSIVE difference between that and DVD+R DL. To find an original DL video dvdrom disc that splits exactly at the unchanged layerbreak point is very much a fluke. That disc must be full to the brim, or it's not as 'compatible' as it could be. Every test I've ever seen has said dvd-r dl are not as compatible as dvd+r dl when the dvd+r dl booktype is set to dvdrom.