> > > We are trying to use ELog on Windows XP with Protection on individual log 
> > > book and we unable to login after creating users even if we give correct 
> > > user name and password login screen reappears. We are able to log in to the 
> > > Elog when we use windows 98 Client we are running Elog on Windows XP and 
> > > without password protection on logbook it is working fine with windows 98.
> > > 
> > > For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server
> > 
> > First, upgrade to 2.5.4-5 (if you haven't done so). If the problem persists,
> > please start elogd on the server with the "-v" flag, capture the screen output
> > and send it to me by email so that I can have a look. Please send also your
> > elogd.cfg file.
> > 
> > - Stefan
> 
> Mr. Stefan
> 
> Following is elogd.cfg file text:
> 
> [global]
> port = 8080
> Main Tab = Home
> Protect Selection page = 1
> 
> [Daily Log]
> Password file = pwdfile
> Self register = 0
> Login expiration = 0
> Admin user = user
> Logout to main = 1
> Theme = bubbles
> Comment = Daily Call tracking and Issue Solving
> Attributes = Author, Type, Category, Subject
> IOptions Author = icon6.gif, icon7.gif
> Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
> Options Category = General, Hardware, Software, Network, Other
> Extendable Options = Category
> Required Attributes = Author, Type
> Page Title = ELOG - $subject
> Reverse sort = 1
> Quick filter = Date, Type

Mr. Stefan

We tried installing elog on another pc with almost the same configuration and are 
able to run it without any problems now.

> >

> > We are trying to use ELog on Windows XP with Protection on individual log 
> > book and we unable to login after creating users even if we give correct 
> > user name and password login screen reappears. We are able to log in to the 
> > Elog when we use windows 98 Client we are running Elog on Windows XP and 
> > without password protection on logbook it is working fine with windows 98.
> > 
> > For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server
> 
> First, upgrade to 2.5.4-5 (if you haven't done so). If the problem persists,
> please start elogd on the server with the "-v" flag, capture the screen output
> and send it to me by email so that I can have a look. Please send also your
> elogd.cfg file.
> 
> - Stefan

Mr. Stefan

Following is elogd.cfg file text:

[global]
port = 8080
Main Tab = Home
Protect Selection page = 1

[Daily Log]
Password file = pwdfile
Self register = 0
Login expiration = 0
Admin user = user
Logout to main = 1
Theme = bubbles
Comment = Daily Call tracking and Issue Solving
Attributes = Author, Type, Category, Subject
IOptions Author = icon6.gif, icon7.gif
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

> >

> W

> We are trying to use ELog on Windows XP with Protection on individual log 
> book and we unable to login after creating users even if we give correct 
> user name and password login screen reappears. We are able to log in to the 
> Elog when we use windows 98 Client we are running Elog on Windows XP and 
> without password protection on logbook it is working fine with windows 98.
> 
> For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server

First, upgrade to 2.5.4-5 (if you haven't done so). If the problem persists,
please start elogd on the server with the "-v" flag, capture the screen output
and send it to me by email so that I can have a look. Please send also your
elogd.cfg file.

- Stefan

> W

No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!

> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
> 
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
> 
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant?  I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> > 
> > EX: 
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> > 
> > Just a thought.
> > 
> > Thanks