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

Conference noted::pwdoswinv5

Title:PATHWORKS V5 for DOS and Windows
Notice:OS2LAN::OS2:[PUBLIC] is alive again, but not what it used to be
Moderator:RANGER::CURLESS
Created:Fri Feb 11 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7404
Total number of notes:27276

7379.0. "PWSETUP : NCONFIG ERROR" by AUBER::CORNU (Valerie CORNU - CSC Evry FRANCE) Wed Apr 09 1997 10:38

    Hi,
    
    Question about the installation of Pathworks V6 for on IBM 330 Pentium
    75 and Pentium 100 :
    
    When running the PWSETUP proc�dure on WFW 3.11, you always obtain :
    
    	NCONFIG caused a GPF in module PWSETUP at 0001:37D5
    
    I found nothing about this message.
    On Compaq DESktop 5100, it works either on IBM 486.
    
    I told the customer to get the last version of PWSETUP.EXE in Pathworks
    V6.0 ECO2 but the problem remains. With a CONFIG.SYS and AUTOEXEC.BAT
    minimum, same problem.
    
    I need an answer because the customer has hundreds of IBM 330 Pentium
    PC's and encounters memory problems. 
    
    Thanks,
    
    Valerie
T.RTitleUserPersonal
Name		DateLines
7379.1Need more info....JAMIN::TELESETSKYWed Apr 09 1997 20:129
    Please supply the customer's autoexec.bat, config.sys, win.ini,
    system.ini and all pertinent configuration file information.
    
    What stage of pwsetup has the customer gotten to when the gpf arises?
    Is it upon pwsetup startup or later?
    
    Regards,
    Marsha T.
7379.2AUBER::CORNUValerie CORNU - CSC Evry FRANCEThu Apr 10 1997 05:1915
    Hi,
    
    They're new elements : with an ETHERLINK III on the same PC, the 
    PWSETUP works fine.
    They tried with V2.3 of the Etherworks drivers. So, I told them
    to try with the last version (V2.5).
    For information, the GPF arises at the beginning of the PWSETUP (after
    asking for the directory where to install Pathworks).
    
    I'll give you the result.
    
    Thanks,
    
    Valerie
7379.390% network adapter config problemSPELNK::curlessSure it's a bug, but did you CLD/QAR it?Thu Apr 10 1997 12:1920
Ah, well then there you have it.

The network adapter memory region on the crashing machines is NOT being
excluded from use by WFWg and or DOS.  

When PWSETUP GPF's, historically it has been because:

1)  The data comming over the wire was corrupted
2)  The network adapter memory address is not excluded properly
3)  There is a hardware configuration problem other than 1&2

and lastly

4)  It is a PWSETUP bug.

#4 is rare.  When another adapter works.... it is almost always #2

Jeff
(Mr. PWSETUP)
7379.4AUBER::CORNUValerie CORNU - CSC Evry FRANCEFri Apr 18 1997 11:495
    Thanks, Jeff,
    
    It was a problem with EMM386 and the exclusion of the memory address.
    
    Valerie
7379.5SPELNK::curlessSure it's a bug, but did you CLD/QAR it?Tue Apr 22 1997 11:124
;-)

Jeff