Hazza Posted October 7, 2013 Share Posted October 7, 2013 I'm a long-time user of ImgBurn and very happy that there are generous souls who share their excellent efforts with the rest of us - thank you ! I have just created an ISO image file of a video DVD. The DVD was created by my domestic DVD recorder (Panasonic). Doing some checks, I discovered that ImgBurn modified the two IFO files and their associated backup BUP files. I also imaged the disc using another well-respected product, which produced an image identical to the original disc. The modified image produced by ImgBurn plays correctly on my PC (VLC media player) and my streamer. The identical image produced by the other program does not play on either PC or streamer. Windows Media Player plays both images correctly once they have been mounted on a virtual drive. Obviously I'm very pleased that ImgBurn has taken steps to make the image usable. I'm curious to know what it did since it is obviously important to know if there are any wrinkles in the transfer process. I think I saw a fleeting screen message "corrected ...", but unfortunately the log file doesn't shed much light in this instance : I 12:38:09 ImgBurn Version 2.5.8.0 started!I 12:38:09 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)I 12:38:09 Total Physical Memory: 16,775,204 KiB - Available: 13,110,140 KiBI 12:38:09 Initialising SPTI...I 12:38:09 Searching for SCSI / ATAPI devices...I 12:38:09 -> Drive 1 - Info: PIONEER BD-RW BDR-205 1.12-GENERAL (S:) (ATAPI)I 12:38:09 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (T:) (SCSI)I 12:38:09 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE!I 12:41:37 Operation Started!I 12:41:37 Building Image Tree...I 12:41:39 Checking Directory Depth...I 12:41:39 Calculating Totals...I 12:41:39 Preparing Image...I 12:41:40 Checking Path Length...I 12:41:40 Contents: 9 Files, 2 FoldersI 12:41:40 Content Type: DVD VideoI 12:41:40 Data Type: MODE1/2048I 12:41:40 File System(s): ISO9660, UDF (1.02)I 12:41:40 Volume Label: RWC2003_FINALI 12:41:40 IFO/BUP 32K Padding: EnabledI 12:41:40 Region Code: 1, 2, 3, 4, 5, 6, 7, 8I 12:41:40 TV System: PALI 12:41:40 Size: 4,230,295,552 bytesI 12:41:40 Sectors: 2,065,574I 12:41:40 Image Size: 4,230,873,088 bytesI 12:41:40 Image Sectors: 2,065,856I 12:41:43 Operation Successfully Completed! - Duration: 00:00:06I 12:41:43 Operation Started!I 12:41:43 Image Contents: 9 Files, 2 FoldersI 12:41:43 Image Sectors: 2,065,856 (MODE1/2048)I 12:41:43 Image Size: 4,230,873,088 bytesI 12:41:43 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888)I 12:41:43 Image Volume Identifier: RWC2003_FINALI 12:41:43 Image Volume Set Identifier: 43476532001F85BDI 12:41:43 Image Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!I 12:41:43 Image Implementation Identifier: ImgBurnI 12:41:43 Image File System(s): ISO9660, UDF (1.02)I 12:41:43 Destination File: E:\!!__TEMP\DVD_VIDEO_RECORDER.ISOI 12:41:43 Destination Free Space: 29,634,039,808 Bytes (28,939,492.00 KiB) (28,261.22 MiB) (27.60 GiB)I 12:41:43 Destination File System: NTFSI 12:41:43 File Splitting: AutoI 12:41:43 Writing Image...I 12:47:41 Operation Successfully Completed! - Duration: 00:05:57I 12:47:41 Average Write Rate: 11,573 KiB/s (8.6x) - Maximum Write Rate: 16,386 KiB/s (12.1x)I 12:48:40 Close Request AcknowledgedI 12:48:40 Closing Down...I 12:48:40 Shutting down SPTI...I 12:48:40 ImgBurn closed! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 7, 2013 Share Posted October 7, 2013 What you've done there is rebuilt the file system based on the files that were on your source disc (i.e. you used Build mode). That's not the same as making a sector by sector copy of the disc (i.e. using Read mode). It will have corrected a few values in the IFO / BUP files so they were correct based on the new layout of files within the image (sector offsets etc). Link to comment Share on other sites More sharing options...
Hazza Posted October 7, 2013 Author Share Posted October 7, 2013 Thank you for your explanation. I had to use build mode because the recorder somehow created several extra empty tracks on the disc, which ImgBurn (rightly) didn't like. All is now clear ... Link to comment Share on other sites More sharing options...
Recommended Posts