| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hi All,
Some of our customers appear to be of the opinion that they do not have
to deintegrate WordPerfect version 2.0 from ALL-IN-1 IOS 2.%, to
upgrade to 3.0 !!! I was a bit taken by all of this confusion and
having looked at the WordPerfect manual for the 3.0 integration it does
not specify that *YOU MUST* deintegrate WordPerfect on your 2.% system
before the upgrade.
So I am enclosing a check list of what needs to be done below to
upgrade to ALL-IN-1 IOS and install/integrate WordPerfect.
1) @WPCORP$OA20DIR:WPCORP$OA20_DEINTEGRATE.COM
2) Upgrade ALL-IN-1 v2.4 to ALL-IN-1 v3.0
3) @WPCORP$OA30DIR:WPCORP$OA30_PREINTEGRATE.COM
The Pre-Integrate cleans up particular OA2.0 files by:
A) Copying the WPCORP$OA20DIR:*DEF.DAT to
WPCORP$OA30DIR:WPCORP_OA_PRINTER<51>_DEF.DAT
B) Deleting any WPCORP Format Master
C) Renaming any ALL-IN-1 v2.x A1LINK.COM & OAET.MAR to OLD_*.*
4) @WPCORP$OA30DIR:WPCORP$OA30_INTEGRATE.COM
5) @WPCORP$OA20DIR:WPOA020_STARTUP DE FULL
By the way OAINI.SCP is not longer required in version 2.% WordPerfect
updated it with some initilisation functions. I got the above from our
local WPC office. By the way there was one customer who did not
deintegrate the 2.0 kit the upgrade finnished and they were able to use
the 2.0 integration BUT ran into problems later on. For obvious
reasons CART will not pick up the WPC elements.
I hope it helps someone and alerts you all to what some customers
though and what one customer did :-).
Regards,
Sunil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3046.1 | Things that i've noticed | AIMTEC::WICKS_A | U.S.A 2 England 0 - I was there! | Thu Jul 22 1993 16:35 | 19 |
Sunil,
great note - surely it should be a STARS article too?
one other gotcha is at step 3C to double-check the contents of
SITELINK30.COM - i'd say that 9 out of 10 customers just rename
SITELINK24 to SITELINK30.COM without removing the reference to
the old WPCORP integration (they usually forget to remove OADEBUG too)
and one clarification on what to do when the customer doesn't do
things properly...
since WPCORP registers its changes to A1V24_SITE_START, A1LINK,
SITELINk24, OAINI and OAET you should remove those elements from
live if the DEINTEGRATE wasn't run before the v3.0 upgrade
Regards,
Andrew.D.Wicks
| |||||