Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cca!mirror!ishmael!inmet!mbate
From: mbate@inmet.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Where is my MSC 5.0
Message-ID: <149000014@inmet>
Date: Mon, 16-Nov-87 12:32:00 EST
Article-I.D.: inmet.149000014
Posted: Mon Nov 16 12:32:00 1987
Date-Received: Sat, 21-Nov-87 01:38:39 EST
References: <1926@uwmacc.UUCP>
Lines: 19
Nf-ID: #R:uwmacc.UUCP:-192600:inmet:149000014:000:1019
Nf-From: inmet.UUCP!mbate    Nov 16 12:32:00 1987


    I never expected to generate so much response to my remark that MicroSoft
    charged my credit card in October  (I now have MSC 5.0 - it must have
    been shipped early November, so it's not big deal for me.)

    However, I do specifically remember what the upgrade offer said about this.
    Checks would be cashed when received, credit cards would be charged when
    the product was shipped.  On MASM 5.0, which was not announced until it
    was ready to ship, they stated that credit cards would be charged upon
    receipt of your order.

    Now that I have MSC 5.0, I'm not sure whether to be pleased or not.  I have     one program that generates an internal compiler error - it compiled fine
    with MSC 4.0 and also with QuickC.  Another goes haywire when compiled
    with the /Oi (generate intrinsic versions of some functions) flag.

    On the other hand, QuickC is very nice for quickly cleaning up your
    compile-time errors and CodeView seems to be cleaner than before.

    - Michael Bate