LIGHTNING UK!

Try using 8x Verbatim DVD+R rather than 16x. They're probably better suited to your drive.

Your drive is misreporting the size of the disc. Just try and burn anyway.

Indeed, ASPI should only be needed by old OS's like Windows 95 / 98 / Me. You're not really still running one of those in 2007 are you?!

is the file somewhere you have write access to? What's the exact message? normally it'll tell you why it can't open it.

nobody.

Sorry, I don't really like that

This will be done one day soon, don't worry. After the multitrack thing is finished, this is probably next on my list.

Joliet is unicode - meaning it uses 2 bytes per character instead of 1. So if the field in the filesystem structure allows for 32 bytes, ISO9660 can have 32 characters, Joliet gets halved to 16.

The 3 brands might have all been the same media ID, hence not really any different at all. If you load the program AND THEN insert the disc, does the message in the status bar change to 'Logical Unit in process of becoming ready', before then going back to 'medium not present' ? It would certainly appear as though the drive just doesn't like those discs.

Make sure you visit the site for your own laptop manufacturer! There's a good chance the xx3x series is for a different one to the xx0x series - and we don't want to be responsible for you bricking your drive!

Perhaps I should just change it to say: 'Are you trying to build a DVD Video image / disc?' [Yes] / [No]

Whatever you've done, it's not right. You've burnt a disc with IFO/BUP/VOB files I assume (?) and yet according to the logs, you've no folders in the compilation - which of course means you don't have those files in a VIDEO_TS folder - which is a basic requirement for a DVD Video disc.

Do you just want to burn the ISO file? You do that in 'Write' mode, not 'Build' mode.

If you've done a full format on the disc (using the default program settings) and in the info window on the right it still doesn't say 'Formatted: Yes', your drive isn't formatting the discs properly. The only fix for that is different media and / or new firmware.

Happy Birthday Kirk!

www.svp.co.uk Oh and i think there's an AX03 firmware for that drive available somewhere - someone just caught me on email saying the drive doesn't burn anything - seems this is common and dell (who happen to use these drives) just swap them out for a decent NEC one.

Oh good, that saves me messing around

If that's supposed to be a DVD Video disc, no wonder it won't work. You appear to have all the files in the root of the disc rather than in a VIDEO_TS folder. The program normally detects DVD Video files in the wrong place and prompts you to see if you actually meant to burn a DVD Video disc. Do you remember seeing any such prompts when building the image?

You're not really giving us much to go on! What type of files are you burning? How are you burning them? Where's the log of the burn? What does the disc look like once burnt if you browse it in explorer?

Yeah you do! It means the program scans the subdirectories of any folder you add to the list (and the subdirectories of those subdirectories etc etc) - otherwise you'd only have files from within THAT folder.

Maybe you haven't burnt one in a while, but could you?! We're not exactly getting anywhere by just looking at your machine failing to produce a steady stream of data in build mode.

Did you burn using 2.3.2.0, or were you using 2.3.1.0? 2.3.1.0 misread some of the file formats and so you'd get a bad burn. In case you were already using 2.3.2.0, is there any chance you can tell me exactly how to reproduce this problem using the software you mentioned? Some screenshots showing what to do etc - otherwise I won't be able to do anything about it. Oh and no you can't change that they burn in alphabetical order.

Try some different discs, your drive doesn't appear to like those and can't initialise them (the drive has to do that before it lets software see them). Check for firmware updates too.

They make it sound so scary... believe me, it's not! You run the exe, select your drive (if you happen to have more than 1) and then click go. (ensure the drive is empty first) When it's done, just reboot. It's not going to touch your computers hard drive or the software on it, so don't worry.

You can't actually count the 6 seconds as the parsing time, that's just the time it took to loop through the file list and display everything in the listbox! Any chance you could time how long the actual 'read ahead' process takes? i.e. by watching the status bar and using a stopwatch! The read ahead should be the quick bit because that's a single api call to read the data from the file in one long stream. That actual parsing is lots of individual file accesses, reading 1 sector at a time - and potentially from all over the place within the file. At the moment that also involves a lot of opening / closing of files, but I've removed that overhead in the latest (unreleased) beta.