> Michael, if this works for you, I will have VEDIT add this entry to
the registry. It obviously
> isn't necessary for everyone, but it appears that it occasionally
helps.
It is very difficult to tell if this really fixes the problem, because,
as I wrote, it only happens from time to time, I don't get this err on a
regular basis and haven't found a systematic way to produce it. So I'm
not sure how to tell whether or not it has helped. I took note of this
advice (and the older one, suggested by Fritz) and will try them when
the error pops up again...
Thanks
Michael
|
|