hernan

yes, i've tried CD-R, CD-RW, DVD+R and DVD+RW any ideas??? i've searched all over the net, and couldn't find a solution yet

Well the thing is that I could leave it for a day, and it would still be writing the lead-in here's another sample of a log. I have cancelled the process after half an hour to show you, that it's still in the 'writing Leadin' ImgBurn1.txt

sorry missed the F6 thing here's the new log ImgBurn.txt

This is a little weird - it should be empty! There's a way to enable logging of buffer commands during a burn, you have to add a registry entry. Under 'HKCU\Software\ImgBurn', make a DWORD entry called 'OVERRIDE_DeviceBufferWithLogging' and set it's value to 1. Then burn another disc having pressed F8 before you start. The program will log all the buffer status commands sent to the drive. Copy + paste that log (or save + attach if it's huge) When you've done that, delete the registry entry again. Same thing happened. I've attached the log ImgBurn.txt

any ideas of what may be wrong, lightning uk??

Here's the log I 14:20:33 ImgBurn Version 2.3.2.0 started! I 14:20:33 Microsoft Windows Vista Ultimate Edition (6.0, Build 6000) I 14:20:33 Total Physical Memory: 1,047,040 KB - Available: 443,184 KB I 14:20:33 Initialising SPTI... I 14:20:33 Searching for SCSI / ATAPI devices... I 14:20:35 Found 1 DVD-ROM and 1 DVD

here's a sample of a imgburn log I 21:01:43 ImgBurn Version 2.3.2.0 started! I 21:01:43 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 2) I 21:01:43 Total Physical Memory: 1,047,040 KB - Available: 316,328 KB I 21:01:43 Initialising SPTI... I 21:01:43 Searching for SCSI / ATAPI devices... I 21:01:45 Found 1 DVD-ROM and 1 DVD

Well, I'm having exactly the same problem. Device Buffer at 0%, and never moves from there. I'm using Vista, but the 32-bit version. I used to have XP SP2, and had the chance to make a burn, but since having Vista, I could not even make one burn. You could say its Vista, but I'd made a research and found out lots of guys that have Vista, and my drive (Samsung SH-S182M) have it fully functioning. I have the latest firmware also. So, theres some program, o some driver, o i dont know thats causing this. Hope someone who reads this, had the same problem and could solve it, because i really dont want format my pc