I'm also supporting this request. 

> Dear Developers
> 
> I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the linux binaries. Have anybody been able to compile a windows versions since 2018?
> 
> Kind Regards Finn

> Dear Developers

> 

> I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the 
linux binaries. Have anybody been able to compile a windows versions since 2018?

> 

> Kind Regards Finn



Hi,



We discussed on windows build some weeks ago and i tried to make one to check if it’s possible.

The result is in https://elog.psi.ch/elogs/Forum/69491

This could help you up to official new build.



.

Laurent

> > Dear Developers
> 
> > 
> 
> > I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the 
> linux binaries. Have anybody been able to compile a windows versions since 2018?
> 
> > 
> 
> > Kind Regards Finn
> 
> 
> 
> Hi,
> 
> 
> 
> We discussed on windows build some weeks ago and i tried to make one to check if it’s possible.
> 
> The result is in https://elog.psi.ch/elogs/Forum/69491
> 
> This could help you up to official new build.
> 
> 
> 
> .
> 
> Laurent

Hi Laurent

I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c

But this cant be the solution - if so the windows version is put to the grave

Kind Regards Finn

Hi Finn,

I've just tested the same archive on new laptop with Windows 11. 
I unzip it and double-click elogd.exe file, bypass defender warning and the server is running.
To test, i open localhost:8080 on web client and it displays the demo logbook.

Btw i didn't test it as a service. What are the 2 libs you said it misses ?

.
Laurent

> 
> Hi Laurent
> 
> I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
> There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
> It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c
> 
> But this cant be the solution - if so the windows version is put to the grave
> 
> Kind Regards Finn

> Hi Finn,
> 
> I've just tested the same archive on new laptop with Windows 11. 
> I unzip it and double-click elogd.exe file, bypass defender warning and the server is running.
> To test, i open localhost:8080 on web client and it displays the demo logbook.
> 
> Btw i didn't test it as a service. What are the 2 libs you said it misses ?
> 
> .
> Laurent
> 
> > 
> > Hi Laurent
> > 
> > I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
> > There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
> > It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c
> > 
> > But this cant be the solution - if so the windows version is put to the grave
> > 
> > Kind Regards Finn

Hi Laurent

OK, i can recreate the unzip to folder and run elogd.exe and it works :-). If i unzip to the folder of the version installed (with the windows installer) where it runs elogd.exe as a service, the service won't start.

The problem with the dll files only applies to the post from Just Keijser containing only the executables (3 files) and these executables repport missing: libcrypto-1_1-x64.dll and libssl-1_1-x64.dll

These versions are a black box for me, are the important?

The unzip version (your version) reports: ELOG V3.1.4-395e101 (I think this is the same number as for the 2018 installed version)
The version with the 3 exe files (my version) from Just Keijser reports: ELOG V3.1.4-1ebfd06c
This site reports: ELOG V3.1.4-bcd7b50

Kind Regards Finn

We use our instance of ELOG as a operations log so that newest events are sorted at the top.

Sometimes we are also up front informed about planned maintenance, and i would be nice to could "pin" them at the top - before the sorting, so that operatores could have them in mind when starting a new shift. Have anyone found a way to solve this?

Kind Regards Finn

The way to do this is to ensure that the date of the entry is in the future.  As a hard -core linux (ab)user of elog, I create an entry, then dive into the yymmdda.log files, and edit it so that the date at the top of the entry is, for example, Sat, 31 Dec 2022 23:59:59.  Then, that entry will remain at the top of the listings until the New Year.  I do this very thing for the very same reason, i.e. to keep one entry at the top of the listings until after a certain date.

It may be that if you have "date of entry" field and sort by that, you could set the date of entry in the future.  I've not tried that.

The same effect could be done by adjusting the computer/server's date to the future, make the entry and then reset back to the present, but that may well be unpopular and impractical.  On a single computer, I have done this, although I then changed to editing the yymmdda.log file directly.

We have always had issues with eLOG crashing intermittently...  I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues...  which really didn't help.

The service now seems to crash every week...  (getting worse)...  Is anyone seeing these issues in Windows servers?  Any suggestions??