Subj : SOM.IR corruption To : Mike Luther From : Will Honea Date : Wed Jan 15 2003 12:37 am Mike Luther wrote to All on 01/13 ML> What is the rule of thumb on all this SOM madness? If this ML> kind of thing can wreak an application collection like ML> this, what do we really need to do to check this? Does one ML> really have to make a special trip around the SOM.IR ML> directories to see what REALLY has been pranged, every so ML> whatever times? ML> ML> Just how does this SOM thing work anyway and what ARE the ML> caveates? Mike, the rule that works for me is that NOTHING supercedes the Warp system directories. VACPP 3 had a bad habit of back leveling SOM that would kinda sneak up and bite when you least expected it. I don't know what SOM directories are used by Lotus - don't run the critter - but keeping everything subservient to the original system ir's works for me. WTF! Just looked at config.sys and what a mess on the set somir= line - how the heck is this thing running, anyway? Anyway, reset it and I'll see what happens - maybe that where some of the funnies are coming from lately. FYI, the MCP1 with CP03 has the following: Directory of E:\OS2\ETC 9-06-00 12:42p 66,058 0 a--- REXX.IR 6-30-99 4:28p 496,503 0 a--- SOM.IR 11-14-00 6:06p 60,855 0 a--- WPDSERV.IR 11-14-00 5:53p 274,823 0 a--- WPSH.IR 4 file(s) 898,239 bytes used and each in referenced with an explicit path in config.sys. Will Honea ___ þ KWQ/2 1.2i þ I'm an OS/2 developer...I don't NEED a life! --- Maximus/2 3.01 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) .