| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 80.1 | NT v4.0 is NOT a problem | YAE385::curless | | Tue Jan 07 1997 12:34 | 7 |
| 80.2 | | THOLIN::TBAKER | The Spirit of Apathy | Tue Jan 07 1997 13:01 | 4 |
| 80.3 | eXcursion / DECnet ?? | BULAN::peoto.soo.dec.com::bulan::ptorlind | | Thu Jan 09 1997 03:03 | 12 |
| 80.4 | Not until Winsock 2.0 ships | YAE385::curless | | Thu Jan 09 1997 08:48 | 9 |
| 80.5 | Clarification Needed re: DECnet Support in PW32 | MKOTS3::HAHN | SBU Americas Technical Support Group | Tue Feb 04 1997 12:30 | 16 |
|
Jeff,
I just wanted to confirm what I think I am hearing. If a customer has a PC
running Windows 95, and they want to connect to file and print services offered
by a PATHWORKS OpenVMS Lan Manager server via DECnet, they will not be able to
do it using the PATHWORKS 32 product. The DECnet stack and any application
using DECnet simply do not work. Is that correct?
As an alternative, if a customer needs DECnet for a Win95 PC right away, I
suspect that a customer could still order PW for Win95 via the PW DOS/Windows
V6.0 QA-0TLAA-H8 kit, correct?
Thanks,
Dave
|
| 80.6 | my understanding | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Feb 04 1997 13:34 | 7 |
| Nononono.... DECnet works, just the Winsock interface to it that
won't until Microsoft releases the 2.0 bits. Non-winsock applications,
including NetBIOS applications (including the redirector or
"workstation service" which is what makes file/print connections) will
not suffer.
|
| 80.7 | correction | JAMIN::MAJEWSKI | | Tue Feb 04 1997 14:52 | 23 |
| I just wanted to confirm what I think I am hearing. If a customer has
a PC running Windows 95, and they want to connect to file and print
services offered by a PATHWORKS OpenVMS Lan Manager server via DECnet,
they will not be able to do it using the PATHWORKS 32 product.
The DECnet stack and any application using DECnet simply do not work.
Is that correct?
** NO, the above is NOT correct!!
PATHWORKS 32 V7.0 offers DECnet connectivity on W95 and WNT.
What will not be available on W95 in PW32 (initially) is
WinSock 2 DECnet. This is because Microsoft has not yet
released WinSock 2 for W95. WinSock 2 on WNT was part of
the WNT V4.0 release.
PATHWORKS 32 will support WinSock 2 on W95 in a patch kit
as soon as possible.
As an alternative, if a customer needs DECnet for a Win95 PC right
away, I suspect that a customer could still order PW for Win95 via
the PW DOS/Windows V6.0 QA-0TLAA-H8 kit, correct?
**correct.
|
| 80.8 | Which apps are affected? | MKOTS3::HAHN | SBU Americas Technical Support Group | Tue Feb 04 1997 18:17 | 8 |
|
Thanks for the clarifications.
eXcursion and CTERM have been mentioned in this string as applications which
will not work out-of-the-box using DECnet in PW32 because they use/require
the Winsock 2.0 support. Are there any other PW32 applications that are
affected?
|
| 80.9 | When and How? | ALFSS2::OLSEN_G | Hey y'all, how y'all doin'? | Tue Mar 18 1997 11:37 | 17 |
| It appears that Exceed (Hummingbird) is in this "broken" group as well.
Customer says Exceed starts, allows him to open a decterm window then
gets a fatal error. If he doesn't acknowledge the error by clicking the
OK button, he can work in the decterm window. If he hits the OK in the
error window, decterm stops and Exceed terminates.
Question - When Microsoft releases the winsock 2 component, will we
distribute it with the patch noted or will they have to get it from
Micosoft. If the latter is true, how does Microsoft intend to
distribute it.
ALSO - Winsock 2 doesn't support simultaneous multiple protocols
(according to what I've read). Seems that that is
a step backward and is going to bite us. No?
Gary
|
| 80.10 | | JAMIN::WASSER | John A. Wasser | Tue Mar 18 1997 15:05 | 15 |
| > Question - When Microsoft releases the winsock 2 component, will we
> distribute it with the patch noted or will they have to get it from
> Micosoft.
If Microsoft make it available in time we hope to ship it
with the "TIMA" release (V7.0a). If not, we ship without them.
> If the latter is true, how does Microsoft intend to distribute it.
I would guess that you could download it from Microsoft.
> ALSO - Winsock 2 doesn't support simultaneous multiple protocols
> (according to what I've read).
Where did you read that? I don't think it is correct.
|
| 80.11 | | SPELNK::curless | | Tue Mar 18 1997 17:51 | 7 |
|
The issue is SELECT does not span protocols... so you have to handle
selects over separate transports as separate selects... so it changes
the code... i.e. support two transports, do two selects, three, do three...
not nice, considering Winsock 1.1 on NT did....
Jeff
|
| 80.12 | an interim solution for 16 bit apps..... | JAMIN::REICHLEN | | Fri Mar 28 1997 13:46 | 11 |
| If you currently have a *16 bit DECnet* winsock 1.1 application that
used the winsock.dll that came with W95 V1.0, your application will work
without Winsock 2.0 for now. The PATHWORKS 32 CD contains the winsock.dll
in the PWSDK\BIN directory. Copy it down from the CD but be careful
not to delete the winsock.dll from Microsoft. Use this as in interim
solution only.
Diane
|