When I load an application into BoundsCheck for Windows 3.x, BoundsChecker hangs before my application even comes up.
This is most likely a case of not allocating enough symbol memory. In some cases, BoundsChecker cannot deal with low symbol memory gracefully. You can increase the symbol memory under the Settings menu.
Do not choose 0 for automatic calculation. This does not work with larger modules. Simply choose the number of K that is needed to load symbols for all modules that you are BoundsChecking.