[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

7342.0. "Pathworks v6 on new Venturis 5120" by NETRIX::"[email protected]" (Paul Smith) Thu Feb 27 1997 07:35

My customer is trying to get PATHWORKS v6.0 installed on his new Venturis
5120.
He has successfully configured his EtherWORKS Turbo card and he obtains a
connection to the PATHWORKS service and runs pwsetup.exe.
After selecting the WFW #3 Template he successfully runs through the
configuration and is then told to reboot.
After rebooting he successfully logs into WFWG and at the point of creating
the PATHWORKS icons it just hangs.

The BIOS has been upgraded to v1.09

Any ideas ???
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
7342.1No #3 wfw template ships with PW v6.0 ClientJAMIN::TELESETSKYThu Feb 27 1997 11:1514
    PATHWORKS V6.0 does not ship with a WFW #3 template; only a WFW #1 and
    WFW #2 template exist as WFW related templates on the kit.
    Did the system administrator create a 3rd WFW template and post it on
    the v6.0 system service?
    
    Please recheck the customer's template.  Post the template file the customer
    is running.
    
    Just a hunch, did the customer choose ems or load high during a 
    custom install?  Maybe the 
    customer's PC is running out of memory.  Choosing load hi and /or ems
    within a pwsetup.exe screen may solve the customer's boot problem.
                  
    -Marsha
7342.2NETRIX::"[email protected]"Paul SmithWed Mar 26 1997 07:3511
Sorry that was a typo, is was template #2.

He has tried this on several of these Venturis PCs, all hanging at the same
point.
When performing the same installation on other DEC PCs it works fine.

Any further ideas..

Thanks
Paul
[Posted by WWW Notes gateway]
7342.3Optimize conventional memory.....etc.JAMIN::TELESETSKYWed Mar 26 1997 15:3715
    
    Please check emm386 settings.  The PW icons are created when win.ini
    runs PWCONN is run. See thread around note 926.22, the PC may have
    a memory issue. Some of note 926 deals with a Venturis and memory
    issues. The venturis PC is known to have issues with its bios files & 
    memory.
    
    Does startnet.bat and your initial reboot of the PC run without any
    error messages -before- windows is launched?
    Before windows launches, is the PW local directory on the path? or has
    the PC run out of environment space.
    
    Try to optimize the memory on the PC by tweaking your config files.
    
    -Marsha
7342.4NETRIX::"[email protected]"kernel::smithpaTue Apr 01 1997 02:5310
I think I found the problem...

'DMI' yet again seems to be conflicting with PATHWORKS. Once all references
are removed PATHWORKS installs almost correctly, apart from not running
PWICON.EXE.

Any comments will be appreciated.

Paul.
[Posted by WWW Notes gateway]