AWE64-OS/2 Newsgroup
I no longer develop this legacy resource.
The Archive | About This Newsgroup
The Archive
Newsgroup Index
Note: While the index is correctly threaded, the newsgroup messages (below) are not (they are in order of the message number). For this reason, it would be best if you used the back button on your browser to avoid confusion.
- Welcome - Russ (Apr 1999)
- MIDI banks - Rustem (Apr 1999)
- Re: MIDI banks - Benjamin van den Hout (Apr 1999)
- Re: MIDI banks - ccfang (Apr 1999)
- How to make AWE64 work - Benjamin (Apr 1999)
- Re: MIDI banks - ccfang (Apr 1999)
- Re: MIDI banks - Benjamin van den Hout (Apr 1999)
- trouble with SB PnP AWE32 - bostjan.vilfan (Apr 1999)
- Re: trouble with SB PnP AWE32 - Russ (Apr 1999)
- Will the AWE64 drivers work with SB Live PCI? - GerrysMailBox (Apr 1999)
- Re: Will the AWE64 drivers work with SB Live PCI? - Russ (Apr 1999)
- MOUSE.SYS after AWE64-DeviceDriver! - Joerg Sievers (Apr 1999)
- Finally Got AWE64 PnP Working - Richard Fiveash (Apr 1999)
- Re: Finally Got AWE64 PnP Working - Richard Fiveash (Apr 1999)
- Microphone in Warp 4 (AWE64) - Frank L. Jones (Apr 1999)
- Help with SB AWE64 settings???? - drjflowers (May 1999)
- Worked after OS/2 reinstall - Anonymous (May 1999)
- SB 64 PCI - ckuhroeber (Jun 1999)
- Re: SB 64 PCI - martin.mausen (Jul 1999)
- Re: SB 64 PCI - spinoza (Sep 1999)
- Re: SB 64 PCI - martin.mausen (Jul 1999)
- 3F8,OS/2,& AWE64 - zeppelin (Jul 1999)
- Has anyone succeeded in getting a PCI Sound Card to work in OS/2? - Russ (Jul 1999)
- Re: Has anyone succeeded in getting a PCI Sound Card to work in OS/2? - Anonymous (Sep 1999)
- Ensoniq PCI Driver Location - Russ (Mar 2000)
- Re: Has anyone succeeded in getting a PCI Sound Card to work in OS/2? - Anonymous (Sep 1999)
- No sound after suspend - Bill (Jul 1999)
- Re: No sound after suspend - Axel Hagedorn (Aug 1999)
- Microphone in Warp 4 - David Iniesta (Aug 1999)
- Re: Microphone in Warp 4 - Anonymous (Aug 1999)
- AWE 64 won't work - Dan Egli (Sep 1999)
- Re: AWE 64 won't work - Anonymous (Sep 1999)
- Clipped wav files - Brad Taisey (Dec 1999)
- Wave and MIDI driver won't load in WIN-OS/2 - DMA buffer allocation problem - susimon (Feb 2000)
- Any device driver programers out there? - Russ (Mar 2000)
- Anyone have the audio software for SB 32 PNP? - ed (Apr 2000)
- SoundBlaster Live! OS/2 Beta drivers available - Russ (May 2000)
- AWE64 background hiss problem - Ed Balme (Jul 2000)
- Sound Blaster CD help - djensen (Aug 2000)
- Slow Mp3s? Hows that possible? - skydiver (Nov 2000)
- Re: Slow Mp3s? Hows that possible? - skydiver (Nov 2000)
- MIDI - DRSmith (Apr 2001)
- Awe64 for Dos GAmes - J Maycotte (Jul 2001)
Newsgroup Messages
Note: While the archive index is correctly threaded, the newsgroup messages (below) are not (they are in order of the message number). For this reason, it would be best if you used the back button on your browser to avoid confusion.
#1 - "Welcome"
Welcome to the new AWE64 for OS/2 Newsgroup.
I've received several e-mails over the last week with requests that probably are best answered by more than one person and it would benefit everyone to have them visible for all to learn from.
This newsgroup is hosted on my server. The advantage is that I control when messages are deleted from the server (one year by default). The disadvantage is that you need to bring this page up in your Web browser to view and post messages rather than having them mailed to you.
The originator of a message will have their posting mailed to them, but generally not the answers.
Participation is the key to the success of this newsgroup. Keep checking back. If it is as popular as I think it will be it should be very useful. Thanks for all your input!
Russ
#2 - "MIDI banks"
Hi!
I have installed this drivers and my SB AWE64 works. But sometimes I should load MIDI banks manually in order to listen MIDI. Do you have some ideas how to load banks by default or some AWE64 banks with the size no more 512K?
Best regards,
Rustem
#3 - "Re: MIDI banks"
Hi,
> I have installed this drivers and my SB AWE64 works. But sometimes I should load MIDI banks manually in order to listen MIDI. Do you have some ideas how to load banks by default or some AWE64 banks with the size no more 512K?
I don't know a solution to your problem of having to load banks manually, but there are some MIDI banks in the \mmos2\sbk directory. Or have you already discovered these? One is really weird. It's called user-defined or something like that. When you play music with it, it sounds like the sound of a drainpipe :)
Regards, Benjamin van den Hout
#4 - "trouble with SB PnP AWE32"
I have a Sound Blaster PnP AWE32 card, and I'm having trouble completing the installation Warp 4. With the help of several people I have managed to get it to install without error (no complaints on boot), and the CD player works. However, the sound object does not work, and no system sounds are produced. I cannot get it to play any of the listed files. I went to the MMOS2 directory, and tried playing files with the PLAY.CMD program. I get the error message "No device driver found".
Any help would be appreciated.
Regards,
Bostjan
#5 - "Re: MIDI banks"
I bought AWE64 about a year ago, and have not been able to enjoy it. So what is the procedure to make it work?
Chih
> Hi,
>
> > I have installed this drivers and my SB AWE64 works. But sometimes I should load MIDI banks manually in order to listen MIDI. Do you have some ideas how to load banks by default or some AWE64 banks with the size no more 512K?
#6 - "Re: trouble with SB PnP AWE32"
> I have a Sound Blaster PnP AWE32 card, and I'm having trouble completing the installation Warp 4.
(==Text removed==)
I get the error message "No device driver found".
Take a look at your CONFIG.SYS file. The following is what mine looks like for a *standard*(not PnP) AWE32 running Warp 4 on the D: Drive:
DEVICE=D:\MMOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:8 /M:330 /N:SBAUD1$ /Q /P
DEVICE=D:\MMOS2\AUDIOVDD.SYS SBAUD1$
SET MMBASE=D:\MMOS2;
SET DSPPATH=D:\MMOS2\DSP;
SET NCDEBUG=4000
RUN=D:\MMOS2\MIDIDMON.EXE
DEVICE=D:\MMOS2\SSMDD.SYS
DEVICE=D:\MMOS2\R0STUB.SYS
DEVICE=D:\MMOS2\MIDI.SYS
DEVICE=D:\MMOS2\VCSHDD.SYS
RUN=D:\MMOS2\QRYMMCD.EXE
This setup is the default settings for Sound Blaster:
Port Address = 220
MIDI = 330
IRQ = 5
DMA 8-bit = 1
DMA 16-bit = 5
Colin Hildinger's The Official Unofficial Guide to Using the Creative Labs AWE32,SB32, and SB16 with OS/2 Warp page http://www.ionet.net/~colin/awe32.html [link no longer works] may help you as well. His suggested course of action is:
1.Install the AWE32 PnP drivers using selective install
2.Run Creative's install and install the new AWE 32/64 drivers
3.Make sure you answer "yes" to replace all existing files, even if it says that they're newer. Also make sure you select the PnP option in Creative's install.
4.Shutdown, reboot, and enjoy.
Good Luck!
Russ
#7 - "How to make AWE64 work"
> I bought AWE64 about a year ago, and have not been able to enjoy it. So what is the procedure to make it work?
I suggest you read the instructions on this page first. Also download the drivers from this page, because I first had another version that claimed to be a AWE64 driver, but in fact was not. If you stil have problems after using the instructions on the page, we will be happy to help you solve your problems!
Benjamin van den Hout
#8 - "Will the AWE64 drivers work with SB Live PCI?"
Hello Russ, I'm Gerard Fernandes from India and I badly need help. Since I only recently got access to the InterNet, I was totally unaware about no further support from Creative for its future cards on OS/2. Thats really a pity because the latest SB Live is a terrific card anyway you look at it. And its about the only easily available high end Audio Card in India. I wanted to know if the AWE64 drivers will work with the PCI SB Live card. The port address is 6100 (instead of 220). There are no DMA channels and the new IRQ is 10. So the AWE32 OS/2 drivers can't "see" the card at all. The card ships with a DOS driver that makes it visible at A=220, I=5, D=1, H=5, P=330 (this works well for DOS games in a pure DOS environment). But since DOS drivers load after OS/2 drivers this method does not work for OS/2. Anyway, this driver doesn't even make the card visible to Win 3.1 on a pure DOS/Win 3.1 environment either. So since these new AWE64 drivers are PnP enabled, are they capable of picking up the card address from the BIOS or detecting the card at its configured address/IRQ (6100/10)? Or is there a workaround that can make the DOS driver (to make it visible at the old adress) load before the OS/2 driver? I am going to try this out. If I have any success (doubtful!) I will post details on this site. In the meanwhile, any help/information/guidance/advice will be appreciated. Thanks and regards, Gerard Fernandes
#9 - "Re: Will the AWE64 drivers work with SB Live PCI?"
> I wanted to know if the AWE64 drivers will work with the PCI SB Live card. The port address is 6100 (instead of 220). There are no DMA channels and the new IRQ is 10. So the AWE32 OS/2 drivers can't "see" the card at all. The card ships with a DOS driver that makes it visible at A=220, I=5, D=1, H=5, P=330
You might try *changing* or *adding* the settings to your CONFIG.SYS file that I posted in the reply to "Trouble with SB PnP AWE32" (previous message). Change the settings for the DMA and Port listings to conform with the requirements of your card. You'd need to be sure that IRQ 10 was available to use.
One thing about the SB cards under OS/2: they can only handle one sound source at a time. If you have the OS/2 system sounds "on" the DOS and WinOS/2 programs will be unable to access the sound card. I generally have the OS/2 system sounds disabled and go into the DOS and Windows programs to configure the sound to "optional" from "required" which OS/2 sets by default. You might see an error message from time to time if the previous WinOS/2 session isn't finished unloading before you start another session (or if an OS/2 program is using the sound card) but unless you are running a program that requires the sound to work you can proceed anyhow. Don't worry about "fixing" anything since this is only an error about the card unable to accept requests from more than one source at a time.
You might also try the OS/2 Super Site Forum http://forum.os2ss.com/forums/get/hardware2.html [link no longer works] Hardware Issues listing. There are some entries there about the PCI sound cards under OS/2.
When you have a solution worked out, please post it here for others to use. That's what this forum is all about.
Russ
#10 - "MOUSE.SYS after AWE64-DeviceDriver!"
Hi!
My AWE64 VALUE is only running when the MOUSE.SYS-Driver will be loaded AFTER the AWE-DeviceDriver.
If you have any problems, test it and put the MOUSE.SYS-Driver behind the AWE-Driver!
I am using a Logitech BusMouse and the SB AWE 64 Value.
Greetings
Jogi
#11 - "Finally Got AWE64 PnP Working"
After trying for a week (off & on) to get sound on OS/2 Warp 4 following all the advise on this page and constantly coming to a dead end. I was playing around with the line in the config.sys and I found if you just have the following line:
DEVICE=C:\SBOS2\SBAWED2.SYS
that's all nothing else the driver loads it displays the PnP info on startup and I finally have sound.
#12 - "Microphone in Warp 4 (AWE64)"
I can't get the microphone to work well. the drivers are functioning okay, except for the microphone, which sounds distorted. Is there a fix for the microphone? what file operates the mic? and is there a way to fix that?
#13 - "Re: Finally Got AWE64 PnP Working"
as a follow on, Russ sent me an email as to where this line is in my config.sys, it is on line 10, the first 10 lines are as follows:
SET COPYFROMFLOPPY=1
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:C
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,WARPCENTER
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
DEVICE=C:\SBOS2\SBAWED2.SYS
#14 - "Help with SB AWE64 settings????"
Can anyone help me?? I recently purchased the AWE64 Value sound card. Installation appeared to go normally, as the PnP worked fine, or so I thought. The problem is, now everything that comes through the speakers has a HEAVY reverb effect. (it sounds like it's coming from the bottom of a well!!) I've tried everything I can think of to reduce (or eliminate) the reverb effects, but to no avail. This is really just an annoyance, as the sound is working, but I'd really appreciate ANY help that anyone could suggest to correct this problem. Thank you.
P.S. System is a 233 AMD/K6, running with Windows 95.
#15 - "Worked after OS/2 reinstall"
System: AWE64 PnP, CYRIX P300
I tried as per instructions on an existing system. AWE32 PnP install went ok. When attempting to install the AWE64 files I got "failed to uodate mmpn2.ini" error. Did a fresh install with format. Applied FP10 which I already had prepared using Quick Fix. Install of AWE64 ran clean. Install included /Q and I added /P. I have sound out and mic in. I then removed everything after SBAWED2.SYS. I still have sound and mic. Thank you Ray
#16 - "SB 64 PCI"
Hi !
Shortly I got an Soundblaster 64 PCI. Unfortunately there are no drivers for this card :-((( How can I make the card (i.e., drivers for older sound cards) run in OS/2 Warp 4 (FP 10)
Thank you !
Christian.
#17 - "3F8,OS/2,& AWE64"
Having obtained the "Brazil Pak" courtesy of Mr Gaetano, I was extremely pleased to finally enjoy my SB32 pnp with all the utilitys. I went out a purchased an AWE 64 value card, but could not get it to work until after first "REM"ing out com.sys or moving com.sys to after the SBAWED2 driver.
Research indicated that others have experianced problems similar if com.sys loaded prior to the audio driver, and following the experiances of others got the AWE 64 working fine, but my 3 week old 3com/USR v.90 pnp "only" modem became dysfunctional.
This is a pretty heavy trade off, so I experimented a bit and found that in addition to "REM" ing out the COM.SYS line, or moving it to after the SBAWED2 driver, I could also get the SBAWED2 driver to work if I merely specified a non standard address for com1 i.e., (1,160,4) (2,2F8,3) worked perfectly for liberating the SBAWED2 driver, but no matter how I tried to configure the modem as com1 or com2, it just would not work. after 3 weeks of trying, the old SB32 pnp modem is back in and working properly, but of course now I get error messages every time I launch a WIN-OS/2 session about not having enough sound card memory.
I'd like to put the AWE64 back in service, but not at the expense of my net connection.
Any suggestions?
Random observations: (A) the AWE64 has a modem connection port for voice modems that I am not using, is this possibly causing a conflict for resourses reserved? (B) the AWE64 value has no IDE connector, and I have never had an IDE device other than the IDE connector on the SB32 pnp card which was never connected to anything, in this all SCSI machine, yet RM VIEW indicates that a "CT" device has registered IRQ 10 as a resource. By coincidence, I have discovered that the soundblaster IDE driver (which I have never loaded to my knowledge) functions at 3F0. Not knowing how the "Brazil Pak" was assembled, is it possible that Gaetano either included portions of the IDE driver by accident, or in a "clever port to OS/2" may have sucked up portions of a Winxx driver that included referance to the IDE driver.
There seems to be a 'Helen' out there who is extremely adept at resolving many of these problems.
Nothing would make me happier than for her, or anyone else to show me where I've blundered.
So, to 'Helen' or any of you 'Helen' types, I say "En Gaurde!!"
This one has me a bit puzzled
#18 - "Re: SB 64 PCI"
Hi Christian, did you get any answer for your problem with SB64 PCI? Today i got a SB64PCI to and now i have the same problem like you. Please, can you help me? With hopefull gretings from germany!
Martin
> Hi !
>
> Shortly I got an Soundblaster 64 PCI. Unfortunately there
> are no drivers for this card :-(((
> How can I make the card (i.e., drivers for older sound cards) run in OS/2 Warp 4 (FP 10)
>
> Thank you !
>
> Christian.
#19 - "Has anyone succeeded in getting a PCI Sound Card to work in OS/2?"
There are a number of people that are asking for help with getting PCI sound cards to run under OS/2. I don't have such a card and am unable to help them at this point, although I am trying to find out the differences in the drivers that ship with them.
Has anyone managed to get one to run under OS/2? If so, let me know the proceedure and I will post it here or on the Awe64 OS/2 Page, giving you full credit.
Thanks to all that support others by replying to the requests for help on this newsgroup! :-)
Russ
#20 - "No sound after suspend"
My SB PnP installed and works without a problem. However, after the computer comes out of suspend mode, there's no sound until I reboot the machine (reinitialize the board, I'm guessing). Any ideas.
#21 - "Microphone in Warp 4"
Well, I would ask to all of you how did you manage to use de VT dictation program (OS/2 Warp 4) using an AWE64.
With less lucky than the upper message, I can't get any kind of sound recorded with my microphone (the original that cames with W4).
I wonder if there's a script or a config file that has to be modified to set the microphone to "on" from the begining of the OS/2 Session.
Thanks in advance.
#22 - "Re: Microphone in Warp 4"
> I wonder if there's a script or a config file that has to be modified to set the microphone to "on" from the begining of the OS/2 Session.
I apologise if any of you are thinking about this problem.
This silly guy that's replying his own message didn't try to put the power adaptor of the Andrea's microphone on its correct position (I had to press it in a dangerous way in order to join the two parts completely).
Well, some good news I had to add is that I tried too the sentence from config. sys DEVICE=C:\SBOS2\SBAWED2.SYS (something like these, I didn't memorize it) with no parameters, and my AWE64 PnP was recognized with no problem and everything (now yes, everything!), worked fine.
Thanks for all!.
#23 - "Re: No sound after suspend"
No idea yet! I have the same problem. Let me know, if you should find a way to let the card wake up properly after suspend. - I'll do so, too.
#24 - "Re: Has anyone succeeded in getting a PCI Sound Card to work in OS/2?"
Hi, I have the SB64V PCI and I have installed the ENSONIQ.EXE driver from IBM. This driver is designed for ES1371 chip but my card has the ES1370 as I see in the Creative web site. Now my card plays perfecly (there is no MIDI support in this driver)
I don't know why!
Stefano
#26 - "AWE 64 won't work"
Ok folks. I am confused now.
I followed the instructions, installed AWE32 driveres for my awe64 and rebooted. Didn't load. Ok, we were expecting that. Then I run the update. It runs, swaps out the drivers. Reboot, still doesn't load. So I add the /G to the device= line. Now it doesn't find the card period, so I rewrite the line as stated on the previous page (device=c:\sbos2\spawed2.sys /a:220 /i:5 /h:5 /m:330 …) Now the system loads ok, says configuring PnP card w/ config.sys settings. Cool. Boots up, and nothing. I still cannot play sounds, movies don't open. Is it a driver issue? Or do I need to remove MMPM/2 and reinstall it and the driver? Which is it? I also tried using the Awe control pannel that comes w/ the beta drivers. It says it cann't open the AWE32 physical device driver.
Anyone got any ideas?
Thanks!
#27 - "Re: SB 64 PCI"
> Hi Christian,
> did you get any answer for your problem with SB64 PCI? Today i got a SB64PCI to and now i have the same problem like you. Please, can you help me? With hopefull gretings from germany!
>
> Martin
Hi Martin, I have the SB64V PCI and i have installed the ENSONIQ.EXE driver from IBM. This driver is designed for ES1371 chip but it works correcty and now may card plays!!! There is no support for MIDI :-(((
Bye
Stefano
#28 - "Re: AWE 64 won't work"
Are you using a PS/2 mouse? Do COM and VCOM appear after SBAWED2.SYS on CONFIG.SYS?
What about trying SIO drivers?
You can find then on hobbes, or ask ftpsearch for SIO160D.ZIP
Hope this works.
Write us otherways!
#29 - "Clipped wav files"
I have an AWE64pnp value and was wondering, has anyone had the situation where wav files are clipped, they seem to play at the correct volume but they are all shortened to under a second of play. Also, the system will lock under certain circumstances, ie scrolling in netscape when the error wav is played. I've tried all of the fixes on any of the awe 64 web pages that I have found but I don't recall anyone addr the issue of clipping, any help would be greatly appreciated, Brad
#32 - "Wave and MIDI driver won't load in WIN-OS/2 - DMA buffer allocation problem"
Hi,
I have successfuly installed the drivers for my AWE64 PnP card and they work OK under OS/2. But when I start a WIN-OS/2 session I get the following message: "Sound Blaster 16 Error DMA buffer allocation problem. The Wave and MIDI driver is not enabled"
I use the following line in the config.sys file: Device=F:\MMOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:8 /M:300 /N:SBAUD1$ /G
The system.ini entries are the ones suggested by "helent" on the VOICE website.
Any idea anyone? Thanks in advance.
Regards Jeno
#33 - "Ensoniq PCI Driver Location"
> Hi, I have the SB64V PCI and I have installed the ENSONIQ.EXE driver from IBM.
This driver is designed for
> ES1371 chip but my card has the ES1370 as I see in the
> Creative web site.
> Now my card plays perfecly (there is no MIDI support in this driver)
The ENSONIQ.EXE file is found on the OS/2 Device Drivers On-Line Page [this site is no longer available] under the Multimedia Audio section. Look for Ensoniq Corporporation on this page for the file.
Russ
#34 - "Re: Wave and MIDI driver won't load in WIN-OS/2 - DMA buffer allocation problem"
Hi, Jeno,
Do you have the OS/2 System Sounds enabled (the box checked for "Enable system sounds")? This box is in the Sound icon properties in the System Setup folder for Warp 4.
The SB cards are unable to work with more than one sound source at a time. In order to get Win-OS/2 sessions with sound on my AWE32 I had to disable (uncheck) this box.
I also see a similar error when trying to start another (separate) Win-OS/2 session when one is already loaded.
Russ
#35 - "Any device driver programers out there?"
Creative has an Open Source page that is aimed at the Linux market, but if someone is able to use the resources there to create an OS/2 driver you could make a lot of folks happy!
The page is located at http://opensource.creative.com/ [information no longer there]. If you are interested and the page has useful code to work with, let us know and others may join the project.
#36 - "Anyone have the audio software for SB 32 PNP?"
Hi, I just got a used Sound Blaster 32 PNP (not AWE) Sound card without the software that came with it…Does anyone happen to have the Audio Software and Wavesynth software that came with it?…or where i can find it?…Already went to creative labs…but they dont have the original program, only an update…uhg. Thanks, Ed
#37 - "SoundBlaster Live! OS/2 Beta drivers available"
Thanks to Jan Magne who located this driver. More information is available on WarpCast.
A beta OS/2 driver for the Creative Labs SoundBlaster Live! soundcard has been ported from the Linux audio drivers.
The features include:
- Up to 32 simultaneous wave playback streams
- One record stream
- Full duplex
- Support for the IOCTL90 mixer interface
- RTMIDI playback & recording (not yet implemented in this release)
Full source code (GNU license) available at the Netlabs CVS server:
- [email protected]:d:/netlabs.src/sbliveos2
- Login as 'guest' with password 'readonly'
This driver is tested with Warp 4 and Warp Server for E-Business only. It is not tested with Warp 3.
Download at http://www.xs4all.nl/~sandervl/sbliveos2.zip [link no longer works.]
Note: Beta software may not be stable and you should exercise caution when installing it on a production machine. However, Jan reported that this driver worked fine.
#38 - "AWE64 background hiss problem"
When I use my AWE64 there is a background hiss with digial noises which makes proffessional recording impossible due to poor quality. Does anyone know how to solve this?
#39 - "Sound Blaster CD help"
I realise this is the wrong topic for this specific question, but I'm not sure where else to ask.
I'm trying to install OS/2 on my old 486, however, the CD drive is an old Panasonic which plugs into my old Creative Labs Sound Blaster card, and the installation floppy disks won't allow me to access the CD drive to read off the CD. So I'm trying to get a driver that can be loaded from the floppy during the installation process to enable the install program to read the CD drive.
It's most frustrating.
Could someone email me at and offer a suggestion or two? I haven't been able to find the appropriate driver yet.
Thanks.
Douglas.
#40 - "Slow Mp3s? Hows that possible?"
I have a 600mh computer with 64 megs RAM… It has an Audio pci 64v soundblaster card. When I attempt to play MP3s, the song slows WAY down about 2/3 of the way in…
Once the MP3 slows down, its stays constant. ( Its SO slow that you cant understand a thing) I have tried with the Napster and Windows player with the same results. It played all the way thru ONCE. Funny thing is…. once it slows down, moving the bar slide to the left (to re start the song from the beginning) results in a slow song from the very beginning. However, if I re start the song from the PLAY button (on Napster or Windows player) it will play fine till it gets about 3/4 of the way into the song, then slows down again. I'm at my wits end with this and appreciate any further help. Sky
#41 - "Re: Slow Mp3s? Hows that possible?"
Just found out that my friends computer wont play Midis or Wavs all the way thru either. They play fine about 3/4 of the way then slow down. Installed new drivers in the sound card…no difference. *sigh
#42 - "MIDI"
Is there a way to adjust the MIDI volume in OS/2? My sound level is about a 1/3rd of what the other devices are.
PC 350 200Mhz Warp4 Fixpack 11
#43 - "Awe64 for DOS Games"
I boguth my awe64 long time ago and it works great, though just a few days ago y found my old games and wanteed to play. Ya know remeber those old good times, i thought they would sound grat with my soud card, i was expecting a lot. My surprise was that after i install all the games and chageing configurtation and ports i still was unable to make them sound, The sound just won't work.
Does anybody knows how to configure my card the games or whatever need to be configure to ,make them work right.
thx