LIGHTNING UK!

It's too difficult to implement and I can't be arsed.

It's 110% pointless for Verify mode. The second it hits a problem it's already failed verification. The option is already there for read mode.

You had a bad burn. Is that drive in a HP machine? If so, do this firmware update. http://h10025.www1.hp.com/ewfrf/wc/generic...=en&lang=en

Get the 1.65 Firmware update and try again. http://sony.storagesupport.com/dvdrw/dru190a_dwn.htm

I'd be interested to hear where the files are coming from that contain v2.4 tags. All the testing I'd done was with my own stuff that I'd encoded rather than downloads. Any tagging program will tell you the version of the ID3 tags used in the file. I just happen to use 'ID3-TagIt' because it's the first free one I came across and it looked pretty decent. The ACM issue was a late bug introduced during a tidy up / bit of optimisation at the VERY end of the beta cycle. What can I say... these things happen. If MS would update their filter to deal with v2.4 tags then this wouldn't ever have been a problem, but it seems even the newest filters in Vista still can't handle them. Shame really.

ISO is the wrong format for that type of disc really. Leave it on BIN or select WAV if you prefer.

No, there's not I'm afraid. File name info etc is already put in the log from all modes except build. If you need that info from build mode, take note of what you add to the source box manually. You could also run a 'dir /s %1 > dirlist.txt' type command from the command prompt to log everything included.

That media is quite new out so you'd need an up-to-date firmware that actually supported it. Try some verbs, they seem to have the best support over a wide range or drives.

The acm problem is fixed for 2.4.1.0. However, it would only fallback to ACM if DirectShow was failing. In my experience that only ever happens if said MP3 has an ID3 v2.4 tag. Windows's built in filters simply can't handle it. So try and use a decent bit of tagging software to remove all tags on that file and then recreate it as required - ensuring that only v2.3 gets used. It might also be worth looking at the file in a hex editor if you're ok with that kinda thing and checking for tags manually.

Help menu -> ImgBurn Logs. Firmware / booktype thing sounds like bad info to me. Ignore it and update to SB06 or whatever.

It's not his fix really, it's mine. It was never really designed for previewing inside a larger container (i.e. an image file), it expects to be fed VOB files and requires custom tweaking to get around that.

It's just your drive not recognising / initialising the disc properly. See if there are any firmware updates available for it. If it's reporting the wrong size and you know for a fact that they're 80 min CD's etc, there should be no problem with burning them to that extent. It'll either work or error out - in your case it seems to work. Just make sure you enable the 'Verify' option to check everything is present and correct.

Does Read mode work on said disc?

Use a different dye then. You said others had worked, go back to those.

load up imgburn and see if it picks up the new firmware version

It doesn't format in the same way ImgBurn does, that's why it always leaves the 'formatted?' status in limbo.

Is the drive light flashing on the AOPEN? It looks like it actually wrote the firmware code, just the checking got stuck... so hopefully if you do have to reset the PC it'll be ok. Maybe try flashing it again? As for burning in the other PC, slow it down to 2.4x and update to TS12 firmware http://samsungoms.com/eng/firmware/fwdownl...ode=&os_no=

Try a firmware update http://download.aopen.com.tw/userdownload_...del=DUW1608/ARR EDIT: Beaten!

1. That's all down to the drive. If it hangs, it's out of ImgBurn's hands. As you noticed, when I/O hangs, it REALLY hangs. The OS can't really recover from it (without some 3rd party tool to force a bus reset) and you have to press the 'reset' button or power down. 2. Every time the buffer runs out the drive has to 'pause' and that means it has to perform relinking. That normally results in some sort of PIF spike - how bad it is varies from drive to drive (based on write speed and media used I guess). 3. Locking is covered in the FAQ.

So long as it initialises it properly, you should have no problems in reading/verifying the disc. If it keeps coming up with DVD+RW for a DVD+R disc and erroring out in the same way with every 'Read' command it's sent, you might like to contact LiteOn and see if they can fix it.

This is a drive/firmware/media issue. At the moment the drive is doing an awful job of initialising the media after the burn. For example, this is before the burn: I 02:08:39 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x) this is after: I 02:16:07 Source Media Type: DVD+RW (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 4x) DVD+R -> DVD+RW ? Ummm ok! Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x -> Speeds: 4x ? Ummm ok! There is nothing I can do in ImgBurn to fix that, software doesn't even come into it.

Seems you forgot to attach the log

Technically it's not merging them. The file is not opened/read/added to/written back, it's simply overwritten by the new set of graph data that contains info from the entire process - i.e. Write and Verify - where it's all held in memory.

/s is the only one I know of. Personally, I'd re-package it as an msi or whatever and do it properly.

The program will tell you if any file/folder names have been truncated / modified due to your settings, keep an eye on the log window. A virtual drive acts just like a real one except it accepts disc images and not real discs. You 'mount' your image in the virtual drive and to windows, it'll look like a real one - showing up in explorer / my computer etc. You still do the 'building' with ImgBurn.