CDF - Revision history

Orin at 02:48, 25 January 2023

2023-01-25T02:48:40Z

← Older revision		Revision as of 02:48, 25 January 2023
Line 26:		Line 26:
	The only issue may be certain sectors that are in a different mode so the data portion of the sector may be a different length. Scanning a raw dump of the disc might work out better as certain data types such as FMV or audio		The only issue may be certain sectors that are in a different mode so the data portion of the sector may be a different length. Scanning a raw dump of the disc might work out better as certain data types such as FMV or audio
	may use this other CD-XA mode so the structure of the sector is different. My tool will need to be able to handle both paths. One where you scan the CDF directy but may have to skip any file types that require sectors with data greater than 2048 and one that can scan a bin file and handle those special cases. I still need to find an index for the game. The HED file and PE_DISK.01 and .02 are byte-for-byte identical on each disc.		may use this other CD-XA mode so the structure of the sector is different. My tool will need to be able to handle both paths. One where you scan the CDF directy but may have to skip any file types that require sectors with data greater than 2048 and one that can scan a bin file and handle those special cases. I still need to find an index for the game. The HED file and PE_DISK.01 and .02 are byte-for-byte identical on each disc.

			TEMP: 2023/1/24
			Some additional notes before a re-write. The structure of the index for these are not based on the LBA of the disc but offsets are based location inside the file itself. STAGE0 and it's separate header index entries start from 0 for example. Others have the header embedded at the start of the file. There is more than just normal indexes as there may be folders and then a separate list of files that may be listed as streaming. This requires more looking into but could be due to streaming may be video related that may use a different reading mode and sector size.


	== See Also ==		== See Also ==
	[[HED]]		[[HED]]

Orin at 03:12, 30 July 2018

2018-07-30T03:12:51Z

← Older revision		Revision as of 03:12, 30 July 2018
Line 4:		Line 4:

	Note: Formats are aligned to sectors. Any change to files may require full rebuild of whole image. This is typical of PS1 games.		Note: Formats are aligned to sectors. Any change to files may require full rebuild of whole image. This is typical of PS1 games.

	~~{\| class="wikitable"~~
	~~!colspan="15"\|Disk 1 (SLUS-01042)~~
	\|-
	~~! LBA !! Name !! Description~~
	\|-
	~~\| 0000023 \|\| SYSTEM.CNF \|\| PS specific~~
	\|-
	~~\| 0000024 \|\| PE_DISK.01 \|\| Unknown if used (watermark/signature?)~~
	\|-
	~~\| 0000025 \|\| SLUS_010.42 \|\| Program~~
	\|-
	~~\| 0000204 \|\| INIT.BS \|\| "Published by..." image.~~
	\|-
	~~\| 0000210 \|\| STAGE0.HED \|\| Header? Possibly some LBA locations~~
	\|-
	~~\| 0000214 \|\| STAGE0.CDF \|\| Data archive?~~
	\|-
	~~\| 0030255 \|\| STAGE1.CDF \|\| Data archive. Has soundless STR~~
	\|-
	~~\| 0075564 \|\| STAGE2.CDF \|\| Data archive Has soundless STR~~
	\|-
	~~\| 0100127 \|\| STAGE3.CDF \|\| Data archive~~
	\|-
	~~\| 0117576 \|\| INTER0.STR \|\| All FMV with sound.~~
	\|-
	~~\| 0225526 \|\| DUMMY.DMY \|\| Dummy file that is actually a video not related to the game.~~
	\|}

	There may be a pattern for how files are stored and accessed. At the start of each sector, after the CD-XA header, if the sector is the start of a new file, there will be 16-bytes in front of it first. First 4-bytes with a random number. Then a single byte which represents how many sectors this file will occupy. The rest is zeroed out. With this, I was able to write a program that would go sector-by-sector looking for this header than matched. I was able to extract 1,049 background images in full.		There may be a pattern for how files are stored and accessed. At the start of each sector, after the CD-XA header, if the sector is the start of a new file, there will be 16-bytes in front of it first. First 4-bytes with a random number. Then a single byte which represents how many sectors this file will occupy. The rest is zeroed out. With this, I was able to write a program that would go sector-by-sector looking for this header than matched. I was able to extract 1,049 background images in full.

Orin at 03:12, 30 July 2018

2018-07-30T03:12:42Z

← Older revision		Revision as of 03:12, 30 July 2018
Line 1:		Line 1:
	[[Category:Archives]]		[[Category:Archives]]
	Used in the following games:		Used in the following games:
	* Parasite Eve 2 (PSX)		* [[Parasite Eve II]] (PSX)

	Note: Formats are aligned to sectors. Any change to files may require full rebuild of whole image. This is typical of PS1 games.		Note: Formats are aligned to sectors. Any change to files may require full rebuild of whole image. This is typical of PS1 games.

Orin at 18:12, 5 March 2018

2018-03-05T18:12:24Z

← Older revision		Revision as of 18:12, 5 March 2018
Line 51:		Line 51:
	\|}		\|}

	~~Random Hints~~...		Temp: 2018/03/05 From what I have gathered, CDF does not have any type of index in itself however each entry has an identifier at the start of the data portion of the sector that is 16 bytes in length. This contains a unique identifier that is used to determine the content type followed by at least 1 byte that indicates how many frames the data occupies. This goes along with my original findings long ago but now it seems more clear.
			The only issue may be certain sectors that are in a different mode so the data portion of the sector may be a different length. Scanning a raw dump of the disc might work out better as certain data types such as FMV or audio
	~~hSPK hONE~~		may use this other CD-XA mode so the structure of the sector is different. My tool will need to be able to handle both paths. One where you scan the CDF directy but may have to skip any file types that require sectors with data greater than 2048 and one that can scan a bin file and handle those special cases. I still need to find an index for the game. The HED file and PE_DISK.01 and .02 are byte-for-byte identical on each disc.

	== See Also ==		== See Also ==
	[[HED]]		[[HED]]

Orin at 19:52, 4 March 2018

2018-03-04T19:52:26Z

← Older revision		Revision as of 19:52, 4 March 2018
Line 42:		Line 42:
	\| 05FF0008 \|\| BS Format (Backgrounds) \|\| ? \|\| ?		\| 05FF0008 \|\| BS Format (Backgrounds) \|\| ? \|\| ?
	\|-		\|-
	\| 07FF0008 \|\| ~~Unknown~~ \|\| ? \|\| ?		\| 07FF0008 \|\| String (1byte)? \|\| ? \|\| ?
	\|-		\|-
	\| 02010008 \|\| Unknown \|\| ? \|\| ?		\| 02010008 \|\| Unknown \|\| ? \|\| ?
Line 50:		Line 50:
	\| 06010008 \|\| Unknown \|\| ? \|\| ?		\| 06010008 \|\| Unknown \|\| ? \|\| ?
	\|}		\|}

			Random Hints...

			hSPK hONE

	== See Also ==		== See Also ==
	[[HED]]		[[HED]]

Orin at 20:50, 25 September 2016

2016-09-25T20:50:05Z

← Older revision		Revision as of 20:50, 25 September 2016
Line 50:		Line 50:
	\| 06010008 \|\| Unknown \|\| ? \|\| ?		\| 06010008 \|\| Unknown \|\| ? \|\| ?
	\|}		\|}

			== See Also ==
			[[HED]]

Orin at 03:08, 27 July 2016

2016-07-27T03:08:57Z

← Older revision		Revision as of 03:08, 27 July 2016
Line 38:		Line 38:
	!colspan="15"\|File Formats		!colspan="15"\|File Formats
	\|-		\|-
	! Value !! Temp		! Value !! Temp !! Occurrences (Disk1) !! Occurrences (Disk2)
	\|-		\|-
	\| 05FF0008 \|\| BS Format (Backgrounds)		\| 05FF0008 \|\| BS Format (Backgrounds) \|\| ? \|\| ?
	\|-		\|-
	\| 07FF0008 \|\| Unknown		\| 07FF0008 \|\| Unknown \|\| ? \|\| ?
	\|-		\|-
	\| 02010008 \|\| Unknown		\| 02010008 \|\| Unknown \|\| ? \|\| ?
	\|-		\|-
	\| 01010008 \|\| Unknown		\| 01010008 \|\| Unknown \|\| ? \|\| ?
	\|-		\|-
	\| 06010008 \|\| Unknown		\| 06010008 \|\| Unknown \|\| ? \|\| ?
	\|}		\|}

Orin at 02:57, 27 July 2016

2016-07-27T02:57:30Z

← Older revision		Revision as of 02:57, 27 July 2016
Line 50:		Line 50:
	\| 06010008 \|\| Unknown		\| 06010008 \|\| Unknown
	\|}		\|}

	May have figured out the pre-file header stuff that appears before the *.BS files. Not sure what the 05FF0008 part is yet but the number after that, that single byte, may be a number used to tell how many sectors this file uses. This should fix my auto extractor from having to guess the length of the data.

Orin at 02:57, 27 July 2016

2016-07-27T02:57:07Z

← Older revision		Revision as of 02:57, 27 July 2016
Line 47:		Line 47:
	\|-		\|-
	\| 01010008 \|\| Unknown		\| 01010008 \|\| Unknown
			\|-
			\| 06010008 \|\| Unknown
	\|}		\|}

	May have figured out the pre-file header stuff that appears before the *.BS files. Not sure what the 05FF0008 part is yet but the number after that, that single byte, may be a number used to tell how many sectors this file uses. This should fix my auto extractor from having to guess the length of the data.		May have figured out the pre-file header stuff that appears before the *.BS files. Not sure what the 05FF0008 part is yet but the number after that, that single byte, may be a number used to tell how many sectors this file uses. This should fix my auto extractor from having to guess the length of the data.

Orin at 02:55, 27 July 2016

2016-07-27T02:55:51Z

← Older revision		Revision as of 02:55, 27 July 2016
Line 45:		Line 45:
	\|-		\|-
	\| 02010008 \|\| Unknown		\| 02010008 \|\| Unknown
	\| -		\|-
	\| 01010008 \|\| Unknown		\| 01010008 \|\| Unknown
	\|}		\|}

	May have figured out the pre-file header stuff that appears before the *.BS files. Not sure what the 05FF0008 part is yet but the number after that, that single byte, may be a number used to tell how many sectors this file uses. This should fix my auto extractor from having to guess the length of the data.		May have figured out the pre-file header stuff that appears before the *.BS files. Not sure what the 05FF0008 part is yet but the number after that, that single byte, may be a number used to tell how many sectors this file uses. This should fix my auto extractor from having to guess the length of the data.