Pages: [1]   Go Down
  Print  
Author Topic: AWE64 drivers for Win3.1  (Read 3239 times)
0 Members and 1 Guest are viewing this topic.
seskanda
Member
*
Offline Offline

Posts: 42


View Profile
« on: September 17, 2005, 02:06:24 AM »

Anybody got'em? Creative's support site just has updates NOT the actual drivers, and I searched high and low throughout the net and this link is all i could find that had the driver BUT its for Win9x only. i'd prefer the complete package w/bundled software, but the driver itself WILL suffice.

Thanks in advance!!
Logged
Dustin
Senior Member
*
Offline Offline

Posts: 296



View Profile
« Reply #1 on: September 17, 2005, 02:23:08 AM »

Everything you need can be obtained from creative-------->  http://us.creative.com/support/downloads/download.asp
Logged

-Dustin
seskanda
Member
*
Offline Offline

Posts: 42


View Profile
« Reply #2 on: September 17, 2005, 06:33:31 AM »

Nope, wrong. The ONLY thing of use there is CTCMBBS.EXE, which is the Plug 'n' Play manager that allows win3.11 to detect the card. S16DW3UP.EXE is, as the last two letters suggest, an update file that will NOT work on a PC that doesn't have the original drivers.I tried  S64BASIC.EXE and it seemed to just install some windows apps, and utilities, like the mixer, control panel, etc; this was after i ran winsetup.exe, btw. They did NOT install the Windows 3.1 DRIVERS!

When i manually tried to install them Through Main--> Control Panel --> Drivers i pointed to "unlisted or updated driver" I choose the first thing there, the Creative MIDI Instrument Mapper; luckily that device installed WELL. However, afterward, as i tried the actual drivers themselves things go awry. Besides the creative MIDI instrument mapper, three other drivers appear there, as well, which are the REAL drivers: Creative Stereo Music Synthesizer driver, SB AWE 64 MIDI synthesizer driver & SB AWE 64 Wave/Aux/Mixer/Midiport driver. When i tried the first one, clicking BOTH current and new options this error pops up:

"Cannot load the Creative Music Synthesizer Driver driver. The driver file may be missing. Try installing the driver again, or contact your system adminstrator."

OF course, I tried again but it gave the same message. When I tried the next one from the list another error comes up:

'Sound Blaster AWE32 MIDI Synth

VSBAWE.386 is not installed'

I already checked the C:\SB16 folder and the VSBAWE.286 file IS there! It's in the winappl sub-folder. Afterward, the exact same message that occured when i tried to install the creative music synth pops up, except, of course, it refers to the AWE64 MIDI instead. And when i try the last device from the list the same error error that occurred when i tried to install the creative music synth pops up AGAIN, except, of course, it refers to the AWE64 Wave/Aux/Midiport driver this time. I also tried the current and new buttons for these last two drivers.
Logged
Marten
Global Moderator
By Invitation Only
Senior Member
*
Offline Offline

Posts: 1,857



View Profile
« Reply #3 on: September 20, 2005, 12:43:03 AM »

I wasn't even aware that there was a Win3.1 driver for the AWE64.  Unfortunately, my old AWE64 CD is in Washington, and I am in California, and so I cannot put it up online for you presently.  If someone will remind me a month or two later I will see what I can do Smiley
Logged

Dustin
Senior Member
*
Offline Offline

Posts: 296



View Profile
« Reply #4 on: September 20, 2005, 11:31:38 AM »

Quote from: seskanda
Nope, wrong. The ONLY thing of use there is CTCMBBS.EXE, which is the Plug 'n' Play manager that allows win3.11 to detect the card. S16DW3UP.EXE is, as the last two letters suggest, an update file that will NOT work on a PC that doesn't have the original drivers.I tried  S64BASIC.EXE and it seemed to just install some windows apps, and utilities, like the mixer, control panel, etc; this was after i ran winsetup.exe, btw. They did NOT install the Windows 3.1 DRIVERS!

When i manually tried to install them Through Main--> Control Panel --> Drivers i pointed to "unlisted or updated driver" I choose the first thing there, the Creative MIDI Instrument Mapper; luckily that device installed WELL. However, afterward, as i tried the actual drivers themselves things go awry. Besides the creative MIDI instrument mapper, three other drivers appear there, as well, which are the REAL drivers: Creative Stereo Music Synthesizer driver, SB AWE 64 MIDI synthesizer driver & SB AWE 64 Wave/Aux/Mixer/Midiport driver. When i tried the first one, clicking BOTH current and new options this error pops up:

"Cannot load the Creative Music Synthesizer Driver driver. The driver file may be missing. Try installing the driver again, or contact your system adminstrator."

OF course, I tried again but it gave the same message. When I tried the next one from the list another error comes up:

'Sound Blaster AWE32 MIDI Synth

VSBAWE.386 is not installed'

I already checked the C:\SB16 folder and the VSBAWE.286 file IS there! It's in the winappl sub-folder. Afterward, the exact same message that occured when i tried to install the creative music synth pops up, except, of course, it refers to the AWE64 MIDI instead. And when i try the last device from the list the same error error that occurred when i tried to install the creative music synth pops up AGAIN, except, of course, it refers to the AWE64 Wave/Aux/Midiport driver this time. I also tried the current and new buttons for these last two drivers.



Seskanda,

   Windows 3.11 is basicly a DOS graphical user interface. I use this operating system all the time and found everything I needed for installing my Sound Blaster AWE 64 in windows 3.11 at the creative website. You do need CTCMBBS.EXE, as well as SBBASIC.EXE. During the installation (you must first install CTMBBS.EXE) of the SBBASIC.EXE file, it will ask you if you want your AWE 64 to operate in Windows 3.11. Assuming your native Windows directory is "C:\WINDOWS" you would provide that path and the software will add a AWE 64 control panel to the desktop. Using both of the above mentioned drivers, I was able to get my AWE 64 runnning in Windows 3.11. You don't need Windows specific drivers because Windows 3.11 isn't a completely contained operating system. It relies heavily on DOS to carry out it's operations. The DOS drivers will detect the presence of Windows 3.11 and copy the nessesary files to the Windows directory to enable full operation of the AWE 64 in both Windows and DOS.

Hope this helps (let me know if it doesn't....I went through this a thousand times before I found out that the DOS drivers work for Windows)
Logged

-Dustin
seskanda
Member
*
Offline Offline

Posts: 42


View Profile
« Reply #5 on: September 28, 2005, 05:38:59 PM »

Quote from: Dustin
Seskanda,

   Windows 3.11 is basicly a DOS graphical user interface. I use this operating system all the time and found everything I needed for installing my Sound Blaster AWE 64 in windows 3.11 at the creative website. You do need CTCMBBS.EXE, as well as SBBASIC.EXE. During the installation (you must first install CTMBBS.EXE) of the SBBASIC.EXE file, it will ask you if you want your AWE 64 to operate in Windows 3.11. Assuming your native Windows directory is "C:\WINDOWS" you would provide that path and the software will add a AWE 64 control panel to the desktop. Using both of the above mentioned drivers, I was able to get my AWE 64 runnning in Windows 3.11. You don't need Windows specific drivers because Windows 3.11 isn't a completely contained operating system. It relies heavily on DOS to carry out it's operations. The DOS drivers will detect the presence of Windows 3.11 and copy the nessesary files to the Windows directory to enable full operation of the AWE 64 in both Windows and DOS.

Hope this helps (let me know if it doesn't....I went through this a thousand times before I found out that the DOS drivers work for Windows).


Well, I tried SBBASIC.EXE as well , but i STILL got the exact same message as w/S64BASIC.EXE. However, my problem is SOLVED, after i found the AWE64 driver for Win 3.1 on the net somewhere (apparently they are as rare as a dodo!) I WILL provide the link if anybody else needs'em.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to: