On 05 May 97, Stein-Ivar Johnsen wrote to John Giannini:
 JG>> ! 04 May  1:32:46 OPUS LANGERR: Can't find RY.USL
 JG>> : No such file or directory
 JG>> ! 04 May  1:32:46 OPUS LANGERR: Can't find RY.USL
 JG>> : No such file or directory
 JG>> ! 04 May  1:32:46 OPUS Can't increase Ä^(garbage here)
 JG>> DAY: No such file or directory
 JG>> : 04 May  1:32:46 OPUS End (2)
 SJ> You have to use the ENGLISH.USL included in the release package, or some
 SJ> of the other language files released in 179LNG02.ZIP Do you have the
 SJ> right path for LANGDIR in the Language Section in your BBS.CTL file?
I had the correct English files installed, and my paths right.  Been running 
1.73a since 1990.  But I *have* discovered the problem.  it was memory. See, 
most of the time 1.79.x works just fine but sometimes - like denoted in the 
above log - Opus spazzed out.  Not only did it do weird stuff like the above, 
but I would get colors flashing on my screen, and the background color of the 
date/time field on the Opus waiting screen would cycle without me doing 
anything...   Opus would also lock up on me, or in one case it absolutely 
hung my modem and from that point on even Telix or Procomm couldn't get my 
modem to act right again.  And yesterday I got a totally new error on one 
Opus spaz - a "Cross Linked Device" error" which bumped me clean out of Opus 
out to Dos.
I discovered if I rebooted when stuff like this happened, everything was fine 
again.  The problem apparently has to do with Opus fragmenting memory, then 
choking on that fragmented memory.  I have 20 megs of RAM on this machine, 
but when you try to do something with 1.79.x, like abort an outbound call in 
progress, Opus can totally spaz out.  I can now reproduce a "spaz state" 
almost at will.  Rebooting gets me in the clear again.  This instability is 
another reason I am returning to 1.73a.  It seems to be more stable.
--- GoldED 2.50
---------------