Talk:DatabasePackedFile - Revision history

GeneralOperationsDirector at 15:08, 7 October 2010

2010-10-07T15:08:56Z

Rick: Talk:DBPF moved to Talk:DatabasePackedFile

2008-06-28T00:15:43Z

Talk:DBPF moved to Talk:DatabasePackedFile

Delphy at 20:48, 3 January 2007

2007-01-03T20:48:20Z

Jfade at 19:16, 3 January 2007

2007-01-03T19:16:04Z

Delphy at 08:35, 3 January 2007

2007-01-03T08:35:01Z

Jfade: /* Compressed or Uncompressed */

2007-01-03T04:07:23Z

‎Compressed or Uncompressed

Delphy at 21:12, 1 January 2007

2007-01-01T21:12:13Z

Albmont: /* Compressed or Uncompressed */

2007-01-01T20:14:46Z

‎Compressed or Uncompressed

Delphy at 23:41, 31 December 2006

2006-12-31T23:41:24Z

Albmont: Compressed or Uncompressed

2006-12-31T19:18:53Z

Compressed or Uncompressed

← Older revision		Revision as of 15:08, 7 October 2010
Line 1:		Line 1:
		+	[Thank you, FordGT90Concept; I didn`t know how, yet. --GeneralOperationsDirector 2010-Oct-07]
		+
	It's a Sims 2 wiki yes, but it also has Simcity 4 modding information on it thats linked from Simtropolis, so try not to remove all the Sim City 4 stuff. :) [[User:Delphy\|Delphy]] 17:10, 1 August 2006 (EDT)		It's a Sims 2 wiki yes, but it also has Simcity 4 modding information on it thats linked from Simtropolis, so try not to remove all the Sim City 4 stuff. :) [[User:Delphy\|Delphy]] 17:10, 1 August 2006 (EDT)
	:I didn't, I just changed the focus to Sims2. [[User:Jaxad0127\|Jaxad0127]] 17:21, 1 August 2006 (EDT)		:I didn't, I just changed the focus to Sims2. [[User:Jaxad0127\|Jaxad0127]] 17:21, 1 August 2006 (EDT)

← Older revision		Revision as of 20:48, 3 January 2007
Line 35:		Line 35:

	: Added the info about the header again. And I see, when you first said file I assumed you meant the entire DBPF, which is what threw me off. I've always referred to the individual files within the DBPF as resources, though I guess both are correct. It just threw me to see it referred to as a file at first though, heh. But the DIR resource or the header of the actual compressed file, both are valid ways of checking. --[[User:Jfade\|Jfade]] 14:16, 3 January 2007 (EST)		: Added the info about the header again. And I see, when you first said file I assumed you meant the entire DBPF, which is what threw me off. I've always referred to the individual files within the DBPF as resources, though I guess both are correct. It just threw me to see it referred to as a file at first though, heh. But the DIR resource or the header of the actual compressed file, both are valid ways of checking. --[[User:Jfade\|Jfade]] 14:16, 3 January 2007 (EST)
		+
		+	:: Excellent thanks for adding that. :) [[User:Delphy\|Delphy]] 15:48, 3 January 2007 (EST)

← Older revision		Revision as of 19:16, 3 January 2007
Line 33:		Line 33:

	I was under the impression that every ''compressed'' file thats in a DBPF is listed as the DIR resource, which is a seperate list from the actual Index itself - so checking just the DIR and matching that against the Index should be (and has been for me) enough to indicate if a resource chunk is compressed or not, but your way of also matching the first 9 just provides extra error checking. [[User:Delphy\|Delphy]] 03:35, 3 January 2007 (EST)		I was under the impression that every ''compressed'' file thats in a DBPF is listed as the DIR resource, which is a seperate list from the actual Index itself - so checking just the DIR and matching that against the Index should be (and has been for me) enough to indicate if a resource chunk is compressed or not, but your way of also matching the first 9 just provides extra error checking. [[User:Delphy\|Delphy]] 03:35, 3 January 2007 (EST)
		+
		+	: Added the info about the header again. And I see, when you first said file I assumed you meant the entire DBPF, which is what threw me off. I've always referred to the individual files within the DBPF as resources, though I guess both are correct. It just threw me to see it referred to as a file at first though, heh. But the DIR resource or the header of the actual compressed file, both are valid ways of checking. --[[User:Jfade\|Jfade]] 14:16, 3 January 2007 (EST)

← Older revision		Revision as of 08:35, 3 January 2007
Line 29:		Line 29:

	::::: Another weird thing though is that not every resource in a DBPF file is always compressed so it's not as easy to flag the entire file as being compressed/uncompressed. What I did with my programs is once I've pulled the sizes from the index I check the first few bytes of the actual resource. Within the first 9 bytes of a compressed resource it gives the compressed size and uncompressed size along with some other info, (which I don't see on the DBPF compression page anymore BTW, was that removed/lost? I'll re-add what info I have if it is.) But anyhow, if the "Compressed Size" that I get from those first 9 bytes matches the size from the index then I know that the resource needs decompressed. I don't even really pay any attention to the DIR resource, though maybe I should. Shrug --[[User:Jfade\|Jfade]] 23:07, 2 January 2007 (EST)		::::: Another weird thing though is that not every resource in a DBPF file is always compressed so it's not as easy to flag the entire file as being compressed/uncompressed. What I did with my programs is once I've pulled the sizes from the index I check the first few bytes of the actual resource. Within the first 9 bytes of a compressed resource it gives the compressed size and uncompressed size along with some other info, (which I don't see on the DBPF compression page anymore BTW, was that removed/lost? I'll re-add what info I have if it is.) But anyhow, if the "Compressed Size" that I get from those first 9 bytes matches the size from the index then I know that the resource needs decompressed. I don't even really pay any attention to the DIR resource, though maybe I should. Shrug --[[User:Jfade\|Jfade]] 23:07, 2 January 2007 (EST)
		+
		+	:::::: Jfade, I couldn't find a good description of what those beginning 9 bytes where - specifically the second block of 5. If you could fill that in, that'd be great.
		+
		+	I was under the impression that every ''compressed'' file thats in a DBPF is listed as the DIR resource, which is a seperate list from the actual Index itself - so checking just the DIR and matching that against the Index should be (and has been for me) enough to indicate if a resource chunk is compressed or not, but your way of also matching the first 9 just provides extra error checking. [[User:Delphy\|Delphy]] 03:35, 3 January 2007 (EST)

← Older revision		Revision as of 04:07, 3 January 2007
Line 27:		Line 27:

	:::: Yup! Completely and totally weird. That's Maxis for you. Personally I would have just added a single byte to the index as you would. You'll find a lot of things in these package files don't really "make sense" from a normal point of view, but I guess we have to work around them to make the programs we make... [[User:Delphy\|Delphy]] 16:12, 1 January 2007 (EST)		:::: Yup! Completely and totally weird. That's Maxis for you. Personally I would have just added a single byte to the index as you would. You'll find a lot of things in these package files don't really "make sense" from a normal point of view, but I guess we have to work around them to make the programs we make... [[User:Delphy\|Delphy]] 16:12, 1 January 2007 (EST)
		+
		+	::::: Another weird thing though is that not every resource in a DBPF file is always compressed so it's not as easy to flag the entire file as being compressed/uncompressed. What I did with my programs is once I've pulled the sizes from the index I check the first few bytes of the actual resource. Within the first 9 bytes of a compressed resource it gives the compressed size and uncompressed size along with some other info, (which I don't see on the DBPF compression page anymore BTW, was that removed/lost? I'll re-add what info I have if it is.) But anyhow, if the "Compressed Size" that I get from those first 9 bytes matches the size from the index then I know that the resource needs decompressed. I don't even really pay any attention to the DIR resource, though maybe I should. Shrug --[[User:Jfade\|Jfade]] 23:07, 2 January 2007 (EST)

← Older revision		Revision as of 21:12, 1 January 2007
Line 25:		Line 25:

	::: That's a kind of very skewed logic, isn't it? So the whole purpose of this DIR resource is just to repeat what is in the index, and if the DIR is exactly identical to the index, it means the file is compressed, otherwise it means the file isn't? They use 20 or 24 bytes when one bit would suffice? That's not fairly simple, that's exotically complex! [[User:Albmont\|Albmont]] 15:14, 1 January 2007 (EST)		::: That's a kind of very skewed logic, isn't it? So the whole purpose of this DIR resource is just to repeat what is in the index, and if the DIR is exactly identical to the index, it means the file is compressed, otherwise it means the file isn't? They use 20 or 24 bytes when one bit would suffice? That's not fairly simple, that's exotically complex! [[User:Albmont\|Albmont]] 15:14, 1 January 2007 (EST)
		+
		+	:::: Yup! Completely and totally weird. That's Maxis for you. Personally I would have just added a single byte to the index as you would. You'll find a lot of things in these package files don't really "make sense" from a normal point of view, but I guess we have to work around them to make the programs we make... [[User:Delphy\|Delphy]] 16:12, 1 January 2007 (EST)

← Older revision		Revision as of 20:14, 1 January 2007
Line 23:		Line 23:

	::Basic programming. The DIR resource has a list of compressed files based on the various TGI stuff (Type, Group, Instance ID, Instance ID 2). Each file in the index also has TGI info. So, what you do is basically check if a file from the index exists in the DIR array then it must be compressed. What I did with my PHP code was to basically add a field to the index array called compressed, then if a file exists in the DIR resource it tags the index entry as being for a compressed file, then when I come across a file later on, I just check in my index array and if compressed == true, then I know it contains compressed data. Fairly simple, really. [[User:Delphy\|Delphy]] 18:41, 31 December 2006 (EST)		::Basic programming. The DIR resource has a list of compressed files based on the various TGI stuff (Type, Group, Instance ID, Instance ID 2). Each file in the index also has TGI info. So, what you do is basically check if a file from the index exists in the DIR array then it must be compressed. What I did with my PHP code was to basically add a field to the index array called compressed, then if a file exists in the DIR resource it tags the index entry as being for a compressed file, then when I come across a file later on, I just check in my index array and if compressed == true, then I know it contains compressed data. Fairly simple, really. [[User:Delphy\|Delphy]] 18:41, 31 December 2006 (EST)
		+
		+	::: That's a kind of very skewed logic, isn't it? So the whole purpose of this DIR resource is just to repeat what is in the index, and if the DIR is exactly identical to the index, it means the file is compressed, otherwise it means the file isn't? They use 20 or 24 bytes when one bit would suffice? That's not fairly simple, that's exotically complex! [[User:Albmont\|Albmont]] 15:14, 1 January 2007 (EST)

@@ Line 15: / Line 15: @@
 ::::: I saw the code, I guess I could understand it (even though I know nothing of PHP and I could not run it), but I think there's something missing there. The code reads some of the files, but not all of them. I am specially interested in the "Property Set", the one with $value['typeID'] == 'EBCF3E27', because this is where Pets Bodyshop introduced a bug, and I would like to list all the packages that were infected with this Pets virus (there is no outfit in the Property Set). [[User:Albmont|Albmont]] 14:05, 31 December 2006 (EST)
 == Compressed or Uncompressed ==
 The text says " To check if a file is compressed you first need to read the DIR resource, if it exists", but there's no hint to '''how''' we can know if the file is compressed or not, neither here nor in the DIR entry. [[User:Albmont|Albmont]] 14:18, 31 December 2006 (EST)

← Older revision		Revision as of 19:18, 31 December 2006
Line 15:		Line 15:

	::::: I saw the code, I guess I could understand it (even though I know nothing of PHP and I could not run it), but I think there's something missing there. The code reads some of the files, but not all of them. I am specially interested in the "Property Set", the one with $value['typeID'] == 'EBCF3E27', because this is where Pets Bodyshop introduced a bug, and I would like to list all the packages that were infected with this Pets virus (there is no outfit in the Property Set). [[User:Albmont\|Albmont]] 14:05, 31 December 2006 (EST)		::::: I saw the code, I guess I could understand it (even though I know nothing of PHP and I could not run it), but I think there's something missing there. The code reads some of the files, but not all of them. I am specially interested in the "Property Set", the one with $value['typeID'] == 'EBCF3E27', because this is where Pets Bodyshop introduced a bug, and I would like to list all the packages that were infected with this Pets virus (there is no outfit in the Property Set). [[User:Albmont\|Albmont]] 14:05, 31 December 2006 (EST)
		+
		+	== Compressed or Uncompressed ==
		+
		+	The text says " To check if a file is compressed you first need to read the DIR resource, if it exists", but there's no hint to '''how''' we can know if the file is compressed or not, neither here nor in the DIR entry. [[User:Albmont\|Albmont]] 14:18, 31 December 2006 (EST)