OAF - Revision history

Orin at 21:19, 18 August 2014

2014-08-18T21:19:08Z

← Older revision		Revision as of 21:19, 18 August 2014
Line 32:		Line 32:
	\|}		\|}

			== Research ==
			Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.

	File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o		File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o
Line 37:		Line 39:
	Filenames are null terminated/separated by a 0x00 and might not have any whitespace in the filename/path since looks like they used underscores like most people do. XD		Filenames are null terminated/separated by a 0x00 and might not have any whitespace in the filename/path since looks like they used underscores like most people do. XD

	~~== Research ==~~		There is a little bit of data before or after each data entry. Unsure what it means right now.
	~~Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be~~ a bit ~~tricky but only two ways I can think~~ of ~~this working is it stores the start offset of the file name for a specific~~ entry or it ~~loads all file names into memory~~.

Orin: /* Structure */

2014-08-18T09:18:22Z

Structure

← Older revision		Revision as of 09:18, 18 August 2014
Line 11:		Line 11:
	\| 12Bytes \|\| Unknown \|\| Appears to be same data on all archives		\| 12Bytes \|\| Unknown \|\| Appears to be same data on all archives
	\|-		\|-
	\| 4Bytes \|\| Offset \|\| ~~Start offset~~ for ~~file~~ list		\| 4Bytes \|\| Offset \|\| Offset for filename list
	\|-		\|-
	\| 4Bytes \|\| Unknown(?) \|\| Padding or part of 8 byte number		\| 4Bytes \|\| Unknown(?) \|\| Padding or part of 8 byte number

Orin: /* Structure */

2014-08-18T09:16:42Z

Structure

← Older revision		Revision as of 09:16, 18 August 2014
Line 13:		Line 13:
	\| 4Bytes \|\| Offset \|\| Start offset for file list		\| 4Bytes \|\| Offset \|\| Start offset for file list
	\|-		\|-
	\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number		\| 4Bytes \|\| Unknown(?) \|\| Padding or part of 8 byte number
	\|-		\|-
	\| 4Bytes \|\| File Count \|\| Number of Files inside.		\| 4Bytes \|\| File Count \|\| Number of Files inside.
Line 21:		Line 21:
	! Size !! Content !! Description		! Size !! Content !! Description
	\|-		\|-
	\| 4Bytes \|\| Unknown \|\|		\| 4Bytes \|\| Unknown \|\| No idea what this is... maybe some kind of CRC or hash?
	\|-		\|-
	\| 4Bytes \|\| Offset \|\| File location		\| 4Bytes \|\| Offset \|\| File location
	\|-		\|-
	\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number		\| 4Bytes \|\| Unknown(?) \|\| Padding or part of 8 byte number
	\|-		\|-
	\| 4Bytes \|\| File Size \|\| Size of file(?)		\| 4Bytes \|\| File Size \|\| Size of file(?)

Orin: /* Structure */

2014-08-18T09:16:04Z

Structure

← Older revision		Revision as of 09:16, 18 August 2014
Line 35:		Line 35:
	File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o		File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o

	Filenames are null terminated/separated by a 0x00 and might not have any whitespace in the filename since looks like they used underscores like most people do. XD		Filenames are null terminated/separated by a 0x00 and might not have any whitespace in the filename/path since looks like they used underscores like most people do. XD

	== Research ==		== Research ==
	Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.		Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.

Orin: /* Structure */

2014-08-18T09:15:50Z

Structure

← Older revision		Revision as of 09:15, 18 August 2014
Line 35:		Line 35:
	File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o		File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o

	Filenames are null terminated/separated by a 0x00		Filenames are null terminated/separated by a 0x00 and might not have any whitespace in the filename since looks like they used underscores like most people do. XD

	== Research ==		== Research ==
	Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.		Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.

Orin: /* Structure */

2014-08-18T09:14:22Z

Structure

← Older revision		Revision as of 09:14, 18 August 2014
Line 33:		Line 33:


	~~NOTE! Number might~~ be ~~8 bytes~~ rather than ~~4? 64 bit int~~?		File offsets may just be of a 'long long' data type, which is a 64bit number stored over 8bytes rather than 4bytes of padding. I wonder I could just use as streamoff. That's typedef as long long... right? O.o

	Filenames are null terminated/separated by a 0x00		Filenames are null terminated/separated by a 0x00

Orin: /* Structure */

2014-08-18T09:02:46Z

Structure

← Older revision		Revision as of 09:02, 18 August 2014
Line 34:		Line 34:

	NOTE! Number might be 8 bytes rather than 4? 64 bit int?		NOTE! Number might be 8 bytes rather than 4? 64 bit int?
	Filenames are null terminated/~~sperated~~ by a 0x00
			Filenames are null terminated/separated by a 0x00

	== Research ==		== Research ==
	Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.		Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.

Orin: /* Structure */

2014-08-18T09:02:25Z

Structure

← Older revision		Revision as of 09:02, 18 August 2014
Line 30:		Line 30:
	\|-		\|-
	\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number		\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number
	\|-
	~~!colspan="15"\|Filename Entry~~
	\|-
	~~! Size !! Content !! Description~~
	\|-
	~~\| Size+1Bytes \|\| Filename \|\| null terminated string~~
	\|}		\|}


	NOTE! Number might be 8 bytes rather than 4? 64 bit int?		NOTE! Number might be 8 bytes rather than 4? 64 bit int?
			Filenames are null terminated/sperated by a 0x00

	== Research ==		== Research ==
	Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.		Different from the ones I'm used to. A quick look doesn't show much of a normal index but file names may be stored at the end of the file. This could be a bit tricky but only two ways I can think of this working is it stores the start offset of the file name for a specific entry or it loads all file names into memory.

Orin: /* Structure */

2014-08-18T09:01:52Z

Structure

← Older revision		Revision as of 09:01, 18 August 2014
Line 30:		Line 30:
	\|-		\|-
	\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number		\| 4Bytes \|\| Unknown \|\| Padding or part of 8 byte number
			\|-
			!colspan="15"\|Filename Entry
			\|-
			! Size !! Content !! Description
			\|-
			\| Size+1Bytes \|\| Filename \|\| null terminated string
	\|}		\|}

Orin: /* Structure */

2014-08-18T09:00:33Z

Structure

← Older revision		Revision as of 09:00, 18 August 2014
Line 9:		Line 9:
	! Size !! Content !! Description		! Size !! Content !! Description
	\|-		\|-
	\| 12Bytes \|\| ~~Common~~ \|\| Appears to be same data on all archives		\| 12Bytes \|\| Unknown \|\| Appears to be same data on all archives
	\|-		\|-
	\| 4Bytes \|\| Offset \|\| Start offset for file list		\| 4Bytes \|\| Offset \|\| Start offset for file list