wishfull Posted December 16, 2007 Posted December 16, 2007 The importance of the following for your personal situation is unknown to me. Few weeks ago, burning an image there was a burn error about halfway saying: Address not found- wrong address etc.. Twice successively, one 8.5 and one 4.7gb. Two discs in the waste bin. Before this ImgBurn all in default. Done some checks and in the logs of my software firewall(Outpost) I found: "Outgoing blocked" and more. My firewall blocked ImgBurn/DVDDecrypter complete when burning a disc and when it made an attempt to update or whatever triggered the firewall, perhaps this could have been the problem in the past. First: Changed ImgBurn and DVDDecrypter in trusted progs. Second: I changed the settings of Img in: Events>check for program update>never. For DVDdecrypter: Settings>events>uncheck "check for program update". No errors since. Greetings, Wishfull
LIGHTNING UK! Posted December 16, 2007 Posted December 16, 2007 A burn error would have nothing to do with checking for updates. (In these situations it helps if you provide the real / full error). It should go without saying that if you want the program to check for updates then you need to allow it through your firewall. Likewise, it's silly saying the program can check for updates and then blocking it from doing so at the firewall. That's like someone saying: Sure, you can drive my Ferrari.... but if you get within 10m of it you'll die.
wishfull Posted December 16, 2007 Author Posted December 16, 2007 Attn: Lightning UK Not sure I understand what you are saying? In all my progs, Windows included, the auto update is cancelled and only firewall and anti-vir are allowed. Auto update for Img is not necessary. Last 12-04-2007. In default Img updates every day-week....etc.. Done some adjutment in Img and back to default again, forgot check update to never. In general all my progs are blocked by the firewall for outgoing traffic or changing the registry and other uncommon behaviour, when not trusted or with limited permission to do so. Done a search and found an old Img log. The failure times correspond exactly with the old Outpost logs info times saying update blocked. This is why I thought the firewall/img combination is probably the reason. Since the adjustments in my first post, no more failure. For your info: (This is a log from a 8.5 disc write failure at 54% after a layer change at 50% and ImgBurn in Default) ; ImgBurn Version 2.3.2.0 - Log ; zondag, 14 oktober 2007, 13:11:20 I 12:43:01 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D00-01) (Speeds: 2,4x) I 12:43:01 Destination Media Sectors: 4.173.824 I 12:43:01 Write Mode: DVD I 12:43:01 Write Type: DAO I 12:43:01 Write Speed: MAX I 12:43:01 Link Size: Auto I 12:43:01 Test Mode: No I 12:43:01 BURN-Proof: Enabled W 12:43:03 Optimal L1 Data Zone Start LBA: None Found! (VTS_02) I 12:43:03 Optimal L0 Data Zone Capacity: 1.965.568 I 12:43:03 Optimal L0 Data Zone Method: ECC Block Boundary, VOBU Boundary I 12:43:32 Filling Buffer... (40 MB) I 12:43:33 Writing LeadIn... I 12:43:36 Writing Image... (LBA: 0 - 3924860) I 12:43:36 Writing Layer 0... (LBA: 0 - 1965567) I 13:03:44 Writing Layer 1... (LBA: 1965568 - 3924860) W 13:05:03 Failed to Write Sectors 2090336 - 2090367 - Unknown (Internal Target Failure) (0x44, 0x86) W 13:05:03 Retrying (1 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (2 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (3 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (4 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (5 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (6 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (7 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (8 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (9 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (10 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (11 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (12 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (13 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (14 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (15 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (16 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (17 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (18 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (19 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:05:03 Retrying (20 of 20)... W 13:05:03 Retry Failed - Invalid Address For Write W 13:08:45 Retrying (21)... W 13:08:45 Retry Failed - Invalid Address For Write E 13:08:52 Failed to Write Sectors 2090336 - 2090367 - Unknown (Internal Target Failure) (0x44, 0x86) I 13:08:52 Synchronising Cache... I 13:08:53 Closing Track... I 13:08:58 Finalising Disc... W 13:10:16 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Tracking Servo Failure E 13:10:45 Finalise Disc Failed! - Reason: Tracking Servo Failure I 13:10:45 Finalising Disc (Last Attempt!)... E 13:10:45 Failed to Write Image! E 13:10:45 Operation Failed! - Duration: 00:27:44 I 13:10:45 Average Write Rate: 2.757 KB/s (2.0x) - Maximum Write Rate: 3.360 KB/s (2.4x) I 13:11:20 Close Request Acknowledged I 13:11:20 Closing Down... I 13:11:20 Shutting down SPTI... I 13:11:20 ImgBurn closed! Greetings, Wishfull
volvofl10 Posted December 16, 2007 Posted December 16, 2007 I 12:43:01 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D00-01) (Speeds: 2,4x) theres part of your problem, the discs your using try some verbatim 2.4x (made in singapore) with the MKM 001 dye
LIGHTNING UK! Posted December 16, 2007 Posted December 16, 2007 What I mean is... Either you allow updates (and allow it to pass through the firewall) or you turn updates off. You shouldn't allow updates and then block it, that's just pointless. When you install the program it asks if you want to check for updates so there's really no excuse. The error you've got there is nothing to do with the program checking for updates or not checking for them. The update code runs in it's own thread (in the background) so unless your firewall is corrupting ImgBurn's memory, it wouldn't go anywhere near the other threads doing the burning. The update code is also only called at the moment the program loads - so for it to error out when the drive did, it would have had to have taken over 20 minutes to realise there was a problem. Would the firewall really block the connection in a way that it takes that long to bomb out? What if it wasn't multithreaded - you'd be waiting 20mins for the program to start! If you've always used RICOHJPN-D00-01 media, no wonder you got errors. The quality of that media can vary quite a lot - that's why we only recommend Verbatims for DL burning.
Recommended Posts