LIGHTNING UK!

There's enough error correction on data discs to leave it at max. The only time you'd want to slow it down is for things like CD-DA (Audio) discs (which 2.3.2.0 doesn't support anyway!).

oh right, that would just open another instance of ImgBurn. Sorry, can't help you with that.

You mean specify multiple lists? As in /SRCLIST "C:\List1.txt|C:\List2.txt" ? That's the only way I can do it so if your software can't output like that then I won't bother.

The first error is the real one, not the one you see when the program retries the write operation. So basically, according to the writer, you're getting a rather generic 'Write Error' as it starts on the 2nd layer. Switch to Verbatim.

The times are relevant to that PGC, so it's basically at the very start. It looks to me as though the original LB would be the 2062600 one as it has an entry in PGC 1 which appears to be the big one and SPLIP is already 'false'. The preview window shows you the LB cell (the one selected) and the one before it. Clearly if you select an option that's cell 1 then there's nothing before it - hence no Cell- or Cell+ buttons.

That thread must have been an old one as clearly it's no longer true! The thing is, obviously you can't move files within an ISO, so unless some cells are already aligned correctly, you're stuck. Fair enough, in such cases you wouldn't get the layer break selection screen pop up. If the program can't find any when the files are in an ISO, I would recommend you rebuild the image by extracting the files from the image and then using Build mode. As you've been given options and you're burning an ISO, just select one of them and get on with burning it!

If it's an image, just assume the one with SPLIP = false to be the original LB. So basically that's the one you should select. ImgBurn is better now at finding the LB without the need for the MDS - but it's still not perfect. In your case however, it appears to have worked just fine. There is no way for anyone other than you to know which is the best one for the job, every project is different. Of course not every project will have the same options or colours of stars available so don't think you must follow EXACTLY what was done in the guide. The whole idea of the 'preview' button is so you can look through the choices and make an informed decision.

Ok, I've gone back to /SRCLIST now I know that TC doesn't let you specify the file name that it passes to IB. Everything I said about /SRC taking *.TXT and *.LST (in build mode at least) is now null and void!

No, it's simply a burning tool.

I am THE developer! As the Highlander bloke says, "There can be only one"

You're way ahead of yourself, these things are for the NEXT release, not the current one that dates back to April. Yes, if you only supply 1 CLI parameter the others will be whatever ImgBurn loads from the registry. You should at least add the /MODE and /BUILDMODE (or /OUTPUT) ones though. That's a real pain that TC won't output to anything except *.tmp files. Oh and you'd want the %L one in TC itself.

There's a windows powertool (powertoy) available direct from MS (for free) that does that too.

Physical appearance means nothing on the Internet, it's all about how you come across

Oh well, at least the story had a happy ending - even if you did have to reinstall the entire OS!

I've never heard of that burner personally but your only hope of burning those discs is to get a firmware update that makes the drive support them. To be honest you'd be better off trying to return them.

There's no threshold like that, it's just a case of showing an above average interest in the program (hanging around here for far too long) and me liking you

I really can't remember, sorry. 2.3.2.0 was released in April and a lot has been added / changed since then. If it's not working how I said, it probably wasn't in there.

As it's just the one command that's not working correctly I doubt it's the cable. Still worth swapping it out though I guess. To be honest, I've no idea what could possibly cause that at all. Any chance you could try the drive in another PC? You'll need some sort of system info program to tell you what it's connected to - controller wise. The 'ATAPI' bit isn't normal for XP and a controller running in (S)ATA mode though. It looks more like AHCI. Assuming you have an Intel chipset on that board, try installing the latest Intel Matrix driver (and the chipset one whilst you're at it). http://www.intel.com/support/chipsets/inf/ http://support.intel.com/support/chipsets/imsm/

lol what's wrong with that?! Ok, well they're deffo in there for the next version if not the current one. (It's been so long I've forgotten what I've added and when!) EDIT: Actually there was no support for those bits when creating the log file so I've just added them.

This is for when you're in Build mode I assume? I'm pretty sure it's just [DATE], [TIME], [DATETIME] !

What are you after exactly? I recall there being one for the date / time but that's about it.

The first log you posted you must have not done the Tools -> 'Search for...' thing. If you had you'd have had a much bigger log. Debug would of course need to be disabled AFTER the search and not before it! lol Anyway... Ok, you've got big issues somewhere. The 'Inquiry' command is the one used to get the name of the drive etc. For some reason your machine is returning a buffer full of 'FF'. FF just happens to be that funny 'y' character. What's your drive connected to? A real motherboard chipset SATA port or a 3rd party chipset one? (i.e. jmicron) SATA drives work best when the controller is set to ATA mode rather than RAID or AHCI.

Yeah you didn't actually do what I needed you to. Once you've pressed F8 to enable debug mode go into the Tools menu and select the 'Search for SCSI / ATAPI devices...' option. Then copy + paste it all again.

2 files types are now support for the folder/file list actually. *.LST and *.TXT Pass a single file with either of those extensions via the /SRC switch (when in Build mode) and the program will assume each line in the file is a folder / file name. You can also drag+drop a single *.LST/*.TXT file on the application icon and it'll load it into Build mode in the same way. (The same happens for supported image file extensions where it loads up in Write mode.

Scrap that, if you pass a *.txt file via the /SRC command it'll treat it as a list file. The chances of someone burning a (single file) txt file as a real text file via CLI are slim to none - and if they do, they'll just have to live with it that they need to use the gui instead.