In general, if you replace the dll and sys file and restart things they will use the new DLLs.
For user mode, restart is probably closing all application using DAPL and restarting them or even just renaming existing DLL and than copy the new one, and new application will use it. For kernel, this might mean that one will have to download DAPL and restart it. I don't know what this really means, but if there are only a few applications using DAPL, this shouldn't be a problem as well. In any case, this is not really related to the question weather checked builds are being installed or not. Thanks Tzachi > -----Original Message----- > From: Sean Hefty [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 22, 2008 7:44 PM > To: 'Fab Tillier'; Tzachi Dar; [email protected] > Subject: RE: [ofw] error trying to install Windows stack > > >The DLLs are there to provider kernel bypass functionality > (mthcau.dll) > >and user-mode support (ibal.dll and complib.dll). It comes down to > >whether you want to install the kernel bits only with the > INF and then > >require a different installation mechanism for the user-mode > bits, or > >whether you install everything from the INF. > > From an end-user's perspective, installing everything is > fine. But it's not clear to me if changes can make > development easier. > > If I make a fix to, say, DAPL, does that require > re-installing the kernel drivers? I would like a way to > build and install a single driver only, or a single library. > Is there an easy way to do this? > > - Sean > > _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
