Hi, folks:
Following Jon Bale's advice to follow my own instructions (documented in
Robelle's SMUG Book under "How to read a manual"), I re-read his original
post with great care and, sure enough, I found this treasure buried in
there:
____________________________________________________________
How can you avoid experiencing this problem on your IMAGE
database?
Although we cannot be sure that the defect we repaired is the
unique cause of this problem, I will assume that it is, for
the purpose of addressing this question. The simplest
answer, then, is: Install and use one of the TurboIMAGE beta
patches mentioned above. This is the only option that I
recommend.
____________________________________________________________
So, there it is, straight from the boss's keyboard!
Let me stress that this is THE ONLY OPTION that Jon recommends. So, all of
our collective wonderings about "what to do" were caused by our too-quick
reading of his original post.
FYI, the patches are (quoting again from Jon Bale's original post):
We have developed a fix for TurboIMAGE that removes this
defect. Patches will be created for MPE/iX 5.0 and MPE/iX
5.5. The MPE/iX 5.0 patch is TurboIMAGE version C.06.23 and
has Patch ID TIXKX11. The patch for MPE/iX 5.5 is TurboIMAGE
version C.07.07, has Patch ID TIXKX13, and is built on the
version of IMAGE released on MPE/iX 5.5 Express 3.
Be sure to quote Jon Bale when you contact HP's Response Centers.
Before contacting HP's Response Centers, though, you might want to re-read
Jon's original document. For your convenience, I placed it at Adager's web
site a while ago:
http://www.adager.com/DdxPostJon.html
_______________
| |
| |
| r | Alfredo mailto:[log in to unmask]
| e | http://www.adager.com
| g | F. Alfredo Rego Tel 208 726-9100
| a | Manager, R & D Labs Fax 208 726-2822
| d | Adager Corporation
| A | Sun Valley, Idaho 83353-3000 U.S.A.
| |
|_______________|
|
