| 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 |
pw 32 v7.0
NT 4.0 workstation sp2
clone pentium pro dual cpu 200mhz
Since the installation of pathworks the machine freezes intermittantly
the mouse no longer moves and they have to reboot the system.The print
services and remote access were not install so decnet, lat, licensing
are the only thing running from the kit.Here at the csc we can reproduce
the problem on a digital venturis FX 5133sm with nt 4.0 sp2
workstation.The only thing here that stop the hanging was removing
pathworks entirely.Also we disable power management and it had no
effect on the problem.So can we troubleshoot this problem is there a
way to see in which code the machine hang at, are there debug version
that would help in this case.What troubleshooting approach would the
pw32 engineers recommend.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 210.1 | I can confirm that Show-stopper... | CPEEDY::COOK | Just say NO to that AccViO! - Java!!! | Mon Apr 07 1997 16:43 | 27 |
Yup, I can confirm the UI/mouse-cursor-freezing behavior reported
in the base-note. My machine was NT 4.0/SP2,single-CPU Intel 486/66.
(I can narrow the possibilities down a bit, since I did *not* have
DECNet installed when my UI/mouse-cursor froze. I'd done a custom
install and had chosen LAT and Remote-access, but *not* DECNet, and
*not* licensing. I then installed PowerTerm. Mine didn't freeze-up
until the next day...I was *guessing* that it was LAT related, but
I don't know for sure. But, on a second machine, which had PW32
installed in an identical fashion, I've disabled the LAT-functionality
and I've never seen the UI-freeze symptom on that machine.)
I've since de-installed the product on the first machine. (That was
painful...hope someone is working on a 'de-install' procedure...even
some BAT files that could be invoked by hand would be a great start
for the next release! I followed the readme doc's deinstall notes,
and it took me about 20-30 minutes to de-install by hand.)
I finally re-installed, choosing just the core/base functionality
and then PowerTerm. (It was PowerTerm functionality that I really
wanted.) See my other note (#187) for the gory details.)
Cheers...
Dave
| |||||