| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 95.1 | See note 84 | JOBIM::VUJNOVIC | I�t�r��t���l�z�t��L���l�z�t�� | Thu Jan 23 1997 16:30 | 15 |
| 95.2 | Deselect everything | TLE::LUCE | Charlie Luce, Digital Unix QCS | Thu Jan 23 1997 18:36 | 6 |
| 95.3 | Telnet only: deselect everything | JOBIM::VUJNOVIC | I�t�r��t���l�z�t��L���l�z�t�� | Fri Jan 24 1997 03:49 | 14 |
| > -< Deselect everything >-
>
> I've run the PATHWORKS 32 setup, deselected everything, and then
> installed PowerTerm 525, and I'm connected over Telnet as I type.
That's essentially what 84.5 is saying. So, deselecting everything
seems to bring in
DECTAL.DLL and its related files
ASLAPI.DLL and its related files
which is the only thing PowerTerm uses from PATHWORKS 32. Telnet
is already there as part of the platform. Not sure where Winsock
comes into play...
|
| 95.4 | a manual way... | nova05.vbo.dec.com::BERGER | | Fri Jan 24 1997 03:54 | 9 |
| Slo
FWIW, I'm running PowerTerm/Telnet on NT 3.51 Alpha after running the
setup of Powerterm and copying DECTAL.DLL, ASL*.DLL, PWTELNT.DLL to
the PowerTerm directory. Seems to work just fine, including Single
Logon. The only thing this leaves out is the event logging stuff but
it doesn't bother me.
Vincent
|
| 95.5 | We'll eventually know... | JOBIM::VUJNOVIC | I�t�r��t���l�z�t��L���l�z�t�� | Fri Jan 24 1997 08:05 | 15 |
| >FWIW, I'm running PowerTerm/Telnet on NT 3.51 Alpha after running the
>setup of Powerterm and copying DECTAL.DLL, ASL*.DLL, PWTELNT.DLL to
>the PowerTerm directory. Seems to work just fine, including Single
>Logon. The only thing this leaves out is the event logging stuff but
>it doesn't bother me.
If you want the languages, you'd also need the PWASSTxx.HLP and .CNT
files for the Password Assistant help. That should be it.
In this version, PowerTerm is not using the Event Logger directly
at all, but I guess you are referring to DECTAL.DLL and PWTELNT.DLL,
which do.
Regards,
Slobodan
|
| 95.6 | just choose licensing | VMSNET::M_SMITH | | Fri Jan 24 1997 09:03 | 8 |
| re .1
We have installed powerterm under nt and win95. Then we run pw32
setup and select just licensing. This seems to get us everything we
need for powerterm over telnet.
Michael
|
| 95.7 | It's getting better and better... | JOBIM::VUJNOVIC | I�t�r��t���l�z�t��L���l�z�t�� | Fri Jan 24 1997 11:26 | 0 |
| 95.8 | or just VT320 | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Jan 27 1997 14:35 | 32 |
| re: .6
>...setup and select just licensing....
also selecting just VT320 (which actually makes more sense from a
what-to-tell-the-customer standpoint :-) works to, at least with
today's pw32daily bits.
13:56:45 LOG0002N: Start Logging at 13:56:45, on Monday January 27, 1997
13:56:47 LOG0015N: Message Logger Service (PWLOGSVC) V1.0.000
13:56:47 LOG0011N: NT Version 4.0, Build (1381)
13:56:47 LOG0012N: Hardware Platform: Intel 486 (305), Processor(s): 1
13:56:03 CORE0001S: DECCORE Version 1.0.4
13:56:03 CORE0002S: Copyright (c) 1995,1997 Digital Equipment Corporation
13:56:04 IOCB0006N: DECIOCB Installed successfully
14:05:01 PWIO0001S: IOCB/DSCB Interface Library (PWIOCB32) Version 1.0.011 Loaded Successfully.
14:05:01 TNET0001S: pwtelnt (pwtelnt) Version V7.0.007 Loaded.
14:05:02 CTRM0001S: pwcterm (pwcterm) Version V7.0.007 PWCTERM Loaded.
14:05:02 TAL0001S: Terminal Access Library [32-bit] (DECTAL) Version 1.0.012 Loaded Successfully.
14:05:13 TNET0003N: Session 0 opened to host mickey
14:06:01 TNET0004N: Session 0 closed. Status = 0
14:06:03 CTRM0002N: CTERM Unloading
14:06:03 TNET0002N: PWTELNT Unloading
14:06:03 PWIO0002N: PWIOCB32.DLL Unloaded Successfully.
14:06:03 TAL0002N: DECTAL.DLL Unloaded Successfully.
14:25:59 PWIO0001S: IOCB/DSCB Interface Library (PWIOCB32) Version 1.0.011 Loaded Successfully.
14:25:59 TNET0001S: pwtelnt (pwtelnt) Version V7.0.007 Loaded.
14:25:59 CTRM0001S: pwcterm (pwcterm) Version V7.0.007 PWCTERM Loaded.
14:25:59 TAL0001S: Terminal Access Library [32-bit] (DECTAL) Version 1.0.012 Loaded Successfully.
14:26:00 TNET0003N: Session 0 opened to host pwrks.alf.dec.com
|
| 95.9 | on both win95 and wnt? | VMSNET::DMCFARLAND | | Mon Jan 27 1997 14:46 | 7 |
| steven,
does this work with BOTH win95 and wnt? it seems i read something
somewhere that it worked on one, but not the other...?
di
|
| 95.10 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Jan 27 1997 15:16 | 3 |
| I don't know, diane, give it a try :-)
sorry, but all my testing's been on Goofy thus far.
|
| 95.11 | How integrated is eXcursion installation? | JOBIM::VUJNOVIC | I�t�r��t���l�z�t��L���l�z�t�� | Tue Jan 28 1997 13:28 | 10 |
| Out of curiosity, what if you just want to install eXcursion (I've
not done it with recent versions...)
I realize it does not need DECTAL and talks directly to telnet
and DECnet, but I'm not sure if it needs anything else.
(Just trying to find out if PowerTerm is the least integrated one,
but I guess I already know the answer...)
Slobodan
|
| 95.12 | my $.02 | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Jan 28 1997 13:47 | 5 |
| based on the facts that
- eXcursion has all along been designed as a stand-alone product
- eXcursion does not take advantage of the Password Assistant
...I would suspect that it still does not require any other PW bits,
but have not done any testing to prove this.
|
| 95.13 | LAT or TELNET no DECnet; or CTERM&DECnet PowerTerm Works | JAMIN::TELESETSKY | | Fri Jan 31 1997 11:29 | 23 |
|
Using a WinNT v4.x client, I've found that the following configurations
chosen from the PW32 client work with PowerTerm :
Run PW32 setup and select nothing, PowerTerm works over TELNET
Run PW32 and select only LAT and maybe Licensing, PowerTerm works over LAT
You -don't- have to install DECnet to use PowerTerm over LAT or
TELNET.
In order to run PowerTerm over CTERM, you have to have DECnet AND
Winsock2. In Win NT v4.0, winsock2 is already incorporated in WinNT
v4.0 and this configuration will work. However, in Win95 the winsock2
is not released yet and neither PowerTerm -nor- Vt320 will work over
CTERM and DECnet on it.
Regards,
Marsha T. January 31, 1997
|