Leaderboard

Another simple tool which pulls the data out of both FILELIST.INF and COMPRESS.INF and exports it to tab delimited files which you can view in notepad or Microsoft Excel(best viewed). It makes it a lot easier to see what is in the files without looking at it in HEX. Download

UPDATE: READ THIS Here is what I presently know about the file format: It is a 3 file archive. COMPRESS.INF, FILELIST.INF, & GAMEDATA.GTC COMPRESS.INF hold information on null bytes found in GAMEDATA.GTC. FILELIST.INF hold file names and pointers to them of some kind. GAMEDATA.GTC holds the files. FILELIST.INF The list of files, 136 byte blocks: First 128 bytes = File path (null terminated). uint32 {4} = Unknown pointer. 0 indexed and each greater than the rest (unless the next uint32 {4} = 0, then reused) so almost certainly points to the file. uint32 {4} = Unknown pointer. As files that are likely bitmaps of the same resolution have the exact same value, almost certainly the file size. NOTE: the first uint32{4} can exceed the size of the gamedata.gtc file. Most likely, the pointer is only correct after the files in gamedata.gtc are decompressed. This file's structure is different between the games. (Thanks origamiguy!) COMPRESS.INF (Drome) 12 byte blocks: uint32 {4} - Pointer to start of a data chunk in GAMEDATA.GTC uint32 {4} - Length of non-null data at the end of the chunk uint32 {4} - Length of the chunk COMPRESS.INF (LEGO Racers 2) 20 byte blocks: uint32 {4} - Pointer to start of a data chunk in GAMEDATA.GTC uint32 {4} - Length of non-null data at the end of the chunk uint32 {4} - Length of the chunk unknown {4} - unknown. Most likely meaningless. unknown {4} - unknown. Most likely meaningless. GAMEDATA.GTC Stores all the files listed in filelist.inf. Has non-null groups separated by null groups. Uses some form of compression, most likely index based. Possibly separate for each non-null group in the file.

@Cyrem I believe this will help you with your mission: ;)

I was actually trying to get a 1999 copy because I wanted to see the trophies myself, and I found out that, in the 2001 version, the loading screens are put into a yellow frame and the menu background is around that. But now that I know that it can run without a JAM, I want it even more. Well, go knock yourself out with that extractor. My brother (known as rioforce or rio) and I were talking about this last night because I told him... well, about this topic. He mentioned something that may explain why the 1999 version can run without a JAM but the 2001 version has to. Did you happen to beta-test LEGO Universe? If so, you'll know what I'm talking about. When Beta launched, the most of the game files were sitting on the hard drive uncompressed. They could be viewed, swapped, and modded. This was probably done so the devs could work on the game easier. It wasn't until mid-beta that they were compressed. After that, they only way to run LU was with the compressed files (until there was a patcher bug and someone figured out how to run the game without the compressed files). Rio thinks this same thing might have happened with LR1. The game was designed to run without the JAM for easier development, and the code to run it like that was not removed at launch (the 1999 version). When XP came out and it was updated for it (the 2001 version), they removed that code and made it where it has to run with the JAM.

Thanks Extreme. Unfortunately i'd need a bit more than a RC engine to get this to fly. But hey you never know, one day i might be able to make a LEGO aeroplane fly...

O.T. BTW, if you want to have a YouTube video play in your most, do the following: YouTube Link Here

I think you might be wrong about it being 12-byte. Here's what I've come up with so far: COMPRESS.INF 20 byte blocks: uint32 {4} - Pointer to start of a data chunk in GAMEDATA.GTC uint32 {4} - Length of non-null data in the chunk uint32 {4} - Length of the chunk (including the null data, that's why the subtraction thing works) unknown {4} - no idea yet. unknown {4} - no idea yet.