LIGHTNING UK!

ImgBurn doesn't support 'building' multisession discs. That's why you can't 'update' a file. Because you don't say either way, can I assume you're using a DVD-RW rather than a DVD+RW? ImgBurn always closes a disc when it burns - so no more data can be added (again, it doesn't support multisession 'building' so there's no need to leave it open or create a new one). Maybe that's why Explorer can't add to it? Files aren't in a 'format' (ISO9660, Joliet, UDF etc), they're just data. Build mode doesn't know or care about the format of the disc/drive the source files are coming from. For the most part (i.e. 99% of the time), using the program's suggestion would be the right thing to do. If you're messing with special custom built os installation discs then you're in the other 1%. Sorry but you'll just have to deal with the suggestion popping up - or turn it off in the settings. If you want to 'copy' a disc, you'd 'read' it to an image and then 'write' that image to disc. You shouldn't be using Build mode at all. What does the structure of your output folder actually look like? If the program sees a special folder name that it recognises (VIDEO_TS, BDMV, I386 etc), it'll try and put things in the right place for the user. Again, for the most part, this would be correct. There has to be a line between just doing something and prompting for confirmation for every little thing it tries to do in order to help. If I made the program prompt for everything it currently does automatically, everyone would go nuts... but at least you'd be happy.

You should build your images (or burn the VIDEO_TS folder directly) with ImgBurn, not whatever you're using now. DVD Video discs don't usually include the Joliet file system. If your player supports seamless ok (you'd know about it by now if it didn't) then it's fine. Depending on what's being offered, you should preview the layer break positions in order to make an informed choice. The stars are there as a guide (based on technical info, not actual video content), that's all.

That's nothing to do with the Create CUE File window, the code for that function hasn't changed in years. What you're seeing is probably a result of the following change added in 2.5.3.0. So the problem is more general than that. ImgBurn wasn't remembering the path, Windows was. I'll make the program do it (for that window and others like it) so it works for the new IFileDialog stuff too.

Ok so the program expects to find a (boot image) file called 'w2ksect.bin' in C:\... and clearly it doesn't exist. I'm not entirely sure what you're trying to do, but if it's related to creating an XP install disc, follow my guide instead. http://forum.imgburn.com/index.php?showtopic=11190

Yeah, try installing the Rapid Storage Tech driver from here - http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=3334&DwnldID=20023&lang=eng&iid=dc_rss You should put that on if the controller is in AHCI or RAID mode. I think it'll say it's not required if you aren't in either of those two modes.

That error is from your controller drivers - potentially masking a real error from the drive. What chipset does your board use? What controller is the drive attached to? Try burning at 8x, you'll have more chance of getting a decent burn. 'CMC MAG-M01-00' isn't a dye we'd associate with decent discs.

Your controller drivers are returning that initial error, it's not coming from the drive itself. The 'Write Error' after the first retry is coming from the drive though. What chipset does your board use? What controller is the drive connected to? There's nothing special about RITEKF1 media and you'd do well to try some decent discs. You want MCC/MKM Verbatim discs or something by Taiyo Yuden.

There's no easy way to do this with ImgBurn. The only ways to create a CUE file containing CD-TEXT info are: 1. To read a disc already containing CD-TEXT info. 2. To use the 'Create CUE File' feature and add files that contain a supported form of metadata (i.e. ID3 tags in MP3 files). 3. To use the 'Create CUE File' feature and type the artist/performer info in manually.

You don't know until you try

http://forum.imgburn.com/index.php?showtopic=8000

You don't need to extract a boot image for Vista or 7, there's a file that's part of the installation files for that (etfsboot.com). I've linked the boot image file in the XP guide now to make it a bit easier for people without their own original CD.

Modern Plextor and Asus drives are just rebranded LiteOn style drives (based on the same Mediatek chipsets). You're better off buying a real LiteOn as you benefit from more frequent firmware updates.

The version makes no difference. Your drive controls the burn, not the program. The updates fix bugs in the program's own logic - and the current version works just fine. There are some things you can try mentioned in the following thread... http://forum.imgburn.com/index.php?showtopic=8000

I'm not sure how you expect that image to be of any use to us. All it shows is the size of the drive, the amount of space used up and the amount of space remaining. Windows search can find files within a date range too. Just open an explorer window (i.e. 'Computer' off the start menu), press F3 (or CTRL+F), click the 'Advanced Search' button on the right and then mess around with the date range boxes on the left. Not only that, searching for *.iso would have done. You're familiar with wildcards yeah? If not, you are now. Did you actually have any image files listed in ImgBurn's 'Recent File' menu thingy? If so, do any of those files still exist in the paths it mentions? If not, you're probably worrying about nothing.

Ok, the MDS has nothing to do with this problem. Your drive is just having trouble writing to that disc. Try another full erase/format on it and then give it another go. After that I'd just use a different disc.

They'll be wherever you put them! YOU have to specify the destination path. If you don't (and just enter a file name in the destination box), they'll be in your documents folder - like I said earlier. As for the treesize thing, well you aren't going to have too many new/large files on your hdd so use the 'Date Modified' and 'Size' colums to find them. If you were burning DVD sized images you can ignore folder that aren't around that size. You could even have windows search for files created in the past week or whatever. ImgBurn also keeps a record of the most recent files. Switch to build mode (image file output) and take a look at them on the 'File' menu. It might give you a clue.

MDS file aren't plain text files, they never have been. If you have a problem, please post the log - as per the pink box up the top

Use a new 'empty' disc.

No, there's just the one version.

Try looking at the cdfreaks / cdrinfo drive reviews. This wasn't ever really an 'ImgBurn Support' question anyway.

No, it's a GUI app.

You need the boot image from the original bootable cd. It's not part of the files/folders that you can see on the disc when you browse with Explorer or whatever and it's not bundled with ImgBurn. El Torito is an extension of the file system. It's an extra bunch of descriptors that point to a boot catalogue and a boot image. Your BIOS will check for the existence of the El Torito descriptors when deciding if a disc is bootable or not. If it is, it'll parse said descriptors and 'run' the boot image - that's what then kickstarts the installation program. You can get the boot image here - http://forum.imgburn.com/index.php?showtopic=16578&view=findpost&p=126019

ISOs (and all other supported image file formats) are burnt in Write mode. i.e. 'Write image file to disc'

It looks fine to me. Try running the codec tweak tool and see if it can find a problem. http://www.free-codecs.com/download/codec_tweak_tool.htm You could also try playing one of the problem wav files in GraphEdit and see if it errors out.

The only time it writes stuff to the hdd is when you build an image file from files/folders rather than burning those files/folders directly to a disc. If you've done that, the image will either be in the root of the drive or in your documents folder. Empty the recycle bin and try using something like 'TreeSize' to figure out where your space has gone.