Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!brahms!desj
From: desj@brahms.BERKELEY.EDU (David desJardins)
Newsgroups: net.micro.pc,net.lang
Subject: Re: Info re: Microosft OEM MASM Upgrades
Message-ID: <11349@ucbvax.BERKELEY.EDU>
Date: Sat, 4-Jan-86 12:08:09 EST
Article-I.D.: ucbvax.11349
Posted: Sat Jan  4 12:08:09 1986
Date-Received: Sun, 5-Jan-86 02:19:43 EST
References: <8798@microsoft.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: desj@brahms.UUCP (David desJardins)
Organization: University of California, Berkeley
Lines: 16
Xref: watmath net.micro.pc:6422 net.lang:2014

In article <8798@microsoft.UUCP> sandraj@microsoft.UUCP (Sandra Jacobson)
writes:
>
>Users of a Microsoft OEM'ed Macro Assembler/MASM (with (C) Microsoft on it)
>can now to update to the latest version of the Microsoft Macro
>Assembler v 4.00.  ....
>
   This is very interesting.  Presumably Microsoft will admit that this was
prompted by the recent complaint.
   On the one hand this shows that Microsoft is willing to support their
customers even if when they are not required to do so, which is certainly good.
But on the other hand it seems to provide an incentive for more people to flame
on the net with their misconceived notions about what kind of support is owed to
them.  After all, if it gets results...

   -- David desJardins