LIGHTNING UK!

This doesn't sound like it's anything to do with ImgBurn, try another forum.

lol yeah that's a lame suggestion Jason

That is very odd then as it's only the same messagebox function that's being called.

Don't burn at 4x, new drives are optimised for speed, especially with decent media. Go for 8x at least (12x would be fine). How did you solve the FSCTL_LOCK_VOLUME error? Hopefully not by just turning off the 'exclusive access' option! It's very unusual to get the 'Invalid Address For Write' as the first error. Normally it occurs after a write error but your log doesn't show anything like that.

lol what exactly did I fix?! Just looks like it's not reporting the correct size for the disc and that's your drives problem really. If you compare image sizes, the drive says: I 10:37:20 Source Media Sectors: 53,442 Yet the RN one said I 10:52:30 Image File Sectors: 53,440 (MODE1/2048) That's 2 sectors different. As I go by what the drive reports in response to being issued the 'Get Capacity' command, I can only assume the info it provides via the 'Read TOC' one is different (again, this is a drive problem). Copy + paste the info from the right panel in ImgBurn (with the dodgy disc in the drive) and we'll know for sure.

Basically, at the moment your drive is producing really bad (low quality) burns on the media you're using. So bad in fact that it then can't read back what it's just written (that's what the 'Verify' stage checks for). If you use decent quality media in your drive then the burn quality will improve and your problems will go away.

How truncated exactly? Your player would probably support ISO9660 and Joliet file systems. Maybe you've switched it to ISO9660 + UDF within ImgBurn, hence your player is stuck using ISO9660 which is limited to file names of 8.3 characters long (i.e. xxxxxxxx.yyy). Make sure the 'file system' option is set to ISO9660 + Joliet + UDF (or just ISO9660 + Joliet) and try again.

You should probably slow the scan speed to 4x too.

Put a disc in your drive and read it from the info panel on the right. Drives do seem to jump between 1 of 2 numbers when they initialise the discs though - and of course DVD+R is different to DVD-R.

Try again with decent Verbatim / Taiyo Yuden media. You might also like to consider crossflashing to the real firmware as that drive is an OEM Lite On SOHW-1653S.

How does your player display the file names? Are they truncated or still the same as when they're on your hdd?

lol I'd love it if he did. I'd certainly be more interested in watching TV about politics! Clarkson rules!

Many thanks

Yup, they appear to be.

Glad it helped

Don't pay over the odds for the Plextor, I'm pretty sure it's just a rebranded Pioneer 112/212.

The order wouldn't be anything to do with me, surely that's down to your player.... or rather *you* pressing play on the right file?! They're stored in alphabetical order within the file system (as is required by the specs).

Yup and then you can just press the green down arrow with the red 'x' int it (on the toolbar) to move between the untranslated strings.

I'm pretty sure there's an option in the 'File' menu (in DVDShrink) for loading from an image file.

Only new strings will need to be translated. They get added onto the ends of the sections.

It depends on your burner, you might not be able to do it at all. The book type options are accessed either via Tools -> Drive, or via the 'Book' icon down the bottom right of the main window (in most of the modes).

Yeah I do the same via an MRU type variable.

It's not just the folders you have to monitor, it's all the settings too. A lot of them can change the tree structure or mean different things are required in the way of file systems etc. They all change the total size of the image. So yeah, as you say, it's not worth it

Also, isn't this where the 'Calculate' button comes in? It tells you how big your project is and how much over/under you are. Seeing Explorer say it's 4.37GB doesn't really help because obviously there's 50mb (either way) of error in that figure. So you'll see 4.37GB in there and think hmm I've got 4.37GB free on my disc too so why doesn't it fit?! Displaying in Bytes/Sectors is the only way around that. EDIT: I've added tooltips to places where size info is shown in bytes, they use this format: 'X bytes (X KB) (X MB) (X GB)'

When ImgBurn opens your project it's really just configuring certain settings in the GUI and once it's done that, it knows nothing about what you've just done. I'll add the file name to the log window if you like though.