[net.micro.pc] MASM 4.0 announced

kim@mips.UUCP (Kim DeVaughn) (12/11/85)

[ ... go ahead, eat my bits ... ]

Just read in the 12/10 issue of PC WEEK (p. 14) that Microsoft has released
Rev 4.0 of MASM.  Some of the enhancements mentioned are:

        o  handles 400K source files
     
        o  handles 15% more symbols
     
        o  paths can be defined for Includes
     
        o  file-buffer sizes can be set from 1K to 63K
     
        o  enhanced DEBUG;  swapping of development and execution screens;
           display of original source
     
        o  LINK is supposed to be up to 25% faster
     
        o  LINK supports "file compression"
     
        o  the "make" utility supports macro-definitions and inference rules

Looks like a similar upgrade policy as last time (to 3.0).


[ personal FLAME ON ... ]

Of course, even though I have their buggy Rev 2.x assembler, they won't give
*me* a break on a new revision ... *my* floppy is from Fujitsu, even though
it is  says "(c) Microsoft".  And it is MICROSOFT that threatens the wrath
of God if I don't abide by *their* license agreement.  Talk about having it
"both ways"!

Fujitsu, of course, has no intention of supporting their customers in this
matter ... "it's not *our* assembler ... call Microsoft".   Bahhh!

Don't you wish sometimes you could treat your customers that way ... if only
your customers were Microsoft, et al!

[ FLAMEs OFF ... ]
     

Anyway, just thought I'd pass the info along (I really *hate* to help
Microsoft out, though).

/kim


Obviously, I'm not affiliated with Microsoft or Fujitsu, except as a
dis-satisfied customer.
--

UUCP:  {decvax,ucbvax,ihnp4}!decwrl!mips!kim
DDD:   415-960-1200
USPS:  MIPS Computer Systems Inc,  1330 Charleston Rd,  Mt View, CA 94043

matt@prism.UUCP (12/15/85)

/* Written  2:53 pm  Dec 11, 1985 by kim@mips in prism:net.micro.pc */
/* ---------- "MASM 4.0 announced" ---------- */
> 
> Just read in the 12/10 issue of PC WEEK (p. 14) that Microsoft has released
> Rev 4.0 of MASM.  Some of the enhancements mentioned are:

Well, I've got a copy of MASM 3.1 that will reliably trash the fixed disk of a
640K AT (with IDEA type 2 20 meg. disk).  Seems that any time I run the
assembler, it leaves lost clusters on the disk.  The lost clusters are
crosslinked into REAL files, however.  When chkdsk and related programs try to
reclaim them, real files get corrupted.  Anyone else seen this problem?

Needless to say, I will NOT be trading up to MASM 4.0, as I refuse to do any
more business with Microsoft unless absolutely necessary.  I'm quite happy with
PASM from Phoenix (MASM 3.1 compatible, but faster and with fewer bugs).

------------------------------------------------------------------------------
 Matt Landau      	 {cca, ihnp4!inmet, mit-eddie, wjh12} !mirror!matt
 Mirror Systems, Inc.	 2067 Massachusetts Avenue
			 Cambridge, MA   02140
------------------------------------------------------------------------------
These opinions are mine.  I don't know if my employer would even understand
them :-)