Computing.Net > Forums > Windows 95/98 > AWE64 will not initialize in DOS

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

AWE64 will not initialize in DOS

Reply to Message Icon

Name: Luna M
Date: November 13, 2003 at 08:36:25 Pacific
OS: Win98 v 4.10.1998
CPU/Ram: P166 MMX/80MB RAM
Comment:

I have an old Pentium computer that I want to use as a DOS/old Windows game machine.

It is running Windows 98 (not SE)

The soundcard is an AWE64 Gold ISA. I've installed the card and it works fine in windows. I also gathered the required files and edited the autoexec.bat and config.sys to load the DOS drivers on startup. The drivers all load fine--but when I boot the computer into DOS, I get this message:

Could not detect PnP soundcard. Please be sure the hardware is properly insterted. If the problem persists contact technical support.
ERR012: AWE32 Initialization failed.

I have no sound in any games (obviously). I've researched this extensively and verified I have the correct drivers and DOS applications. I seriously doubt the sound card is damaged. Is there anything more I can do to try and remedy this problem?

For reference:

My Autoexec.bat
--
SET BLASTER=A220 I5 D1 H5 P330 E620 T4

@ECHO OFF
PROMPT $P$G
PATH c:\windows;c:\windows\COMMAND;C:\;c:\pkzip
SET DIRCMD=/O
SET TEMP=C:\PBTOOLS\WINTEMP
SET WINPMT=[WINDOWS] $P$G
SET CTCM=C:\AWE64
SET SOUND=C:\AWE64
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\AWE64\MIXERSET /P /Q
C:\AWE64\AWEUTIL.COM /S


My Config.sys
--
DEVICE=C:\WINDOWS\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\EMM386.exe NOEMS I=B000-B7FF
FILESHIGH=50
BUFFERSHIGH=20
STACKSHIGH=0,0
FCBSHIGH=1
DEVICEHIGH=C:\WINDOWS\MOUSE.SYS
DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE
FILES=20
DEVICE=C:\AWE64\CTCM.exe
REM the next two lines are not required for all games
DEVICEHIGH=C:\AWE64\CTSB16.SYS /UNIT=0 /WIN95 /BLASTER=A220 I:5 D:1 H:5
DEVICEHIGH=C:\AWE64\CTMMSYS.SYS



Sponsored Link
Ads by Google

Response Number 1
Name: Dan Penny
Date: November 13, 2003 at 09:00:41 Pacific
Reply:

Try looking in your bios setups for PnP. There's a good possibility that your bios has such. They may be one of the "main" screens, or they may be under ADVANCED. If you find settings, ensure that they're enabled.

Your config file settings look OK, though it's been a long time since I had an AWE64 set up on one of my machines. I have a CD for that, but alas it's still packed (I moved in June) as I no longer need it.


0

Response Number 2
Name: Luna M
Date: November 13, 2003 at 09:20:05 Pacific
Reply:

The only options I have under the BIOS are "Use PnP OS" and "Use BIOS Setup."

Use PnP OS is currently selected.

Under PnP OS I have the options "Windows 95" "Use other PnP OS" and "Disable." It's currently set to Win95.

Under BIOS PnP Setup (which is not selected), it gives me a list of IRQs:

IRQ 4 - Available
IRQ 5 - Available
etc.
I can change "available" to "used by ISA device."

There is also an option to enable/disable ISA Shared Memory (it's disabled right now).

So, to recap, currently the BIOS is set to Use PnP OS, Windows 95 (no other options are selected).


0

Response Number 3
Name: gene
Date: November 13, 2003 at 09:58:37 Pacific
Reply:

I wonder why you are getting this error message:
"ERR012: AWE32 Initialization failed."
When you are trying to install an `awe64' driver.


0

Response Number 4
Name: Luna M
Date: November 13, 2003 at 10:03:42 Pacific
Reply:

*ahem* Because some of the drivers are virtually unchanged between the two. In fact, for DOS, the AWE64 requires some files that are found in the SB16 archives. I promise you, I have the proper drivers. That is, of course, unless Creative decided to bundle the incorrect drivers on the AWE64 installation CD.


0

Response Number 5
Name: Dave
Date: November 13, 2003 at 10:46:47 Pacific
Reply:

Luna is correct, the drivers for the AWE32 are the same as for the 64. The only difference between the two cards is, The AWE32 has 32 hardware sound fonts and the AWE 64 has 32 hardware and 32 software sound fonts. The extra sound fonts are software driven, and not dependant on the drivers for the card.


0

Related Posts

See More



Response Number 6
Name: Luna M
Date: November 13, 2003 at 11:08:25 Pacific
Reply:


Well, in any case, I fixed the problem--sort of. If I do a cold boot into DOS mode, the card inits fine...but if I try to reboot into DOS from Windows, it fails. :( I'd like to be able to fix this problem, but I can live with it if I can't. I still have no idea what's wrong, although--since a cold boot seems to be the answer--maybe it has something to do with another driver/device/set environment that is conflicting? I have no clue...


0

Response Number 7
Name: gene
Date: November 13, 2003 at 13:34:21 Pacific
Reply:

You could try setting up the Dosstart.bat file with loading the drivers. It is used when going from windows to Dos.
c:\windows\dosstart.bat


0

Response Number 8
Name: Dan Penny
Date: November 13, 2003 at 13:58:30 Pacific
Reply:

"but when I boot the computer into DOS, I get...."

I thought you were booting into raw dos, and not a "Restart in DOS Mode" from windows. If you want this to work in both worlds, what gene suggests is what I was going to suggest next. The DEVICE=C:\AWE64\CTCM.exe can be called from the dosstart.bat file as it's an executable and not a .sys driver;

C:\AWE64\CTCM.exe

and then the rest from your autoexec.bat can follow below that line.

SET CTCM=C:\AWE64
SET SOUND=C:\AWE64
SET BLASTER=A220 I5 D1 H5 P330 E620 T4
SET MIDI=SYNTH:1 MAP:E MODE:0
C:\AWE64\MIXERSET /P /Q
C:\AWE64\AWEUTIL.COM /S

You may have to re-arrange the loading order. (As I said, been a long time since I ran an old ISA SB.)


0

Response Number 9
Name: DAVEINCAPS
Date: November 13, 2003 at 14:10:03 Pacific
Reply:

In addition to installing the drivers in dosstart.bat it'd be a good idea to disable 'PnP OS' as that sometimes interferes with loading dos drivers when exiting windows to dos.


0

Response Number 10
Name: Luna M
Date: November 13, 2003 at 15:01:25 Pacific
Reply:

"I thought you were booting into raw dos, and not a "Restart in DOS Mode" from windows. ..."

Yeah, sorry about that, I should have specified (talk about the solution being right under your nose...don't I feel silly).

I've taken the suggestions mentioned here and it has finally fixed the problem completely. Thanks to everyone who helped out!



0

Response Number 11
Name: Dan Penny
Date: November 13, 2003 at 15:06:14 Pacific
Reply:

Yeah, great learning place huh? ;>)


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: AWE64 will not initialize in DOS

computer will not start in dos www.computing.net/answers/windows-95/computer-will-not-start-in-dos/163325.html

Win98 did not load properly, will not boot in Safe Mode www.computing.net/answers/windows-95/win98-did-not-load-properly-will-not-boot-in-safe-mode/41421.html

win.com will not run in DOS mode. www.computing.net/answers/windows-95/wincom-will-not-run-in-dos-mode-/156755.html