Andreas Mohr wrote:
>
> On Sun, Aug 13, 2000 at 05:31:23PM +0000, Eric Pouech wrote:
> > Andreas Mohr wrote:
> > >
> > > Hi Eric,
> > >
> > > we still get
> > > ERR("IData not found for pid=%08lx. Suicide !!!\n",
>GetCurrentProcessId());
> > > , the DllEntryPoint *never* has to be called !!
> > > And Wine does just that: it doesn't call it.
> > what ? for implicit loaded DLLs, LibMain is called when InitTask is performed, so
> > it seems there's a bad dependency in DLLs loading sequence somewhere
> >
> > could you also post the same trace but with -debugmsg +dll
> No, that's not the case.
> tools/winebuild/README says:
> "init" specifies a function which will be called when this dll
> is loaded. This is only valid for Win32 modules.
>
> And NE_InitDLL gets called for mmsystem.dll.
> And of course it stops right here:
> if (!pModule->cs) return TRUE; /* no initialization code */
>
> This is because of:
> pModule->cs = 0;
> in tools/winebuild/spec16.c/BuildModule16().
>
> So what to do ?
> Implement init functions for Win16 builtins or what ?
I'm not talking about the 16 bit init functions, but of DllEntryPoint
exported function:
NE_DllProcessAttach( pTask->hModule ); called from InitTask invokes
every DllEntryPoint of each module referenced by pTask->hModule
so the DllEntryPoint of MMSYSTEM shall be called at that time
but I fear the wp<don't remember the name>.dll is called first and
performs some calls inside MMSYSTEM which DllEntryPoint has not been
called yet
so, can you provide the -debugmsg +dll trace
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
