LIGHTNING UK!

ok and what does it say in the statusbar? Does it make a difference if you have a disc in the drive or not?

The discs aren't finalised but I'm sure that shouldn't be an issue. There's no TOC stuff in your Disc Information text... I wonder why that is? Are you using v2.4.4.0? Oh and don't wait a month, if the post isn't on the front page I'll never look at it again - so just 'bump' it if you're waiting for an answer.

That was for their benefit mate, not yours

Yes, but obviously if it fails at the end you've wasted the time it's taken to burn + the cost of the disc.

I doubt your drive supports that dye (MBI 03RG40). You could try updating the firmware on your drive. http://www.firmwarehq.com/download_332-fil...19-20A.zip.html Run the 'K251GN90.exe' file from that zip. If even the updated 2.19 firmware doesn't support them, use different discs.

FYI, the 'AWS' thing doesn't mean/do anything unless you actually configure it... it'll just burn at MAX speed. http://forum.imgburn.com/index.php?showtopic=4249

That doesn't really answer my question - as your answer is unrelated. What do you see here? http://forum.imgburn.com/index.php?act=UserCP&CODE=50

Thanks, it's now live on the website.

You don't need to rename anything, the program just limits the names in the file system to 8.3 characters. I'd be amazed if ISO9660 works when ISO9660+Joliet didn't. Are you really really really sure your player supports MP3 discs?! Do you have a manual for it? They normally say how the discs need to be burnt for them to be compatible (mine does anyway).

log log log log log log log log oops, I forgot to say 'please'

It won't destroy anything, it'll just error out - either at the start or at the end.

What do you see under My Controls -> Subscriptions -> View Forums ?

Yes you do, just copy + paste what you see in the Log window.

That's a Nero log, this is the ImgBurn forum. If you want help then you need to: 1. Be using ImgBurn. 2. Post an ImgBurn log.

I doubt anyone has ever tried overburning a BD-R, personally I wouldn't risk it.

1. Downloading the thing in the FAQ isn't a magical fix, you're supposed to use to get a debug log and then show it to me. 2. If the drive can't read the disc, no wonder it was taking a while. You probably had a crappy burn - are you using decent media? Try burning at 8x or 12x instead of max (if that's what you're doing). 3. If you system gets hung up then it gets hung up. ImgBurn is not in control once the command has been sent to the drive and if if never gets a response it doesn't have the ability to abort anything. On bootup your machine does lots of stuff, once it's finished it'll idle again.

There's no such thing as verifying a read operation, it simply doesn't apply/exist. I've never known anyone to be anal enough to want to do it - reading and then reading again seems pointless. If it's really that important to you then you should read the disc twice and use a 3rd party to compare the two (or turn on md5 calcs and compare those).

Updated the website to 'v.1.0.0.7 fix01'

Trouble is, is it broken - we just don't know the exact cause yet. You never did tell us which chipset your board uses - Intel, Nvidia? Do you happen to know the exact model of motherboard you have? (probably only applies if you built the pc yourself)

Bad disc? Drive needs cleaning? Drive is faulty? What make is your laptop? Perhaps they'll have a firmware update for the drive to make it better.

I'd remove the cdrb one.

Different types of media need different commands to be sent to the drive in order to finish off the burn/finalise the disc. DVD-R doesn't need much because you have to tell the drive exactly how big the track is before the burn actually starts rather than saying where it ends (after the burn).

It's based on 1.0.0.5, of course certain (newer) strings aren't going to have been translated yet.

Technically, the installer doesn't actually change any. That's all still done by ImgBurn itself the first time you run/close it down. I know that needs to change but I haven't gotten round to doing it yet.

If you're having problems, do the sensible thing and post a log. We can then recommend things like firmware updates or changing the write speed.