Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!lll-tis!ptsfa!ihnp4!cbosgd!mandrill!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.sys.amiga
Subject: Re: losing MIDI bytes
Message-ID: <685@neoucom.UUCP>
Date: Wed, 9-Sep-87 09:04:19 EDT
Article-I.D.: neoucom.685
Posted: Wed Sep  9 09:04:19 1987
Date-Received: Sat, 12-Sep-87 07:43:50 EDT
References: <689@mtuxo.UUCP>
Distribution: comp
Organization: Northeastern Ohio Universities College of Medicine
Lines: 16
Summary: lock out other processes, perhaps?


In reference to the aritcle mentioning ocasionally losing MIDI
bytes:

I was wondering about the practicality of putting forbid() and
permit() on either side of your part of the code that is reading
the system exclusive data dump.  If it is only a burst of 400 or so
bytes, it doesn't seem that unreasonalbe to lock out competing
processes for that amount of time, provided that you aren't doing
the dump very frequently.

True, it would be a kludge, but would probably be a little simpler
than writing your own serial device driver.

Bill
(wtm@neoucom.UUCP)