| 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 |
P. 6-4 of the installation guide contains a reference (section 6.4)
concerning reviewing object libraries and .OBJ files in the SITE
Source directories for "incompatibility" with ALL-IN-1 V3.0.
As this is a preinstallation task, how does one determine if any
customized files/libraries here are "incompatible?" Will the
CART have anything to say about potential incompatibilities with
respect to these files?
Thanks,
Steve
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 70.1 | They're not used until after the upgrade... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Feb 21 1992 09:22 | 16 |
During installation, the link is done excluding any object files and
libraries in the site areas, so there's a good chance that the image
will come up working.
After the installation, when you start hacking around with SITELINK to
include all ths stuff preparatory to a relink, we're warning you that
*NOW* we'll start picking up the site stuff and you should review it.
the CART doesn't cover objects, since neither they, nor the source that
generates them, were supported by CM prior to V3.0. Apart from that,
it's obviously an impossible task to look at an object file and see if
it's going to work with V3.0. It's hard enough with forms and scripts!
Hope that's clearer,
Graham
| |||||
| 70.2 | Understood | GLOVES::ALLERTON | Steve Allerton 343-0205 | Fri Feb 21 1992 11:49 | 9 |
Graham,
Yes, much clearer thanks...I noticed that the recommendation reappeared
as a postinstallation task...
Regards,
Steve
| |||||