ggbal

I used RW disc. So it is not write once. What I tried to do is use exact same computer, same burner, same bios setting, same os/patch, same driver, same disc, and same files to burn using different burner software. I am not saying ImgBurn is worse than others. In fact, it is the best I tried so far. I just wanted to point out that in the exact situation (granted you can not do that in the exact time, but who can?), two different software yielded different result. One succeeded and one failed. Now from engineering perspective, it could be one of the windows update conflicts with ImgBurn, or something wrong with my hardware or software that makes ImgBurn stop working. That's fine. But it seems to me, somehow, CDBurnerXP can work or can ignore whatever conflicts the software has. BTW, I have to use CDBurnerXP now (to answer your first question). Not because it is better. It just because ImgBurn stops work and CDBurnerXP works. How innocent it is! Again, I didn't try to say ImgBurn sucks. I would say it is a very good software. It is just somehow not working in my environment when others can. And I have CS MS as well. So at least I am not a total idiot. :-) I just don't have media with other manufacture now. If I do, I certainly want to test. But again, if that works, it only indicates ImgBurn has some problem dealing with my current media in my current environment. Still didn't solve the problem. In terms of BIOS setting, I didn't do it just because I have other stuff on that SATA controller. Not sure changing setting will impact those device. Besides, I have workaround, i.e. using CDBurnerXP. The opportunity cost for me do all other try out is too high at this moment. I still want to use ImgBurn though. But I guess I have to try it for every new release to see whether that problem will go away.

Disc is not the problem. I changed multiple discs and didn't solve the problem. Firmware is SB03. Questions is why CBurnerXP can do it in the same machine on the same disc?

Why IDE? It is in the SATA channel.

Just tried, didn't work. Same problem.

Updated following to the latest: 1. SATA controller/chipset driver 2. ImgBurn to 2.5.0 3. firmware to latest 4. Vista to SP2 Then I tried. But I still got the same hanging as described in my original post. I wanted to make sure it is not something wrong with my burn. So I installed CDBurnerXP in the same machine and used it to burn the same DVD. It worked just fine. So it seems that ImgBurn has some thing to do with it to make the program hanging during writing sectors.

Thanks for replying. I have already used 2.5.0.0. In fact, I initially found the problem when I used 2.5.0.0 a couple of weeks ago. Then I revert to 2.4.4.0 to see whether the problem is there as well. So latest version doesn't solve this problem. On SATA controller driver, I am using Vista SP1 with all critical updates. I don't remember that I specifically installed a SATA driver, so it must be the one that Vista has. How do I get the updated drivers for the SATA controller? Thanks, GG

I have been using ImgBurn for years. It worked fine until a week ago. It now almost always hangs while in writing sectors. It could happen any place when 1%, 5%, or 25% is completed. It hangs on both 2.4.4 and 2.5.0. Please see log below. Looking for help. Here is the log from latest instance: I 22:25:42 ImgBurn Version 2.4.4.0 started! I 22:25:42 Microsoft Windows Vista Home Premium Edition (6.0, Build 6001 : Service Pack 1) I 22:25:42 Total Physical Memory: 3,142,876 KB - Available: 1,883,860 KB I 22:25:43 Initialising SPTI... I 22:25:43 Searching for SCSI / ATAPI devices... I 22:25:43 Found 1 DVD