BJ> I know I've seen Bo report on this before, but I 
 BJ> can confirm that the dupe checker in squish in the 
 BJ> 3.02b code snapshot is broken.  The Linux 3.03b 
 BJ> squish is tossing messages as dupes that my OS/2 
 BJ> system (running squish for the tosser, need to look 
 BJ> up the version number) sees as good messages (i.e. 
 BJ> messages are not a dupe).....
 WG>  
 WG> Thanks for the feedback. It was not clear to me whether 
 WG> this was a squish problem, or a squish/unix problem. 
 WG> Now we need to figure out *why* it's doing tha. :)

From memory, I believe Scott released a beta version of Squish after the
Y2K features that I didn't like -- possibly related to dupe handling.  So,
there may be a more generic issue.....  And I may just need to kill off the
dupe files and let them start again to solve the problem.....  Time will
tell....  [Ok, now to go look up which *.sq? file needs to be deleted for
testing this theory....]

 BJ> Entering messages via the Maximus full screen 
 BJ> editor works, as long as I use control-k control-d 
 BJ> to end the message, instead of the control-z that 
 BJ> I'm used to.  [I still need to disable the shell 
 BJ> interpreting certain control characters.]
 WG>  
 WG> If my fixes don't do it for you, you can always use 
 WG> stty(1) to change the key combinations which general 
 WG> the INT/SUSP signals until a real fix is devised.

I figured I needed to find the stty documentation and write a shell script
for starting Max in console mode.  I already do this for OS/2, but haven't
done it for Linux yet.  Once done, with the sttty issues fixed, that should
take care of that problem....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01