I should say before I go any further that this is the floppy version
of the game, so I'm just missing music and sound f/x.
My next option was to try booting my PC into DOS 6 and trying that.
Well, that all works EXCEPT for the sound. Not a squeak do I get from
my AWE64.
Now, the AWE64 is an ISA-based plug and play card, as a result of
which I've used the Creative Configuration Manager, installed the DOS
drivers, etc. The card tests out fine and produces sound using
Creative Labs' DIAGNOSE programme.
I've also looked at the Troubleshooting section of Lucasarts' web site
and tried all their tips on sound problems such as ensuring you use an
IRQ of 2, 5 or 7, DMA 1, etc. All to no avail.
Could the speed of my PC have anything to do with it? It's a Celeron
600 overclocked to 900 MHz. Or is it some incompatibility with the
AWE64 sound card?
I'm at a loss now. What else can I try?
I really want to play this excellent game again, but I hate playing
games without sound!
Thanks,
Phil
"Phil" <pdav...@aol.com> wrote in message
news:3be6b65c...@News.CIS.DFN.DE...
>Same here, I couldn't get The Dig to play sounds on my sister's new machine
>with XP. :\
:-(
My problem though is that I can't get sound when I boot into DOS, ie
*without* XP at all. :-(
Phil
I got sound in Fate of Atlantis in DOS mode of Win 98 using an
AWE 64. But I couldn't do it with a boot disk. I had to use the
Start button and shut down to DOS mode by that route.
I had the CD version of Fate of Atlantis and used a slow
computer (233 MHz K-6) because I couldn't get it to run on
my 400 MHz computer with the SBLive (kept freezing) and
the midi music sounded rotten.
I don't know if slowing down the computer would help with the
sound at all. You could try running the game with moslo to see
if it makes a difference.
There are several patches for Fate of Atlantis at the LucasArts
website (some for the floppy version and some for the CD version)
http://support.lucasarts.com/patches/indy-fate.htm
but I don't know if any would solve your problem.
atlantis r and off you go ( i hope :)
works great for me
grtz
Phil <pdav...@aol.com> schreef in berichtnieuws
3be6b65c...@News.CIS.DFN.DE...
>I got sound in Fate of Atlantis in DOS mode of Win 98 using an
>AWE 64. But I couldn't do it with a boot disk. I had to use the
>Start button and shut down to DOS mode by that route.
>I had the CD version of Fate of Atlantis and used a slow
>computer (233 MHz K-6) because I couldn't get it to run on
>my 400 MHz computer with the SBLive (kept freezing) and
>the midi music sounded rotten.
Interesting, thanks. Doesn't seem to work for me though under Win 95.
:-(
>I don't know if slowing down the computer would help with the
>sound at all. You could try running the game with moslo to see
>if it makes a difference.
Nope, no luck I'm afraid.
>There are several patches for Fate of Atlantis at the LucasArts
>website (some for the floppy version and some for the CD version)
>http://support.lucasarts.com/patches/indy-fate.htm
>but I don't know if any would solve your problem.
I'm tried them, but no joy. Thanks very much for your suggestions,
hopefully I'll get there in the end. Hopefully ...........
Phil
>Hiya,
>you might wanna try loading some drivers in dos
>c:\windows\ctcm
>and the aweutil in program files\creative\ctsnd
>AWEUTIL /EM:MT32 gives you roland mt32 emulation
>
>atlantis r and off you go ( i hope :)
>works great for me
Thanks for the suggestion. I just tried that and get the error:
mpu-401 initialization failed
Any ideas what might cause that?
Thanks,
Phil
>You need a decent!!! legacy sound driver for XP. The one M$ delivers is
>not very good. An english company has produced a better one which
>supposingly works with XP and Win2k. Don´t ask me for its name however,
>I once had a demo version in my hands and it worked with FOA in Win2k.
>
Thanks, I'll look it up.
Any ideas on the other part of my question, ie how I can get sound in
FoA when booting to MS-DOS?
Thanks,
Phil
Try posting the contents of the autoexec.bat and config.sys
you're using and maybe somebody will have an idea for
what to change to improve things.
>Try posting the contents of the autoexec.bat and config.sys
>you're using and maybe somebody will have an idea for
>what to change to improve things.
>
A good idea, thanks.
Okay, here's my config.sys:
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE 4096
DEVICE=C:\CTCM\CTCM.EXE
DOS=UMB
DOS=HIGH
FILES=40
Country=044,850,C:\WINDOWS\COMMAND\country.sys
FILES=40
DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:1
DEVICE=C:\SB16\DRV\CTMMSYS.SYS
and here's my autoexec.bat:
SET CTCM=C:\CTCM
SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H1 E620 T6
SET MGA=C:\MGA\SETUP\
C:\CTCM\CTCU /S
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\SB16\DIAGNOSE /S
C:\SB16\AWEUTIL /S
C:\SB16\MIXERSET /P /Q
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOS;c:\logitech\mouse
SET TEMP=C:\DOS
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
doskey/insert
SET lmouse=c:\logitech\mouse
Thanks in anticipation. :-)
Phil
What's ctcm.exe?
> and here's my autoexec.bat:
>
> SET CTCM=C:\CTCM
> SET SOUND=C:\SB16
> SET BLASTER=A220 I5 D1 H1 E620 T6
> SET MGA=C:\MGA\SETUP\
> C:\CTCM\CTCU /S
> SET MIDI=SYNTH:1 MAP:E MODE:0
> C:\SB16\DIAGNOSE /S
> C:\SB16\AWEUTIL /S
> C:\SB16\MIXERSET /P /Q
> @ECHO OFF
> PROMPT $p$g
> PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOS;c:\logitech\mouse
> SET TEMP=C:\DOS
> keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
> doskey/insert
> SET lmouse=c:\logitech\mouse
What's ctcu?
Are they Sound Blaster drivers? If so, should they really be used
together with the ones in C:\SB16\ ? I don't know, but it looks to me
that you might be mixing different versions of sound drivers. You could
try putting REM before those two lines, or the SB16 lines. (rem =
remark: the lines will be ignored, and it's easy to resore to their
prior state.)
Besides the commands I don't recognise, I see nothing wrong with those
files. Do you get any error messages when starting FoA?
Rikard
>What's ctcm.exe?
It's Creative's Configuration Manager (DOS-based) that allows DOS
programs to access the settings for their Plug and Play sound cards.
>> and here's my autoexec.bat:
>What's ctcu?
CTSU.EXE can be run separately to setup the sound card itself (ie IRQ,
I/O, etc).
It and CTCM are both required and added by the relevant installation
program.
>Are they Sound Blaster drivers? If so, should they really be used
>together with the ones in C:\SB16\ ? I don't know, but it looks to me
>that you might be mixing different versions of sound drivers. You could
>try putting REM before those two lines, or the SB16 lines. (rem =
>remark: the lines will be ignored, and it's easy to resore to their
>prior state.)
Thanks for the suggestion. Just tried that and still no luck. :-(
What puzzles me is that Doom works fine with sound, but that's a newer
program and I assume it accesses the sound card differently.
>Besides the commands I don't recognise, I see nothing wrong with those
>files. Do you get any error messages when starting FoA?
None at all. Well, only if I try the Roland sound option, then it
moans there are no drivers loaded. Fair enough as there aren't. :)
We'll get there in the end ........ I hope!
Thanks,
Phil
Have you tried (copied from helpme.doc on my FoA CD):
ATLANTIS s%p/%i/BUFFER_SIZE(Optional)
- - -
і і АДДДД The size of the buffer in K used for
і і spooling digital sounds from the
і і CD drive (default 8K).
і і
і АДДДДДДДДДДДД The IRQ used to signal an end of DMA.
і
АДДДДДДДДДДДДДДД The IO Port used to communicate with
the sound hardware.
That would mean, with your settings:
ATLANTIS s220/5
I think that should at least give an error message if it doesn't work.
Rikard
>That would mean, with your settings:
>
>ATLANTIS s220/5
>
>I think that should at least give an error message if it doesn't work.
Sadly it didn't work, but no error message either.
Incidentally, I'm using the floppy disk version - maybe it makes a
difference?
I wish I could get hold of the CD version, but am unwilling to pay
again seeing as I've already paid for my floppy disk original.
Thanks again.
Phil
>> mpu-401 initialization failed
>>
>> Any ideas what might cause that?
>>
>I'm not sure, does that happen when you start the game or when you try the
>aweutil?
Only when I start AWEUTIL with the /EM:MT32 option.
Thanks,
Phil
I've finally managed to resolve this issue by setting my BIOS to
recognise the operating system as Plug and Play.
Thanks to you all for your suggestions - we got there in the end. :-)
Phil