Paul, at 19:42 on May 26 1995, you wrote to Bill Grimsley...

BG> 1.  QEMM Exception #13 at 6620:FFFF, error code: 0000
BG>     AX=0925 BX=6F77 CX=6B72 DX=7720 SI=7469 DI=2068 BP=6168
BG>     DS=6472 ES=6177 SS=393C SP=1E3A Flags=7782
BG>     Instruction: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

BG> Different registers each time, but the same instruction (00 x 15 times).

PE> I don't know how to debug using this.

Neither do I.  Sadly, mine is an "evaluation" copy of QEMM 7.02,
the special one which has no documentation or manuals.  |-)

BG> 3. Then it hung the machine completely, requiring a full power down.

BG> All reproducable instantly.  Enter a message area, start scanning 
BG> through the messages with the arrow key, and poof!

PE> I thought you couldn't reproduce the problem before?  What did 
PE> you change to be able to reproduce it?

I have absolutely NO idea.  All I know is that I unpacked the newest exe
into my DOS point directory, rebooted native DOS, and it immediately
failed.  Not just once, but every single time.  It is completely unusable
here.  It is also not beyond the realms of possibility that I had
accidentally been testing the stable 3.05 prior to that.  However, 3.1.a
definitely fails within a minute.

BG> Conclusion?  She's fucked Jim.

PE> Just tried it again here, even booted under DOS 5.  Works perfectly, arrow, 
PE> ctrl-arrow, repeating, banging, etc etc not a fault.  Maybe you guys should 
PE> all come down here to read your mail?  I need to either be able to 
PE> reproduce the problem, or else we get into the arduous process of placing 
PE> debug messages every second line. 

I hope for your sake it doesn't come to that.  What changed so dramatically
between versions that turned the stable 3.05 into the 3.1.a piece of shit?

PE> Can you make it have NO function 0, and then tell me the *exact* sequence 
PE> of keystrokes to reproduce the error.  Like "type
"msged". Go Alt-A.  
PE> Cursor down 4.  Enter to select area (area has 5000 messages in it).  
PE> Cursor left.  Hang".

I'll do this and post the results shortly (I need to reboot now).

PE> P.S. Don't crosspost messages, it only makes things confusing.
PE> Post in one echo or the other.

I thought you'd want to know ASAP, as x-posting Noel's messages should save
a couple of days of email lag.  But, as you're obviously not serious about
fixing it, I won't bother next time...

PE> P.P.S. I'll probably be trying to get it to work under properly
PE> under Watcom this weekend, so maybe that will make this other
PE> problem go away.

If you want to attach the new exe(s) when recompiled, do so and I'll let
you know if it works any better (i.e. at all!).

Regards, Bill
@EOT:

--- Msgedsq/2 3.10 alpha