LIGHTNING UK!

What I guess you have to understand is that what I added is BIN/CUE support in Read/Write mode. Nothing more, nothing less. Audio CD support is only in there because those modes now support CUE files. To be able to work with (read/write) CD Extra discs, I also needed multisession support. The 'Create CD CUE File' is exactly what it says, it makes a text file, that's all. There's nothing clever behind it. Don't try and make it into something it's not. It's not designed with any particular disc type in mind - i.e. it's not actually for making an Audio CD, it just happens to be able to. Without it, the only way to write an audio cd would be to first 'Read' it from a disc or have an existing image. I knew that wasn't going to be enough, hence the reason for it's existence - although in a very generic sense. It's an 'Advanced' feature and the 'Session' button is really only there for completeness as it's supported by the CUE file implementation. The feature simply provides a means of doing something (making a basic CUE file). It's down to you (the hopefully knowledgeable end user) to ensure that the whole thing actually works.

Anything that's not divisible by 16 (sectors) will be padded by the drive when you burn to DVD+ media. That's it, end of story! It's not for me to know/say if the xbox guys have taken that into account, you'll have to run that by them.

Yes sorry you're way off. ImgBurn can't be used to create a CD Extra disc from scratch (why would you ever want to?!) but it'll read / write an existing one. The 2nd session option in the 'Create CD CUE File' option can only be used when the data track you're adding has been created with the appropriate starting LBA. Otherwise all the LBA's will be starting from 0 when really session 2 might start at LBA 100000. It would also work if you'd extracted the cd-da/data tracks off a cd extra disc as individual files - rather than an image. I hope that clears things up.

Assuming the image is correct in the first place, you've nothing to worry about. Everyone is in the same boat because they all use DVD+R DL media and all the drives will pad out to the nearest ECC block.

DVD+ (plus) format media will always burn so the total number of sectors is divisible by 16 (the size of an ECC block). The drive does this itself.

No, pre-BenQ I'm afraid, it's the Dell 2407

lol you should try 1920x1200 That said, I only use that res because I have a big screen. 19" is pretty much the standard with most new PC's these days. 1024x768 is probably all you'd want on a 15".... it's just everything looks MASSIVE in 800x600 and totally kills the user experience, not to mention websites etc word wrapping like crazy!

As mentioned above, you can't make an ISO to shove on the end. It's has to have come from a disc where it was already in the exact same LBA or the file offsets will all be off and it'll die a horrible death! That said, it shouldn't not burn and then not give you an error. I'll look into it. It copes with real CD Extra discs just fine - like via Read -> Write.

To be honest, it's a quick and dirty box, I didn't pay massive attention to validating everything (and I'd probably not even though about those two!). I'll tweak it for the next release

Many thanks and good luck. Of course DT has been updated recently so maybe you initial issue with that has been sorted anyway? DT is by far the best virtual drive going (and I can't stand MagicISO/PowerISO!). Also, MagicISO is on v5.4(build 251) now... why don't you try the newer version? EDIT: Ooops, it's known as MagicDisc, not MagicISO and your MagicDisc is the current version.

If you enabled I/O debug mode before it tries to get the drive status, the last entry in the log will be the command the virtual drive is hanging on. (Keep the log window open!) Report that to the MagicISO people. If you copy + paste everything from the (I/O debug enabled) log here too, that might help.

That's probably their problem (the virtual drives) and not mine then. DAEMON Tools works fine. Commands should not make your system freeze. They should work or they should error out.

Maybe it's an OS language thing then because it's fine here. Use the 'About' box to send me an email and I'll reply with a special build to check something. If the function where I set the GUI font isn't actually doing anything (as I would expect on your PC as it's only XP), it must be something totally different and perhaps out of my control.

Looking at the form dimensions, it's 649x596 so I don't see why it wouldn't fit? Are you perhaps running 120dpi ?

Ah ok, not quite the problem I thought it was. As an XP user, the font would be the same one as normal. I don't know why it's smaller to be honest! I'll look into it but I'm not sure it's actually caused by anything I'm doing. I don't run 120dpi so I'd never see this kind of problem. EDIT: I just put a VMWare XP session into 120dpi and it looks the same as your 'old' screenshot.

That's all the standard windows dialog boxes allow for I'm afraid. The first button can open multiple files but it doesn't do folders at all. The second does folders but only 1 at a time. So yeah, just D+D it. It's really meant for burning an entire structure rather than just a few folders from a certain other few folder. Stick with Nero or whatever if you need that extra flexibility with your layout.

It just uses the Vista default GUI font now instead of forcing Tahoma. So it looks different but it shouldn't really be much/any smaller.

Indeed, you're adding files that represent tracks in the Create CUE window, not files to burn as-is. Even then, you can't build an ISO and just shove it on the end for CD Extra, the LBA addresses in the file system will be all wrong.

1. The option is 'Cycle tray before Verfiy'. 2. You can't.

Read the 'ReadMe.txt' file. It might give more info on what each one does.

I was really hoping people would use at least 1024x768 these days!

It's extra pregap...nothing to say somebody wouldn't want that! The way I see it, I worry about the fixed stuff, you worry about the gaps YOU want on the disc. 99.9% of people wouldn't be thinking - Damn, I need to add a 2 second pregap to the first track to keep it inline with the redbook specs! Ok so ImgBurn might be a bit different to what you're used to but that not really a bad thing is it? I like to break from the norm It's also the kind of thing you do once and then remember (if you're smart enough to know your stuff in the first place). So at most you'll have an invisible extra 2 second gap at the start of the disc before you realise the fixed 2 second gap is put there automatically. As I say, the 1st track pregaps are not part of the CUE file and so I don't think they really need acknowledging in the GUI. It's just more to confuse the newbie people. When you load the CUE into write mode the 'Image Information' screen will give you the full breakdown anyway if people want to double check things.

Yup, it sure does. 2 second pregap before the first track in the session is done automatically, as is the 2 second gap between tracks of different sector modes. (you can't see the 1st track in session ones in the cue file but you can the other ones - if you look at it in notepad or whatever).

Harsh but fair I think?! It's easy to miss what's right in front of you so I cut him some slack.... blu wasn't feeling quite so generous

It's a very odd issue and I suspect nothing to do with the settings (as there aren't any used in that part of the program!). A machine reboot could have solved it.