LIGHTNING UK!

You could do it in a user logon script, or yes, just do it in HKLM\Software\ImgBurn. If no HKCU\Software\ImgBurn exists, it'll get the default settings (well, as many as you specify) from HKLM\Software\ImgBurn when it's started and then save them to HKCU\Software\ImgBurn when the it's closed.

'Verify Not Required' is specific to BD-R and is the exact name of flag as specified in the MMC specs. It stops the drive performing automatic write/verify as it goes along (which then slows the burn to a crawl).

Can you copy + paste the disc info text from the box on the right when you're in Write mode please.

No, never just ignore them. When you get one, something isn't right. It could be a memory issue, it could be general I/O comms issue, it could be bad error correction on the drive's part... but there IS (or at least there was) an issue. If you use what ImgBurn tells you and then perform a 2nd test (of your choosing) to confirm/deny the issue then that's fine.

Do you have autorun/play/insert enabled? This is just the OS messing up. You can usually give it a nudge in the right direction by closing ImgBurn, ejecting the disc, refreshing the 'My Computer' window, putting the disc back in, refreshing the 'My Computer' window again. It just needs to notice the media has changed.

It can burn any size ISO, you just need to have the right size media to put it on to. Disc images (ISO etc) are burnt in Write mode.

Post the log please - as per the pink box up the top

Well, the first thing you should try is disabling any sort of wireless security on the router and then see if it can connect ok. If it can, move the security up 1 level (probably from 'none' to 'wep') and then try it again. Then repeat until it stops working. Where you have to use keys and passphrases, use simple ones first and then go for the complex ones if they work ok.

Some drives will even round up when burning DVD-R. ImgBurn itself is working fine though and doing exactly what it should be doing.

There's already a warning for when users build UDF 2.50+ *data* discs. I didn't feel it was required for people building *BD Video* discs - real BD software players don't need the 3rd party driver. Then of course there are the people that never have any intention of playing the disc on their PC - they have BD hardware players (PS3 etc). MPC HQ can't play BD discs properly (at the moment anyway). You need a proper 'licensed' BD player like PowerDVD, WinDVD, TotalMedia Theatre etc. Nope, no plans for an editor. I don't like editing, I'd always prefer to build a new image from scratch. You can do that easily enough by mounting the ISO in a virtual drive program and then adding the contents of the virtual drive back into Build mode. You can't legally 'make' a proper PS2 DVD. As such, there will never be a guide for it. (plus it's not something I do or know anything about)

Can you provide more info please, at this point I don't really know what you're talking about.

Don't be At least the answer is now here on the forum for others to find

Whilst I do appreciate the time you spent signing up and posting this bug report, if you were in my position, would you be able to do anything with the info you've provided? Probably not. Where's the 'proof' as it were? Where's the log from the burn and read operations? Where's the disc info from the burnt disc? It's very likely this is perfectly normal. Drives sometimes round up the number of sectors that get burnt to the nearest multiple of 16 - so if you had an image of 15, the drive would make the up to 16. This is particularly true when using DVD+ (plus) format media.

Messageboxes don't allow that level of control. You could use Advanced input mode if you want to see exactly what's being burnt. Anyway, I assume you've either turned off DVD Video filtering now or will just remember that your non DVD Video content doesn't in fact belong in the JACKET_P folder - so you're all sorted.

Sorry, my mistake, I thought I'd made ImgBurn always warn the user when using UDF 2.50+ on an OS that doesn't support it, but it turns out that it only does that when building a Data disc, not a BD Video one as you're doing. You can find more info about 3rd party UDF parsers in the FAQ - post #13 http://forum.imgburn.com/index.php?showtopic=59&view=findpost&p=123963 Rebooting normally works if the OS doesn't detect changes made to the disc after it has been burnt - but that's not the issue here. Your issue is that XP can't read UDF 2.50. If you'd tried to play the disc with a proper BD player - i.e. PowerDVD, WinDVD - it should have worked fine. You just can't browse the disc in explorer.

Ok so that looks fine. The program knows you're building a BD Video disc. Are you not able to browse the contents of the burnt disc in Explorer/My computer? (and you've tried rebooting?) It looks like you've got a 3rd party UDF 2.50 driver installed - normally, Windows XP cannot parse UDF 2.50+. Support for it was first added in Vista. That's correct yeah? Yes, the program just saves whatever is in the log window to the log file when it's closed down. Real-time logging only goes to the log window, not the log file.

It doesn't matter what media you're burning to, BD Video content would still be UDF 2.50. The 'MODE1' thing doesn't matter as it couldn't ever be anything other than MODE1 on DVD/BD. The log you posted starts with 'W 15:08:15 Waiting for buffers to recover... (LBA: 709984)' which of course isn't actually the first line. Maybe you cleared the window or something before saving it or exiting the program. Anyway, the important bit (everything that was above what's there now) is now missing.

Removing the controller entries is easy, you select it, click uninstall and then reboot. That's all there is to it. Any admin account should have been fine. Permissions are usually set on groups (i.e. 'Administrators') rather than users (i.e. 'Administrator').

You missed loads of the log out - and it's the important stuff! Yes, MODE 1/2048 and UDF 2.50 are fine (normal) for BD Video discs.

This isn't something ImgBurn / we can help you with, sorry.

ImgBurn does nothing special when it reads or writes. It just reads the data from every sector on the disc to an image file and then writes that data back to the same sectors on a new disc. If that's enough for your needs then so be it. We don't get into why something will or won't play back on certain devices.

If the entire contents of the BDMV folder will fit on a DVD, it should be working just fine. Can you post the log from where you burnt it to disc?

It isn't really deleting anything though is it, it's filtering based on your options. Dialog boxes get annoying (I already have way too many), hence why the messages are just logged into the log window - which of course should be open all the time.

My version does actually mention (in the log window) the files filtered out from DVD Video folders - it's probably new in what will be 2.5.6.0 though (I honestly can't remember off hand). I just checked back to v2.4.0.0 and the jacket_p filtering is definitely in it. You can turn off DVD Video filtering (hence why I said 'By default') but that then applies to the other 2 folders too and I wouldn't recommend it.

Maybe try cleaning your drive with a cleaning disc. After that you'd have to try a different spindle of discs (to rule them out as being the problem) - Stick with Verbatim MKM-001-00 or MKM-003-00 though. If they also fail, it might be time for a new drive. Get a 'normal' size external one (or 'normal' size internal one in a USB enclosure to give you more choice) because all slimline ones are pretty rubbish.