Aha .. ;)

 SD> *** Quoting Rich Wonneberger from a message to Sean Dennis ***

RW> Can this file be set to read only?? I had this problem with sharing
RW> the DOS version of Fox Pro.  I had to set the attribute of an .inf
RW> file that each workstation accessed.

Could have been opened in error as read-write, not read only!

 SD> Actually, it was a third-party driver (XF86SUP.SYS) 
 SD> that I was using for another program.  I removed that 
 SD> driver and all of those problems have disappeared.  
 SD> Don't ask me why or how, but it has. :)

Wait until you hit this in the Lotus Smart Suite package with the SOM.IR
files!  If you have Lotus Smart Suite, I've discovered the only way to keep
from corrupting them, at least as far as 1.7,, is to open Lotus 123 and
close it just after you boot up.  Otherwise, if you use WordPro from it to
view .DOC files on an exit shell call basis, say from File Freedom to read
those M/S files, you'll sometimes get corruption of the SOM.IR files and
have to re-install the application or the corresponding SOM.IR files from
backups!

As far as I can see, somehow, in Lotus, they are opening the SOM.IR files
as read-write, of all things!  And when the shell operations don't somehow
see that in their environment for the call .. poof - either SOM.IR files
that are only 128 bytes long or, I think 512 bytes long in some cases!  And
thus garbage.  Don't have the latest SS collection. But this has been in
there since the original version and I can't get it fixed although the
corruption is known in the Lotus forums that others have seen too..

Be glad your other program threw you the error you could see to find and
fix this.  Without trashing your application installations.

;)


--> Sleep well; OS/2's still awake! ;)

Mike {at} 1:117/3001

--- Maximus/2 3.01