LIGHTNING UK!

I can assure you that using task manager to end task on ImgBurn isn't going to corrupt your OS. The sync cache command is processed by the drive and ImgBurn simply waits for it to say it has finished. If yours isn't finishing, either your drive got stuck processing it (doesn't like the discs etc) or your drivers are messing with the response. If the drive is stuck, you'd have to totally power the machine off so it can reset properly. Take the disc out as it powers back up. If it's the drivers, update them. What controller have you attached the drive to? Right click the drive selection drop down box and pick family tree. Close the prompt that comes up and then copy + paste everything from the log window please.

Not unless that player can play avi files too, no. Use Dvd flick or ConvertXtoDVD to convert to the proper dvd video format.

Ah sorry, that's my fault then. The 3 attachments aren't spaced out when viewing your post via tapatalk on my phone. I clicked on the middle of a long blue attachment link and it was the ibg file. The log shows it burnt and verified ok, so you've nothing to worry about. All data is present and correct.

Do the logs from both look the same? I have no experience of burning such a CD so I'm afraid I can't really help.

It's probably off your screen somewhere. You can uninstall and reinstall to fix it, or close ImgBurn, open regedit, navigate to 'HKCU\Software\ImgBurn' and delete the log window position value.

The file you've posted there is the graph data file, can you upload the log instead please? The pink box at the top has a link to a guide on log files.

I believe it defaults to moving the dvd video folders to the start, so yes, it would be burning them to the first layer. Don't forget layers on a double layer disc aren't as large as a single layer disc.

Is the ini file configured to run it in portable mode?

This isn't an ImgBurn issue. Does the tray of your drive actually eject?

Truncate writes as much as the disc reports it will hold. Overburn tries to write the entire image. Your drive will error out when the program asks it to write beyond the end of the disc, it won't damage itself.

I'm sure that once you sort out your drivers, everything will work as intended. Which version of IRST do you have installed?

You're losing the real error there, probably due to the drivers being used for the controller. You did well by putting the drive on the Intel one though, that's where it belongs. Try in safe mode and see if you get a different message.

What's the message in the status bar at that point?

If powering it off and on doesn't work, the drive has probably died. Test mode wouldn't cause that, it's just a co-incidence that it's died. Even the more up-to-date 103D firmware dates back to 2006, so it's had a pretty good run. http://www.firmwarehq.com/NEC/ND-6650A/files.html

I don't really understand. If your path in the ini is relative (and assuming it never gets overwritten), I don't see how it would know to point to any previous drive letter etc.

You probably need to edit the settings ini file directly for that.

You're using rubbish 'UME' discs. Buy the Verbatim MKM-003-00 ones that everywhere tells you to use.

You did 'Verify' too yes, not just burnt? Drives often appear to burn successfully (no error reported during 'Write' phase) but produce unreadable discs (error reported during 'Verify' phase).

That image is too small for SAO mode burning on most drives. Change the Write Type to TAO, burn it and then change it back to SAO.

This is not an xbox support forum.

If it works, it works. If it doesn't, you'll know to try other discs.

Set the 'Publisher' field to something else on the 'Labels' tab.

You need the MKM-003-00 discs. Import them from elsewhere if you have to. Yes, the default settings work best, that's why they're the defaults!

I'm talking about regular/official LiteOn firmware. http://www.firmwarehq.com/download_2131-file_4L17.EXE.html

Another spindle of MKM-003-00 may work ok. You haven't actually said you've tried another one. Try flashing the drive's firmware again. That may clear things out - assuming the flash util will let you install the same version again.