last updated at 21 Jul, 2002 22:08 (3 times)
As posted within the OS2 News by Craig:
Anyone running Lotus Notes for windoze under Odin might be interested in the following.
I have been running Lotus Notes v5.0.3 for a while under older versions of Odin. The Lotus directory structure was copied from a windoze NT machine, and the notes.ini was trimmed right down so that when I started Lotus Notes it treated me as a new user, asked for my user.ID file, and setup my local environment based on my existing setup on the notes server.
Replication never worked properly, so I had to open my mail database on the server (slow) and use archive to move mail down to my local PC. Also, the database icons were always black squares.
After initial startup and login there was a hang of about 30 seconds and then an error message. Replying to this message would cause a crash, so I just left it there, changed focus back to Lotus Notes, and after that most functions worked ok.
I tried upgrading to newer builds of Odin, but the 30 second hang at startup became a permanent lockup and crash of Lotus Notes. I finally discovered that there is a setting in the user mail profile for "Check Subscriptions" and it appears that this check is done after initial login. Unchecking this option box removed the 30 second hang and crash at startup. This enabled me to upgrade to newer builds of Odin which fixed up some functions of Lotus Notes with database buttons, etc.
I recently upgraded to Odin build 20020627 and was surprised to see that finally the database icons were correct, instead of just black boxes. I was encouraged to attempt replication of my server mailbox down to my local PC. The "New Replication" commenced and showed me the replicator page and a progress report, which was further than previous attempts would get. The replication proceeded and appeared to complete, but then there appeared an Odin error message and Lotus Notes crashed.
Restarting Notes showed the new local replica and it appeared usable. Opening the replicator page and pressing "start" kicked off a replication process and it completed ok, with no crash. I have fiddled with the replicator settings and it now seems pretty stable! I am still manually pressing the "start" button to kick off replication, but will soon try out the automated feature to schedule replications during the day. Currently pressing the other button for just "send/receive mail" (I think thats the button title) causes a crash so I haven't pressed that since... I just use the "start" button.
I changed the replication settings from medium priority to 'Low Priority'. Replication appears to be more stable now, but I haven't done enough testing to prove this change made the difference.
Most of the replication settings I did not change. They were things like:
Do send deletions out.
Don't send changes out for the title & catalog information.
Don't send changes out for the local security properties.
Allow incoming changes to Forms & Views.
Allow incoming changes to Agents.
Allow incoming changes to Access Control Lists.
Allow incoming changes for Deletions.
Changing these things may work fine. I just haven't messed with them.
Thanks to Netlabs and the Odin team for allowing me to keep running OS/2 in a windoze Lotus Notes v5 server environment, and thanks for the ongoing improvements to Odin to now allow me to use replication, because going to the server mailbox is SLOW!!
Using the latest Odin weekly ftp://ftp.os2.org/odin/Weekly/odin32bin-20020627-release.wpi
Hopefully this is useful to other OS/2 users who have been abandoned by Lotus.