LIGHTNING UK!

As above! Try a CD/DVD cleaner in it before calling Dell though.

There's a guides forum. Read the guides and try again. If you're stuck at a specific point, we're gonna need a LOT more info to be able to help you.

It doesn't have a valid filesystem - hence nothing will be able to read it. Tell DVDShrink to output to a VIDEO_TS folder rather than an ISO. The use Build mode within ImgBurn to burn that folder - as per the guides in the 'Guides' forum. That should solve your problems.

Watch the buffer bar though, it should actually stay on 100% all the time because the HDD should be loads faster than the burner. Or perhaps that log you posted was just a fluke odd/bad one when the OS was indexing or something.

No, sorry it's not. As you say, it takes the program out of scope. I actually can't see much of a reason to edit an ISO personally. If I ever did, I'd mount the ISO in DT, copy the files to my hdd, replace the ones I need to and then build another ISO. I'd fell much better (safer) about doing it that way too.

You could make it 40 just as a test but I would think it's still going to drop back down to zero and cause buffer recovery to kick in.

I wonder why your machine can't keep filling the buffer quickly enough though... that's most odd as you've obviously got a decent pc if it's running Vista. Are you busying doing other stuff whilst burning? You should leave Verify enabled. It's the best way to know if you've just made a decent burn. If the verify fails, you've got problems - and clearly you'd never know about them if you don't use that feature.

Yeah, that's an invalid ISO. You also appear to have issues with your PC as those 2.4x discs are only burning at 1.0x !

The drives always change to say 'CD Drive' if you put a blank in that doesn't have a volume label. It happens to everyone, not just you. As such, don't worry about it As for playing the bkf file, I should think a search on Google would tell you something. But of course you didn't need to actually burn the file to a disc so you could play it, you could have played it from your hard drive.

It looks like the drive isn't burning the discs properly. As such, I'd have to say it's faulty. Check for a firmware update before anything else though (if you haven't already).

You can't backup any protected discs with ImgBurn. So if it's worked in the past, they can't have been protected.

You're trying to read a commerical (protected) DVD and that's not something ImgBurn can do. As as side note, I thought 'Stranger Than Fiction' was some weird statement / comment being made, not that it was the name of a film! LOL

Sorted

It's using a sector size of 2332 which isn't supported by ImgBurn at the moment. I'm working on adding support right now - I had planned on releasing 2.3.0.0 tonight but it can wait until this is finished

No, it won't copy those. If that's what you're trying to do, you'll need to go elsewhere I'm afraid.

It's probably easier if you email it then. The address is in the 'About' box. For getting the first 5mb, get this: http://download.imgburn.com/grab5m.zip

You must have clicked the button to the right of the floppy disc image by the 'Graph Data' text. That button does the same thing as selecting 'Display Graph Data using DVDInfoPro' from the menu. Perhaps you were just randomly clicking and did it accidently? In any case, it won't prompt for DVDInfoPro unless to tell it to display the info using it. Again, sorry, I really don't know! It's not like the program is stuck in a 'while' loop or anything... some API call must just be taking ages to complete - and they're obviously not part my code, so I can't edit them.

They look like RAR files, so you need to unrar them! www.rarsoft.com

ElbyCDIO has nothing to do with ripping discs, it's an I/O interface, nothing more.

Correct. If you hide it, that's out of order and I'm likely to send the boys after you.

You can enter data in Build/Read modes via the keyboard - i.e. source / destination files, volume labels etc. Clearly I can't then just allow a character to change the mode or you wouldn't be able to use those letters in the fields or it would switch modes! The new real keyboard shortcuts are the CTRL + ALT + ?. You should use those. The others are only still in there because I did some lower level coding especially for them, but of course they're limited to modes where no other keyboard input is possible.

Once the terminated flag has been set within a thread (as is the case here), it'll terminate just as soon as it possibly can. I've honestly no idea why it's taking so long on your machine, I've never seen it happen on anyone elses. No, you just don't click the button that tells the program to display the info using DVDInfoPro - i.e. it's your own fault. It HAS hung. It's waiting for the thread to terminate and will sit there until it does. There's no timeout so it'll only finish when it finishes. You can't skip it because the thread is deleted once it's finished running.

Any chance you could post up / email me the first 5 mb of the image? I'll examine it and see what the problem is.

If you have a VIDEO_TS folder containing IFO/BUP/VOB files and want to burn a DVD Video disc, it really doesn't matter which guide (from those two) you look at. It all really depends on if you want to take the quick route (#1 / on-the-fly / more risky) or the normal route (#2). To be honest though either one would be fine. #2 is just a little more work. If you have an existing ISO/MDS file, you use 'Write' mode. NEVER use Build mode. Write mode will create a disc BASED on the ISO, Build mode will create a disc with the ISO just being a normal file on it (i.e. you'll be able to see the *.iso file on the burnt disc as you could when it was on your hdd). It says 'choose' because you can't burn 2 things (images) onto 1 disc. That's not how Write mode works. An ISO file is an entire disc image, sector for sector. You select the MDS file because it contain info about the ISO that would be lost if you'd just selected the ISO directly. The MDS automatically knows the actual disc data is stored in the ISO so don't worry that the MDS is only a few KB in size.

If it's in the actual open/save dialog box, that's windows own doing and nothing to do with ImgBurn. You'd have to find the MRU lists that windows keeps and empty those.