LIGHTNING UK!

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.

Just double click the destination field and it'll let you rename it directly.

Yes, 'Continue' is the same as 'Ignore' - meaning 'Ah, don't worry about it, just burn away!'. That's fine until something else tries to access the drive or sends the wrong command and you end up with a nice coaster. You have to use Process Explorer to find out what's preventing ImgBurn from getting exclusive access over the drive - it's all detailed in the FAQ.

The good news is it's auto booktyping to DVDROM anyway. The bad news is you're using RITEK DL discs and everyone knows they're awful. Use Verbatims instead. Even then, I don't know if your drive will burn them any faster than 2.4x - that fact that it's the year 2007 doesn't really come into it! You also need to update to ImgBurn 2.3.2.0.

So you're saying that when you put a disc in, it automatically generates the destination file name, then you eject it, put in a different one and the name stays the same? When you eject the disc between name changes, does the program change the 'destination' field back to saying 'Please select a file...' ? I've just tested it here (with default settings) and it's working ok for me.

Quite right, too chewy! The program doesn't (shouldn't) need updating for burning to any drive. That's the whole point of a 'standard'. Hardware follows it + software follows it = both play nicely together. As for booktype / advanced settings, I only add those if it's worth it and possible for me to work out the commands. Of course for that to ever happen, I need to buy the drive and I'm really not fussed about buying an Asus one.

I have no control over the server. If the security stuff running on the server doesn't like something you're typing in, you just have to edit your post. We're all in exactly the same boat here. I've not had a 403 message in aaaaaaages now and clearly I do post quite often and I've posted a lot of normal logs.

It's not the write mode that's the problem, it's the general way ImgBurn works. Everything is/must be 1 track. So if you only wanted 1 track on your audio disc, that would be fine. Clearly that's not going to cut it in the real world though! lol I need to change the entire program so it can write multiple tracks by making it more aware of the disc layout. Multisession isn't needed for a basic Audio CD, but I see little point in making it work with multiple tracks but then not going the whole way to make it cope with multiple sessions too.