So... Arena and Daggerfall

On Sun, 16 Apr 2006 12:31:54 -0400, Xocyll <Xocyll.DeleteThis@kingston.net>
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
@ECHO 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
 >> Stay informed about: So... Arena and Daggerfall 

Reply to message from "Captain Heyrab" <Captain_underscore_Heyrab@yahoo.
com> (Mon, 17 Apr 2006 03:19:27) about "Re: So... Arena and Daggerfall":


>> The line in the config.sys reads DEVICEHIGH=C:\VIBRA16\DRV\ VIBRA16.
>> SYS /UNIT 0 /BLASTER=A220 I5 D1 H5 P330 T6. I know that my mouse is
>> using IRQ 4, but I don't know if any other IRQs are being used. How do
>> I find out? I also know that the sound works fine when I just boot up
>> normally and play Daggerfall.
>> --
>> Nyctolops

CH> Might try changing I5 to I7 and let Arena re-detect the card.
CH> Although, if you already get sound in the detection program then it
CH> should be okay as-is. The DOS command "mem /c" or "mem / p" might shed
CH> some light on the problem.


*cough* IRQ7 is used by the Printer port usually. Just pull out the SB16
and get ANY other Soundblaster instead of it. IIRC the SB16 was a piece of
garbage. I remember once trying to get a computer to work for a
networksession with a SB16 in it. This card used to mix the system up
completely and I couldn't ever get it to work perfect. I then pulled out an
old SB1.0 and the machine worked fine with it.



Bye
Dirk Pfeiffer <dirk.DeleteThis@dbx501.de> Mon, 17 Apr 2006 08:25:08 +0200

=========================
Reality is something for noobs that can't handle Computergames!
=========================
Posted with Qusnetsoft NewsReader 2.2.0.8
 >> Stay informed about: So... Arena and Daggerfall 

Dirk Pfeiffer wrote:

> Reply to message from "Captain Heyrab" <Captain_underscore_Heyrab@yahoo.
> com> (Mon, 17 Apr 2006 03:19:27) about "Re: So... Arena and Daggerfall":
>
>
> >> The line in the config.sys reads DEVICEHIGH=C:\VIBRA16\DRV\ VIBRA16.
> >> SYS /UNIT 0 /BLASTER=A220 I5 D1 H5 P330 T6. I know that my mouse is
> >> using IRQ 4, but I don't know if any other IRQs are being used. How do
> >> I find out? I also know that the sound works fine when I just boot up
> >> normally and play Daggerfall.
> >> --
> >> Nyctolops
>
> CH> Might try changing I5 to I7 and let Arena re-detect the card.
> CH> Although, if you already get sound in the detection program then it
> CH> should be okay as-is. The DOS command "mem /c" or "mem / p" might
> shed CH> some light on the problem.
>
>
> *cough* IRQ7 is used by the Printer port usually. Just pull out the SB16
> and get ANY other Soundblaster instead of it. IIRC the SB16 was a piece of
> garbage. I remember once trying to get a computer to work for a
> networksession with a SB16 in it. This card used to mix the system up
> completely and I couldn't ever get it to work perfect. I then pulled out
> an old SB1.0 and the machine worked fine with it.

Funny, the first SB were the ones to use IRQ7 by default. Since the SB Pro
all SB cards use IRQ5 instead because of that same Printer port mess you
cite.

I think you got something mixed up in your card references
 >> Stay informed about: So... Arena and Daggerfall 

Reply to message from Christophe Cavalaria <chris.cavalaria.TakeThisOut@free.fr> (Tue,
18 Apr 2006 00:54:3 about "Re: So... Arena and Daggerfall":


CC> Dirk Pfeiffer wrote:

>> Reply to message from "Captain Heyrab" <Captain_underscore_
>> Heyrab@yahoo. com> (Mon, 17 Apr
>> 2006 03:19:27) about "Re: So... Arena and Daggerfall":


>>>> The line in the config.sys reads DEVICEHIGH=C:\VIBRA16\DRV\ VIBRA16.
>>>> SYS /UNIT 0 /BLASTER= A220 I5 D1 H5 P330 T6. I know that my mouse is
>>>> using IRQ 4, but I don't know if any other IRQs are being used. How
>>>> do I find out? I also know that the sound works fine when I just boot
>>>> up normally and play Daggerfall.
>>>> --
>>>> Nyctolops

>> CH> Might try changing I5 to I7 and let Arena re-detect the card. CH>
>> Although, if you already get sound in the detection program then it CH>
>> should be okay as-is. The DOS command "mem /c" or "mem / p" might shed
>> CH> some light on the problem.


>> *cough* IRQ7 is used by the Printer port usually. Just pull out the
>> SB16 and get ANY other Soundblaster instead of it. IIRC the SB16 was a
>> piece of garbage. I remember once trying to get a computer to work for
>> a networksession with a SB16 in it. This card used to mix the system up
>> completely and I couldn't ever get it to work perfect. I then pulled
>> out an old SB1.0 and the machine worked fine with it.

CC> Funny, the first SB were the ones to use IRQ7 by default. Since the SB
CC> Pro all SB cards use IRQ5 instead because of that same Printer port
CC> mess you cite.

CC> I think you got something mixed up in your card references

I am referring to his advice to change I5 to 7(!!) <---*hint*

And actually that was the MAIN reason they changed the default setting to
I5 since the SB PRO you mention....

So...nothing mixed up here

Bye
Dirk Pfeiffer <dirk.TakeThisOut@dbx501.de> Tue, 18 Apr 2006 11:46:21 +0200

=========================
Reality is something for noobs that can't handle Computergames!
=========================
Posted with Qusnetsoft NewsReader 2.2.0.8
 >> Stay informed about: So... Arena and Daggerfall 

"Nyctolops" <nyctolops.DeleteThis@vla.nospam.com> wrote in message
news:odd642pep2lkcuasl06m1hr5t4d6gp1tig@4ax.com...
> On Sun, 16 Apr 2006 12:31:54 -0400, Xocyll <Xocyll.DeleteThis@kingston.net>
> 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
> @ECHO 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 refreshing 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.
 >> Stay informed about: So... Arena and Daggerfall 

Reply to message from "Captain Heyrab" <Captain_underscore_Heyrab@yahoo.
com> (Sun, 23 Apr 2006 03:38:33) about "Re: So... Arena and Daggerfall":


CH> "Nyctolops" <nyctolops.RemoveThis@vla.nospam. com> wrote in message news:
CH> odd642pep2lkcuasl06m1hr5t4d6gp1tig
CH> @4ax.com...
>> On Sun, 16 Apr 2006 12:31:54 -0400, Xocyll <Xocyll.RemoveThis@kingston.net> 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
>> @ECHO 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

CH> That was a refreshing discussion of IRQ settings, there always were
CH> conflicts over those...

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

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

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

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

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

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



IIRC it was also important in WHICH order you loaded things into upper
memory. Back in those days I was very good in optimizing config.sys and
autoexec.bat and had quite a few options in my boot menu to play with. XMS,
EMS or none of both...

Though it's amazing how lazy one got with Windows XP and how many things
you just forget. I tried to dig out some old discs to refresh my memory,
but none of them work anymore. So I am afraid I won't be of much help....

:-/



Bye
Dirk Pfeiffer <dirk.RemoveThis@dbx501.de> Sun, 23 Apr 2006 09:30:35 +0200

=========================
Reality is something for noobs that can't handle Computergames!
=========================
Posted with Qusnetsoft NewsReader 2.2.0.8
 >> Stay informed about: So... Arena and Daggerfall 

On Sat, 22 Apr 2006 21:38:33 -0400, "Captain Heyrab"
<Captain_underscore_Heyrab RemoveThis @yahoo.com> wrote:


>That was a refreshing 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

I need that line for Arena to start at all. One of these days I may
get brave and reinstall my soundcard software using some suggestions
from the manual. I hesitate to do it, because it works fine now for
everything but Arena.

>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.

I checked and normally nothing at all is running in upper memory.

>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.
>
I am getting used to playing Arena without sound. It is a fun game
and I am enjoying it. I do have a question. Do the constant effect
items wear out like they do in Daggerfall? I have looked through the
manual and I can't find any mention of whether they do or not.
--
Nyctolops
 >> Stay informed about: So... Arena and Daggerfall