| Title: | Digital PATHWORKS 32 |
| Moderator: | SPELNK::curless |
| Created: | Fri Nov 01 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 337 |
| Total number of notes: | 1612 |
An existing PWKS for DOS and Windows has been using the SDK tips,
mostly to be able to use DECnet sockets from a Windows applications.
I cannot see a SDK / Toolkit on the new PATHWORKS 32 System
I can only read one line in the Sales Update saying " Protected-mode
DECnet..... Winsock 2 support"
Does this mean that we provide API/sockets (or whatever name is the
right one) so that the customer can port his 16-bit DECnet-enabled
application to be a 32-bit DECnet-enabled application, and sit it on
top of PATHWORKS 32 ?
Best regards from pAris,
Philippe
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 131.1 | JAMIN::WASSER | John A. Wasser | Thu Feb 20 1997 10:37 | 14 | |
> I cannot see a SDK / Toolkit on the new PATHWORKS 32 System Look at: \I386\Pwsdk \Alpha\Pwsdk \W95\Pwsdk > Does this mean that we provide API/sockets so that the customer can > port his 16-bit DECnet-enabled application to be a 32-bit DECnet-enabled > application, and sit it on top of PATHWORKS 32 ? Yes. If they want to use the WinSock 2 interface on Windows 95 they will have to wait for Microsoft to ship it. | |||||
| 131.2 | Customer application should still work.. | JAMIN::REICHLEN | Fri Feb 21 1997 13:25 | 15 | |
If your customer has a 16 bit Winsock 1.1 DECnet application
on W95 then he should still be able to run:
In \w95\pwsdk\bin there is the same WINSOCK.DLL that
shipped with PATHWORKS for Windows 95 V1.0a. Be careful
*not* to delete any WINSOCK.DLL that comes with the
Windows 95 OS because that'll be your Winsock 1.1 to
Winsock 2.0 shim when Microsoft supplies Winsock 2.0
on Windows 95.
My recommendation is to upgrade to Winsock 2.0. If this is
done then your customer will have no need to use the WINSOCK.DLL
supplied by PATHWORKS 32.
| |||||