Conqueror

Funny thing is, I've hard people say that use nero for single layer discs and ImgBurn for dual layer. However, I'm getting the opposite results. ImgBurn is working fine with DVD-R discs and problematic with dual layer discs, whereas Nero is now giving me coasters with single layer discs and working fine with dual layer. Why am I the only one having opposite results? I'm gona wait till I get different brand discs.

Yeh, so I'm back after burning a DVD using "Incremental" and "Perform OPC" settings in ImgBurn. First of all, the burn FAILED once again. DVD drive can't even detect the disc and keep looping endlessly trying to detect it, with green light flashing. Secondly, as I have complained HERE, when I woke up, there was no log. The computer was still on but the program was closed because I chose "close program" after burning. I did not choose "shutdown computer". Therefore there was no shutdown process that interfered with log writing, yet log was not written. So I could not find out what the problem was with burn. I wrote the same Image with Nero, and it wrote it first time. Verified it. I even installed the game I was backing up and it worked fine. Nero did warn me before burn that the media isn't in the database and that I should verify after burning. I continued anyway and verified and no problems. Looks like no hope for me with ImgBurn with these DVDs. I'll try again when I buy a new pack of different DVD. Looks like ImgBurn is only good with supported DVDs, whereas other programs like Nero, Windows Image Burner, IsoMagic, MagicIso, Alcohol20% all have no trouble writing unsupported DVDs (yes I have tested all those with the TDK discs I use). So why is ImgBurn the only one having problems?

Yeh, I think I'll save the hassle and start using Verbatim only. I always knew they were best, but still kept getting cheap TDK from a local store since I had always used TDK single layer without any problems. Looks like it's a different story with dual layers. But I heard that even Verbatim have dodgy inferior quality ones. The ones you buy in a spindle.

How can I tell what the actual brand of the media will be before buying the pack, opening them and checking with some tool. The DL disks that I use have the covers 100% like this: http://www.shopneo.co.uk/tdk-ritek-s04-8x-double-layer-dvdr-10-pack-pr-17042.html But as you can see, those are RITEK-S04, whereas mine were CMC MAG-D03.

OK. Thanks.

OK, a lot to reply to. @Lightning UK!, Thanks for the technical info. I see what you're saying. Although the disc created with WIB is finalised. I have checked and confirmed this using discspeed tool. Also, are you saying that some data was not written to the disc using WIB? But I have verified and it's all there. I've even reinstalled the game I was backing from Steam and it worked fine. @Cynthia, Sorry I was wrong. I wasn't aware that there was a new firmware. Last time I check couple of years ago and nothing was out after T06. They released versions TS07 and TS08 one year after TS06, which I missed. Nevertheless, as mmalves pointed out, the new firmware still doesn't support the TDK (CMC MAG-D03) media that I'm using - so says the latest Media Code Speed Edit v1.2.0.5. The list is exactly the same as the one posted in the screenshot by Cynthia. Here's the screenshot for the TS08 firmware that's I'm using now: But I'm surprised that although I've been getting some coasters, I've been able to burn quite a few successfully with programs other than Nero and ImgBurn. Anyways guys. Your responses were different to how they were when i came to this forum, maybe I saw that because I came here with a bad mood after making a lot coasters. I've had time to relax and look at this objectively. Looks like I've been using bad media. Firmware was out of date but even the latest one doesn't make my drive better for dual layer DVDs. Can anyone recommend me some good dual layer DVDs, which are not too costly. Thanks. Oh, and yeh I got the message about incremental write function. I'll try that.

You're wrong there. I had already updated my firmware to latest firmware and I know what speeds my drive supports.

If it was all down to simply burner/firmware/media, then it shouldn't matter what software you use, right? That's what you trying to say aren't you? Then why do someone software give coasters (like ImgBurn) and some burn without problems (like the basic windows disc image burner)? In my generosity and to remove the shadow of doubt, I tried one final test before I abandon this software. Your "colleague" stated that the error was due to the fact that I was burning at 2X when I should be burning at 2.4X. Well that's exactly what I did. I tried burning at 2.4X and guess what? I got an error in the log complaining that I was selected the wrong write speed: But I wasn't stupid enough to continue with the burn and make another coaster. So I cancelled it and used windows disc image burner without problems once again. Like I said, I know that my dual layer TDK DVDs supports 8X, 4X, 2X and 1X. For DVD+R, my drive supports: 16X, 8X, 4X, 2X, 1X So I don't know where this 2.4X number came from in ImgBurn. Looks like I'm the one who should be in the "Beta Team" and not all you lot who come and jump on anyone who complains.

That is exactly what I was going to do after making 6 coasters with ImgBurn. Moving along. But someone tried to label the fault on me, or my media or burner. And now, even you want to have a go at proving that ImgBurn is not the fault. So why are you wasting time? ImgBurn isn't some supernatural flawless software that no one should be "bashing". No software if perfect. if you don't want people to complain about it, then why make this forum? And why discuss about problems if you don't care? So maybe you should not be wasting your time here if you don't like listening to people complaining about ImgBurn. I'm not afraid to call a spade a spade. if I see a fault, I will report it. it doesn't mean I'm bashing ImgBurn or against it. I don't even care. I'm not the owner of Nero or something. It wouldn't matter to me if ImgBurn was great and all others were not. In fact, i would like that. But as current trend is showing, ImgBurn isn't that great. From my experience at least.

I have always burned the same media with 1X or 2X with Nero with the same drive. And they haven't given any coasters. I don't know why ImgBurn is showing 2.4X. Besides, if 2.4 is the speed at which I can ONLY write at, then all other options SHOULD NOT be made available to me. But I don't think that's the problem since I've burned at 2X with other programs. Yes, I have. And no problems with it. I've checked not one or two DVDs, but packs of them. Most of the times I choose "verify" in the programs and always verify myself by physically loading the DVD and installing or browsing images/videos on the DVD from start to end.

If the speed at which you write is wrong, then ImgBurn shouldn't give you the option to write at that speed. I've always written at 2X with other burners without problems. My media supports: 8X 4X 2X 1X Anyway, here's the log, not that it's gona help: ; //****************************************\\ ; ImgBurn Version 2.5.0.0 - Log ; Friday, 04 December 2009, 12:39:07 ; \\****************************************// ; ; I 07:54:56 ImgBurn Version 2.5.0.0 started! I 07:54:56 Microsoft Windows 7 Ultimate Edition (6.1, Build 7600) I 07:54:56 Total Physical Memory: 3,406,968 KB - Available: 2,405,592 KB W 07:54:56 SPTD can have a detrimental effect on drive performance. I 07:54:56 Initialising SPTI... I 07:54:56 Searching for SCSI / ATAPI devices... I 07:54:56 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM! I 08:12:54 Operation Started! I 08:12:54 Source File: C:\......iso (information removed for privacy reasons) I 08:12:54 Source File Sectors: 4,059,008 (MODE1/2048) I 08:12:54 Source File Size: 8,312,848,384 bytes I 08:12:54 Source File Volume Identifier: ... (information removed for privacy reasons) I 08:12:54 Source File Volume Set Identifier: 492055064920545E I 08:12:54 Source File Application Identifier: NERO BURNING ROM I 08:12:54 Source File Implementation Identifier: AHEAD Nero I 08:12:54 Source File File System(s): ISO9660, Joliet, UDF (1.02) I 08:12:54 Destination Device: [1:0:0] TSSTcorp CD/DVDW SH-S162L TS06 (E:) (ATA) I 08:12:54 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) (Speeds: 2.4x) I 08:12:54 Destination Media Sectors: 4,173,824 I 08:12:54 Write Mode: DVD I 08:12:54 Write Type: DAO I 08:12:54 Write Speed: 2x I 08:12:54 Link Size: Auto I 08:12:54 Lock Volume: Yes I 08:12:54 Test Mode: No I 08:12:54 OPC: No I 08:12:54 BURN-Proof: Enabled I 08:12:56 Book Type Setting: DVD-ROM I 08:12:56 Optimal L0 Data Zone Capacity: 2,029,504 I 08:12:56 Optimal L0 Data Zone Method: ECC Block Boundary I 08:16:38 Set L0 Data Zone Capacity Succeeded! I 08:16:39 Filling Buffer... (40 MB) I 08:16:48 Writing LeadIn... I 08:19:39 Writing Session 1 of 1... (1 Track, LBA: 0 - 4059007) I 08:19:39 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4059007) I 08:19:39 Writing Layer 0... (LBA: 0 - 2029503) I 08:40:11 Writing Layer 1... (LBA: 2029504 - 4059007) W 09:00:18 Failed to Write Sectors 4013120 - 4013151 - Reason: Write Error W 09:00:18 Retrying (1 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (2 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (3 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (4 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (5 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (6 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (7 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (8 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (9 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (10 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (11 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (12 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (13 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (14 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (15 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (16 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (17 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (18 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (19 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 09:00:18 Retrying (20 of 20)... W 09:00:18 Retry Failed - Reason: Invalid Address For Write W 12:33:44 Retrying (21)... W 12:33:44 Retry Failed - Reason: Invalid Address For Write W 12:33:46 Retrying (22)... W 12:33:46 Retry Failed - Reason: Invalid Address For Write W 12:33:47 Retrying (23)... W 12:33:47 Retry Failed - Reason: Invalid Address For Write W 12:33:47 Retrying (24)... W 12:33:47 Retry Failed - Reason: Invalid Address For Write W 12:33:48 Retrying (25)... W 12:33:48 Retry Failed - Reason: Invalid Address For Write W 12:33:48 Retrying (26)... W 12:33:48 Retry Failed - Reason: Invalid Address For Write W 12:33:48 Retrying (27)... W 12:33:48 Retry Failed - Reason: Invalid Address For Write W 12:33:49 Retrying (28)... W 12:33:49 Retry Failed - Reason: Invalid Address For Write W 12:33:49 Retrying (29)... W 12:33:49 Retry Failed - Reason: Invalid Address For Write W 12:33:49 Retrying (30)... W 12:34:04 Retry Failed - Reason: Invalid Address For Write E 12:36:26 Failed to Write Sectors 4013120 - 4013151 - Reason: Write Error E 12:36:26 Next Writable Address: 4012632 I 12:36:26 Synchronising Cache... W 12:36:41 User opted to skip the 'Close Track/Session/Disc' functions. E 12:36:41 Failed to Write Image! I 12:36:41 Exporting Graph Data... I 12:36:41 Graph Data File: C:\Users\...\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CD-DVDW_SH-S162L_TS06_04-DECEMBER-2009_8-12_AM_CMC_MAG-D03-64_2x.ibg (information removed for privacy reasons) I 12:36:41 Export Successfully Completed! E 12:36:41 Operation Failed! - Duration: 04:23:47 I 12:36:41 Average Write Rate: 520 KB/s (0.4x) - Maximum Write Rate: 3,430 KB/s (2.5x) I 12:39:06 Close Request Acknowledged I 12:39:06 Closing Down... I 12:39:07 Shutting down SPTI... I 12:39:07 ImgBurn closed!

I'm sick and tired of ImgBurn giving me coasters after coasters. I use 8x TDK DVDs and burn them at 2x with ImgBurn. Out of every 10 dual layer DVDs, 6 burns fail with ImgBurn. Before, you say it's bad media or something wrong with my PC, every time I try to burn the same image with built in Windows Disc Image Burner, it succeeds. FIRST TIME. EVERY TIME. See the screens below to see what happens with ImgBurn and what happens with Windows Disc Image Burner. I don't think I will ever use ImgBurn again. Too many bugs and discrepancies. With ImgBurn: With Windows Disc Image Burner:

I can see why you would make a bad programmer. A good program design is one in which every method is loosely coupled and highly cohesive. if you don't know what that means, then you got some reading and learning to do.

I've studied software engineering and one the processes in the software process model is the "Maintenance" phase. This where the developers of the software listen to the customers and correct any bugs or fulfil their requests for extra features. If one leaves this phase out of the software process, then the software that was developed will simply fail and will not attract new customers, or even keep the current ones. Anyway, I'm not here demanding or requesting a change. I simply reported a bug since that's what the developer wants us to do. And the inability to save a log just because a popup had popped up during the execution of the software is definitely a bug and needs to be fixed if the developer is serious in maintaining and attracting "customers" (even though no one is paying for this freeware software.) I have got a copy of Nero that came with my burner. I still chose to use ImgBurn from the success I've heard about it. However, I think that's about to change if everyone keep attacking the person who simply reports a bug that needs to be fixed.

Hi Paladin77, thanks for the reply. In my second post, I had already stated I think the problem was because ImgBurn wasn't given time to write the log before shutting the PC down. So there's no debate here. That issue was closed. I came back after some testing, where I used 3rd party program to shut down the computer to give ImgBurn the time it needs to write the log. However, my tests show that ImgBurn still doesn't write the log properly. This is open to debate since the author had challenge this fact and said that it's impossible for ImgBurn to write a log like that. Since ImgBurn writes the log AFTER it shuts down, then I would agree that if there is an error message waiting to be acknowledged or canceled, then no amount of waiting (or lengthening the process kill time) after ImgBurn completes the burn will fix the bug under discussion. I know for a fact that I opened ImgBurn, opened the autoshutdown program set it up to shutdown 1hr and 15min after the burn completes, since from my experience no burn + verify takes longer than an hour at the speed I write. I enabled the timer and immediately started the burn process. I select "verify", "close program" and "shutdown" for options after completion. I went to sleep when I had made sure that all bars were green and writing had begun. Trust me, no one came to my room. I live alone! lol! And yes I do sleep very late (or early in the morning if you look at it that way! ) - you can see the time of this post in GMT UK time. Thanks for pointing me to the guide though for disabling the warning messages. That should do the trick. However, I feel that it's the author's job to fix this bug and make it bullet proof so that a log is written in any case. How about writing a log as soon as an event occurs. For example, open the program, write a line of log for this session. Start burn, write the log for it. Complete the burn, write the log. Get an error message, write the log. Shut down the program, write the log and THEN close program/shutdown! This would work flawlessly. Of course, the author can choose to ignore this and make the users of ImgBurn's lives miserable!