| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 320.1 | | SPELNK::curless | | Wed May 28 1997 12:25 | 21 |
|
Good question, the identical question was brought up this morning in the
5x5. The problem is the latest Winsock 2 RC from Microsoft causes login
problems with PATHWORKS 32 installed ... and it looks like it is a Microsoft
issue. Winsock 2.0 is currently on HOLD from Microsoft, an offical date is
to be announced sometime this week from them on the availability of
Winsock 2.0 for Windows 95.
We have two options at the moment:
1) Ship PATHWORKS 32 v7.0a with latent Winsock 2.0 support for Windows 95,
like v7.0 did, and HOPE things work
2) Wait for the final release of Winsock 2.0, and ... how ever much time we
need to ensure that the software functions
We will have a decision on which path we are going to take by next week,
any votes would help (please reply to this note, or jamin::curless).
Thanks for being patient,
Jeff
|
| 320.2 | Some Customers Want it Now | VMSNET::P_NUNEZ | | Wed May 28 1997 18:32 | 10 |
| Jeff,
Lets do both - make it available to anyone requesting it now with the
understanding that it's not soup yet (some probably don't care about
the Winsock 2.0 support, but are looking for other fixes); when MS
releases Winsock 2.0, then ship the kit...
FWIW,
Paul
|
| 320.3 | | SPELNK::curless | | Wed May 28 1997 18:52 | 7 |
|
Only problem is... then there would be MULTIPLE versions of v7.0a, try
and sort those out in the CLD...
Jeff
(much like Service Pack 2 for NT v4.0, it depends on the date)
|
| 320.4 | My vote | 42080::BUZYAL::sharkeya | Who am I now ? | Wed May 28 1997 19:14 | 5 |
| Please ship it. Most of my customers have moved to TCP/IP anyway and don't
care about Winsock 2
Alan
|
| 320.5 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu May 29 1997 10:15 | 14 |
|
My vote is, let people that want it use it, with the understanding that
it's "not soup yet", it's "test software".
The confusion resulting from multiple versions out there will be more than
outweighed by the extra testing plus the custumer satisfaction of having
a version that fixes their particular long-awaited problem.
The problem of multiple versions can be helped by making sure the digital
laisons know what version numbers are official. That way, if a customer
complains about a test version, the liason knows to make it a QAR and not
a cld.
/Eric
|
| 320.6 | Potential Impact? | VMSNET::P_NUNEZ | | Thu May 29 1997 10:45 | 12 |
| re .3
Jeff,
Do you have a general feeling for the number of components which may
require changes once MS releases Winsock 2.0? Will it possibly impact
many executables/dlls/etc or only a few?
If multiple versions is a problem, I vote to ship the kit as is and let
7.0b(?) incorporate full Winsock 2.0 support.
Paul
|
| 320.7 | | SPELNK::curless | | Thu May 29 1997 11:06 | 5 |
|
It could just be the Winsock 2 spi for DECnet, but ... it could be DECnet,
the I&C, INF files... worst case 10-20 modules.
Jeff
|
| 320.8 | My 2c worth | GIDDAY::cscds710.stl.dec.com::Harkness | | Sat May 31 1997 11:00 | 11 |
| Jeff,
Just a silly question, but why not go down the service pack road?
My vote is to wait if there is a real ETA from MS. If it is still
a real unknown or a long way out ship now. It would be nice to have
a list of fixes that are to be included in the 7.0a even if it does
not ship for a while.
Greg Harkness
Sydney CSC
|
| 320.9 | voting? | VMSNET::DMCFARLAND | still TurboMom[tm]... | Mon Jun 02 1997 16:37 | 7 |
| voting is going on? has pw become a democracy? ;-)
i am with greg in that i would *love* to see a list (or a prelim
readme) that states what 7.0a fixes.
diane
|
| 320.10 | 7.0a to ssb?? | VMSNET::mtspc.alf.dec.com::Michael | | Tue Jun 03 1997 12:33 | 5 |
| Did 7.0a go to ssb on 6/2/97 as planned?
If so, where is the final kit?
michael
|
| 320.11 | | SPELNK::curless | | Tue Jun 03 1997 19:11 | 19 |
|
No. As noted in other notes, waiting on a verdict on the Microsoft Winsock
2.0 support for Windows 95.
Note:
We have the latest SDK for Winsock 2.0 on Windows 95. When the SDK, and the
new (yes NEW) tcp/ip stack that comes with it is installed on a Windows 95
machine running PATHWORKS 32 (v7.0, or v7.0A, haven't tested v1.0/1.0a)
multicast traffice over NetBeui is disabled... This means that a fairly large
portion of the time the users login fails, netbios name claim over Netbeui
fails... etc.
Microsoft has as of yet been unable to reproduce this problem, we have sent
them two machines configured so as to ALWAYS fail... the should have received
the machines today. As of right now Winsock 2.0 is on hold from microsoft,
and we are in a "it won't work" state,
Jeff
|
| 320.12 | Dates | SPELNK::curless | | Thu Jun 05 1997 12:35 | 12 |
|
PATHWORKS 32 v7.0a will be heading to SSB on June 11th, with an FCS of July 2.
This is with latent Winsock 2.0 support for Windows 95. Winsock 2.0 is
currently on hold (again) due to a problem report we submitted (dealing
with Multicasts).
Jeff
(dates subject to change due to unforseen problems).
|