statically loaded "shared dll"?

[PMV]

I give it up ... i'm to supid

At first the situation:
There are a few kinds of library-using under windows:
1. as statical linked library (like our userlibrarys)
2. as dynamical linked library (dll)
2.1 loaded for every exe which want to use it
2.1.1 dynamically linked (with OpenLibrary() and CallFunction(), ...)
2.1.2 statically linked (Import-command)
2.2 loaded only one in the hole system (like the windows-kernel-dlls)

I hope here are any one who can help me ... please
... the easiest way for me is to use 2.2 ... if there is any chance to do this.
I read there is only one flag in the header, which decided this.

I want to programe a filemanager (for my own fileformat) which is able to
handle multiple fileaccess at the same time. The programmes need to
know in realtime, if another has change it and all programms need the
newest data ... so this is the easiest way i think.

I could realize this with shared memory (mapped file) ... i know, but i
hope some one can help me to solve this problem with the other way.

thanks a lot for all who want to help me

MFG PMV

[freak]

2.2 is a thing of the past (from 16 bit Windows)

Nowadays, every process has its private copy of every dll it loads, even for system ones.
(atleast from the process's point of view)

[PMV]

are you realy shure? ... bad

also shared memory, thanks a lot.

MFG PMV