.GCM file extension!
- Thread starter xhunter
- Start date
Just some more info which I have no idea of it's accuracy (I would go for bohdy's link, but just in case you need the info written different):
===========================
3. DISK & FILE STRUCTURES
===========================
Disk header at offset 00000000
0000-0003 GameName
0004-0005 Comany
0006 Disk ID
0007 Version
0008 Streaming
0009 StreamBufSize
0420-0424 offset of main executable DOL
0424-0427 offset of the FST
Apploader at offset 00002440
0000-0009 Date (version) of the apploader in ASCII
000A-000F padding (0)
0010-0013 Apploader entrypoint
0014-0017 size of the apploader (32 bit)
0020-.... Apploader code (loaded at 81200000 in RAM)
Dol file format
Header Size = 100h bytes
0000-001B Text[0..7] sections File Positions
001C-0047 Data[0..10] sections File Positions
0048-0063 Text[0..7] sections Mem Address
0064-008F Data[0..10] sections Mem Address
0090-00AB Text[0..7] sections Sizes
00AC-00D7 Data[0..10] sections Sizes
00D8 BSS Mem address
00DC BSS Size
00E0 Entry Point
0100-.... Start of sections datas (body)
FST format
1st 32bits = nb of files, then we get a structure repeated for each file
structure looks like that :
NameOffset (32bits), diskAddr (32bits), fileSize (32bits)
if bit 31 of Nameoffset is set, it means we are entering in a directory,
that contains [fileSize] files
===========================
3. DISK & FILE STRUCTURES
===========================
Disk header at offset 00000000
0000-0003 GameName
0004-0005 Comany
0006 Disk ID
0007 Version
0008 Streaming
0009 StreamBufSize
0420-0424 offset of main executable DOL
0424-0427 offset of the FST
Apploader at offset 00002440
0000-0009 Date (version) of the apploader in ASCII
000A-000F padding (0)
0010-0013 Apploader entrypoint
0014-0017 size of the apploader (32 bit)
0020-.... Apploader code (loaded at 81200000 in RAM)
Dol file format
Header Size = 100h bytes
0000-001B Text[0..7] sections File Positions
001C-0047 Data[0..10] sections File Positions
0048-0063 Text[0..7] sections Mem Address
0064-008F Data[0..10] sections Mem Address
0090-00AB Text[0..7] sections Sizes
00AC-00D7 Data[0..10] sections Sizes
00D8 BSS Mem address
00DC BSS Size
00E0 Entry Point
0100-.... Start of sections datas (body)
FST format
1st 32bits = nb of files, then we get a structure repeated for each file
structure looks like that :
NameOffset (32bits), diskAddr (32bits), fileSize (32bits)
if bit 31 of Nameoffset is set, it means we are entering in a directory,
that contains [fileSize] files
- Thread Starter
- #23
renaming the files to .gcm
You need to have ISOBuster 1.6, when you go to open it, it will just say track 1. On the left panel it will say DVD. Right click DVD and then select convert to user data. When it asks you to save it, select the directory you would like it, and rename it to the proper name of the game, and at the end of it put .gcm. THESE ARE NOT ISO'S I DID MORE RESEARCH ON IT. They are made with a few programs all working together to use the GC as the reader and your computer as a server. Without the other users playing, you have a pure IMAGE of the game without any malicious files, so what I've read on about 30 sites. I will test this, and give feed back, to settle this matter.
You need to have ISOBuster 1.6, when you go to open it, it will just say track 1. On the left panel it will say DVD. Right click DVD and then select convert to user data. When it asks you to save it, select the directory you would like it, and rename it to the proper name of the game, and at the end of it put .gcm. THESE ARE NOT ISO'S I DID MORE RESEARCH ON IT. They are made with a few programs all working together to use the GC as the reader and your computer as a server. Without the other users playing, you have a pure IMAGE of the game without any malicious files, so what I've read on about 30 sites. I will test this, and give feed back, to settle this matter.
Eh, look, most of us know this already. The images dumped are 1:1 copies of the discs as the GC reads it (after it has gone through de-encryption if any). With garbage and all.
And it does not use a normal ISO format, so reading it using a program meant for the ISO format common for CD's etc is a waste of time (read earlier posts in this topic). I know its mentioned but somehow you don't get it? A file's last name has nothing to do with what the file really is. If I rename a .mp3 to zip it doesn't make it a zip file which winzip could understand, but it's still in mp3 format.
And it does not use a normal ISO format, so reading it using a program meant for the ISO format common for CD's etc is a waste of time (read earlier posts in this topic). I know its mentioned but somehow you don't get it? A file's last name has nothing to do with what the file really is. If I rename a .mp3 to zip it doesn't make it a zip file which winzip could understand, but it's still in mp3 format.
Last edited:
einstein123
New member
There's one more thing... There ARE DVD readers that can read GC mini-dvds, but windows can't understand the information (It thinks that it is an protected Audio CD)
This happens with the programs that opens isos (they think that the image is an audio)
This happens with the programs that opens isos (they think that the image is an audio)