JG> running 1.73a since 1990.  But I *have* discovered the problem.  it was 
 JG> memory. See, most of the time 1.79.x works just fine 
 JG> but sometimes - like denoted in the above log - Opus 
 JG> spazzed out.  Not only did it do weird stuff like the 
 JG> I discovered if I rebooted when stuff like this happened, everything was 
 JG> fine again.  The problem apparently has to do with Opus 
 JG> fragmenting memory, then choking on that fragmented 
 JG> memory.  I have 20 megs of RAM on this machine, but 
 JG> when you try to do something with 1.79.x, like abort an 
 JG> outbound call in progress, Opus can totally spaz out.  
Are you sure it is OPUS that is fragmenting your lower conventional memory 
(under 640 k) and not something else? It is almost 99.something that the 
problem doesn't care if you have 4, 8, 20 or 32 megs of ram on your machine. 
What kind of watchdog security program (if any) do you use with doors, 
including things like SX, BW or O'QWKer? If you don't use one, look for 
something else that is not properly releasing the memory.
I'm not saying it couldn't be the new opus, but when I had a similar problem 
3 or 4 years ago updating an SX door release, it was an old watchdog program 
used in the drop file, not opus or sx, that actually was causing the 
"fragmentation" problem. There was still enough total memory free, but alas 
the largest block was not big enough to load sx. SX worked in local mode. A 
reboot of course resolved the problem. So did killing the watchdog program. 
Sometimes when you have working sections of your bbs that have been around 
for awhile, a problem only appears when the new release nudges the system in 
a new way.
--- Maximus 2.02
---------------