> I even upgraded to the 2.5.1 version. Then I placed the elogd.c in the SRC 
> folder. Also placed the images in the themes folder.

As I wrote, you have to get the latest elogd.c, revision 1.272 and *COMPILE* it 
(or wait for the next official release). If you cannot compile elogd.c, let me 
know and I can send you the executable.

This was a bug which only occurs under certain conditions, that's why nobody 
has seen it yet. I fixed it, the new version is available under CVS:

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

> the problem only ocures on win 2003 server. I d'dn't test it under xp, 2000, 
> 2002 beause i don't have any of this systems. but it looks that no one else 
> has this problem. would be helpfull to know if there anybody out in 
> cyberspase using elog 2.5.1 with win 2000 or 2002 or even better with win 
> 2003 server? or do you have a 2003 server at psi? 
> for me it looks like a incompatibility of a stack, boffer overrun or somethin 
> in the memory.

I agree. It's most probably a stack overflow problem. The stack size must be less 
on a win 2003 server compared to a xp machine. I know that the threaded display 
requires some more stack space than the other displays. But unfortunately I have 
no win 2003 server here to try.

> since the new server isn't standing here in my office i can not test if older elog 
> versions don't have the problem too. but if your idea of stack or buffer overflow 
> is right, i guess that hoping of the helpfull ms pach or a update of the compiler 
> will be the only what we could do  :-(  it's always the same using software fom a 
> company named "kleinstweich"...  ;-( 

;-))) like that one...

I tried to reduce the memory consumption in the threaded display, can you please try 
the modified version under

http://midas.psi.ch/elog/download/windows/elogd.exe

> BUG#1

Has been fixed. New version under CVS.

> BUG#2
> In single entry view, elog returns an unformatted date value for "Type =
> date" attributes - even when it has been manually entered with the date picker.

Can't reproduce that. Used your config, got the display attached.

> Is there any possibility to start elogd as a service under NT/2000/XP 
> having local service as its user? Yes, I've read the documentation. Maybe 
> things have changed.

What do you mean by "local service as its user"? If you install elogd as a 
service with FireDaemon or via SRVANY.EXE, you use the "Services" section 
under Computer Management ("Verwalten") to configure the elogd service. 
Although the documentation says that one should use the "This account" with 
the appropriate password, it is possible to use the "Local System account" 
as well. But I'm not 100% sure what implications this has for the ownership 
of the logbook database files, but it should be ok in most cases.

> Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe 
> when THREADED is selected. Have not tried your modified version after reading the posted 
> results. Will run with summary view until fixed. Wish I could help but I'm not a 
> programmer. Let me know if you want to test any new elogd.exe's.

This problem has been fixed now, it was a programming bug. New version under

http://midas.psi.ch/elog/download/windows/elogd.exe

The elog daemon uses cascading style sheets (CSS) to format its output, such
as font family, size and color. Some people started to develop new themes
(skins) and posted them at the contributions logbook (such as
http://midas.psi.ch/elogs/Contributions/7).

From my onw experience, I know that this can be a difficult job, since it
means to change the "default.css" file and reloading a page over and over
again. I recently discovered a way to do this much easier: The Mozilla based
browsers (such as firefox, http://www.mozilla.org/products/firefox/) have an
extension called EditCSS (http://texturizer.net/firefox/extensions/#editcss)
which shows the CSS file on the left side of the browser and the web page on
the right side. Changes in the CSS editor are immediately reflected in the
browser window. This way one can change certain entries in the CSS file and
immediately see its consequences. Development of new skins should therefore
become much more easier.