Shadowsoul

Seems that was the problem, disabled AnyDVD and it works flawlessly. Thanks a ton for the answer, didn't think that would be a problem when only verifying.

Just wanted to ask people that probably know alot more than i do about burning so here goes: When burning DVD:s on my old trustworthy NEC ND1300A (flashed with herries RPC-1 region free firmware from ages ago) everything works fine until i try to verify the burn, it always fails due to some expected value that are wrong at the same offset. Always at the same position, no matter what media. Anyone know if it's the writer that's slowly dying or if it's just some other thing? Burning straight from .ISO/.IMG or using an .MDF makes no difference at all. Any help/ideas are welcome, don't want to throw away the burner if the errors aren't really errors (the discs seem to read fine just watching them, just not sure if the errors are serious in any other way). Cheers, Linus ImgBurn reports File 1 (Verbatim MCC003 8x DVD+R): _NEC DVD_RW ND-1300A 1.07 (ATA) Current Profile: DVD+R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 2 289 024 Size: 4 687 921 152 bytes Time: 508:42:24 (MM:SS:FF) Physical Format Information (Last Recorded): Disc ID: MCC-003-00 Book Type: DVD+R Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196 608 Last Physical Sector of Data Area: 2 485 631 Last Physical Sector in Layer 0: 0 I 23:24:57 ImgBurn Version 1.1.0.0 started! I 23:24:57 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 1) I 23:24:57 Initialising SPTI... I 23:24:57 Searching for SCSI / ATAPI devices... I 23:24:58 Found 2 DVD-ROMs and 1 DVD?RW! I 23:26:12 Operation Started! I 23:26:12 Source Device: [0:3:0] _NEC DVD_RW ND-1300A 1.07 (H:) (ATA) I 23:26:12 Source Media Type: DVD+R (Disc ID: MCC-003-00) (Speeds: 2,4x) I 23:26:12 Image File: G:\VACATION.MDS I 23:26:12 Image File Sectors: 2 289 024 (MODE1/2048) I 23:26:12 Image File Size: 4 687 921 152 bytes I 23:26:12 Image File Implementation Identifier: Spruce Technologies I 23:26:12 Verifying Sectors... E 23:28:01 Miscompare at LBA: 165484, Offset: 56 E 23:28:01 Device: 0x00 E 23:28:01 Image File: 0xC0 E 23:28:01 Failed to Verify Sectors! E 23:28:04 Operation Failed! - Duration: 00:01:51 I 23:28:04 Average Verify Rate: 3 064 KB/s (2.2x) - Maximum Verify Rate: 3 363 KB/s (2.4x) File 2 (Traxdata Ritek G04 DVD-R): _NEC DVD_RW ND-1300A 1.07 (ATA) Current Profile: DVD-R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 2 294 976 Size: 4 700 110 848 bytes Time: 510:01:51 (MM:SS:FF) Pre-recorded Information: Manufacturer ID: RITEKG04 Recording Management Area Information: _NEC DVD_RW ND-1300A Physical Format Information (Last Recorded): Book Type: DVD-R Part Version: 5 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196 608 Last Physical Sector of Data Area: 2 491 583 Last Physical Sector in Layer 0: 0 I 23:31:55 Operation Started! I 23:31:55 Source Device: [0:3:0] _NEC DVD_RW ND-1300A 1.07 (H:) (ATA) I 23:31:55 Source Media Type: DVD-R (Disc ID: RITEKG04) (Speeds: 2x; 4x) I 23:31:55 Image File: G:\050812_FINALS.MDF I 23:31:55 Image File Sectors: 2 294 976 (MODE1/2048) I 23:31:55 Image File Size: 4 700 110 848 bytes I 23:31:55 Image File Implementation Identifier: Spruce Technologies I 23:31:55 Verifying Sectors... E 23:33:36 Miscompare at LBA: 137875, Offset: 56 E 23:33:36 Device: 0x00 E 23:33:36 Image File: 0xC0 E 23:33:36 Failed to Verify Sectors! E 23:33:38 Operation Failed! - Duration: 00:01:42 I 23:33:38 Average Verify Rate: 2 757 KB/s (2.0x) - Maximum Verify Rate: 2 866 KB/s (2.1x)

2.0 should be able to handle 1.1 and 1.0-based applications as well afaik Shouldn't really matter if you don't run a seriously out of date system though as .NET 1.0 and 1.1 is part of the different servicepacks released (and even integrated in Win2k3 base). Look in C:\Windows\Microsoft.NET\Framework\ (or whereever you have installed windows) and you should see what exakt versions you have installed (in the form of different folders) And it really shouldn't affect performance in any way, it's only called if an application that uses it is run (and even then it's just a wrapper around the normal WinAPI with some added bonuses that really shouldn't affect the system)