Ross Scroggs wrote:
 
     >MPE/V System Administrators Pay Attention!
 
     >If you've received the MPE/V Release 40 Turbo Update, don't install
     >it without talking to the Response Center. It uses a special version
     >of sysdump to make your update tape. In the process of making a new
     >SL on tape it aborts because the temporary SL is built too small. You
     >have to coldload and restore @[log in to unmask] to get back to a working system.
     >There is a patch that will be available that will fix the broken
     >sysdump to perform correctly. I'm not sure if the patch is actually
     >available yet as we discovered the problem on 9/18 and a CE/SE in
     >Australia had the problem on 9/14.
 
     Having had the honor of being the customer who actually discovered
     this undocumented feature of the Turbo Update process a couple of
     weeks ago ;), and having worked with the lab engineer who wrote the
     sysdump-like program to get the problem resolved, I can tell you that
     there _is_ a patch to "fix" the program.  Whether or not it is readily
     available is, of course, another question.  Once the program is
     patched, however, it works very well.
 
     The problem seems to have stemmed from the fact that the old V'ers
     don't like an SL bigger than 32k.  The program would copy the SL and
     set the FLIMIT to the EOF on the copy, so when it comes time to delete
     and add segments if you have a big SL (lots of HP products), you might
     not see the problem, if, like us, your SL is relatively puny...watch
     out!
 
     As far as restoring @[log in to unmask], my experience was that the COLDLOAD
     sufficed.
 
     Adam Dorritie
     [log in to unmask]