windowsdlls
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
windowsdlls [2009/05/08 08:36] – nopsled | windowsdlls [2009/11/06 22:56] – megadiscman | ||
---|---|---|---|
Line 124: | Line 124: | ||
</ | </ | ||
- | |||
===== OpenMG Secure Module - Implementation Architecture ===== | ===== OpenMG Secure Module - Implementation Architecture ===== | ||
Line 155: | Line 154: | ||
Modules in the plugin-layer at the top would communicate with these " | Modules in the plugin-layer at the top would communicate with these " | ||
they never directly communicate with salwrap/ | they never directly communicate with salwrap/ | ||
+ | There are tough, exceptions, a couple of functions can be used in pfcom trough COM. Its also possible to use SAL (salExec0) using COM (omgmisc.dll DLL link to salwrap.dll salExec0). | ||
< | < | ||
.................................................................................................... + UI | .................................................................................................... + UI | ||
- | SonicStage | + | SonicStage |
.................................................................................................... | .................................................................................................... | ||
^ ^ | ^ ^ | ||
Line 164: | Line 164: | ||
| COM | | COM | ||
v v | v v | ||
- | .................................................................................................... Plug-in layer | + | .................................................................................................... Plug-in layer (AVLib) |
+ CheckOut +Playback | + CheckOut +Playback | ||
+ CheckIn +Convert | + CheckIn +Convert | ||
Line 194: | Line 194: | ||
| | | | ||
v | v | ||
- | | + | |
- | rights information | + | License repository/ |
- | (opf data) | + | |
- | | + | [License information] |
+ | | ||
+ | < | ||
+ | | ||
Line 211: | Line 214: | ||
.................................................................................................... | .................................................................................................... | ||
</ | </ | ||
+ | |||
Line 234: | 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 241: | 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: | ||
Line 252: | Line 256: | ||
* Device.sal: [[devicesal]] | * Device.sal: [[devicesal]] | ||
+ | ===== Links ===== | ||
+ | |||
+ | * [[http:// |
windowsdlls.txt · Last modified: 2010/04/29 14:48 by megadiscman