![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: we are currently in the process of upgrading our pc population from windows for workgroups 3.11 to win95. The wfwg pcs run pathworks 5.1 and the win95 pcs are being installed with pathworks32, both sets use tcp/ip and decnet protcols. the pcs map network drives to an alphaserver 1000 running 7.1axp and pathworks 5.0f, they also map drives and terminal sessions to a vax4105 running vms5.5-2h4 and pathworks 4.1. Over periods of time greater than 15minutes but less than an hour the wfwg pcs lock up completel y and have to be rebooted, the win95 pcs remain unaffected. We currently have 80 win95pcs and 50 wfwg pcs. We have checked for duplicate addresses and network hub failures and are now at a loss for ideas??? The Answer is : PATHWORKS DOS/Windows V5.1 was released in September, 1994. If you are using the V5.1 product on currently available PCs configured with the latest Ethernet interfaces, the problem or problems you are enountering may be timing bugs that are only apparent on the newer, faster systems and smart network interfaces. The current released and supported verion of PATHWORKS DOS/Windows is V6.0a. You are moving in the right direction - upgrade the systems to Windows 95 (or, Windows 98, or NT 4.0) and PATHWORKS 32 V7.1a. Note that PATHWORKS Server V4.1 is NOT Year 2000 ready.
|