04713: c3_telly: chdman not extracting hd images

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04713	Core	Minor	Always	Mar 1, 2012, 09:13	Mar 1, 2012, 19:46

Tester	JWallace	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	No change required	OS	Windows Vista/7 (32-bit)
Status [?]	Closed			Driver
Version	0.145u3	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	04713: c3_telly: chdman not extracting hd images
Description	Out of curiosity, I tried extracting the telly.chd image currently in MAME to and SD card to look at the file structure within. I'm not sure if the image itself is a bad dump, or there's an issue with the extraction logic, but when I run the extraction I get this error, part of the way through the extraction: C:\compile\mamesrc>chdman extracthd -f -i C:\mame\adds\c3_telly\telly.chd -o \\.\PHYSICALDRIVE1 chdman - MAME Compressed Hunks of Data (CHD) manager 0.145u3 (Feb 29 2012) Output File: \\.\PHYSICALDRIVE1 Input CHD: C:\mame\adds\c3_telly\telly.chd Error writing to file; check disk space (\\.\PHYSICALDRIVE1) The image itself generates a 258Mb Fat partition, and allocates the same amount as a blank partition, seemingly splitting the actual space needed to complete the extraction into towo, and not allowing enough to be useful.
Steps To Reproduce	Obtain telly.chd (belongs to set c3_telly) Extract using latest CHDMAN to external drive or VHD. chdman extracthd -f -i C:\path\to\c3_telly\telly.chd -o \\.\PHYSICALDRIVEn Where n is the drive number the extraction is going to Error results
Additional Information	I have tried extracting this image with earlier CHDMAN builds (0.135) prior to the recent changes with the same result, but am unsure as to whether this is a set only thing or a wider problem due to lack of resources for testing.
Github Commit

Flags
Regression Version
Affected Sets / Systems	c3_telly

Attached Files

No.08303 Firewave Senior Tester Mar 1, 2012, 11:26	Extracting to a file works, but the output file is way bigger than 258 MB: 01.03.2012 12:26 541.065.216 out.chd That matches the info of the CHD: Logical size: 541,065,216 bytes I used a v4 CHD. I wonder if you used a v4 or a v5 one.
No.08311 JWallace Developer Mar 1, 2012, 19:45 edited on: Mar 1, 2012, 19:48	Worked when I used an uninitialised drive that's totally fresh and without any previous partition on it. This time 'two' FAT partitions are generated, one containing the core files, one containing additional video for questions etc. Basically, based on the additional tests, this is probably a Windows issue rather than a CHDMAN issue, and it freaking out trying to allocate two partitions in one. Unless CHDMAN is meant to overwrite all existing partition data on force?

No.08303

Firewave

Senior Tester

Mar 1, 2012, 11:26

Extracting to a file works, but the output file is way bigger than 258 MB:

01.03.2012 12:26 541.065.216 out.chd

That matches the info of the CHD:

Logical size: 541,065,216 bytes

I used a v4 CHD. I wonder if you used a v4 or a v5 one.

No.08311

JWallace

Developer

Mar 1, 2012, 19:45

edited on: Mar 1, 2012, 19:48

Worked when I used an uninitialised drive that's totally fresh and without any previous partition on it.

This time 'two' FAT partitions are generated, one containing the core files, one containing additional video for questions etc.

Basically, based on the additional tests, this is probably a Windows issue rather than a CHDMAN issue, and it freaking out trying to allocate two partitions in one.

Unless CHDMAN is meant to overwrite all existing partition data on force?