Paul, at 17:48 on May 28 1995, you wrote to Bill Grimsley...

PE> Millions of things.  Bug fixes, new msgapi, enhancements.  

BG> How can you have millions of changes in an exe which only has 
BG> 220K bytes?

PE> Because some of the changes cancel each other out, e.g. I change 
PE> a 2 to a 3, then a 3 to a 4, then a 4 to a 5, etc, instead of 
PE> getting off my arse and getting a calculator to add 1000000 to 2.  
PE> That plus the studious use of alliteration (hey, it's the only big 
PE> word I know) and Watcom's brilliant optimizations.

As you're obviously highly qualified to do so, when are you standing for
preselection?  You'd do well in politics, Paul.

PE> If the problem had occurred here I would have had a better chance 
PE> of knowing which particular set of changes stopped it working.  
PE> But it didn't stop it from working on my system!

BG> What, in an OS/2 VDM and on an XT?  Pity nobody uses XTs any 
BG> more, and that OS/2 users would use the 32-bit OS/2 exe.  Don't 
BG> you have a native DOS boot partition on your PC at all?  Surely 
BG> you're not all HPFS there, are you?

PE> No, two of my drives are FAT, and I did test it out on my 486-33
PE> running DOS 5.0 native.  Not a whimper.

Interesting, I know that Noel uses QEMM, as do I, but I think Dave uses the
standard EMM386.EXE, so it can't be memory-manager related.  Besides, I
have actually always found QEMM to be far better behaved anyway.  Then
again, it also worked OK on mine the first time I ran it, yet crashed
immediately every time ater that.  Makes it hard, I'll agree.

PE> BTW, the reason the free memory is no longer displayed is
PE> because Watcom doesn't have a "coreleft" function.  What a shame.
PE> Maybe I can write my own in assembler, or maybe I can find an
PE> equivalent for Watcom.  BFN.  Paul.

Oh well, if you can't find an equivalent function, you could always use
that part of the screen to display the current time instead...

Regards, Bill
@EOT:

--- Msgedsq/2 3.10 alpha