hello stefan 
 
sorry for the delay, was out of the office today. i had tested the same config 
and logbook under a "pseudo" win nt installation (suse linux 8.2 with vmware 
4.01 (virtaual pc simualtion) and a nativ win nt 4.0 sp6a: there is no 
problem! as well as this configuration works under linux as daemon. 
 
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. for me it really only occurs under win 2003. thats what i'm 
wondering. the system memory test of the server was ok (no virus, non 
controller problem or something, else, checked the hole stuff agian, just to 
be really shure!) , other apps don't have any problmes (it isonly iis 6 and 
mercure mail server runnig on this system with about 20gb free disk and about 
500mb ram totally and a pentium 4). 
 
if you think you have a chance to reproduce the problem i can zip the config 
file and the log for you. but in my opinion, you will need a win 2k3.  
 
i'd chdcked the file system rights again to be shure that they are ok. also 
i'd checked that elog run as a system service under win 2k3. it should have 
all rights. changing to run eleog with administrator rights didn't change 
anything. 
 
would be great to find out what's happen. in the mean time i let it untreaded, 
hoping no one will click treaded view...  ;-)  for security, the servie is 
configured to restart if it hangs and to boot the system in an emergency, but 
it shouldn't happen evry hour... 
 
thakX! 
ueli 
 
 
 
> All I can offer is send me your config file for the problematic logbook, and  
> I will try to reproduce the error. 
 
 

> 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"...  ;-( 
 
is there a posibility in elog to switch off the threaded view or to say what kind 
of views are allowed? this would be helpfull in this case as well as it may be  a 
nice feature for other users too. elog is very powerfull, fo some users i think 
too powerfull with to many possibilities. i think about something like you made in 
the menu / guest menu option or maybe a flag to say "don't" make threaded dispaly 
possible", like e-mail formating or something else? 
 
 

> > 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 
 
just was back from work today! i have installed the new elogd.exe file (after a 
backup!  :-)  ) and restarted the service. there are basicalle two news, a really good 
one an a bad one: 
 
1. the bad: clicking for a threaded display of the logs will still produce an porobem 
as shown in the screendump of the win 2k3 remote controle console (jpeg-attachement). 
 
2. the really good one: the BIG difference to the original 2.5.1 elogd.exe are two 
points: 
2a) the elgog.exe no more hangs! after a while it comes back to the view before 
clicking threaded view. while trying to dispaly the thread it seems to hang, but just 
semms! (white browser, nothing to see) 
2b) after quitting the error it's bossible to use eleg as normal. no restart of the 
service is more needed. before, a restart of the service has to be done because elogd 
was hanging compleatly. 
 
as you tought, it looks like a stack problem ore someting else. sorry, didn't had 
time enough to find out detailed information of 2k3. also develeoper network from ms 
dosn't bring detailed information about memory handling to the public guys  like me. 
 
the other solution my be, as i wrote, to have a switch for switching of threaded 
display, even a treaded view may be very helpfull in an discussion forum. maybe the 
compiler may coming up with a new version or ms will make a pach, for someting 
absolutly different of course  ;-)  , solving this probleme... 
 
ueli 
 
 

Many Thank's to Stefan for his work!!! He's doing a great job and is offering a better 
service than most comercial programs! Thank you very much Stefan!!! 
 
The new elogd.exe is now runniung 24h on my Windows 2003 Server without any problems. I made 
a little "stress" test too and there wasn't any problems at all. Also threaded view is 
working stable now. 
 
Is seems, that the new eleogd.exe uses a litle bit less of system rescources especially in 
theraded view mode. 
 
System specification for test: Pentium 4 2,4GHz, ASUS Motherboard, 480 MB RAM, SWAP File 1,1 
GB, Windows Server 2003 Enterprise Edition 5.2 including all paches until 15.3.04, IIS 6.0, 
Mercure Mail Server 4, McAffee Virus Scan & Firewall, ELOG 2.5.1 with new eleogd.exe runnig 
as service (system righs) with FireDaemon Lite 1.6GE. 
 
Please note that this problem has been occured under windows (reported for XP, 2000, 2003 
Server) only. Windows NT 4.0 is working well without the new eleodg.exe as well. 
 
 
> This problem has been fixed now, it was a programming bug. New version under 
>  
> http://midas.psi.ch/elog/download/windows/elogd.exe 
 
 

I have some problems of understanding how the "Format <attribute>" parameter
is working. It may be, that there was a similar question in the forum, but I
didn't find it. I'm sorry if I come back with an old question.

I would like to have 2two attributes in the same line. As ex. PersonName,
PersonCity.

If I understand the handbook correctly, it should be posslible with "Format
<attribute> = 1". However, I'm not able to use the "Format <attribute>"
correctly because I do not understand how to use it correctly in the cfg file.

Is there a possibilty of an example by Stafan or does anybody else already
use this feature successfuly and is able to post a example here?

Thank's a lot!

Thank you Stefan! Just was out of the office for some days.

There ar 2 questions in addition:

1. Is there a possiblity to fix the position of the attribut fields if they are in
the same line? As. ex. if one attribute is empty or contain a very short value it may
be possible that the position of the following atrributes in the line are moving to
the left, if the value is very long, they move to the right side. This make it
sometime not easy to read the informations, specially if the user browses trough some
entries, the picture the eyes are scanning is changing.

2. Did I understand you right, that tis will not work while editing? I would like to
put this to the wish list for a uppcoming version (not very importand, but VERY nice
to have), that it may be possible to use Format in the new and edit mode too, because
it is somtimes more comfortable to have some attributes grouped locically in one line
or to have a overview over all attributes on one screen without scrolling while editing.

ELOG has e very big flexibility and I'm amazed how fast and stable it's running under
Linu xas well as under Windows! - I love it!  :-)

Ueli

> > I have some problems of understanding how the "Format <attribute>" parameter
> > is working. It may be, that there was a similar question in the forum, but I
> > didn't find it. I'm sorry if I come back with an old question.
> > 
> > I would like to have 2two attributes in the same line. As ex. PersonName,
> > PersonCity.
> > 
> > If I understand the handbook correctly, it should be posslible with "Format
> > <attribute> = 1". However, I'm not able to use the "Format <attribute>"
> > correctly because I do not understand how to use it correctly in the cfg file.
> > 
> > Is there a possibilty of an example by Stafan or does anybody else already
> > use this feature successfuly and is able to post a example here?
> 
> This forum uses that feature. As you can see, if you display a single entry, the
> author, subject etc. are on a single line. This is achieved with
> 
> Format Author = 1
> Format Author email = 1
> Format Category = 1
> Format OS = 1
> Format ELOG Version = 1
> 
> Note that in the entry form, each attribute is on a separate line no matter what
> the format specifiers are. The single line option only works for the display page.

Thank you Stefan!

1. Will help in the real hard cases!

2. Great! Specially editing adresses or some stutus overviews will be easier with a compleate
overview!

> > 1. Is there a possiblity to fix the position of the attribut fields if they are in
> > the same line? As. ex. if one attribute is empty or contain a very short value it may
> > be possible that the position of the following atrributes in the line are moving to
> > the left, if the value is very long, they move to the right side. This make it
> > sometime not easy to read the informations, specially if the user browses trough some
> > entries, the picture the eyes are scanning is changing.
> 
> Yes there is a possibility. In the format option, you can specify two CSS names, one for the
> attribute and one for it's value. The default ones are "attribname" and "attribvalue". Just
> make new ones by copying these two, renaming it to something like xxxname and xxxvalue where
> "xxxx" is the name of the attribute. You find that in the file themes/default/default.css.
> They contain a field called "width:" which can be changed:
> 
> .typename {
>   width:150px;             <-- must be changed
>   background-color:#CCCCFF;
>   border:1px solid #0000FF;
>   border-top:1px solid white;
>   border-left:1px solid white;
>   padding:3px;
> }
> 
> By having separate classes for all attributed, you can change their width separately,
> accomplishing hopefully what you need.
> 
> > 2. Did I understand you right, that tis will not work while editing? I would like to
> > put this to the wish list for a uppcoming version (not very importand, but VERY nice
> > to have), that it may be possible to use Format in the new and edit mode too, because
> > it is somtimes more comfortable to have some attributes grouped locically in one line
> > or to have a overview over all attributes on one screen without scrolling while editing.
> 
> I will put this on the wishlist.
> 
> Stefan

I did not have the following problem in any snapshot before 23.7.04 .
Actually I do not have a possibility to test the snapshot under an other
system than win xp pro sp 1 (fully pached). 

Using my logbooks as well as the demo logbook works well under older
snapsgots of 2.5.3 as well as long as the "List Display = <attributes>" is
not used!

Using "List Display = <attributes>" produces an ususal output with the text
field content in the first row and a row title of the first 3 letters.

Ex.:
Attributes = Customername, Customeraddres
List Display = Customername, Customeraddres

Output:
¦Cus¦Customeraddres¦

If no record is in the logbook, only the "Cus" is dispalyed! Removing "List
Display = <attributes>" produces a normal output with same logbook!

By the way: Thnak's for the Format in the entry/edit view!!!