Lotus Notes 6.5.1 Forum

I tried it with Red Hat 9B, Suse 9.0 and Mandrake 9.2.

Unfortunatly the installer doesn't work.
So just create an installation under Windows and copy the directory to the crossover-windows directory.
Then add the following dll's: mfc42.dll, mfc42u.dll, msvcp60.dll, msvcrt.dll.
Those can be found in systems32 in the original windows but have to be copied to the windows-directory under crossover.

Then start the whole thing with:/opt/cxoffice/bin/wine --check --cx-app "C:////nlnotes.exe"

The client runs fine - didn't have any problems so far (used Mandrake for the most times). Think the performance is a littlte slower.
Used the Admin-Client and it works too. But stay away from all those things in the Admin-Client that use java-applets - this will crash your notes.
Haven't tried the designer so far.

This all applies to 6.5.1 only (with Crossover 2.1.0)

Harald Gaerttner

PS: I tried to get it run under native wine. Forget it. The easier setup, the better performance and better look (with wine I only got it run in a separate window) are worth the price of a Crossover license!

Finally found something that doesn't work in the client:

The color is missing in the calendar (but works in the mailfile).
In the calendar you get the color only on mouse-over.

Harald Gaerttner

Hi,

I've just downloaded a demo version of Crossover Office (2.1.0) but trying to get Lotus Notes 6.5.1 up and running I get an error saying "Not enough space for thread data".
Did anyone have such a problem?

Regards
Luke

Nope I have not seen that one. Did you follow the method for install shown on the Tips & Tricks page? Did you copy all/correct DLL's? Also the following would help:

Distro:
Kernel:
glibc:
Command used to run notes:
And at what point you recieved the error:
(Startup--before pw prompt/after pw prompt--, opening mail/databases, composing, replication, etc)
Install type for Crossover: (since it's the demo version it's a root install but for future posts...)
And anything you might think would help.

Yes, I had the same problem. Some of the dll's cause the trouble just by residing on your computer (very strange!).

Just use the mfc42.dll and msvcp60.dll and forget the others. Then it should work fine!

Harald Gaerttner