home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hurricane
/
HURRICANE.ISO
/
sound
/
morgl110
/
morgul.faq
< prev
next >
Wrap
Text File
|
1994-11-26
|
7KB
|
141 lines
┌────────────────────────────────────────────────────────────────────────┐
│ This file tries to answer questions before you ask them. If you've │
│ got a problem, read this first before contacting me. If this file │
│ does not help you in your problem, the contact methods for the │
│ author are listed near the end of morgul.doc or at the end screen. │
│ At the end of this file you can read about the coming new features. │
└────────────────────────────────────────────────────────────────────────┘
Q: Where's the advanced filesystem with tagging and so on?
A: Because of public demand, the "Easy" filemode is now the default
mode, so you'll have to disable the easy mode first. (Alt-E, -e)
Q: What about an "Working Directory" setting?
A: I don't think that should be a feature of Morgul at all. If you
use 4DOS, use the following batch file (name it MORGUL.BAT or
something.)
pushd
cd E:\modules
mo
popd
If you do not have 4DOS, just omit the pushd and popd lines.
P: When playing modules with GUS, there is sometimes an odd
"plim"-like sound which doesn't belong in the module.
S: You could try to use the -g or -gt parameters to get rid of GUS
problems.
P: When playing UC2'ed files, UC2 displays an error message saying
"not enough memory".
S: Try using something like Vidram, Stretch or some other program
which increases your conventional memory to 736kb. The other way
is to install UltraStealth. Read Morgul.doc for more details.
P: There's not enough memory to unpack some HA files, while others
unpack just fine.
S: Some HA files are packed with the ASC algorith while others are
packed with the HSC algorithm. Unpacking HSC packed files needs
lots of memory. Read the part concerning UC2 files above for
more help.
P: Morgul is too big and eats up lots of memory.
S: Right. I'm planning to get Watcom C/C++ 10.0, which will have
the capability of producing 16-bit executables. I've been told
Watcom produces the smallest executables in 16-bit mode. Also I
could try reducing memory fragmentation.
Q: When is XMS going to be supported? I don't like memory managers but
would still like to play large modules.
A: Morgul/32, a 32-bit flat memory model protected mode (add your
favourite buzzwords here: multi-threaded, symmetrical
multi-processing, multi-user, object-oriented, whatever :)
version of Morgul will hopefully available in a couple of weeks.
In fact, it has been hopefully available in a couple of weeks
for the last 3 months. Chances are it'll appear soon after this
16-bit version is released.
It will be able to use all the memory in your computer with or
without any memory manager software. Also, about 590kb of memory
in dos shell is possible. Already, Morgul/32 is so ready it will
stay up without crashing for about 20 minutes, if I handle it
with care :)
P: When I try to run MO.EXE, I just get an error message saying:
"Moverlay initialization failure, expected MOVERLAY but got
8"%/·│}╚╚ d"
A: Somebody has been tampering with the executable. Delete it, kill
the guy you got it from and tell me everything about it.
P: I'm running Qemm V7.x. Sometimes in DOS Shell Qemm gives an
exception message when running a program in the shell, offering
to shut it down or to reboot my machine.
S: This problem is because DSMI seems to be partially incompatible
with DIET 1.45f, a public domain executable file compressor.
Files compressed with this software sometimes cause this
problem. Uncompress these files and compress them with something
else, if you like. To uncompress a Dieted executable, use Diet
-ra or a program called Unp, which is an excellent executable
file uncompressor.
Q: Why is the graphics mode so slow?
S: The code itself is not slow at all, it would work even on the
slowest computer, but calculating real volume bars continuously
takes much more power, especially on the GUS.
P: My sound board is something else than a GUS, and Morgul just
does not work under OS/2.
S: Morgul/32 will work under OS/2 with other cards than GUS.
Q: When running under OS/2, screen update is slow. Why?
A: Because Morgul is releasing time slices to OS/2 so that the
rest of the system would not slow down. Use Alt-F9 to toggle
OS/2 timeslice releasing. (Unsupported and "undocumented"
function)
Q: Why is the scope in the graphics mode so crappy?
A: On the GUS, the scope is a graphical presentation of the average
of the currently playing samples in GUS memory. On other cards,
it's a graphical presentation of the voice mix-buffer.
Q: What new features are expected to be implemented during the next
2000 years?
A:
New features to be expected:
Morgul '95, code named Theba, will be released in the beginning of
'95, with lots of new stuff, some of which are:
Much enhanced sound board code and support for FastTracker 2 and
possibly others.
WWW stuff. ( not in Morgul but on the Internet, of course :)
When the binary mailing list is implemented, you can send mail to:
morg-bin@kotakk.fi, with subject: subscribe Morgul with your name in
the message body. Then you will receive the latest Morgul versions
uuencoded in your mailbox. Then, later, if you want to unsubscribe,
send mail to morg-bin@kotakk.fi, with subject unsubscribe morgul,
message body can contain anything you want. This mailing list will
probably work a week or two after release. You can find out whether
or not it exists yet by fingering tnikkane@clinet.fi.
Make Morgul work with every sound board under OS/2 ( currently only
GUS works.)
Support and building instructions for an external Volume Light
System. This is an infinity project, because I don't want to spend
nearly $10 for the parts.
32-bit flat-memory model protected mode version which will be able
to use all the memory of your computer, and which also leaves 590kb
of memory in shell, and is capable of loading several modules into
memory at once.
Easy to use configuration program which edits morgul.cfg.
Features YOU suggest.
An even better graphics mode.
WAV playing.