We should rebase java_i.dll on win32 (using the linker's /base option or the UI in msdev). We need to pick a high number under the 2GB line... something like 0x15000000. Because java_i is loading at nearly the default load address, 0x10060000 i think, it is highly likely to conflict with native dll's written both at javasoft and externally. in fact, it IS currently conflicting with winawt.dll... which i would also suggest we move, to say 0x14000000, for the same reason. the penalty for a load conflict can be a significant... we are potentially computing and patching *11,285* addresses (according to link /dump and lc anyway) because of this load conflict. the CPU to do this isn't a big deal, but we are faulting in several pages from disk which wouldn't otherwise get loaded (so that the os can fixup our import address table.)