VOGONS


First post, by haker120

User metadata
Rank Member
Rank
Member

I have never configured it under Win95 DOS, not DOS Mode in Windows' window. I'm using Phil's reboot to MSDOS because I like it.

The thing is sound works under Win95's DOS but not right away and only in diagnose app. When I'm checking diagnose I have correct 220 next 300 (because collides with MPU-401 in Windows) and IRQ5 impossible to obtain. Next I'm turning app CTCU and after it aweutil which enables TSR and after that I can set values as 220, 300 (or 330, it works here now) 5 1 and 5, I take update settings and after reboot the same however without reboot I managed Rayman installer to scream perfect with settings: SBPro, 5 and 5, I know corect settings are anything Sound Blaster, 5 and 1.

How to finish configuring this particular PC? I just managed with forum help to set up Win95 with USB support now DOS.

I need to mention under DOS6.22 everything was fine but this PC is 233MMX, S3 Trio64V+ 4MB and Voodoo 1 4MB so I couldn't run some games that need Windows 9x. 😁

EDIT: I know how to configure all of this under DOS6.22 because no app says it's incompatible with Windows 3.11 and Win95's DOS mode.

Reply 1 of 2, by Gmlb256

User metadata
Rank l33t
Rank
l33t

CTCM should be used for initialization, not CTCU (that utility isn't intended for Windows 9x, but there is a patched version on the following thread: Patched CTCM/CTCU to remove Windows detection). The sound card resources can be configured in Windows Device Manager, by doing this it will make the necessary changes to CTPNP.CFG. I also highly recommend starting AWEUTIL with the /S command line switch, which only initializes the EMU8K without loading it as a TSR.

BTW, the AWE64 Gold is only compatible with the original Sound Blaster and SB16. That card will output mono if the SBPro option is selected.

VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce3 Ti 200 64 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS

Reply 2 of 2, by haker120

User metadata
Rank Member
Rank
Member

The thing is settings from Windows environment do not apply for DOS session for some reason.

Thanks @Gmlb256, I'll try this tomorrow for me and yes, not ctcu only ctcm. 😁

EDIT: I have now sound and music in games but for some reason CTCM initializes sound environment as SET BLASTER=A220 I10 D3 H5 P300 E620 T6

This is my CTPNP.CFG:

[AWE]
CardId=CTL009E
Serial=060D4616
Csn=1
LogDev=2
Port0=620
Port1=A20
Port2=E20

[PNP]
ReadPort=277

[SB16]
Csn=1
LogDev=0
CardId=CTL009E
Serial=060D4616
Port0=220
Port1=330
Port2=388
Irq0=5
Dma0=1
Dma1=5

And this is my autoexec for DOS session which 'automatically' forces different values unless I manually change them via CTCU.

@ECHO OFF
PROMPT $P$G
PATH=C:\SB16
SET TEMP=C:\WINDOWS\TEMP
SET TMP=C:\WINDOWS\TEMP
SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H5 P300 E620 T6
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTCM=C:\SB16\CTCM
C:\SB16\CTCM /S
C:\SB16\DIAGNOSE /S
C:\SB16\AWEUTIL /S
C:\SB16\MIXERSET /P /Q
@ECHO OFF
GoTo %config%
:EMC
:XMC
:CMC
LH C:\WINDOWS\COMMAND\MSCDEX.EXE /D:OPTICAL
:EM
:XM
:CM
LH C:\DRIVERS\CTMOUSE.EXE /R2
:E
:X
:C
IF EXIST C:\WINDOWS\DOSSTART.BAT CALL C:\WINDOWS\DOSSTART.BAT
REM
REM Nast©pujĄce wiersze zostaˆy utworzone przez system Windows.
REM Nie naleľy ich zmienia†.
REM
C:
CD C:\
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

EDIT2: I fixed it by changing IRQ 10 and DMA5 to be used by ISA devices. Now all works. 😁