Hello Andrew!

Antwort auf eine Message von Andrew Belov an IVAN TODOROSKI:

 AB> IBM never will change the situation with SIQ. Instead, they provide a
 AB> patch in Warp 4 (and Warp 3, beginning with Fixpak #17) that can help
 AB> in some (very few) situations when the user interface locks. It's not
 AB> a solution at all but I think the reason for it is the compatibility:
 AB> some applications may malfunction if the SIQ will be replaced with
 AB> multiple queues. Fixpak #17 already broke the functionality of some
 AB> apps, including MS Word for OS/2 and File Manager from OS/2 v 1.x.

Do you any details about the patch you mentioned?

We use a portable GUI library (StarView) that produces memory leaks with
exactly these OS/2 versions. As StarView is no longer supported we're forced to
track down this problem by ourselfs.

Here are some details:
With the utility Theseus/2 we observed that PMMERGE.DLL allocates memory that
will NEVER be freed (atleast at reboot). The WM_PAINT message seems to be
involved. Normally the StarView library handles this message. If we hook the
WM_PAINT message and call WinBeginPaint/WinEndPaint from this hook, there no
memory leak anymore. (Unfortunately this workaround is not possible in real
applications.)

Did the patch in Warp4/Warp3FP17 change anything that the WM_PAINT message is
involved with?

Any help is highly appreciated!

Bye
  Andreas

--- FleetStreet 1.21+