7
I seem to recall that the SOM.IR file that sits in \os2\etc, when corrupted, can cause Lotus 1-2-3 all sorts of problems.
My experience certainly can attest to this.
Here is what I have on my machine:
Directory of G:\os2\etc
6-30-99 4:28p 496,503 0 a--- SOM.IR
1 file(s) 496,503 bytes used
44,077,031 K bytes free
EDIT
====
I forgot to add, the SOM* files exist in other directories as well, such as:
1) \os2\etc\dsom
2) \os2\system
Not sure to what extent, if any, these may be impacting you, but as I mentioned above I did take to making a backup of the good & working known compies in case they every "go away":
Directory of G:\os2\etc\dsom
8-25-18 6:06p <DIR> 701 ---- .
8-25-18 6:06p <DIR> 528 ---- ..
5-19-25 12:01p 6,384 0 a--- SOMDCLS.DAT
11-10-98 9:36p 6,496 0 a--- SOMDCLS.DAT.working-state
5-19-25 12:01p 6,844 0 a--- SOMDCLS.TOC
11-10-98 9:36p 6,904 0 a--- SOMDCLS.TOC.working-state
5-19-25 12:01p 1,012 0 a--- SOMDIMPL.DAT
11-10-98 9:36p 3,036 0 a--- SOMDIMPL.DAT.working-state
5-19-25 12:01p 60 0 a--- SOMDIMPL.TOC
11-10-98 9:36p 172 0 a--- SOMDIMPL.TOC.working-state
10 file(s) 30,908 bytes used
44,076,982 K bytes free
AND
Directory of G:\os2\system
6-30-99 4:34p 15,056 0 a--- SOMD.MSG
7-30-96 9:42p 15,056 0 a--- SOMD.MSG.working-state
6-30-99 4:34p 780 0 a--- SOME_OS2.MSG
7-30-96 9:14p 780 0 a--- SOME_OS2.MSG.working-state
6-30-99 4:34p 3,718 0 a--- SOMK.MSG
7-30-96 8:23p 3,724 0 a--- SOMK.MSG.working-state
7-30-96 10:05p 1,403 0 a--- SOMR_OS2.MSG
7-30-96 10:18p 3,527 0 a--- SOMUCOS2.MSG
8 file(s) 44,044 bytes used
44,076,982 K bytes free
It's been a while though, and some of this may have been precautionary backup as I installed things such as VisualAge CPP, etc.