Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!ucsd!nprdc!malloy
From: malloy@nprdc.arpa (Sean Malloy)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm command files
Message-ID: <883@skinner.nprdc.arpa>
Date: 15 Sep 88 14:23:52 GMT
References: <13962@agate.BERKELEY.EDU> <2047@cuuxb.ATT.COM> <1825@spdcc.COM <8994@cup.portal.com> <1852@spdcc.COM> <11046@grebyn.COM>
Reply-To: malloy@nprdc.arpa (Sean Malloy)
Organization: Navy Personnel R&D Center, San Diego
Lines: 25

In article <11046@grebyn.COM> marv@grebyn (Marvin Raab) writes:
>In article <1852@spdcc.COM> eli@spdcc.COM (Steve Elias) writes:
>Here's one I can't figure out: Why does my computer screw up Procomm and
>Pcplus sounds *sometimes*? (The sounds sound like they're muffled).

Versions 1.0 and 1.1 of Procomm+ had a bug in the 'beep' routine that
would simultaneously crank the duration down and the frequency up
until all you got was a clicking sound. This was a problem on long
file uploads/downloads, because you couldn't hear the clicking unless
you were listening closely in the same room as the computer. I received
a disk in the mail from Datastorm a couple of months ago that contained
a patch for Procomm+ v1.1 (new v1.1a) that fixed the beep bug and a
couple of others that I hadn't run across yet. 

I find that the attitude Datastorm Technologies takes toward
supporting the Procomm+ package to be a refreshing change from some of
the larger software development houses that will admit that they have
a bug fix release available after you find out about it in a computer
journal, but charge you for receiving the bug fix.



	Sean Malloy
	Navy Personnel Research & Development Center
	San Diego, CA 92152-6800
	malloy@nprdc.arpa