LIGHTNING UK!

Your drive reported a tracking servo failure... so I'm guessing that's what happened. (search for that on google if you're bored). It was just a bad disc. Chuck it in the bin and put another one in the tray. Always ensure you're running the latest firmware for your drive too.

Not really, no. That would mean dynamically resizing stuff.... very pointless in my opinion! It does no harm by being there so it's really a case of leave it be or remove it and tidy up where there will now be a few blank areas within the dialog window.

No, what I'm saying is that an ISO/IMG file is a collection of files in a ready to burn format. i.e. no processing has to be done. You read a chunk of data from the ISO/IMG file and write it to the disc. If a sector holds 2048 bytes of data, you read that from the ISO/IMG burn and burn it to sector 1 on the disc. (Discs (including hard drives) are made up of a bunch of sectors). Then you read the next 2048 bytes and burn that to sector 2. etc etc. With files, you have to first calculate where each and every file will be positioned (sector number wise), and how many sectors they will take up (this depends on the size of the file of course). You then need to build a table (i.e. FAT - File Allocation Table, NTFS - NT File System, ISO, Joliet, UDF - These are all different file systems), so programs/the operating system can perform a lookup on a certain file and know which sector it's located at. That table has to be recorded onto the disc too. Like I said, doing that is not trivial and so at the moment, ImgBurn can't do it. It relies on another program for that and then just burns that image in a simple sector by sector format. When other programs give the impression of burning 'files', they're really just creating an ISO/IMG file on-the-fly as data is always burnt in sectors, starting at 1 and ending at X.

Me too... I'm not even sure 74 mins ones still exist! In this day and age, it is quite possible I could remove it - and have thought about doing so several times. The trouble is, if I remove it, I'm bound to upset someone who DOES want/use it. I just can't win!

Well I never let anything damaging slip past.... just the odd cosmetic issue

Like I said, it's mainly for CD! If you didn't do much CD burning, it'll probably make less sense to you. Sometimes it's just easier to read 73:59:00 for an image size and know it's gonna fit on a 74 min cd rather than needing an 80min one. I don't think of CDs in terms of MB capacity, it's Time capacity for me - being old skool and all that

an img file is like an iso file... and hopefully you know the concept of an ISO?! It's a complete image of the disc. For an ISO, it's just like you read sector 1, and write it to a file. Then you read sector 2 and append it to that same ISO file. The 'file' content of the disc is of NO importance. You're talking about turning files into iso/img files and then durning burning to a cd/dvd turning them back to file...that's not how it works at all, it just looks that way. Burning a collection of files means you have to create the filesystem (i.e. FAT/FAT32/NTFS/ISO/Joliet/UDF etc) on the fly and add the files in the correct places. Seeing as you even asked this question, perhaps that is a little over your head - much in the same way that ACTUAL filesystem creation (in programming terms) is a little over mine! - well, it's non trivial at least

We're not talking about video time here, it's disc time. 25 / 30 FPS for video is obviously very different! Just want to be sure I've made myself clear so as not to confuse anyone!

It's automatic.

It actually shouldn't do that. It should say you've not yet had the correct number of successful copies and ask if you wish to retry for that remaining number. Oh... it only does it if you originally wanted more than 1 copy though. I've now tweaked it so that if there are other images in the queue after the 'failed' one (and the failed one was only queued up with 1 copy in mind), it'll prompt to repeat that image. If there aren't any other queued images, it'll just call it quits and exit how it normally would if you were just burning 1 file. At the moment you can of course select the failed/burnt images and right click + 'queue again'. I don't remember ever having a failure so that part of code never really got any testing! lol

Most programs will auto erase / format media before burning anyway - hence why adding an optional button is pretty pointless. The main reason for me to say 'No' though, is that it would mess up my GUI!

FF = Frames. It comes from the old 'CD' days when 640mb was 74 mins, 7800mb was 80 mins etc. 75 frames = 1 second. 60 seconds = 1 minute.

No

You knew how to use DVD Decrypter's 'ISO Write' feature (mode) - yeah? So ImgBurn's 'Write' feature (mode) is identical to that. It just has some extra bits bolted onto it - like the queueing system. You're confusing everyone (including myself!) by saying ImgBurn has no front end. No front end would make it a DOS application - which clearly it's not! What you really mean is that it doesn't have the ability to READ a disc to an Image file. In saying that, yes you are correct. The name kinda gives away what its primary purpose in life is Look in the Guides forum, I'm sure you can read / follow the VERY short guide I put together, and then you have Corn's which details how to use the Queue. To check the disc has burnt correctly, you just need to have the 'Verify' box ticked. You can Ignore 'Discovery' mode, it's purely for testing media / drive compatibility - with the aim of then scanning the burnt disc in something like DVDInfoPro. OH BTW, the Queue system can be set up to burn multiple copies of the same image. Just follow Corn's guide

Ok, in that case I would say your drive doesn't support those discs properly. A firmware update max fix that - if not, get some verbatim DVD+RW discs.

Click Tools -> Drive -> Erase -> Full. Your drive isn't reporting the media as not being formatted and so the program isn't automatically taking care of things. Showing the full log may have helped - I don't remember the format operation being something that is optional - so I'm not sure how you got it to burn without first doing so.

No, it'll use whatever is already active - i.e. whatever you select in qsuite.

The program doesn't ask anything about DMA! God knows where you got that from!

Oh... according to the filesystem, the image was originally created using Nero. I just assumed you were therefore burning NRG files that you'd created an MDS for.

Sorry, I hope that didn't come across as being rude. It just really seems like I'd be duplicating functionality if I was to implement such a screen. Either way round, you'd have a list of all images in the folder and then be unchecking / deleting the ones you don't want.

Not everyone knows all of the tools and as you were burning with ImgBurn anyway, you need not have mentioned DVD-RB at all. It has nothing to do with the question you asked. No, getting write retries is not 'normal'. However, if the retry worked, everything should be ok. Of course, you can use 'Verify' to double check that.

And surely to have a window where the user can select which images to burn, it is exactly the same as the 'Queue' window you've already got?! Just delete the ones you dont want from within that window.

I guess so, I've never looked it it myself, I just know it's possible somehow!

There is a 'display name' option in this version of the forum software. You should be able to rename yourself via that.

Another good one can be found at www.sysinternals.com One of the best sites on the internet for small FUNCTIONAL admin/advanced user type tools.