[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Multia |
|
Moderator: | ONTIME::SYSTEM |
|
Created: | Tue Oct 04 1994 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 782 |
Total number of notes: | 3413 |
777.0. "LAT and KEATERM startup issue" by COMICS::SYMONDSK () Mon May 19 1997 12:29
Dear All,
I have a customer who is having problems with LAT and KEATERM on his
Intel Multia running V3.2. The exact problem is as follows:
Customer has setup an environment where they automatically fire up a
KEATERM session which in turn logs the session into a restricted
account on their OpenVMS system, which then set's display back to the
Multia and fires several apps back to the Client. The problem with this
is that LAT doesn't start up in time for KEATERM to log in and the user
gets prompted with 'LAT protocol not available'. So the question is, is
it possible to get around this , and if so how.
I thought it maybe possible to delay the startup of the KEATERM
session, but sadly there isn't a pause facility in NT 3.51 which
would allow this.
Any help would be appeciated
Regards,
Kevin Symonds.
(CSC - Basingstoke)
T.R | Title | User | Personal Name | Date | Lines |
---|
777.1 | | GWEN::KAUFMAN | Engineering MGR Xterminals and Multia | Fri May 30 1997 12:15 | 5 |
| This problem is fixed in V3.2-SP1-T3. All autostarted
applications will now wait until all enabled protocols are available.
Regards,
Joel
|