adamordan

It's not file specific. It could be any kind of data on my HFS partition: MP3s, JPEGs, text files, DVD-Video structures, you name it Also it can be single files or complete directory hierarchies. As you can see in the attached image, all file properties are correct. At first I thought maybe it has something to do with buffered/unbuffered I/O but changing the setting doesn't help. In the mean time I've installed the driver on my laptop PC and attached an external HFS formatted drive, and the same thing happens there, so I guess the driver and ImgBurn simply don't like each other But the mystery is why only in build mode

Here it is: I 23:50:40 ImgBurn Version 2.5.0.0 started! I 23:50:40 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 23:50:40 Total Physical Memory: 3,126,064 KB - Available: 2,745,684 KB I 23:50:40 Initialising SPTI... I 23:50:40 Searching for SCSI / ATAPI devices... I 23:50:40 Found 1 DVD±RW! I 23:51:02 Operation Started! I 23:51:02 Building Image Tree... I 23:51:03 Checking Directory Depth... I 23:51:03 Calculating Totals... I 23:51:03 Preparing Image... I 23:51:03 Checking Path Length... I 23:51:03 Contents: 13 Files, 0 Folders I 23:51:03 Content Type: Data I 23:51:03 Data Type: MODE1/2048 I 23:51:03 File System(s): ISO9660, Joliet I 23:51:03 Volume Label: [Not Configured] I 23:51:03 Size: 150,286,336 bytes I 23:51:03 Sectors: 73,382 I 23:51:03 Image Size: 150,339,584 bytes I 23:51:03 Image Sectors: 73,408 I 23:51:03 Operation Successfully Completed! - Duration: 00:00:00 I 23:51:18 Operation Started! I 23:51:18 Building Image Tree... I 23:51:20 Checking Directory Depth... I 23:51:20 Calculating Totals... I 23:51:20 Preparing Image... I 23:51:21 Checking Path Length... I 23:51:21 Contents: 13 Files, 0 Folders I 23:51:21 Content Type: Data I 23:51:21 Data Type: MODE1/2048 I 23:51:21 File System(s): ISO9660, Joliet I 23:51:21 Volume Label: X&Y I 23:51:21 Size: 150,286,336 bytes I 23:51:21 Sectors: 73,382 I 23:51:21 Image Size: 150,339,584 bytes I 23:51:21 Image Sectors: 73,408 I 23:51:23 Operation Successfully Completed! - Duration: 00:00:04 I 23:51:23 Operation Started! I 23:51:23 Image Contents: 13 Files, 0 Folders I 23:51:23 Image Sectors: 73,408 (MODE1/2048) I 23:51:23 Image Size: 150,339,584 bytes I 23:51:23 Image Volume Identifier: X&Y I 23:51:23 Image Volume Set Identifier: UNDEFINED I 23:51:23 Image Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER! I 23:51:23 Image Implementation Identifier: ImgBurn v2.5.0.0 I 23:51:23 Image File System(s): ISO9660, Joliet I 23:51:23 Destination File: C:\Documents and Settings\Adam\Desktop\X&Y.ISO I 23:51:23 Destination Free Space: 30,688,538,624 Bytes (29,969,276 KB) (29,266 MB) (28 GB) I 23:51:23 Destination File System: NTFS I 23:51:23 File Splitting: Auto I 23:51:23 Writing Image... E 23:51:25 Operation Failed! - Duration: 00:00:02 E 23:51:25 Average Write Rate: N/A - Maximum Write Rate: N/A I'm using 2.5.0.0, but it's the same with 2.5.1.0

I'm using ImgBurn on a Bootcamp partition on my Mac, System is XP SP3. I can read files from the HFS+ OS X partition using a read only HFS driver that Apple has provided for Bootcamp users. ImgBurn has an issue in build mode when building images or burning to disc files which are located on the HFS partition. Immediatly in the beginning of the process I get the following error: "Cannot read from file:..... Reason: Reached the end of the file." and the process fails (See attachment). The strange thing is that this only happens in build mode, write mode (burning images or cue sheets of files from the HFS partition) works just fine. Tried to play a bit with the options under I/O tab, didn't help. ImgBurn log does not provide more info. This problem presents itself under XP and under WIN7 so it's not OS realated, other programs on my Windows installation work fine with the driver. It's quite obvious that the it is the HFS driver's fault, it's known to have issues and it is not extremely well written even though it's an official Apple driver, but since most of my stuff is on my Mac partition and ImgBurn is WAY WAY better than all other alternatives (on Mac and Windows) I'd hate giving up using it because of an issue that I'm sure can be resolved... Any solution or workaround would be much appreciated, and thanks for a wonderful app.