CompuServe Messages

Appreciate it, Keith – I think I _may_ have found it. The code that I was referring to setup it's own message port. This involved allocating a signal. The timer close routine did a RemPort and a CloseDevice (in opposite order) but did not do an Explicit "FreeSignal(signum)". It looked to _me_ like it was missing; and I noted that the code didn't check to see if it had really gotten the signal, either – so I changed it to tell me if it couldn't _get_ a signal, and then I also changed the timer close so that the signal was freed. It's not telling me it can't gett signals, and it's not stomping on things anymore, either, at least at this point. I have memwatch running, and so far, so good. I've tried the things that dependably caused it, and they no longer do. I have one more thing to go, that's the download code – it used the same timer code, and stomping occured then, too. Hopefully, that was it. Later I plan to remove the free signal call and leave the screams about "I can't get no signal" in there, and see if it pukes – hopefully, it will, and I can relax. Gadz, I hate bugz! This has been a bad one, too – it wasn't my code that caused it, and it didn't show up when it happened, so it was _horrible_ to find. –Ben–