Re: So... Arena and Daggerfall

"Nyctolops" <nyctolops@[EMAIL PROTECTED]
> wrote in message 
news:odd642pep2lkcuasl06m1hr5t4d6gp1tig@[EMAIL PROTECTED]
> On Sun, 16 Apr 2006 12:31:54 -0400, Xocyll <Xocyll@[EMAIL PROTECTED]
>
> wrote:
>
>>At this point, maybe you should post the contents of the config.sys and
>>autoexec.bat so we can see where everything is and if something crucial
>>is missing.
>
> I was afraid you would say that.  :-)  I will have to type them in, as
> my present computer insists that the floppies I made with the
> information on them are unformatted.
>
>>When Arena detects the card, does it use the info from the SET BLASTER
>>line?
>>You mentioned Daggerfall - what settings does it detect for the sound
>>card - since they seem to work?
>>
> These are the settings which run when I boot up normally -- the ones
> that work with Daggerfall:
> autoexec.bat
> SET SOUND=C:\VIBRA16
> SET BLASTER=A22O I5 D1 H5 P330 T6
> SET MIDI=SYNTH:1 MAP:E
> SET CTCM=C:\CTCM
> C:\VIBRA16\DIAGNOSE /S /W=C:\WINDOWS
> C:\VIBRA16\MIXERSET /P /Q
> C:\CTCM\CTCU /S /W=C:\WINDOWS
> C:\DOS\SMARTDRV.EXE /X
> @[EMAIL PROTECTED]
 OFF
> PROMPT $p$g
> PATH C:\WINDOWS;C:\DOS; C:\MOUSE;
> MOUSE
> SET TEMP=C:\DOS
> \BIN\MSCDEX.EXE /D:MSCD000
>
> config.sys
> LASTDRIVE=Z
> DEVICE=C:\DOS\SETVER.EXE
> DEVICE=C:\WINDOWS\HIMEM.SYS
> DEVICE=C:\CTCM\CTCM.EXE
> DOS=HIGH
> DEVICE=C:\WINDOWS\IFSHLP.SYS
> STACKS=9,256
> DEVICE=\DEV\TAISATAP.SYS /D:MSCD000 /N:1
> FILES=40
>
> Now here are the files which hang up after identifying the sound card:
> autoexec.bat
> SET SOUND=C:\VIBRA16
> SET BLASTER=A220 I5 D1 H5 P330 T6
> SET MIDI=SYNTH:1 MAP:E
> SET CTCM=C:\CTCM
> LH C:\VIBRA16\DIAGNOSE /S
> LH C:\VIBRA16\MIXERSET /P /Q
> LH C:\CTCM\CTCU /S
> LH C:\BIN\MSCDEX.EXE /D:MSCD000 /M:6 /E
> PATH C:\;C:\DOS;C:\MOUSE;
> LH MOUSE
> C:
> CD ARENA_CD
> ARENA
>
> config.sys
> LASTDRIVE=Z
> BUFFERS=20
> FILES=50
> DEVICEHIGH=C:\DOS\HIMEM.SYS
> DEVICEHIGH=C:\DOS\EMM386.EXE RAM 2800 i=b000-b7ff
> DEVICEHIGH=C:\CTCM\CTCM.EXE
> DEVICEHIGH=C:\VIBRA16\DRV\VIBRA16.SYS /UNIT=0 /BLASTER=A220 I5 D1 H5
> P330 T6
> DEVICEHIGH=C:\VIBRA16\DRV\CTMM.SYS
> DOS=HIGH, UMB
> DEVICEHIGH=C:\DEV\TAISATAP.SYS /D:MSCD000 /N:1
>
> I hope you can find something, because it certainly has me stumped.
> --
> Nyctolops

That was a refre****ng discussion of IRQ settings, there always were 
conflicts over those...

Nothing glares out at me except that the Arena boot loads in upper memory 
whereas Daggerfall does not.

I'm wondering if this line should me remmed out. I don't remember exactly 
but it could have been for older DOS versions. Try this and see what 
happens:
REM DEVICEHIGH=C:\DOS\EMM386.EXE RAM 2800 i=b000-b7ff

It is sometimes neccessary to play around to find a good memory
combination. 
The goal is to load as much in upper memory as possible without causing 
problems.  This is where the mem command is useful. It tells you what
loaded 
where and how much room it uses.

DEVICEHIGH can be replaced with DEVICE to load a particular driver in
lower 
memory. Simply remove the LH from the front of an autoexec command to run
in 
lower memory. There is only so much room and it is first come first
served.

Some motherboards also used upper memory and had to be told not too, but 
again I'm foggy on this after so many years.

Good luck, I can't really play Daggerfall on my XP system. I've booted it
up 
in DOSBOX but it isn't like the real thing. Certain moves don't work and
if 
I can't get past the skeleton on the stairs there isn't much point. The 
sound was a big part of the fun.