Abstract: Described herein is a technology facilitating the operation of non-native program modules within a native computing platform. This technology provides a mechanism for aligning—as necessary—parameters of data structures so that program modules or operating systems of different paradigms may use them. The data of parameters of data structures is aligned to match the native paradigm. Typically, such data structures are shared by non-native program modules and the native operating system (or other program modules). It is aligned so that data—that would otherwise be non-aligned and performance hindering—is quickly and easily accessible by the native platform. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.

Abstract: When using a common configuration data structure (e.g., “registry”), the access redirector and entry reflector promotes compatibility and interoperability between differing versions of program modules. The access redirector redirects selected accesses to storage locations (i.e., “nodes”) of a common configuration data structure. The selected accesses are redirected to another node. This redirection stores configuration information for differing versions of program modules at different nodes. However, the differing versions are unaware that they are accessing different nodes. As configuration information in a node is changed, the entry reflector may copy selected portions of such changed information into its associated “reflected” node and vice versa. This reflection allows associated “reflected” nodes to share relevant configuration information that promotes interoperability.

Abstract: When using a common configuration data structure (e.g., “registry”), the access redirector and entry reflector promotes compatibility and interoperability between differing versions of program modules.

Abstract: Described herein is a technology facilitating the operation of non-native program modules within a native computing platform. This invention further generally relates to a technology facilitating the interoperability of native and non-native program modules within a native computing platform. More specifically, this technology involves an emulation of the kernel of the non-native operating system. Instead of interacting with the native kernel of the native computing platform, the non-native program modules interact with a non-native kernel emulator. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.

Abstract: A utility program develops and updates an API-translation layer of an emulator for running programs written for one platform on another platform. The utility builds a module for each API from a set of templates to execute the API's function on the other platform. Generalized function templates iterates through API functions. Exception templates can override the generalized templates in specific cases. Types templates convert individual arguments of the API. Code templates contain code for incorporation into a number of other templates.

Abstract: A license isolation layer isolates application source code from an incompatible target platform license, while allowing the application source code to indirectly use services provided by target platform licensed software. The license isolation layer may include an interface definition and an implementation of the interface definition. The application source code binds to the implementation of the license isolation layer interface definition. The compiled application object file may use services provided by the implementation of the license isolation layer interface. The implementation of the license isolation layer interface may use services provided by target platform licensed software thereby isolating the application source code from applicability of the target platform license.

Abstract: An implementation of a technology is described herein for operating systems and loaders of executable images. Furthermore, the technology, described herein, facilitates the adoption and recognition by an operating system of an otherwise unsupported executable-image format by increasing the ease with which an executable-image loader may be modified. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.

Abstract: Described herein is a technology facilitating the operation of non-native program modules within a native computing platform. This technology provides a mechanism for aligning—as necessary—parameters of data structures so that program modules or operating systems of different paradigms may use them. The data of parameters of data structures is aligned to match the native paradigm. Typically, such data structures are shared by non-native program modules and the native operating system (or other program modules). It is aligned so that data—that would otherwise be non-aligned and performance hindering—is quickly and easily accessible by the native platform. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.

Abstract: Described herein is a technology facilitating the operation of non-native program modules within a native computing platform. This invention further generally relates to a technology facilitating the interoperability of native and non-native program modules within a native computing platform. More specifically, this technology involves an emulation of the kernel of the non-native operating system. Instead of interacting with the native kernel of the native computing platform, the non-native program modules interact with a non-native kernel emulator. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.

Abstract: Untrusted executable code programs (applets or controls) are written in native, directly executable code. The executable code is loaded into a pre-allocated memory range (sandbox) from which references to outside memory are severely restricted by checks (sniff code) added to the executable code. Conventional application-program interface (API) calls in the untrusted code are replaced with translation-code modules (thunks) that allow the executable code to access the host operating system, while preventing breaches of the host system's security. Static links in the code are replaced by calls to thunk modules. When an API call is made during execution, control transfers to the thunk, which determines whether the API call is one which should be allowed to execute on the operating system.

Abstract: A utility program for software development generates a synchronized set of translation modules for application program interfaces in a emulated platform. The utility builds the translation modules from iterated function templates having generalized function code, exception templates with special-purpose code, and types templates for converting data types from the emulated platform.

Abstract: A utility program for software development generates a synchronized set of translation modules for application program interfaces in a emulated platform. The utility builds the translation modules from iterated function templates having generalized function code, exception templates with special-purpose code, and types templates for converting data types from the emulated platform.

Abstract: A utility program develops and updates an API-translation layer of an emulator for running programs written for one platform on another platform. This speeds the development of code such as operating-systems upgrades, where the API set can change frequently. The utility builds a module for each API from a set of templates to execute the module's function on the other platform. Generalized function templates iterate through API functions. Exception templates can override the generalized templates in specific cases. Types templates convert individual arguments of the API. Code templates contain code for incorporation into a number of other templates.