LIGHTNING UK!

1) To do this, the 'Copies' in the queue would have to be implemented like the Write Speed and Device selection stuff - i.e. you'd have to enable and override the default setting (taken from main window) via a checkbox. I'm not sure people would prefer that to the current method. 2) Yes it defaults to 20MB and is not based on ram size. No matter what I do, someone will always fault it If I make it tie in with available ram, someone with 2GB will soon check taskmanager and complain that it's now taking up 256MB when it only use 20 before. If I default it to 40MB, the person with 64mb will moan it's having to swap to hdd. 20MB is small and yet large enough. If you're killing the buffer (and do so all the time) buy another hdd and use that for your images. I would rather leave the user in total control of buffer sizes and start with a conservative size as I am doing at the moment. 3. Have now done current/total copies. Do you REALLY need a static bit of text showing the speed you selected?! What do you gain from it? Surely you just need to see the speed it's actually burning at ('Write Rate'). You can always look in the log for the speed you actually selected. 4. It's called RegEdit 5. Ok, done.

I can't see anyone's name on the birthday list so I'm guessing you lot are actually a day early due to timezones etc So when it's Saturday here in the UK.... Happy Birthday LFC!

Anything that uses more than 1 thread will make use of HT - and ImgBurn is multithreaded. The actual use of HT is controlled by the OS though and it does the job of assigning cpu time slices to these threads - it also controls which CPU (be it real or logical, as in the case of HT) the thread runs on.

Sounds like a media/firmware problem to me. The drive isn't letting the program reserve the track. Check for firmware updates and/or switch to different/better media.

If the MDS supplies the layerbreak position, the IFO files are not examined. Therefore, whatever builds the ISO/MDS must do it correctly in the first place. It's hard to help at the moment because you don't have a real log.... so basically, for now, stick the topic 'on hold' and then reply back when you have a log to show us. Without the real numbers, it's hard to know where the problem lies exactly.

This is the one you want: http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx

Check and see if you're getting minidump files in c:\windows\minidumps. If you are, you can analyse them with Microsoft's debug utility. You can also try messing with the Dr Watson program (drwtsn32.exe) to get some additional debug info.

I have no idea how long you're leaving it to do its thing, but with DVD+RW, ImgBurn will wait until the entire format (foreground + background parts) has finished. This is the only way to ensure the format actually completes and so it's the method I've chosen. To imitate how DVD Decrypter worked, you'd need to turn off the 'Wait for background process' option in the settings on the 'Write' tab.

There shouldn't be any reason for Windows to throw that error unless there really is/was a problem reading from the hdd. Maybe all it needed was to have those sectors written to again and that fixed them.

I guess the server man didn't configure that url to go anywhere. As such, it's going to the default website on the dedicated server - which happens to be dvd-recordable.org

This isn't really the place to be asking, sorry. Try using google or something. Only you know what you want to do.

I think most of us that use TY use the -R version rather than +R. I'd also be tempted to try 4x and 8x. The write strategies might be better than the 6x one. Other than that, there's nothing to say really. It's failing to burn to the media.... not much else we can tell you! The 107 is quite old now in the grand scale of things. Maybe it's time to update to a 111?

Well yeah, but it's more of a general thing, not just for DVD Video images.

Oh and polo, you know the drill... I need loads more info! When EXACTLY are these errors popping up? During the burn? When you open the Queue window? When you add things to the queue window? Without that, I can't even begin to look into it.

I believe files only get put there from BSOD's. Programs never really cause crashes in that way as it's only low level stuff (drivers etc) that crash the OS. For normal crashes, you'd need to configure DrWatson. Click Start -> Run and type 'drwtsn32' (without quotes)

As I said before, there is no link with any drive selected in the queue window. It just happens that if the drive in the main window does not match that of the first image in the queue, the start button gets enabled - regardless of its actual status as to being 'Ready' or not. When you click start, it then switches drives on the main screen and then it's checked to see if it's ready. Anyway, I've added your buttons now so your life will be that little bit easier

and if the image was corrupt, you'd go back to the video_ts folder/files (if they ever existed). After that you'd go back to whatever created the files...etc etc. Somewhere along the line you'd find the problem!

If the program is sending commands, it's the drive that doesn't work well with the media! Whilst this 'polling' is going on, the program isn't actually doing anything other than saying 'Are you done yet?'. The drive is the thing doing all the hard work. btw, am I to assume you're doing a full erase here?

So do they look ok on your PC or are they messed up on that too? Do you verify your burns too? That all go ok?

Send the minidump file over. - c:\windows\minidump As I've mentioned before a few times, there is 1 memory corruption bug I know about in 1.3.0.0 but you'd only see if it if you get one of those 'Potential 'WaitImmediateIO' Deferred Error' errors. Not only that, you certainly wouldn't get it with the beta.

I believe that's enough for 99% of users, and that's good enough for me It's only supposed to be a simple tool after all, one for people that want a specific job done without all the extra fuss.

Deleting would be as easy as appending to it - and so as I said no to deleting, I actually meant no to anything multisession. When you build an image, it doesn't look at / care about the contents of any disc you happen to have in the drive at the time. If you're going to mess with multisession stuff and adding / removing files, why don't you just get dvdram and let windows handle it?! That or install one of those awful packet writing tools that turn the drive into a virtual hdd type thing. ImgBurn's 'Build' mode will quite simply take a bunch of files / folders and make an image out of them (or burn them directly to a disc).

Hopefully, yes!

It doesn't recognise it at all? Are you sure nothing else is using the drive and just not letting ImgBurn see it? Don't pay too much attention to the pretty name explorer shows for the drive, it's almost meaning less. If you want to test the drive, put it in another pc and see if it behaves in the same way.

There IS a bug at the moment in 1.3.0.0 whereby the 'reason' for failure given AFTER a potential waitimmediaio error gets corrupted and displays rubbish. It should be saying the same error the 'potential' one said. That has no effect on anything though and only shows up if your drive has already crapped out. Normally, 'No Additional Sense Info' is basically where the drive failed but didn't have a clue why. You should never really see that error unless firmware programmers have been lazy