[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

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

309.0. "SP3 on NT with pw32 problems" by KAOFS::M_VALLEE (csc hull canada) Wed May 21 1997 12:05

    Has anobidy installed SP3 on nt4.0 with pw32 installed it seems to
    cause problem like blue screen dumps.
    
T.RTitleUserPersonal
Name
DateLines
309.1no crashes hereVMSNET::mtspc.alf.dec.com::MichaelWed May 21 1997 13:457
We have seen problems with nt 4.0 sp3 connecting to v4 pathworks 
servers (see Q166730 in Technet for more info).

Have not seen blue screen crashes (yet?)

Michael

309.2More info neededSPELNK::curlessWed May 21 1997 16:057
Just downloaded SP3, installed it on my system running PW32 v7.0a, no
problem so far... please provide information on what is happening at the
time of the bluescreen... i.e. what applications are running, what options
are set... etc.

Jeff
309.3SP3 and Winsock 2.0DECPRG::PRSS2::csfr::markusMon Jun 02 1997 16:1513
Hi,
I installed SP3 on my Hinote Ultra II. I have PW 7.0. It seems that Winsock 
2.0 support for DECnet is gone (CTERM and eXcursion over DECnet don't 
work). I tried to reinstall PW 32 without efect. Does anybody know how to 
enable Winsock 2.0 support? Actually I can live without Winsock 2.0 support 
till 7.0a (?) will be available but one of our customer has problem with 
crashing eXcursion with ACCESS control enabled (discussed in the eXcursion 
conference). DECnet and LAT  work. 

Jiri 

Prague
Czech Republic  
309.4How to Fix SP3 nuked WinsockSPELNK::curlessMon Jun 02 1997 16:2620
Yup, I saw this as well, and couldn't reproduce the problem.  This worked for
me:

1) look in the location you installed PATHWORKS 32 into, and locate
   the file PWS2DNST.EXE.

2) execute PWS2DNST.EXE, wait for it to finish.

3) run PWS2INST, and wait for it to finish.

You will now have a working Winsock 2.0 stack over DECnet.... this is a
direct result of adding Service Pack 3, and changes in the way NT deals 
with Winsock 2.0 on Service Pack 3 (by the way, there has been NO information
on the changes from Microsoft).

If your customer is seeing crashes with ACCESS control enabled, please make
sure an IPMT case is filed if required.

Jeff
309.5It works now.DECPRG::PRSS2::csfr::markusTue Jun 03 1997 06:468
re.-1

Thanks for hint. Actually I tried to install WS2.0 support without 
deinstalling it first. Now DECnet over WS2.0 works.
I will post our result about eXcursion to the eXcursion conference and 
we will IPMT our customer problem.

Jiri
309.6SPELNK::curlessTue Jun 03 1997 11:015
You really should deinstall, then install... the deinstall cleans the
registry.

Jeff