LIGHTNING UK!

Yeah, of course you can!

Most errors (99%) are due to drive/firmware/media issues. Good discs give good / reliable burns. Bad discs give many coasters.

Use a proper download manager to download the file. Something like 'Reget'. That's what I used and my file loads up fine. The image is 2,749,628,416 bytes in size. vista_5728.16387.060917-1430_x86fre_client-lrmcfre_en_dvd.iso

'Bad' would be if the layer break was at some stupid LBA or it tried to point to files that don't exist. Neither of those are problems you're experiencing (you'd have got errors when you loaded the mds if there was a problem with the files).

Like I said before, download DAEMON Tools, mount the MDS in it as a virtual drive and install it from there. DAEMON Tools is free. If you want to burn to a real disc, put imgburn in 'Write' mode and browse for/open the mds file. Put a blank in your burner and hit the burn button. Don't try to over complicate things, it's pretty basic stuff.

Sorry, you're not really making much sense! If you've got cds, clearly you don't need to put them on cd first - so you're probably confusing yourself (and us). If you have an ISO file or CUE/BIN combo, do as mentioned earlier and mount them in DAEMON Tools. Search Google and you can find info on just about anything - helps to know / understand what it is exactly that you're after though.

You can't ever drag and drop from a browse window. Just use a normal explorer window. The folder dialog box just doesn't support selecting multiple folder. The only way around it is to make my own....and that's not something I'm about to do any time soon. No it's not assembler, it's just normal C++ (from Borland Builder).

You mean you want the files out of the image without having to burn it first? Mount it in DAEMON Tools as a virtual drive.

If the I/O stuff hangs, there's little chance of your system recovering. A reboot if normally the only way to reset the drive. Like most software, ImgBurn waits for these I/O calls to complete. If they don't, it gives the impression of it hanging. If the I/O call ever did return (be it with an error or successfully), ImgBurn would spring back into life. If your machine hangs a lot you should check things like drivers / firmware / bios / filter drivers / cables / power supply etc. Something must be causing the issues. If the ImgBurn process can be terminated, load it again, and if the bus hasn't hung, just click the eject button within the software. It will unlock + eject the tray.

Drag and drop is already supported. The select folder dialog box doesn't support multiple folders. The select file dialog box DOES support multiple files.

Does it say failed to read the file? I see no log entry for a failed write, so I guess it must be a read issue (and perhaps... well, obviously.... I don't log those). I would say that's a problem with your hdd. Run chkdsk on it.

Is that the only burner you have? It probably dates back way before the MMC specs were really taken on by drive - and ImgBurn follows the MMC specs. btw, you know that discovery mode just writes 'nothing' (lots of zeroes) to a disc yeah? If you want to burn something you need 'Write' or 'Build' modes.

The program burnt + verified the disc just fine - so basically, the burn is ok so far as reading it in your PC goes. That doesn't look like a dvd video disc, it's using the wrong file systems and the size of it looks more like a vcd/svcd. If you're randomly burning images / files etc without knowing what you're doing, it might be a good idea to search Google and learn some stuff before wasting any more disc.

That would be fine if there was some mention of it. I can't find any such statement/clue in their cdimage program.

The only way file size is related to this issue is that you're burning nearer to the outer edge of the disc - and therefore more likely to get errors. If you really get that same 'Illegal Mode For This Track' on every disc you try (AND they're different dye types), your drive has probably had it.

I knew what you meant the first time! I'm just saying that perhaps Microsoft made the decision that 32 characters is more than enough to display for the volume label of a disc - even though a filesystem on the disc may actually support more than that. Filter drivers should only change the low level stuff (i.e. when reading a given sector). If that's the case, all programs would read the UDF volume label as being 32 chars in length. IsoBuster and DVD Dec can both confirm it's longer than that. Programs that use the normal API calls to get the volume label will all display the one windows does.

I know he didn't ask about media or dye type but I'm just thinking out loud here. One issue I have with this kind of thing is that a user could select the speed they want and THEN insert the disc. The MRU speed for a given media (on whatever level it's implemented at) would then overwrite their selection and there's no way around that - other than to remove the option of setting write speed until the disc is in the drive. It's almost never ending though because some people may like to burn different media at different speeds depending on the drive they're using. It could also cause issues with the queue, which of course just configures that write speed box on the main page. This suggestion is actually far from new, and as you've seen, I've not done anything about it so far. Normally it's about different speeds for CD / DVD though, or about having the write speed box limit to the speeds supported by the drive on that media.

The same could be said for all types of media - infact, every dye type!

It only checks the 'best' filesystem out of the ones you've selected. So it check if udf is enabled first, and if it is, it looks at udf volume label - then quits. After that, it then checks if joliet is enabled, and if it is, it looks at joliet volume label then quits. Finally, it looks at iso9660 volume label.

You may have been better off using just UDF rather than breaking all the ISO9660 restrictions.

Probably because it considers it too long to display!

I'd hope the ElbyCDIO interface wasn't making up the error! So no, it shouldn't make a difference. Although I always recommend people use SPTI, Mr Bitey might be using Elby because he is running under a 'normal' (non admin) account - where SPTI then wouldn't work.

nope, not a chance. The data comes from the ISO regardless. All the MDS provides is the layer break position - which has already been confirmed as containing the same address the program finds by parsing the IFO files when he just loaded the ISO.

The recognising of discs is down to the drive. Keep an eye on what it says in the statusbar and in the info panel on the right of the main screen, it often gives clues as to what's going on. If the drive doesn't initialise a disc properly the 'Write' button never gets enabled and so the queue cannot progress.

ImgBurn is a burning tool. If your image is too big to fit on a single layer disc (and don't want to use double layer) then you still need to make it smaller. You do not / can not use ImgBurn for that - and as such it's beyond the scope of this forum, sorry.