LIGHTNING UK!

For those manual closes, it's supposed to freeze. The commands aren't issued in a thread and so it ties up the GUI one - meaning the GUI won't respond. Just leave it! The program will 'un-freeze' control when the drive returns control to it - i.e. when it has finished doing what it was asked to do. I already answered that in my previous post. See below ImgBurn didn't see a failure on the sync cache/finalisation commands as an overall 'failure'. That's why it still says it was successful - this has been changed for the next release of ImgBurn. As I said before, I VERY much doubt your DVD Decrypter burns are any different to the ImgBurn ones. ImgBurn is just telling you it failed where DVD Decrypter just plays dumb and the error goes unnoticed. Do your ImgBurn burns NOT verify or something? Ignore that finalisation failed, just try it and see if it is actually working. Again, if you look at the info panel on the right within ImgBurn, what does it say for a DL disc you've just burnt that wouldn't finalise? What does that same info panel say on a disc done with DVD Dec? Changing the subject.... As shamus said, ignore the warning on the NEC page and just update the firmware.

You just downloaded and tried to run this file yeah? ftp://ftp.hp.com/pub/softlib/software5/CO...8-1/sp26626.exe

Nope, you're right dontasciime. ImgBurn is for single track / session data images. The 'nrg' registry shell extension setting has nothing to do with ImgBurn's ability to burn a file. Those options are just so you can right click a file and the context menu has 'Burn using ImgBurn' available as an option. You can always browse to the files manually and burn them - even if the registry shell extensions are not enabled.

They might play find in your standalone but if you play them in your PC and the playing software attempts to read that sector, it to will pause and eventually fail. It might be able to skip over them though because a few sectors here and there is nothing when you talking about millions. Sounds to me as if you're just getting duff burns from the drive. Do you have access to another drive anywhere to see if it IS just a duff burn or if the drive is having trouble reading for no reason?

The commands issued as part of the burn are the same ones that get issued when you do it manually. If you've already hit 'Retry' a few times during the burn, chances are the manual ones will fail too. However, the drive might decide to behave itself a little better if you eject the disc, leave it a while and then try again. Basically, if the disc shows up as 'Status: Complete' in the info panel on the right, you've probably got nothing to worry about because it HAS managed to close/finalise it enough. No you can't do a test on DVD+R DL media, test mode is only supported on -R media (this is NOT an ImgBurn limitation, it's just how the +R and -R specs work). DVD-R format media doesn't need a specific 'finalise disc' command to be sent, it's done automatically when you issue the 'Synchronise Cache' command. Only +R media needs track / session / disc closing commands to be issued. One thing I will point out though is that you're still using the v1.01 firmware. v1.04 is available now and will no doubt improve media compatibility. http://forum.rpc1.org/dl_firmware.php?download_id=2109 Firmware updates are the first thing you should check for when you're having problems.

Are you sure it's not just the power saving settings? Take a look at it in control panel. Unless of course you mean it's turning off the second you start burning?

That is your drive. It's an LG 4166B. Now we know your machine is indeed an HP one, go ahead and update the firmware on the drive using the link spinningwheel provided.

I honestly can't say. Nero might not look for errors during those functions either. I've never been in the situation where my burns consistently fail and I can check such things. You can always finalise manually so don't worry about it too much. ImgBurn also saves the logs by default now so you may already have them saved somewhere. Normally you just click 'Help' -> 'ImgBurn logs'.

I assume you're pressing one of the buttons under the drive selection drop down box? Ignore those and just put the tray back in manually. If I'm right in thinking this is a laptop drive, the trays are always manual ones anyway - so of course the 'Load' button would fail.

The graphics are way better when you're running it via HD. I have mine on 720p, not too struck on the higher res (1080 or whatever it is). Mine's running on a 24" widescreen monitor. I don't have a HD TV to test it on So a pc monitor is fine, just hook the xbox up to a nearby hifi or something - unless you already have kick arse speakers on your pc (I juse use my hifi).

Yes quite. These values are nothing to do with ImgBurn recognising anything, it's to do with your drive recognising it. ImgBurn queries the drive to get the current 'Formatted' status (amongst other things) and displays the result in the info window on the right. If it says 'Formatted: No', the drives initialisation sequence (i.e. done internally by the firmware) has determined the disc hasn't ever been formatted. Where the 'prefer properly formatted DVD+RW' option comes in is where ImgBurn will attempt to perform a full format on any media where the drive does not report 'Formatted: Yes'. If you uncheck that option it will only perform a full format if it says 'Formatted: No' - i.e. you just took the shrink wrap off the disc and tried to burn it. When it just says 'No' (i.e. not 'No (Started)' or 'No (In Progress)') you HAVE to format the media. There are no two ways about it. Any attempt at sending a 'Write' command will just fail with an error saying the media isn't formatted. Where I (within ImgBurn) would issue that 'Format' command and wait for it to totally finish, other programs might just issue it and then start writing data straight away. That's why those programs never leave the disc in a 'Formatted: Yes' state, but ImgBurn does. Each to their own. Yes, I can plug leads into a monitor too... doesn't mean I know what it's doing internally. As I said, ask the drive manufacturers.

DVD Decrypter doesn't see / capture errors during the 'sync cache' or 'closing track / session / disc' stages. That feature is new to ImgBurn. All those processes are performed by the drive, the software simply initiates them - and it must have done that ok or you'd never get to the stage where it fails. So basically I think the problem has always been there, you've just never been told about it - and hence assumed everything was ok.

Sorry, I updated the forum software yesterday and it added a few new features - one of which meant you couldn't see (or 'download' as it calls it) the files. I've just corrected the permissions and you should now be able to view them in the way we'd intended.

All burns in ImgBurn use the exact same burning code. To say build mode didn't work but then write mode is fine, it's just total fluke. The errors come from the drive (as mentioned earlier), not the program. The program just displays them. Nero might be using the 'Incremental' write type rather than DAO/SAO. If your burner prefers that, change the 'Write Type' option in ImgBurn's settings.

VCD/SVCD images cannot be burnt with ImgBurn. The images are made up of multiple tracks and ImgBurn doesn't support that. You would have probably had a bin/cue setup, you need to burn the cue with a program that supports bin/cue files properly - i.e. Nero, Cdrwin etc.

You can resume them, yes. I don't bother though. Less chance of things going wrong if you just start from scratch - I'm also not really sure it would save much time, never tried it! The 'started' one is the status of limbo that most apps seem to leave the disc in. A quick erase is not like a format. Formatting has an actual command associated with it. A quick erase (for DVD+RW anyway) is really down to the program. I just overwrite the first few hundred sectors with zeroes via the normal 'write' command - as would be used when burning normal data to the disc. The 'format' is a command issued to the drive. The drive then goes off and does whatever the programmers of the firmware told it to do. Writing to sectors (i.e. via quick erase) has no effect on the 'formatted' status - that can only be changed via the 'format' command.

Self deprecating humour or not, I was serious in that if you (as a self proclaimed newbie) can tell us which bits were tricky to understand, we'd gladly try and improve them. Yes the prompts by your firewall are part of the code used to check for updates. The microsoft one (along with yahoo and google) are there to determine if there's a connection to the internet available. The zen one is there because that's where the update info file lives. As I said, if you don't want it checking for updates, turn the feature off in the settings. If you turn it off, you'll notice your firewall then stops prompting (unless you've already just allowed it to access it of course). I don't really follow you on the whole start menu thing. When you install the application it makes a folder called 'ImgBurn' within the 'Start' -> 'All Programs' listing. Within that 'ImgBurn' folder there will be a link to ImgBurn.exe (called ImgBurn), a link to the readme.txt file and a link to the uninstaller program. If your folder has magically deleted itself, just reinstall ImgBurn and it'll make it again. There are options within the installer to make desktop / quick launch icons. No need to do it yourself, just click the appropriate checkbox in the installer (they're ticked by default anyway on a totally fresh install).

lol they're the exact states a format can be in. Formatted: No Formatted: No (Started) Formatted: No (In Progress) Formatted: Yes No = It hasn't been done at all - the disc is brand spanking new. No (Started) = An application started doing it but then terminated the format before it actually finished. No (In Progress) = This obviously means it's formatting at that precise moment. Yes = Erm... you need me to explain this?!

You should start verifying your discs as part of the 'write' process. To do that, just ensure the 'Verify' option is ticked where you select the 'Destination' drive. That'll at least prove your PC can read the disc back ok. Nothing looks out of place though so perhaps your player just doesn't like the media very much. Trouble is, you don't get any better than Verbatim! Maybe the 2.4x rated discs would work better for you - rather than the 8x ones you have now. They use the MKM-002-00 dye rather than MKM-003-00

No, it's NOT peculiar, read my response above.

Not with ImgBurn, no. This procedure isn't anything to do with ImgBurn or burning in general really! Search Google and maybe you'll find your answers.

You experienced that 'last resort' case for yourself. It told you that it couldn't find a decent place for the layer break position and that the image wasn't right for burning. That was your first and last warning! When you tell it you want to continue anyway, it splits the image in half and burns it.

ImgBurn WILL show the list even if there is just one option. It never used to, but now a user can do things like toggling the 'seamless' flag, it's needed. I wouldn't get into cell splitting within ImgBurn, that's more or an authoring thing. ImgBurn is all about the burning side of things. If you use ImgBurn's 'Build' mode to create an image/disc from the VIDEO_TS files, you'll get far more choices than if it's just given an ISO.

If you tell us exactly what you can't follow in the guides, we'll improve them. When you install the program you're asked if you want the program to connect to the internet when it starts and check for updates. You clicked 'yes' (or it was already configured in the registry) and so it does exactly that. Once installed, if you change your mind and don't want it to check for updates, turn that option off in the settings. It's on the 'Events' tab. No idea. It'll be in a folder called 'ImgBurn'. Try sorting your start menu program folders by name (right click one of them and select 'sort by name') and then look for it. Optionally, the shortcut will also be on your desktop.

Yes it offers a list of all that it finds. v2.1.0.0 (current version) hasn't got a preview, v2.2.0.0 does and will be released this month.