From: NoEMail@home.org   
      
   >   
   > So the A was a fresh install of 15, but B was an "upgrade" from a prior   
   > 14.2 install?  Don't you think that little tidbit of information might   
   > have been useful to have included in your first post?   
      
   No, that's not what I meant to say. Using the same USB install disk   
   that I used for the original install on A, I installed 15.0 on   
   machine B. I installed some of my stuff from source on B, and   
   ran the machine for a while. Then I upgraded the packages on B.   
   Thereafter the problems started.   
      
   >   
   > Reinstall afresh 15.0 onto B, then copy/compile the custom items you   
   > want to add.  At which point you should have a B that works properly.   
      
   Did that this morning.   
      
   >   
   >   
   > In which case you should have well learned enough to fix this glitch   
   > all by yourself without asking anyone anything.   
      
   Perhaps. I asked for help after everything I tried failed.   
   As I mention in the previous response, the problem seems   
   to have been in the drive. It was a 1TB Samsung 870 EVO, with   
   two equal partitions. I had previously had 14.2 on both partitions.   
   I reformatted the first partition before starting the install.   
      
   >   
   >> The OPENSSL....  stuff came from some early version of Slack, but I   
   >> can't imagine what I did to cause it.   
   >   
   > Sounds like you might have installed some 14.2 packages onto B's 15   
   > install (or the update from 14.2 to 15 borked and left some 14.2 cruft   
   > behind that should have gone away instead.   
   >   
   > A fresh, new, install of 15 on B is probably the best way to clear up   
   > the issue.   
      
   I already agreed to that, and have done so.   
      
   Thanks again Rich.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)