LIGHTNING UK!

Assuming discovery mode works fine, keep an eye on the buffer the next time you do a network burn. If you can see it dropping off slowly whilst the device buffer remains constand you'll then need to look at the network speed. Stick a trial version of DU Meter on or something and watch the pretty graph to see what speeds ImgBurn is able to read from your networked PC at. 8x *might* be pushing it on a 100mb lan, but it certainly should do more than 2x. Doing fake burns during testing, I've easily had ImgBurn hitting 35 - 40 MB/s from a network machine (connected via gigabit lan). That's basically the same speed I get doing a file copy in explorer. btw, optical drives DO NOT like being on controllers in RAID mode. ATA mode is by far the most compatible, use AHCI if you really need to RAID your HDDs and can't avoid it. Better still, buy a

Burn a disc in discovery mode and see what happens with that. This takes other drives out of the equation as everything comes from memory. What mode is your SATA controller in? ATA, RAID or AHCI? (This is a bios setting) What controller is it connected to? What's the controller called in device manager? Have you installed special drivers for it?

Consider it disabled / removed. I'm almost tempted to try and get one of those drives and have a mess around with it. I wonder if mtkflash could be used to salvage it? Anyway, if that command really did kill it, I can only apologise It's been fine on my S203B so it's not like I have / had any reason to think it could be dangerous! No hard feelings I hope.

It's not really meant for being used with a shortcut, its for people calling it inside scripts or from other programs etc. That's not to say it won't work, just that it's not designed for that.

Yes but it's not 1990 now

Nope, not really! If it happens again and again, get back to me with a screenshot of the main window so I can see exactly how much data it's thinks it's read and how much it's supposed to be reading. EDIT: Mount the MDS in DEAMON Tools and then use Verify mode to verify the virtual drive against the image. Just to see if that works! Also please copy + paste everything from the info window on the right when the 'problem' burnt DL disc is in a 'problem' drive.

Sending a command to a drive shouldn't kill it, it should just reject it if it's not supported. I'm not familiar with that particular model but I've seen a fair few other mentioned in the forums and nobody else has come forward with a problem like that.

So you select 'Enabled', click 'Change', it pops up 'Success!' and when you close that box it still says 'Current Setting: Disabled' ? If that's the case, I'll have to pass! I don't think any of my Plextor CD drives support power rec but I'll take a quick look. What happens if you change the setting in PlexTools and then view it in ImgBurn? (and vice versa) Does ImgBurn see that you've enabled / disabled it in PlexTools? Does PlexTools actually see that it's been enabled / disabled if you close down + reopen the program?

If you select 'Enabled' for the plextor one and hit 'Change', does it error out? Not all the plextor drives let you change those settings. Also, it might be different commands for CD Vs DVD drives. I've only ever test it on the DVD ones (as that's all I have).

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.