Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!leland.Stanford.EDU!jessica.stanford.edu!bard
From: bard@jessica.stanford.edu (David Hopper)
Newsgroups: comp.sys.amiga.audio
Subject: Module Players
Message-ID: <1991Apr7.233441.15724@leland.Stanford.EDU>
Date: 7 Apr 91 23:34:41 GMT
Sender: news@leland.Stanford.EDU (Mr News)
Organization: Academic Information Resources, Stanford University
Lines: 29

I would like to know if there is anyone who is successfully using a
module player in a multitasking environment.  With my finally acquiring
IntuiTracker 1.2, I though the bugs would all be worked out.  It still
gurus if you use any terminal program, which is unacceptable.  Here are
the module players I have used:

IntuiTracker 1.1 and 1.2
ModulePlayer 1.7 (is that the name?)
Player (CLI-based, no multitasking allowed)
XTPlayer (good, but no multiple-selection and still crashes
	  occasionally)
Another CLI-based player that locks up the machine and gurus upon
	  exiting (I don't recall the name)

My system is a rev 5.0 1-meg chip A500.  I am planning on bringing it up
to 5 or 7 megs this summer, and I'd like to know if all I need for
IntuiTracker 1.2 (a terrific interface-- my favorite) is some fast ram.

Can anyone offer some feedback?  Can the author of IntuiTracker be
contacted via the Net, or Snail, or phone (I'm desparate, here) or is he
already aware of the comm-program lock-up bug?

I'm beginning to think that the nature of mod. files is incompatible
with stable multitasking.  Any ideas?

Dave Hopper      |     /// Anthro Creep  | Academic Info Resources, Stanford
                 |__  ///     .   .      | Macincrap/UNIX Consultant
bard@jessica.    |\\\///     Ia! Ia!     | -- Just remember: love is life, and
   Stanford.EDU  | \XX/  Shub-Niggurath! | hate is living death. :Black Sabbath