LIGHTNING UK!

If you build on the fly, the program knows the media you're building for and will tell you when you try to actually write the disc that it won't fit. When you're not building on the fly, no there's no way to tell it what media you're aiming for - the options for media type are purely there for the layerbreak stuff - they're not used for anything else. All you can do is hit 'calculate' and work from what it tells you. If you forget to calculate, it's tough luck I'm afraid!

What if you only add 1 file into Build mode for buring? Does it still takes ages to parse the filesystem during a verify? How does that time change as you add more files? Oh and is the EXACT text in the status bar 'Parsing File System' or does it say something in addition to that? I'd actually made 2.3.2.0 change the status a bit more depending on what it was doing. The exact message 'Parsing File System' shouldn't actually be visible for all that long. Just to be clear, this is with you burning + verifying an ISO file that you've already built yeah? Not one you're building on-the-fly direct to a disc?

Sorry, no, ImgBurn can't do it. Mount the image in Daemon Tools and then build a new image based on it, with the addition of the 2 files you want to add. Of you could try UltraISO or whatever the other ones is. MagicISO I think. Personally I'd rather build a new one than edit one.

What made the MDS file and yet gave you an image created by Nero? There's nothing to say the LB in that image is correct. Go back to the raw files (IFO, BUP, VOB etc) and have ImgBurn create it's own layer break position and then ISO file by using Build mode. Of course you'll need to be using Verbatims for it to be a fair test.

Ok, well there appear to be a readable filesystem on the disc. Can't explorer read it?

If you want files off the disc, just copy them in explorer!

Command Line support only. Read the 'ReadMe.txt' file that's installed alongside the program exe.

I doubt it too, you'll just have to wait and see what LUK says. Oh wait, I am LUK. No then.

Being a Mode 1 file (which I suspect this is), the actual user data is only 2048 bytes in that 2352 byte sector. All the rest is error correction stuff etc. Drives tend to perform sanity checks on that data sent to them and will correct it if need be. It's just something they do. Read the MMC specs at www.t10.org if you really want to know about the L-EC area and what it contains.

It's just there because of the type of control it is. They're OS default menus, not my own.

The Queue only applies to write mode, hence it's only visible in write mode. That's the way it is and the way it'll stay I'm afraid. That key isn't one I put there (or try to remove), it's just something the OS decided to add. I'll add it to the uninstaller code manually now though. Thanks

Nope, the drive would just ignore the 1x request and use the closest to it that it DOES support. No point in trying it again. Yes, verbatims are the ONLY way to go! Try to get the MKM-001-00 version (2.4x) rather than the MKM-003-00 (8x) ones. You'll probably have more luck with them because they're THE standard in DL discs.

Hmm yes it's kinda a bug. The file name is only generated automatically if the function gets a file path. The file path is empty if 'None' is selected. It's the root of the most empty drive if 'Generated Automatically' is selected. It's the MRU path if 'Most Recently Used' is selected. and finally, it's the custom path if 'Custom' is selected. That in itself works fine. The problem here is that the MRU variable is never assigned / updated with the MRU path! It's loaded once from the settings when the program starts and that's it. So basically, it'll always be empty (because it's empty on a clean install). The only way to use that variable as it is, is to edit the registry - but then of course because it's never updated, you might aswell just use 'Custom'. So sorry, you'll have to live with 'Generated Automatically' for now. It's fixed for the next version - which won't be out for a while.

Does ImgBurn not see anything on the disc? If you put it in when you're in 'Read' mode, is it able to parse the filesystem and show you the volume label etc of the disc? Copy + Paste the info from the window on the right of ImgBurn.

Well you can see the problem, the drive won't read anything from the second layer and just times out. That's not the program timing out, that's the actual drive timing out. Until you've tried some other DL discs (Verbatims), you can possibly say 'It's not the media'. Just because your last drive was ok with it, it doesn't mean your new one will be - clearly it's not. Speak to Dell and ask why the drive can't read from the 2nd layer on that media. Maybe they'll fix the firmware?! btw, attempting 1x with that drive/media combo isn't going to do anything. The drive / program clearly states that only 2.4x is supported/possible.

Arrgh, I'm a moron, sorry! Bug fixed.

Tools -> Settings -> General Tab -> Shell Extensions -> DVD.

Switching to ASPI doesn't solve the exclusive locking thing, the feature just isn't available under ASPI, hence it's never attempted. It you think about it that way, just turn off the exclusive locking option in the settings - of course that's not something I actually recommend that you do, but then nor is using ASPI! FYI, I found the root of the problem, the Nero ASPI doesn't always seem to like memory allocated using 'VirtualAlloc'. Without changing anything else, I can switch the call to use 'malloc' instead and it works fine. Go figure! I think only Nero could explain that one - and of course they wouldn't because the dll isn't meant for use in other burning apps.

Ah, perhaps it's related to other drivers etc on the pc. If I run ImgBurn in a VMWare session on the pc that doesn't work normally, it works fine.

Nero ASPI doesn't like working with anything other than Nero - well, sometimes it does, sometimes it doesn't. Even low level driver sniffing shows that it does weird things. Just stick to SPTI. If you can't do that, try the Adaptec ASPI or FrogASPI (the latter is an SPTI wrapper anyway). Basically the 'Read' command is just having it's buffer filled with complete rubbish - hence ImgBurn isn't able to parse the filesystem. EDIT: The one I tested was 2.0.1.74. Perhaps the .68 version (as used above) is ok. Perhaps they're actually doing it on purpose to stop it being used with other Apps?

You just burnt 608 sectors to a disc - I can assure you that it should be a LOT bigger than that if you'd done it properly. Oh and update ImgBurn.

If it still says 2.3.0.0, you didn't install it properly. Your drive might not like the maxell media you're using. If there aren't any firmware updates available, you've no choice but to buy some different discs. I recommend Verbatim (I prefer the DVD+R ones) or Taiyo Yuden.

Erm.. maybe. For now, if you really can't cope with using the mouse, open the File menu (Alt + F) and press 'R' for Read.

It's a little odd because pressing refresh just stops and starts the 'autoinsert' polling thread. But that runs anyway and is what detects a disc has been inserted - and that's obviously working ok. Any chance of 3 screenshots of the main ImgBurn window? 1. Of the first disc in the drive (showing correct volume label). eject disc -> insert new one... 2. Of the second disc in the drive (showing incorrect volume label). press Refresh / F5... 3. Of the second disc in the drive (showing correct volume label).

Sorry, there's no such thing as a 'language file' for ImgBurn that I can send you. All the text is hardcoded right now. That may change one day, but not any time soon I'm afraid.