Title: | TeamLinks for Windows |
Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
Created: | Mon Aug 28 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2238 |
Total number of notes: | 9650 |
Teamlinks EFT 3.0 Customer would like to know if it is possible to stop the reboot after the installation. They are writing some installation procedures to install many software programs at the same time and they need to just do one reboot at the end of this procedure. Thanks, Beth Andres
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2129.1 | MANANA::PRINCIPIO | Tue Apr 15 1997 13:58 | 17 | ||
> Teamlinks EFT 3.0 > > Customer would like to know if it is possible to stop the > reboot after the installation. > > They are writing some installation procedures to install > many software programs at the same time and they need to just > do one reboot at the end of this procedure. No, there isn't a way to turn this behavior off. The best thing to do is to close down all the applications (not just TeamLinks) before installing. That will probably prevent the reboot from happening. ...helen | |||||
2129.2 | Just verification | OASS::ANDRES_B | Tue Apr 15 1997 16:13 | 10 | |
Helen, Note 1690.4 says with version 3.0 of TL that a reboot will not be necessary. I just want to verify that 3.0 will not require a reboot after installation. Thanks, Beth | |||||
2129.3 | XANADU::PRINCIPIO | Wed Apr 16 1997 09:24 | 23 | ||
> Note 1690.4 says with version 3.0 of TL that a reboot will > not be necessary. I just want to verify that 3.0 will not > require a reboot after installation. That note was addressing a very specific situation (when a DDE communications error occur). And although it won't force an immediate reboot, if the install detects there is a communication error with DDE, it will tell the user that they need to reboot and it will then exit the installation. So to the correct the problem you need to reboot, but the install doesn't force you to do so. That is just one situation. The installation hasn't been modified to not require a reboot in other circumstances that it always did. So, V3.0 can still cause a reboot. I believe there are a couple of situations that cause a reboot - one is that the install added TeamLinks to the path. That shouldn't be a problem on an upgrade as it's probably already on the path. The other situation can come about because some files are in use during the install. That's why I said it would be best if they shut down all applications. .....helen |