Kernel.bin (or update Gears [halkun])

  • Thread starter Thread starter L. Spiro
  • Start date Start date
Status
Not open for further replies.
L

L. Spiro

Guest
This isn’t in Gears and is in fact listed as “Unknown”.

I don’t know how recent this is or how accurate, so I am just going to throw this on the table and if it’s new, it’s new, and if it is old, it’s old.


The text files inside Kernel.bin are already known to be just text so I won’t touch them.

The first 9 files are listed as unknown, so here is what they are.

1: Command data.
2: Attack data.
3: Unknown.
4: Character starting stats.
5: Item data.
6: Weapon data.
7: Armor data.
8: Accessory data.
9: Materia data.


I am not positive that number 1 is command data, but I believe it is.

Of course, we have already decoded the attacks, characters, items, weapons, armors, accessories, and Materia, but not yet the command data to my knowledge.


It seems pretty straight-forward but I can not be arsed with it.
I’m already too busy on the battle animations and the field files (the rendered images).


Anyway, I kept it short in case this is already known information, but in either case, you can update Gears with this information, halkun.


L. Spiro
 
I am making a note. I apologize that Gears is suspended. School and work is a full-time thing.
 
*DOUBLE POST*, but it's been a few months.....

I've updated Gears, but I was wondering if you woudn't be able to shed some more light into the individual formats? I think we decompiled them before, right?

Is there any logical groupings to the text? 10-27?

Also, I bet dollars to donuts that #3 is the shop inventory listings, as it's the only thing that's missing. ^_^

(WOW! I forgot how much fun it was to work on Gears!)
 
I have all the old file format listings for characters, magic, items, weapons, armors, accessories, and Materia.

Just give me somewhere to send them.


The first file IS definitely 100% command data.
I’ve only messed around with it a little but I have found already that if you set the entire file to a bunch of 0’s that every single attack, command, item, everything you can do in battle will target the character who is casting the attack.  Even summons.  And not only that, they will ONLY attack that character.  Megalixir will only heal one character (the character using it), etc.
I managed to kill Red XIII 13 times over by having him cast Knights of Round on himself.

The first byte of command data is the targeter.  It is the same way as the targeters for items and magic.  0x00 = Target Self (And Only Self).

That is all I have really decoded from them.  It is all that really matters, at least for now.


1: Command Data
2: Magic Data
3: Shops?
4: Character Data
5: Item Data
6: Weapon Data
7: Armor Data
8: Accessory Data
9: Materia Data
10: Command Decriptions
11: Magic Decriptions
12: Item Decriptions
13: Weapon Decriptions
14: Armor Decriptions
15: Accessory Decriptions
16: Materia Decriptions
17: Key Item Decriptions
18: Command Names
19: Magic Names
20: Item Names
21: Weapon Names
22: Armor Names
23: Accessory Names
24: Materia Names
25: Key Item Names
26: Battle and Battle-Screen Text
27: Summon Special Names (shown at the top of the screen when you cast a summon [Diamond Dust, Ultimate End, etc.])


Files 10-27 are LZS-compressed while 1-9 are not.
If you uncompress 10-25, stack them into one large file, and then LZS-compress it, you will have Kernel2.bin.

I do not know why, when they were so concerned with space, they needed two copies of every item name and description.


L. Spiro
 
send it to halkun2002 at yahoo dot com

Files 10-27 are LZS-compressed while 1-9 are not.
If you uncompress 10-25, stack them into one large file, and then LZS-compress it, you will have Kernel2.bin.
Click to expand...

Wow, that's amusing....
 
LZS == Lempel-Ziv-Stac

It's a funny acronym until you realize it's the last names of the devopers.

Abraham Lempel Works a HP now.
http://www.hpl.hp.com/about/bios/abraham_lempel.html

Jacob Ziv is a professor at the Israel Institute of Technology
http://www.marconifoundation.org/pages/dynamic/fellows/fellow_details.php?roster_id=23

Stac Electronics did the last bit. They made a hard drive compression program called "Stacker" which, it would seem, was stolen by Microsoft (Doublespace). On going a google search, it would seem I wound up in Microsoft's dirty laundry. Stac sued MS for patent infrigment on the stac algo.

http://www.vaxxine.com/lawyers/articles/stac.html

Intresting....


++++ EDIT +++++

Oops, It's actually "Lempel-Ziv-Shannon-Fano, Satisitcal plus Arthimitic " (LZSS+A) compression. The Stac algo is still patented.

Claude E. Shannon was a mathematician for bell labs. Won the nobel prize.
http://www-groups.dcs.st-and.ac.uk/~history/Mathematicians/Shannon.html

The LZSS+A algo was devoped by Professor Haruhiko Okumura
http://oku.edu.mie-u.ac.jp/~okumura/index-e.html

He actaully works on the Linux Kernel too. Go him! He speaks english as well.

I wonder if I should put this into Gears?
 
Well, since psx dat files (and perhaps others files) are compressed using lzss, I thinnk it should be interesting to explain this compression, but this is not the most important part of Gears.
 
If you add the explanation about this compression to gears, well, I uh-

Okay ficedula is a nice guy but his format descriptions are the hardest things to read on Earth.

If you need this description in Gears I could rewrite it.


L. Spiro
 
One of the more amusing things about Gears is you can tell It's written bu lota people from all over the planet.

Go ahead and rewrite. I very much would like corrections. In the end, I would like it all to liik the Terrence's Battle Mechanics doc I have in there.

Speaking of which, wasn't he working on the Battle scripting system?

Speaking of scripting systems, I wonder how far along Qhimm is on the Field script?
 
LZS == Lempel-Ziv-Stac
Click to expand...
Oh this reminded me of LZW archive type (like RAR or ZIP), in this case LZW stands for Lempel - Ziv - Welch iirc ( I dont know why do I remember such a noninportant information ;) ... so looks like competitive alogrithm
 
LZS == Lempel-Ziv-Stac
Click to expand...
Oh this reminded me of LZW archive type (like RAR or ZIP), in this case LZW stands for Lempel - Ziv - Welch iirc ( I dont know why do I remember such a noninportant information ;) ... so looks like competitive alogrithm
Click to expand...
LZW is a different algorythm. It forces a token size say 9 bits with an escape token for dictionary enlargement (in this case all 1's in the bitstream).  The data is packed in a bit stream. Patterns are compressed by reading the stream and issuing a new token for repeated data.  The algorythm doesn't require the dictionary to be stored because the packed data is used to regenerate the data.
To keep the dictionary size smaller they limited the token count.  I think ZIP originally used 12 bit tokens and newer versions added up to 16.  This of course takes much longer to compress. Hence they put 'fast' and 'best' compression settings. These just change the maximum token size before the dictionary is FLUSHED and restarted :)

ZIP used Shannon - Fano bit compression to further reduce the size of the data. It's like Hoffman compression only it seems to do a better job on more random data.  These are BITWISE compression algorythms so.. it gets weirder from that point.

Cyb
 
On another note:

Unisys U.S. LZW Patent No. 4,558,302 expired on June 20, 2003, the counterpart patents in the United Kingdom, France, Germany and Italy expired on June 18, 2004, the Japanese counterpart patents expired on June 20, 2004 and the counterpart Canadian patent expired on July 7, 2004.
Click to expand...

http://www.unisys.com/about__unisys/lzw
 
Updated some more stuff on Kernel.bin. (Funny how finals are coming up and all of the sudden small Gears updates happen.... I wonder if that is somehow connected? )
 
Status
Not open for further replies.
Back
Top