jeffatrad Posted February 14, 2008 Share Posted February 14, 2008 I am using the new ImgBurn to make UDF 2.5 isos. It fails every time at 63% to 85% of the way through with a "Insufficient system resources exist to complete the requested service". What does this error even mean? I have tons of memory and your process isn't using that much, I have TBs of space left... Link to comment Share on other sites More sharing options...
mmalves Posted February 14, 2008 Share Posted February 14, 2008 Can you please post the log from that attempt? You can find it Help/ImgBurn Logs. Link to comment Share on other sites More sharing options...
jeffatrad Posted February 14, 2008 Author Share Posted February 14, 2008 Here you go... ImgBurn.log Link to comment Share on other sites More sharing options...
dontasciime Posted February 14, 2008 Share Posted February 14, 2008 just tried with mine and no problem with udf 2.50 I 20:33:05 ImgBurn Version 2.4.0.0 started! I 20:33:05 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 20:33:05 Total Physical Memory: 3,406,252 KB - Available: 2,893,772 KB W 20:33:05 Drive C:\ (FAT32) does not support single files > 4 GB in size. I 20:33:05 Initialising SPTI... I 20:33:05 Searching for SCSI / ATAPI devices... I 20:33:06 Found 1 DVD-ROM, 1 DVD±RW, 2 DVD±RW/RAMs and 1 BD-RE! I 20:33:26 Operation Started! I 20:33:26 Building Image Tree... I 20:33:26 Calculating Totals... I 20:33:26 Preparing Image... W 20:33:34 Fix VTS Sectors Failed! - Reason: Could not find VIDEO_TS.BUP file. I 20:33:34 Contents: 9 Files, 2 Folders I 20:33:34 Size: 4,684,025,856 bytes I 20:33:34 Sectors: 2,287,122 I 20:33:34 Image Size: 4,684,644,352 bytes I 20:33:34 Image Sectors: 2,287,424 I 20:33:34 Operation Successfully Completed! - Duration: 00:00:08 I 20:33:38 Operation Started! I 20:33:38 Building Image Tree... I 20:33:38 Calculating Totals... I 20:33:38 Preparing Image... I 20:33:39 Contents: 18 Files, 4 Folders I 20:33:39 Size: 10,971,592,704 bytes I 20:33:39 Sectors: 5,357,223 I 20:33:39 Image Size: 10,972,233,728 bytes I 20:33:39 Image Sectors: 5,357,536 I 20:33:39 Operation Successfully Completed! - Duration: 00:00:00 I 20:33:57 Operation Started! I 20:33:57 Building Image Tree... I 20:33:57 Calculating Totals... I 20:33:57 Preparing Image... I 20:33:58 Contents: 27 Files, 6 Folders I 20:33:58 Size: 17,199,718,400 bytes I 20:33:58 Sectors: 8,398,300 I 20:33:58 Image Size: 17,200,381,952 bytes I 20:33:58 Image Sectors: 8,398,624 I 20:33:58 Operation Successfully Completed! - Duration: 00:00:00 I 20:34:28 Operation Started! I 20:34:28 Building Image Tree... I 20:34:28 Calculating Totals... I 20:34:28 Preparing Image... I 20:34:28 Contents: 36 Files, 8 Folders I 20:34:28 Size: 23,538,677,760 bytes I 20:34:28 Sectors: 11,493,495 I 20:34:28 Image Size: 23,539,351,552 bytes I 20:34:28 Image Sectors: 11,493,824 I 20:34:28 Operation Successfully Completed! - Duration: 00:00:00 I 20:34:40 Operation Started! I 20:34:40 Building Image Tree... I 20:34:40 Calculating Totals... I 20:34:40 Preparing Image... I 20:34:40 Contents: 36 Files, 8 Folders I 20:34:40 Size: 23,538,677,760 bytes I 20:34:40 Sectors: 11,493,495 I 20:34:40 Image Size: 23,539,679,232 bytes I 20:34:40 Image Sectors: 11,493,984 I 20:34:40 Operation Successfully Completed! - Duration: 00:00:00 I 20:34:56 Operation Started! I 20:34:56 Building Image Tree... I 20:34:57 Calculating Totals... I 20:34:57 Preparing Image... I 20:34:57 Contents: 36 Files, 8 Folders I 20:34:57 Size: 23,538,677,760 bytes I 20:34:57 Sectors: 11,493,495 I 20:34:57 Image Size: 23,539,679,232 bytes I 20:34:57 Image Sectors: 11,493,984 I 20:34:59 Operation Successfully Completed! - Duration: 00:00:03 I 20:34:59 Operation Started! I 20:34:59 Image Contents: 36 Files, 8 Folders I 20:34:59 Image Sectors: 11,493,984 I 20:34:59 Image Size: 23,539,679,232 bytes I 20:34:59 Image Layer Break Position: 5,746,992 I 20:34:59 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,298,496) I 20:34:59 Image Double Layer Profile: DVD+R DL (Min L0: 0, Max L0: 2,086,912, Media Capacity: 4,173,824) I 20:34:59 Image Volume Identifier: TEST I 20:34:59 Image Volume Set Identifier: 384EA45C00AF61F7 I 20:34:59 Image Application Identifier: ImgBurn v2.4.0.0 I 20:34:59 Image Implementation Identifier: ImgBurn I 20:34:59 Image File System(s): UDF (2.50) I 20:34:59 Destination File: H:\UDF 250 TEST\TEST.iso I 20:34:59 Destination Free Space: 46,138,597,376 bytes (45,057,224 KB) (44,001 MB) (42 GB) I 20:34:59 Destination File System: NTFS I 20:34:59 File Splitting: Auto I 20:34:59 Writing Image... I 20:43:01 Operation Successfully Completed! - Duration: 00:08:01 I 20:43:01 Average Write Rate: 47,792 KB/s (34.5x) - Maximum Write Rate: 61,413 KB/s (44.3x) [edit] I thought you meant building. I posted without looking at your log ImgBurn does not copy / read / protected disc's Also it appears you are running out of hard drive space , and remember don't bend down to pick up the soap Link to comment Share on other sites More sharing options...
mmalves Posted February 14, 2008 Share Posted February 14, 2008 I 10:33:25 Destination File: j:\fulldisc2\12 Monkeys HD\12 Monkeys HD.isoI 10:33:25 Destination Free Space: 16,317,937,496,064 bytes (15,935,485,836 KB) (15,561,997 MB) (15,197 GB) I 10:33:25 Destination File System: NTFS I 10:33:25 File Splitting: Auto Your J:\ drive is a network share, right? For some reason Windows doesn't like when you write/read very large files over network shares, and sometimes bombs out the transfer with that message. You may be able to get around this limitation by splitting the image (Tools/Settings/Build/File Splitting) and later using ImgBurn to burn that image from the MDS file. Link to comment Share on other sites More sharing options...
jeffatrad Posted February 14, 2008 Author Share Posted February 14, 2008 I 10:33:25 Destination File: j:\fulldisc2\12 Monkeys HD\12 Monkeys HD.isoI 10:33:25 Destination Free Space: 16,317,937,496,064 bytes (15,935,485,836 KB) (15,561,997 MB) (15,197 GB) I 10:33:25 Destination File System: NTFS I 10:33:25 File Splitting: Auto Your J:\ drive is a network share, right? For some reason Windows doesn't like when you write/read very large files over network shares, and sometimes bombs out the transfer with that message. You may be able to get around this limitation by splitting the image (Tools/Settings/Build/File Splitting) and later using ImgBurn to burn that image from the MDS file. Can't they just retry the read and write a couple times, before bombing out? If this is common, wouldn't it be easier to work around the problem that way? Link to comment Share on other sites More sharing options...
dontasciime Posted February 14, 2008 Share Posted February 14, 2008 http://support.microsoft.com/kb/304101 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 14, 2008 Share Posted February 14, 2008 You ARE (or at least should be) given the option to retry... did you not do so? Link to comment Share on other sites More sharing options...
Recommended Posts