LIGHTNING UK!

I think that's just a glitch in the browser window. Notice the treeview (left) doesn't match the listview (right). The treeview is wrong, the listview is correct. Look the disc with something like IsoBuster, I'm sure you'll see it's fine.

There's no way ImgBurn is doing what you're saying. Are you perhaps not just seeing what Windows displays for discs it thinks it can write to? Try and get me a screenshot of what you're seeing. Clicking 'Yes' to ImgBurn's prompt would leave you with 'Instalador' and 'Portable' in the root of the disc. Clicking 'No' would leave you with 'Finale 2011' in the root of the disc.

Do you fully understand what the prompt is asking? If you add the folder 'C:\Stuff to burn' to the source box and click the 'Yes' button, only the contents of that folder will end up on the disc - so when you browse the disc you *WILL NOT* see the 'Stuff to burn' folder. If you click 'No', when you browse the disc you *WILL* see the 'Stuff to burn' folder. I can't comment on what you're seeing without knowing the full path name of the folder you've added to the source box and the names of files/folders it contains.

Yes, it's fine when Build mode makes an ISO from a multisession/track disc because it will have built a totally new image based on the files the disc contains (through the eyes of OS). Read mode doesn't work at file level, it works at sector level and would try to create an exact image based on the physical layout of the disc. It knows the disc contains multiple sessions/tracks and that such discs cannot be stored in an ISO file. Even though it changes the file extension to BIN, even that is useless. No multisession/track info is recorded (saved) anywhere for DVD/HD DVD/Blu-ray media (it should probably be in the MDS file but it isn't) and so the BIN file is also useless as no program would ever see anything beyond the first session/track. So where I said using Build mode is the best way of dealing with those discs, it's actually the ONLY way! The next version of ImgBurn will block Read mode from making images of such discs and suggest that Build mode should be used instead. For multisession CDs or single session DVD/HD DVD/Blu-ray, Read mode is still the best way of making an image - assuming there no reason to rebuild the file system using Build mode (for moving the layer break etc).

I can't help until you post a log - I did ask nicely in post # 2. Assuming your ImgBurn settings are ok, it must the source files (and / or folder structure) that's wrong - in which case you should take this problem up with the author of multiAVCHD over at the Doom9 forums.

DVD-R isn't an option. Either you leave it as DVD+R DL or you set it to DVD-ROM.

Your CUE file for a single audio.raw track should look as follows: REM SESSION 01 FILE "audio.raw" BINARY TRACK 01 AUDIO INDEX 01 00:00:00 TRACK 02 AUDIO INDEX 01 01:52:31 TRACK 03 AUDIO INDEX 01 02:32:56 TRACK 04 AUDIO INDEX 01 03:50:50 TRACK 05 AUDIO INDEX 01 04:09:53 TRACK 06 AUDIO INDEX 01 04:22:54 TRACK 07 AUDIO INDEX 01 04:31:55 TRACK 08 AUDIO INDEX 01 04:47:18 REM LEAD-OUT 04:58:26 REM SESSION 02 FILE "data.bin" BINARY TRACK 09 MODE2/2352 INDEX 01 00:00:00 You had the LEAD-OUT bit wrong, that's all. It uses the LEAD-OUT to know how much data there is in the last INDEX. i.e. LEAD-OUT value - (minus) last INDEX value = size of INDEX. Your LEAD-OUT value was smaller than the INDEX value and that's why it didn't work. It just meant the last index was calculated as having a size of 0. I've added a check/prompt for such issues now - not that it should ever really be needed if the CUE files are created properly (i.e. by the software itself)

Can you show me the message in ImgBurn please... after all, that is what this forum is for!

You're getting a BIN file because you have a multisession DVD. An ISO cannot represent that type of content, it's only for basic layouts (single session, single track). If you actually try and do anything with the ISO from that other program, you'll notice it doesn't contain anything other than the 1st session... so files in later sessions simply won't exist/be accessible. What you've done there by using Build mode is indeed the best way of dealing with such discs. It'll create you a nice new clean (single session/track) image with all the files in it that you'd expect to be there (based on the data from the last session on the disc - as Windows sees it).

'RITEK-S04-66' is the dye/MID of the discs you've purchased. The brand name on the disc doesn't mean anything, it's the dye/MID that's important. Multiple brands can use the same dye/MID. So you could buy 2 spindles of discs with 2 totally different brand names on them end up with exactly the same discs (dye/MID). I checked Firmware HQ for an updated firmware for your drive but it didn't list anything. So you should look at getting a decent external drive (normal size, not slimline - a normal size internal desktop drive in an enclosure is the best option) or trying to buy the 2.4x speed Verbatim discs (MKM-001-00 dye/MID). No, updating Vista won't do anything for this problem. It makes the entire Vista OS a lot better and more secure though!

Your drive is probably too old to support 'RITEK-S04-66'. http://forum.imgburn.com/index.php?showtopic=8000 Why haven't you got any service packs installed for Vista?

Yes, DVD Flick, ConvertXtoDVD, AVStoDVD. If your drive just keeps producing unreadable discs when you use 'CMC MAG. AM3' stuff, buy some better ones. Look for Verbatim or Taiyo Yuden instead.

What program are you using to create the AVCHD folder structure in the first place? Post a log of you burning + verifying such a disc please.

It's not just the error message that we need to see. The logs are saved automatically, you can access them via the option in the Help menu. Like I said, you don't have mpg files on a proper DVD Video disc so either it's not converting properly or you're not burning the right thing.

The fact you have a file on it called *.mpg means you haven't convert them to DVD Video format properly or you aren't burning the right thing. The burn failures are probably down to the discs you're using. We might be able to help you if you post a log - as per the pink box up the top

If the drive is in a laptop, you'd get the firmware from whoever made it. It looks like it may have been Acer, in which case, good luck with that! (They aren't very good with releasing firmware updates)

1x doesn't exist, the supported speeds for your drive/firmware on MCC-004-00 media are: 6x, 8x, 12x, 16x Where did you get that 8L72 firmware from? It might be worth trying to (cross)flash with the latest 8L0C firmware instead. http://www.firmwarehq.com/Lite-On/iHES208%2B2/files.html If the flasher rejects your drive you'll have to get a firmware bin file for the iHES208 from the MyCE forums and flash it with a 3rd party flash tool you'll also find on that site. Have you tried a disc from another spindle? Maybe you got a bad batch.

Try burning at 16x or 24x instead of 4x. Try using Taiyo Yuden CDs instead of lower quality CMC based stuff.

Like I said, the TAO bug is a known one that has since been fixed. You'll have to wait for 2.5.6.0 to try TAO out properly.

Quick erasing a DVD+RW is a waste of time. If your drive is having trouble burning to one, do a full erase (format) on it and try again. As for the 2nd log, try burning at a slower speed. 'Max' (22x) is unlikely to be the optimal one. There's also a SB07 firmware update available for your drive. http://www.firmwarehq.com/Samsung/SH-S223C/files.html

The fault is a bad drive/firmware/media combination. Yes you should test again with Verbatim. It's all detailed in here... http://forum.imgburn.com/index.php?showtopic=8000

It's all in here... http://forum.imgburn.com/index.php?showtopic=8000

lol, looks easy.

Ok but that doesn't change the answer. If the API is failing because there's not enough memory available in the format it needs it, you need to make the buffer smaller. I assume you mean 'recover' rather than 're-allocate'. A hdd should easily be able to cope with any speed burn (it's only ~32mb/s at 24x after all) - unless it's a really slow old one, heavily fragmented and/or being taxed by other applications. Building an ISO and then burning it will be easier on the system that trying to burn lots of little files on-the-fly. You have to take the antivirus overhead into account when you do that, along with general random access involved in burning lots of little files.

Stop using such a big buffer. For whatever reason, the 'VirtualAlloc' API function is unable to allocate 512MB.