windowsdlls
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
windowsdlls [2009/09/27 09:18] – nopsled | windowsdlls [2009/11/06 22:56] – megadiscman | ||
---|---|---|---|
Line 238: | Line 238: | ||
The OCM files (except for init.ocm which contains an extra layer of packing) are interpreted as [[OCMBytecode]] | The OCM files (except for init.ocm which contains an extra layer of packing) are interpreted as [[OCMBytecode]] | ||
- | Here is a decode | + | Here is a decoder |
* It does not name imports from salwrap, it just puts offsets into the import table into a generic name. Check here for some name [[OCMSalwrapExports]] | * It does not name imports from salwrap, it just puts offsets into the import table into a generic name. Check here for some name [[OCMSalwrapExports]] | ||
* It is unable to parse named exports | * It is unable to parse named exports | ||
Line 245: | Line 245: | ||
The output of the program is an assembler source file (completely unreadable) that is intended to be compiled by the GNU assembler (Win32 port or cross-assembler in linux) and then loaded into a good disassembler, | The output of the program is an assembler source file (completely unreadable) that is intended to be compiled by the GNU assembler (Win32 port or cross-assembler in linux) and then loaded into a good disassembler, | ||
- | [[codeblockparser]] | + | [[codeblockparser]] |
Some info about analysing an OCM file can be found in this part of chat log: | Some info about analysing an OCM file can be found in this part of chat log: |
windowsdlls.txt · Last modified: 2010/04/29 14:48 by megadiscman