Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
This morning, I have developped a problem with VWSLAT. The VWSLAT program simply crashes with ACCVIO every now and again. Usually this happens when connecting to a new session, however it happens (albeit less often) at other times too. I copied the .exe from PRNSYS and that had the same problem. Nothing (that I know of) has changed on this system. I haven't got a clue where to start looking for the problem. Any help would be greatly appreciated. Graham
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3025.1 | Probably one of these | AGBEAR::HORNER | A.G.Bear, Old fashion teddy bear | Mon Jul 02 1990 13:37 | 12 |
There are two common problems that cause this. One is something has corrupted your VWSLAT$LAD.DAT data file. The only solution is to delete the old one, and create a new one. The other problem that is beginning to show up is from LAT services started from a V5.3 LTLOAD.COM file. There was a problem in the file that caused services to be broadcast with a garbaged identification string. VWSLAT does not accept this very well. The bad identification strings can be spotted by examining services using a terminal server that has the same group codes enabled. Both of these are discussed at length in the VSG::VWSLAT conference. Dave | |||||
3025.2 | VWSLAT conference - not at the moment!!! | RUTILE::POTTS | Tue Jul 03 1990 13:38 | 5 | |
Thanks.. I'll have a look at both of those solutions. The VWSLAT conference is currently broken! Graham |