Peter

And I thought I was the only one with this problem. I had a call open = with S.I. here in the UK for about four weeks because they had not seen = this. I only use FSBrowse from the FSP product and it seems to happen = sporadically too.

After many crashes I reckon it was happening after a system crash caused = by accessing the same areas of memory (not necessarily, but most often, = SAS induced). I chose the 'Thorough' option for ScanDisk and recovered = some lost clusters and I stopped getting un-refreshed screens.

S.I. could only recommend getting hold of the shareware WinTune95 to see = if my system was optimised, but I've not pursued this yet. It seems to = me that when the crash happens, an area of disk (possibly being used by = the swap file) is being corrupted. Is this possible?

Given that the problem is happening with a product that needs a lot of = memory (i.e. FSP) could it be linked with swapping the contents of the = Log and PGM windows to disk??

I'm waiting for the QuickView that is suppposed to be incorporated with = Wave 2 of 6.11 and then I'll stop using FSBrowse altogether (hopefully = this will stop the problem happening).

I'd be interested to know if any users have encountered the = 'un-refreshing' with any product *other than* FSP.

Nelson

---------- From: Peter Lund[SMTP:PeterL@OFM.WA.GOV] Sent: 28 May 1996 15:14 To: Multiple recipients of list SAS-L Subject: Re: Access Violation(80000602)

I've been getting the 80000602 Access Violation error for months and = have tried all the things that SI has recommended. One thing that very often does it for me is coming out of the Libraries window after having browsed/edited a dataset with FSP. I've learned to watch for a few tell-tale signs. - Often the program editor will not fully refresh after closing the Libraries window. Switching to the log or output window and maximizing/minimizing a couple times and then switching back to the = program editor seems to refresh it. - Often, doing anything (literally) in the program editor if it is incomplete will cause the 80000602 error. Unfortunately, none of this happens every time, just at the most = inopportune times. It makes it difficult to really pinpoint a cause. It seems from this thread, however, that there are multiple paths to this same error.

Pete Lund WA State Office of Financial Mangement peterl@ofm.wa.gov