Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!hplabs!sdcrdcf!trwrb!cepu!ucsbcsl!hbo From: hbo@ucsbcsl.UUCP Newsgroups: comp.sys.amiga Subject: Re: DMCS "quiet" upgrade ... sleazy business practices Message-ID: <484@ucsbcsl.UUCP> Date: Tue, 5-May-87 10:46:21 EDT Article-I.D.: ucsbcsl.484 Posted: Tue May 5 10:46:21 1987 Date-Received: Fri, 8-May-87 04:24:29 EDT References: <8705020654.AA19822@ingres.Berkeley.EDU> Organization: U.C. Santa Barbara Lines: 33 Doug Merritt lists a few bugs in DMCS, I'd like to add my list. 1: If you load too many instruments, 10 or so, the sounds menu crashes. The rendering of the menu goes glitched, and the lower reaches drop off the bottom of the screen, becoming inaccessable. The last item in the sounds menu is the "remove instrument" option, so the only way to recover from this bug is to reboot! 2: MIDI input is badly broken. After an indeterminate number of notes (usually less than three) it is time to talk to the guru. 3: On my 512K machine, the measures menu takes a vacation when the MIDI drivers are loaded along with a score and instruments. This is due to lack of memory, since it doesn't happen on my friends 2.5 meg machine. I have written to EA twice, and called four times. The last phone conversation took place yesterday (4 May) and resulted in a promise of an upgrade within 10 days. I am not holding my breath, since I have been repeatedly lied to by them in this regard. My overall impression of DMCS is that it is a bloated, top heavy and buggy mess. It is obviously written entirely in C, since it doesn't fit into 512K of RAM. No wonder the picture of the authors in the manual shows them wearing dark glasses: they don't want to risk identification! (.5 :-)) -- Howard Owen, Programmer/Analyst PHYSNET: SBPHY::HBO University of California, Santa Barbara BITNET: HBO@SBITP Physics Computer Services ARPA: hbo%sbphy@LBL.ARPA usenet: ucbvax!ucsbcsl!hbo