LIGHTNING UK!

Red is good, yeah?

lol turn your monitor brightness up You may also have a setting in your graphics card properties for directdraw overlay stuff.

Get the name right mate, it's ConvertXtoDVD now! DivX is a registered trademark and can only be used from DivX themselves - hence the name change

Yeah the damn thing has gone on the blink again.

Posting a log would help, there are lots of different errors it could be. But if you're already using Verbatim DVD+R DL media, it must be your drive and/or its firmware. Check the firmware is up to date. If that still doesn't fix it, your drive has probably worn itself out. (or you had a dodgy batch of verbatims)

The file association stuff in the settings has nothing to do with what files are supported / not supported. The image is just not considered valid because it contains no filesystem. So basically, ImgBurn won't burn it because it won't be readable in Windows anyway. Where did you get the file? Do you know what it's supposed to be? Are you sure you're meant to burn it to a cd/dvd?

Your drive probably dates back way before they started following MMC specifications. Sorry but you're out of luck, your drive is not supported. I might be able to figure something out if you press F8 before clicking the write button, then press F8 again after it has totally failed. SAVE the log as a file and attach it in a post.

I defrag my drives quite frequently (if I don't set a schedule to do it for me), but what I mean is that I don't take note of which files are fragmented and which aren't. I do tend to do drive c: a lot more often than my other drives though and I never use c: for building / burning images. So long as all the pretty little blocks are up one end of the drive I'm happy

lol I can't say as I check my drive's fragmentation level that closely, but I saw it for the good suggestion it was

Cool, I'll do that for the next version then. I hadn't seen that 'SetEndOfFile' function before now but I knew this kinda of thing was possible because lots of programs seem to allocate the full size needed for a file before actually writing anything. Perhaps I'll limit it to just doing it on NTFS though if there's a lot of overhead on FAT. EDIT: Done it now. Thanks again.

Once you have your VIDEO_TS folder (or IFO/BUP/VOB files), just read the Guides forum. It tells you how to burn them using 'Build' mode.

ConvertXToDVD can do it all. or for the burning bit, use ImgBurn.

Boooo.... they're not the *real* ones in my copy of Vista. I wish they were though!

Unless your player supports MPEG4/DivX then that's not going to work. You'd need to convert them to normal DVD Video format - and that's not something ImgBurn can help you with. Search Google and I'm sure you'll find something useful. ConvertXToDVD is the name of one app that springs to mind.

Update your firmware and perhaps stick to 8x media next time. http://www.de.nec.de/software/1858_Firmwar...500A_WIN10A.zip That's the 1.0A firmware, you're currently only on 1.07.

I know what you're getting at polopony but I'd take a true 1:1 image over a 'built' one any day - unless the original one was made by a bunch of cowboys of course!

It's more a problem using all the 'W' API functions rather than the 'A' ones. I didn't want to just define 'unicode' for the app globally because that would break Win9x support so I've had to write wrapper fuctions for everything. The GUI side of things was handled by using TntUnicode components - without those it wouldn't have ever been possible! - Borland development apps are entirely ANSI.

That doesn't really prove anything and there's nothing to say a retry on SPTI wouldn't have worked. What's particularly strange is that you were able to re-use the disc in the first place - normally you can't if a burn fails. I've never used anything other than SPTI and so if there was a problem with it, it's safe to assume that would NOT be the case.

Nope, max is max. It'll burn as quickly as the drive will let it. How are your buffers? Always at 100% or there-abouts? How is your plextor connected to the PC? IDE, USB, Firewire?

All I can say is that it's in testing! When we're happy it's at least semi bug free (I had to change a lot to get unicode working), it'll be released. Best I can offer right now is 'November' !

ImgBurn isn't really designed for burning to multiple drives and it would be a pretty big job to change that, sorry. I'm not saying it'll never happen, just that it won't be happening any time soon.

You've probably got hotlinking enabled on your hosting server - so you can't link to it on another website.

Sorry, no. This forum is for supporting ImgBurn, which is a burning tool and nothing to do with copying DVD's etc.

v2.1.0.0 only handles ansi characters I'm afraid. The next release supports unicode. It's unusual that a normal looking file name like that would fail though. Why isn't it just named using a minus sign in the first place?!

Naughty thing, glad you sorted it I just checked mine, I'm running 6.1 already! phew!