I do use Oevent. and I have replaced Opus.exe Many times thinking that was 
part of my original system hanging symptoms. comp.exe said old and new 
vfersions were the same. so that was not a help. As far as how your oevent 
works right on weekend and specific days part is the mysterious quirks. Beign 
Msdos does not use module CRCs. a file can get hosed and the operating system 
will still run it up until the hosed part comes to ahead. Os9 Level 2 would 
not allow a corrupted or potentally virused .EXE or .Com to even get into 
memory, it gives error 237 and throws it on the trash heap. Finding trashed 
files in my opus root which number several MEGABYTES. could take days. if it 
were os9. a simple Indent [module or program name] running in a batch file 
could find the bad files. mark em for me to delete and replace. How come 
Msdos 6.22 never adopted that as an internal option/configuration of Msdos 
6.22? It would kill lots of viruses too.
        That brings a possible question into play. where did you get your 
opus 1.73a? Its possible that you got a more "virgin" copy than I did. as 
parts of the OECC/AVatar codes don't work on my system either. For example 
the Oacomp 1.20 [DISPLAY] directive does not display anything on my oups. 
leaving me to use [CALL] which sometimes leads to [PROBLEMS] configuring the 
[MOREON] and [MOREOfF] verbs in my display scripts. maybe I need a new opus 
1.73a archive. thats why i asking where you got yours so I can get mine from 
the same source.
                                        Michele Marie Dalene
P.S if you got it from Rights ON!. then thats where I will querry for the 
latest updates.  
 
--- MailBase 4.11
---------------