Dead easy... You're looking at a serialized tree; the "code" you mention is
actually a node ID of that node's parent, and node id's are assigned
incrementally as new folders are seen. eg:

1 ROOT code = 1,0 (1 - meaningless)
2 BIN code = 1 (means it's under ROOT)
3 HELP code = 1 (under ROOT)
4 SETUP code = 1 (under ROOT)
5 IMAGES = 3 (under HELP)
6 BASE = 4 (under SETUP)
7 DIRECTX = 4 (under SETUP)
8 GAMESPY =  4 (under SETUP)
9 TOOLKIT = 4 (under SETUP)
10 VIDEO = 6 (under BASE)
11 DRIVERS = 7 (under DIRECTX)
12 ENG = 11 (under DRIVERS)
13 FRN = 11 (under DRIVERS)
14 GER = 11 (under DRIVERS)
15 ITN = 11 (under DRIVERS)
16 SPA = 11 (under DRIVERS)

Peculiarly, it's serialized in terms of distance from the root, rather than
on a branch-by-branch basis. Though this shouldn't matter; what it does mean
is that you'll pretty much always have to rebuild the ENTIRE tree to read a
folder. Scary, huh?

Oh yeah... names are padded in size to be at an even number of bytes long -
which is where the extra null comes from.

Simon
--
Clairvoyeurism - the supernatural ability to predict what someone will look
like naked.
----- Original Message -----
From: "Martijn Groen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, December 09, 1999 08:40
Subject: help


Hi,

Can someone help me with the CD-ROM pathtable structure?
There must be some sort of structure in it!

I've included one example of a pathtable.

Hoping someone can help me.

Greetz,

Martijn Groen



Reply via email to