> All in all, it sounds like the symptoms of internal
> scheduling failure in
> MPE. Critical tasks are simply not being performed on a
> timely basis, perhaps
> because some IMAGE-based process is not periodically
> releasing itself to the
> control of a task scheduler.

Sounds more like a programming defect of the oversight persuasion: whoever
coded the update to these tables failed to consider the possibility that
information could be put into them faster than it was being taken out, and
thus failed to provide proper synchronization to ensure that the writing
processes were forced to wait until some room had been made for the new
data. Whether or not the consumer of the table data is executing "on a
timely basis" should not matter; the code should handle the situation where
the consumer simply can't keep up with the producers.

Steve Dirickson   WestWin Consulting
[log in to unmask]   (360) 598-6111