ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65760
|
Thu Feb 28 01:56:53 2008 |
| Uwe | uweho@web.de | Question | Windows | 2.7.3 | Re: Problem updating from 2.7.2 to 2.7.3 |
Stefan Ritt wrote: |
Uwe wrote: |
Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
|
The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from
http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html
|
Thanks, that fixed it... |
68729
|
Thu Feb 1 03:12:03 2018 |
| Yves | vanhaarlemyves@gmail.com | Question | Windows | 2.9.2->3.1.3 | v3.1.3 does not work with logbooks from v2.9.2? | I have just upgraded elog from 2.9.2 -> 3.1.3.
3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.
Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.
When running 2.9.2 on the same machine, all runs wel (attachment 2)
cfd file: (I only left in one logbook - they are all configured the same)
[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y
[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type
Any ideas on how to solve this? |
68733
|
Fri Feb 2 00:02:54 2018 |
| Yves | vanhaarlemyves@gmail.com | Question | Windows | 2.9.2->3.1.3 | Re: v3.1.3 does not work with logbooks from v2.9.2? - solved | Hi Andreas,
Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories (version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking and removing all the logbook files in the main directory version 3 now works.
Cheers,
Yves
Andreas Luedeke wrote: |
Hi Yves,
just my two pence, maybe they help you to figure out what's going on:
versions 2.* had all entries of one logbook in one directory. Version 3.* create a subdirectory for each year. This had been added for me: if you use AFS for logbook storage, then you have a limit on how many files you can put into a single directory.
So the first time you start elogd 3.* with data from an elogd 2.* it should move all your logbook entries into sub-directories for each year. If that would have happened, you would not be able to use these logbook directories with the 2.9.2 version.
Maybe your logbook client is not allowed to create sub-directories? Although I would guess that it then would just throw an error message and stop.
Cheers, Andreas
Yves wrote: |
I have just upgraded elog from 2.9.2 -> 3.1.3.
3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.
Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.
When running 2.9.2 on the same machine, all runs wel (attachment 2)
cfd file: (I only left in one logbook - they are all configured the same)
[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y
[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type
Any ideas on how to solve this?
|
|
|
67699
|
Mon Sep 8 14:51:35 2014 |
| Sara Vanini | vanini.sara@gmail.com | Question | Linux | latest | default font style | Hi,
is it possibile to set a default font style: format, font, size, color, etc? how?
Thanks a lot
Sara
|
67701
|
Tue Sep 9 15:42:53 2014 |
| Sara Vanini | vanini.sara@gmail.com | Question | Linux | latest | Re: default font style |
Thanks! but I'm lost in the themes/default/default.css file.... which is the entry I have to edit for the style of the body text (Format "Normal") of the elog pages?
Sara
|
68698
|
Mon Nov 13 12:58:41 2017 |
| Sara Vanini | vanini.sara@gmail.com | Bug report | Linux | 3.1.1-1-1 | drop-down list not working | Hi,
after ubuntu 16 system upgrade, elog version (3.1.1-1-1) on firefox version 56.0+build6-0ubuntu0.16.04.2 , the drop-down menus (Styles, Font, Size, etc) don't work anymore.
How can I fix it?
Many thanks!
Sara |
69089
|
Fri Jan 24 14:56:04 2020 |
| Sara Vanini | vanini.sara@gmail.com | Bug report | Linux | 3.1.3 | editor hangs intermittently | Hello,
I'm using ELOG with Ubuntu 19. When I create or edit an entry and I start writing, it hangs for few seconds, resumes, and all over again intermittently.
How can I fix it?
Best
Sara |
69090
|
Fri Jan 24 14:56:56 2020 |
| Sara Vanini | vanini.sara@gmail.com | Question | Linux | Windows | 3.1.3 | local usage on windows + Linux virtual machine | Hello again,
I love to use elog, but I don't need any other accessing it for the moment. So, it is possible to run elog locally on my PC, and make it not accessible from outside?
Moreover, I installed elog on a linux virtual machine running with Virtual Box on Windows 10. Is it possible to open/edit my elog both from the linux VM and from the Windows system? without any accessibility from outside my PC?
Many many thanks
Sara |
|