From: "James C. Sewell" 
Back on Jun 13th I responded to a posting from Fred Holmes.  Unfortunately
I sent it to tse-pro instead of tsepro .  I think the principal may
help others with future upgrades so I am going to resend it here to the
right address.
At 08:00 AM 6/13/97 -0500 FRED HOLMES, whom God loves, said:
>It would be nice to also have
>a detailed recipe for accomplishing the maintenance release
>upgrade from 2.50a . . . to 2.50e 
The unfortunate part of it is that depending on how much you have
customized your TSE a ecipe could be either disaster or astonishing
success.  In my case I've changed the UI so uch that a recipe would kill me.
One thing I did to help this is the following (assuming you are using the
TSE.UI file):
1. Take any functions that you have added to the UI and put 
   them in another file.  Mine is JCS.UI (my initials.)  
2. Put the line
         #include ["jcs.ui"]  // Custom ui code.
   somwhere near the top of the TSE.UI file.
3. Put a comment at the top of JCS.UI reminding me of all the
   changes I have to make to TSE.UI that can't be moved to a
   different file.  Example: I have hooks that need to be called
   in the whenloaded() routine so I just copy the code to the
   comment and it's cut-and-paste to restore it to the new version
   TSE.UI when it comes in.
This saves a LOT of time and work when I get a new version.  All I have to
do is to add he #include line and cut/paste 5 lines for my other
customizations.
Hope it helps!
   Jim
---
---------------