LIGHTNING UK!

They're normally the same hardware, one is just in a shell (i.e. the external case). If you have the option (and you have a desktop pc rather than a laptop), always go internal. If you have a laptop, you're probably better off with an external because the slim-line drives are generally rubbish!

For decent burns you need the drive/firmware/media combo to work nicely together. Yours doesn't. Basically you can do 1 of 3 things... 1. Find an updated firmware for your drive that likes MAXELL discs more than your current. 2. Find a new drive that likes MAXELL discs. 3. Buy some different media that your drive does like. You could also probably give a cleaning disc a quick whirl in the drive and see if that sorts things.

Personally I'd want 1 hdd for every 1 or 2 optical drives. It's the random accessing that kills transfer rates. You'd be better off using a program that supports a single read -> multiple writes.

Use Taiyo Yuden or Verbatim media. Your drive doesn't like the stuff you're currently using and that's why it's erroring out.

You can do it now. Just drag the image file into the 'Create CD CUE File' window and then add your audio tracks after it. Once you've got your CUE file, burn it in Write mode. Mixed mode CD's are the easy ones!

Try making your own images, then you'd get the dvd file. This isn't an xbox forum so if you can't search and find the info for yourself (it's all here), you're on your own.

From what I recall, people use a certain LBA for the layer break - which is normally done automatically by loading the .DVD file and not the .ISO. Where is your .DVD file? As such, there's no problem with what ImgBurn has done, the issue is with your source files.

2.4.2.0 is the latest version, you need to update. What don't you understand exactly? First it burns, then it verifies. Both were successful so what is the problem you're having? The log doesn't show one.

Odd definition of a 'bug' ! (moving thread to suggestions) This is an option YOU can enable already and they're saved in ANSI format because not many other programs can read Unicode files.

There is a purpose built 'Verify' feature, use that.

Maybe you'd have more luck with BinFlash (win32gui version from http://binflash.cdfreaks.com/ ) You can get the raw firmware bin file from - http://liggydee.cdfreaks.com/page/en/Optiarc-AD-7170A/ (4th one down on that page)

Why would I want to do this?! Either use ImgBurn or don't.

This is the important bit. Your usb controller and the enclosure controller are clashing in some way which is causing the device to timeout far too early and basically get 'ejected' from the system.

Looks like a driver issue to me. Nvidia controller perhaps? The program is getting bogus error codes from your drive/system so if you fix that, ImgBurn will work just fine.

They're both just shortcuts to 'Build' mode. One sets the 'Output' to 'Device' and the other sets it to 'Image File'. All of the burning is done via one main function so it doesn't matter what you're burning, the I/O commands are exactly the same. If the drive is randomly bombing out then it obviously has an issue with doing what you're telling it - i.e. burning that media at that speed.

Remember that it's the chipset inside the enclosure that would be the problem, not the brand of the enclosure itself. There's nothing to say both of those aren't using the same one.

One makes an image file, the other burns to the disc.

Yes, happy birthday from me too!

If their drive was working properly then the system would know it's there and ImgBurn would pick it up. Why don't you try Virtual CloneDrive. You can get the latest beta (which is the one to be using) from over at the slysoft forums.

That or you've got an old version of DAEMON Tools installed and it's locking ATAPI.SYS preventing them from installing properly.

Your drive produced a bad burn and the disc doesn't appear to be readable when the drive jumps from layer 0 to layer 1. If it happens again, try burning at a different speed. You have these 'supported' ones to choose from and you've already tried 2.4x.

You already know the answer. Whilst your friend's drive might support 'CMC MAG-D02-00' discs ok, yours doesn't. http://forum.imgburn.com/index.php?showtopic=8000

The speeds the drive is reporting still aren't at all consistent but I guess something is better than nothing

'Physical Object Name' would suggest it's on the JMicron port. JMicron drivers can be found here: ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/ Make sure your motherboard bios is up-to-date as that'll no doubt update the JMicron bios too.

Burn + verify the (now confirmed 'ok') image using Write mode. If it all checks out ok then you know it's 100% readable in your drive and the only thing stopping it from booting is the machine (motherboard/bios/whatever) itself.