Changes between Initial Version and Version 1 of Ticket #69, comment 6


Ignore:
Timestamp:
Jun 15, 2011, 6:32:56 PM (13 years ago)
Author:
dmik
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #69, comment 6

    initial v1  
    1 Okay, the source of the problem is clear now. When a Java application starts, it loads the corresponding version of JVM.DLL (e.g. client or server) manually by full path [1] and then loads a bunch of other DLLs (e.g. JZIP.DLL) that have the JVM module as a dependency in the imported module list [2].
     1Okay, the source of the problem is clear now. When a Java application starts, it loads the corresponding version of JVM.DLL (e.g. client or server) manually by full path ![1] and then loads a bunch of other DLLs (e.g. JZIP.DLL) that have the JVM module as a dependency in the imported module list ![2].
    22
    33If there is only one version of JVM.DLL currently loaded into the system at step 1, everything is fine: when DosLoadModule() resolves the dependencies of JZIP.DLL at step 2, it finds this already loaded instance of JVM and uses it. But if there are two different versions of JVM.DLL already in memory, DosLoadModule() seems to simply pick up the one loaded first which is not always right.