LIGHTNING UK!

One is made by Lite-On and the other is made by Optiarc. This has nothing to do with ImgBurn and therefore doesn't belong in the 'ImgBurn Support' section.

Stop asking to be spoon fed everything and do your own research. It takes 2 seconds to find the answers to most questions using Google.

You can already get ImgBurn to display the MD5 of an image it creates by reading a disc or whatever. Tools -> Settings -> General -> Page 2 -> Calculate MD5 Hash Values. The values then get written to the log window.

Sorry but I need to see the log.

I'm still not seeing that email?

You don't delete it, you have to uninstall it properly. Did you use the installer as linked to in post # 3? ImgBurn will continue to display that message if the registry entries don't get cleaned up properly.

Use the one in the program's 'About' box (off the 'Help' menu). Thanks.

Do bare in mind that in you remove the SPTD driver without also removing the program that installed it in the first place (normally DAEMON Tools), said program may cease to function - at all or just in the same way (i.e. less functionality).

To make it ready for a special type of burn. Normally you wouldn't ever do it.

ImgBurn relies on DirectShow for all audio decoding, and that relies on various filters installed on the system. As you're only doing MP3, those filters would normally be built into Windows so I can't even really tell you to try a different one! The MP3 filters (especially old ones in XP) sometimes have problems with metadata (cover art etc). The also don't like mono files. What are the properties of the files that don't work? Examine one such MP3 in MediaInfo and let us know what it says - or upload a problem file / email it to me so I can check it myself. You can search/Google for the SPTD thing, it's been answered several times before.

That's different, it's not erasing it, it's just formats it to enable spare areas and defect management.

ImgBurn is a GUI app. The command line stuff is a bonus and should be treated as such.

How can you be confused?! CD-R, DVD-R, DVD+R and BD-R *cannot* be erased and therefore you can only write to them once. CD-RW, DVD-RW, DVD+RW and BD-RE *can* be erased and therefore you can write to them several times.

If you board is anything like all the other ones around these days, you'll have 6 ports on that Intel controller. 2 of those are normally the SATA 3 (6Gbps) ones and the other 4 are SATA 3 (3GBps). Obviously you want the SSD on the primary SATA 3 - Port 0 or whatever. Then stick the hdds on Ports 1 and 2. The burners then follow on Ports 3, 4 and 5.

This isn't a suggestion (is it?) so I'm not sure why you posted it in the 'Suggestions' forum? You'd be MD5'ing all of the sectors on the disc. They start from LBA 0 and run until 1 less than what's show for the size of the disc (The 'Sectors' value under 'Disc Information' in the box on the right). So if that 'Sectors' value said 10, you'd read sectors (LBA) 0 - 9.

Ah it was on a different controller was it? I figured you had all of them on the Intel one I assume you're on the latest bios for the motherboard and the latest Intel Rapid Storage Tech drivers? They're all things that could help out.

Just add 'DVD+R DL' to the list and pick a speed for it.

Ah yes, oops. There's actually code in there to stop it from auto calculating. I'm sure I put it there for a good reason at the time, so I'll leave it where it is. btw, your forum email address is dead. I keep getting 'mail delivery failed' reports for the subscription emails the board is trying to send you.

If you like auto calculate, why not just enable the checkbox in the GUI?

I'd have expected it to be caching/buffering in memory (non swap file regions only), not anywhere else. Your SSD should be quite safe. Did you reinstall when you put the SSD in? If it worked ok before with 3, maybe you had already enabled that option? It could also be something with the drivers you're now running. Don't forget that the speed of drives trails right off as they fill up (as seen in your screenshot), so make sure you defrag the drive to ensure all the data is as close to the start of the drive as possible.

http://forum.imgburn.com/index.php?showtopic=12200

Well, you wouldn't normally want the OS to buffer/cache a 4, 8. 25 or 50GB file as you burn it to disc. It zaps the machine of resources that are better used elsewhere. Not only that, as you're typically only reading it once from start to end, it's fairly pointless. So for that reason, it's disabled by default. The option basically controls whether or not the program sets the 'FILE_FLAG_NO_BUFFERING' flag when calling the 'CreateFile' Windows API function (which it does to open files for reading/writing).

That's due to bad file association on your system. It's a normal ISO. ISO has once upon a time been associated with WinRAR, but then VLC has taken over but you've got some WinRAR leftovers (i.e. the file type description)

It already can.

I guess you have to assume your hdd can't cope with the 3 simultaneous transfers. Is it quick in its own right? Do a transfer rate test in HD Tune Pro or something. See what happens if you enable the 'Reading - Always Use Buffered I/O' option on the I/O tab in the Settings and try to burn another 3 images/discs in Write mode with 'Test Mode' enabled.