| 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 |
Hi, I wonder if someone can help me with this interesting problem. In the past customer had the following configuration. Shared installation of Windows for Workgroups V3.11 Shared installation of TeamLinks V2.5 office.ini located on the M: drive of every user. Now they have the following configuration Local installation of Windows NT V4.0 Workstation Shared installation of TeamLinks V2.7 office.ini located on the M: drive of every user Althought the path variable has been modified to include M:\, TeamLinks still looks for the office.ini in the \WINNT directory. Even if you rename office.ini in the \WINNT directory and start TeamLinks a new office.ini will be created in the \WINNT directory. Is there a way or method to tell TeamLinks to use the office.ini on the M drive. Regards, Martin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2132.1 | TAMARA::CUMMINGS | Jerry Cummings, TeamLinks | Thu Apr 17 1997 11:15 | 10 | |
As far as I know, there is no way to use any OFFICE.INI that is not in the Windows System directory. I imagine some of the support people will see this not and correct me if I'm wrong, but I'm pretty sure we've had this problem a long time. Jerry | |||||
| 2132.2 | We'll wait until TeamLinks is 32 bits | UTRTSC::SMEETS | Workgroup support | Fri Apr 18 1997 06:26 | 8 |
Hi Jerry, Thanks for your answer. So we'll have to wait until TeamLinks is fully 32 bits and uses the registry to store it's settings. Regards, Martin | |||||