it seems that the plugins for either fusion, or the vfs
are really not well identified before they are
attempted to load, it's more than plausible that
someone will screw with theconfig and attempt to load a
subsystem plugin into the vfs.
basically I need a way to identify a DLL, I think a new
entry point into each DLL might be in order here, one
which when called, can reply with information on the
plugin type, the name, and some other information,
perhaps it might help me to make the code more robust,
each plugin I have, I use the entry point to ID the
plugin and either load or refuse to load it, depending
on the response.
(this was prompted cause I found that it's possible
that the VFS might mistake the OGLGraphics DLL instead,
I Got a weird error where inside the VFS, it called a
function inside the OGLGraphics dll, which is NEVER
supposed to happen, so I guess it happened here and I
need to prevent this in future)
