At 07:46 AM 11/28/00 -0800, you wrote: >Hi Paul, > >Not that this is any explicit solution but I have seen a similiar type of >problem on NT systems where there were two identical configured NT >workstations. One worked and the other would never function correctly. It >turned out that the NT workstation that would not work correctly had a >corrupted DLL. (Don't ask how we found it - ugly). Of course there could >have been other problems but we knew we had at least one bad DLL so we used >the 'Microsoft solution to everything'. Re-installing NT then the service >pack again fixed it. > >Yuk, what a way to do system maintenance! > Hi John, Thanks for this information. It sounds similar to the experience of Brian Anderson, one of our JDEbug users. JDEbug worked fine on his dekstop Windows workstation. He then installed the JDE on a laptop running Windows 2000, using exactly the same JDE setup. JDEBug would not launch on the laptop. Finally Brian reinstalled everything on the laptop: Windows 2000, service pack 1, Emacs, JDK 1.3, the JDE. Now JDEBug would launch correctly but it would not stop at breakpoints. So he reinstalled Windows 2000, WITHOUT service pack 1. Now everything worked. - Paul
