LIGHTNING UK!

If they're ISO's, multisession wouldn't help anyway. Extract the contents of the ISOs, then make another one from scratch with the contents combined.

There's a 1.37 version available. http://forum.rpc1.org/dl_firmware.php?download_id=1781 If that still doesn't work then you'll have to find some different discs. Try the Verbatim DVD+R ones instead of the DVD-R ones. You may as well just get the 8x ones as that's all your drive can handle.

Change the 'Insert Next Disc - Auto OK' slider in the settings to a smaller value?

Yes it's fixed in 2.1.0.0 You're given the 'seamless' option in the box where you select the layer break.

If you have the appropriate drive, do a disc quality / PIPO scan of the said discs. (Using DVDInfoPro or CD Speed) Maybe your drive isn't burning to them very well. Some being ok, some being slighlty over the edge so that it causes skipping.

None of them are probably layerbreak points - there will be only 1 real one. The 'layer break' checkbox in PgcEdit is just its 'friendly' way of showing the state of the SPLIP (Seamless Playback Linked In PCI) flag. If you go by the layerbreak box in ImgBurn, just look at the stars to see where's a good place for it. If you have lots of them and can't decide, post a screenshot and we'll pick!

I'm sure you realise this now, but it's not WHERE you post that's the problem, it's WHAT you post.

A full log would have been nice, we can't tell much from little snippets like that. Chances are, you're using cheapo discs that your drive doesn't burn to very well - or the dye on the disc was just faulty. Check for a firmware update for your drive and ensure you use decent Verbatim (MCC dye) or Taiyo Yuden discs.

Most of this has been answered in your other thread. Please don't duplicate stuff. Most layer break cells are marked as SPLIP = No by default, that's why it's often better to just look for cells marked as such when you're offered a list. If your player supports seamless layer breaks (and yes, you test that by playing a disc with a seamless layer break so that it has to actually change layers), you're fine to enable the 'Seamless' checkbox. If you want it seamless, you must enable the seamless option so the cell flag gets set so SPLIP = Yes (and not No!).

Erm....yes there is, it's the 'Seamless' checkbox on the 'Create Layer Break Position' window! If you then use the MDS file to burn, the whole 'seamless' thing doesn't even come into the equation. The seamless flag is something in the IFO files, the layer break physical location (as taken from the MDS) is something on the media. So loading the MDS will mean ImgBurn doesn't touch the IFO files from how you've already configured them. If you want to find the layerbreak position (physical one) on an original, put the disc in the drive and look at the 'Layer Information' down the bottom of the info panel in ImgBurn.

You have to watch what you type in or you'll trigger the server security apps - and they're out of my control. Just dont add too many dashes, dots etc. Certain words/combinations are not allowed.

Go into the settings and on the 'Events' tab, check the 'save the log' and 'append existing' options. Then you'll start getting stuff in your logs folder. Please be careful where you use the word 'Crashed'. An I/O error is nothing of the sort, it's where your drive errors out and ImgBurn then simply displays that error. I/O Error are, 99% of the time, related to a bad drive/firmware/media combo. If you can't update your drives firmware, buy some different discs. We recommend Verbatim (MCC dye) and Taiyo Yuden. If you change discs and they still fail, your drive has developed a fault.

So sorry, what's it doing.... not shutting down the computer and instead going into standby mode?

How very very strange! I wonder what they're hooking / disabling that kills my tooltips Hopefully they'll sort it eventually.

Actually, it's even easier than that. The 'Layer Information' is in REAL sectors, not those offset by the 'First Physical Sector of Data Area'. So the LB address (or rather, first LBA on L1) is just 1,814,608.

Xeron, No you have offended me in the slightest! Sorry if you misread my post and I offended you, it was not intentional. I was talking about ZoneAlarm... and that if it's blocking Tooltips and things, then the 'feature' that's doing it is pretty crappy. Tooltips are not part of my code, they're handled by Borland. I merely associate a string with the control, it handles the rest.

lol what a crappy pointless thing to add in the first place - well, if it really is that causing the tooltips to break. I mean, that's pretty core OS functionality - right?!

One thing I will say for Firefox, the spelling checker with MS Word style underline is the bollocks! Why on earth didn't MS copy that idea in IE7.... crazy people!

Ok, this is the important bit... All attempts to send the 'SET STREAMING' (or 'Set Write Speed' to you and I ;-) ) command are failing with that 'Logical Unit Communication Time-Out' error. I've no idea why they're failing, perhaps something weird is going on with your drivers. As the drive is showing up as scsi, I guess the drive must either be on a 3rd party ide controller or you've got some weird drivers on for your motherboard ide channels.

Sorry, I don't really know what to do here. It's always worked for me, on everything from Windows 95 right up to Vista x64. Before the splashscreen comes up, there is no code! That's the first thing I do. So as you're not seeing it, it must be crashing on the general load sequence of DLL's etc and thats not something I have control over - or at least not knowingly. That 'reload' doesn't look 'clean' to me. What if you JUST install XP, ImgBurn and nothing else? Have you run memtest on your pc recently incase it's some form of memory corruption?

I wouldn't class that kind of feature as a 'Tool' and I'm not sure how you can go thinking the 'create dvd mds' file is anything like on the same level as building an iso. Changing the volume label within a given image file, that's a handy tool. Being able to extract layer break info from IFO files in an image, that's a handy tool. Building a DVD Video ISO image is a fully fledged feature. But I didn't want people to JUST think ImgBurn did DVD Video ISO's....quite the opposite in fact. I spent a lot of time ensuring it could be used for anything and everything file/data related. That's why Build mode is as flexible as it is. If I just wanted it to do DVD Video I would indeed just let the user input a single source folder and totally forget about all the other options. What we did (myself and the beta team) was to make Build mode as intelligent as possible. It tries hard to detect if you're attempting to make a dvd video disc and will not let you configure any odd settings that could make bad things happen. So all you need to do is add your folder to the source box and click 'Build'. It's hardly rocket science and corny very kindly put together a good few guides for people to follow - so nobody really has any excuse for getting it wrong.

I don't really want to discuss this matter any further, we've each had our say and we know where we stand.... trouble is, I can't leave it at that! I want to point out that some form of ISO Build mode was always on the cards. I attempted it back when I was still doing DVD Decrypter but kinda gave up because it was overly complex for a tool that wasn't all about burning. Before its implementation, people threw the whole 'make it burn normal files and create ISO's' idea around like it would take 5 minutes. You've no idea how frustrating that is. Anyway.... Of course ImgBurn IS all about burning and so I knew eventually I had to try again. ~13,000 lines of code later, and that's without any real integration into the GUI, it was done. Maybe you don't fully appreciate the amount of time I DO put into this program? Even the most simple of things (to an end user) may actually take a day or two to code. The 'Build' thing took weeks of intensive / solid work. That's why I have to just be blunt about things and say yes I'll do it, or no I won't. I can't keep everyone happy, I am only human after all. ImgBurn is supposed to be 'fun' for me, that's the only reason I do it. If I know I'm not going to be pleased/impressed when I've finished implementing something, or I know it's going to be really boring doing it, I won't bother. Support for DAA images etc is of absolutely no interest to me at all, hence I really have no motivation to do it. Not only that, you try finding the specs for a 'closed' image file format... it's pretty much impossible! As I said before, if a certain image format is a pain for you to burn, don't use it in the first place! I myself have managed to go 27 years without needing to use/burn DAA files so I know it's not a ridiculous thing to say! Reading a disc to an ISO is something we've heard sooooo many times that it just annoys me when people even mention it now. It's not like it's a new suggestion and you'd think the 3000 threads already suggesting it in this forum might be enough for people not to suggest it again - obviously they're not because people still do it. The feature was not forgotten or left out by accident, it was very much left out on purpose. If you look at the last few threads in this forum you'll come across a great suggestion about adding the ability to set the write speed for a given media in a table and have the program use that every time it burns that media. Now THAT is a good suggestion - and actually one we'd touched on briefly in a previous thread. That one has now been implemented and will be ready for the next release. It's a feature that'll be used by the kinds of people that should be using my tool.... people who already know what they're doing.... people like me. ImgBurn was never meant to replace the likes of Nero, and even more so, Nero Express. If people need their hands held whilst burning, they should stick to programs with pretty wizards where they just have to click 'Next' and understand what day of the week it is.

Ok, I really need you to do a little something for me... I think the problem might be coming from your regional settings and how the write speed '2,4x' is being (or rather not being) converted to a floating point value on your pc. If the conversion fails, it defaults to 'Max' you see. I say this because I've just tried my 109 and the conversion goes ok and the correct write speed gets set and is accepted. So anyway, here's what I need you to do. Leave the write speed configured to 2.4x and try burning a DVD+RW rewritable or DVD-R/-RW with 'Test Mode' enabled. Just before you hit the 'Write' button, press the F8 key. It'll then add loads of additional I/O debug code into the log. Once it's started burning, abort the burn, save the log and attach it in your next post. Don't forget to press F8 again after the burn to disable I/O debug mode Many thanks.

Sorry, so it never sets the write speed properly on *any* media? What I mean is that it's odd if it works ok on normal dvd-r / dvd+r but just no on double layer.

The speed is set about 3 times in slightly different ways. If the drive choses to ignore all 3 then I'm afraid there isn't much I can do about it. Does the write speed stuff work ok on normal media? Maybe it's a firmware bug for DVD+R DL media only. It's all the same where ImgBurn is concerned. When I have time I'll dig my 109 out of the cupboard and see if it's erroring out as I try to set the write speed.