David J Taylor wrote: > Maarten Wiltink wrote: > [] >> As it happens, I recently had cause to install a clean Windows >> somewhere and downloaded what turns out to be vegas-v2. As of five >> minutes ago, >> a new NTP is gathering loopstats. >> >> Thanks! >> >> Groetjes, >> Maarten Wiltink > > That's good news, Maarten. > > So, one question which now arises is: how should the current Windows NTP > handle the libeay32.dll version issue? Having it packaged with Meinberg's > distribution, and putting it into the application directory seems to be an > approach which works. > > Should those installing by copying ntpd.exe etc. from Zip archives be > expected to look after libeay32.dll themselves? Should the bindings be > dynamic rather than static so that ntpd can fall back if the required > entry point or even the DLL isn't available? Should the "correct" version > of libeay32.dll always be included with the Zip archive? >
Meinberg should be copying it to the same directory as the ntpd.exe file which should not be the system32 directory. Hopefully they are creating their own directory. I don't know as I have never used their installer. Danny -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions