It connects to pin 5 of the PAL/GAL chip.

moved to Sound

Hi,

It is a really Old Post, but do you know where is the Jumper to disable the Adlib Port on the GUS Classic 3.4 ?
It conflict with the OPL2 in my Atari PC2 😀

FreddyV wrote:

It is a really Old Post, but do you know where is the Jumper to disable the Adlib Port on the GUS Classic 3.4 ?

Nowhere.
Such a jumper only exists on GUS ACE.

I did some tests with a GUS MAX 2.1 and a separate FM sound card, and as long as the GUS was kept initialised with SBOS disabled, FM was fine. Issues arose when the GUS wasn't initialised. Didn't test with a GUS classic, so cannot confirm the same behaviour.

Grzyb wrote:

Nowhere.
Such a jumper only exists on GUS ACE.

Ok,
If I start my player (That does init the GUS) I think it may work, I will test again and tell you.
Then, I will compile a small GUs Init Software (For 8086)

Yes, because I use the GUS on a 8088 Computer 😀

Hi,

It does not work. I succeeded to have Adlib in LOOM one time, I don't remember how.
Does anybody know the register to initialize to remove the conflict with the Adlib card ?

Edit: UltrInit is working on a 8088, so if I run it, The Adlib is detected.

FreddyV

ULTRINIT.EXE disables Adlib ports, but I guess it doesn't run on 8088 ?
So, probably all you can do is to debug ULTRINIT.EXE and make your own version for 8088.

j^aws wrote:

I did some tests with a GUS MAX 2.1 and a separate FM sound card, and as long as the GUS was kept initialised with SBOS disabled, FM was fine. Issues arose when the GUS wasn't initialised. Didn't test with a GUS classic, so cannot confirm the same behaviour.

I'm convinced at this point that Ultrinit disables the Adlib port, then does a scan on the machine for a writable Adlib port. If it doesn't find one, the GUS MAX Adlib emulation is enabled. If the Adlib port is discovered, then Ultrinit will not enable Adlib functions on the MAX. Once you enable SBOS and full Sound Blaster emulation, Adlib functionality is likely forced as a result of the Sound Blaster being an Adlib-compatible device. My Sound blaster Pro 2.0 and GUS MAX compatibility issues all disappeared when I used Ultrinit as well. At one point I was able to use a modified Windows Sound Source driver someone hacked to point at the GUS MAX, but then I changed a setting and added a Voodoo 1 and some sort of conflict appeared. Now, if I could enable the WSS support while having the GUS MAX on DMA 3/IRQ 5 and still retaining the DOS-window-in-98 support for GUS games, I'd think my sound card options would be perfectly set. That's a bit out of the scope of the thread and enters a whole world of "creating problems for yourself that add little, if any, benefit."

MrSmiley381 wrote:

j^aws wrote:

I did some tests with a GUS MAX 2.1 and a separate FM sound card, and as long as the GUS was kept initialised with SBOS disabled, FM was fine. Issues arose when the GUS wasn't initialised. Didn't test with a GUS classic, so cannot confirm the same behaviour.

I'm convinced at this point that Ultrinit disables the Adlib port, then does a scan on the machine for a writable Adlib port. If it doesn't find one, the GUS MAX Adlib emulation is enabled. If the Adlib port is discovered, then Ultrinit will not enable Adlib functions on the MAX. Once you enable SBOS and full Sound Blaster emulation, Adlib functionality is likely forced as a result of the Sound Blaster being an Adlib-compatible device. My Sound blaster Pro 2.0 and GUS MAX compatibility issues all disappeared when I used Ultrinit as well. At one point I was able to use a modified Windows Sound Source driver someone hacked to point at the GUS MAX, but then I changed a setting and added a Voodoo 1 and some sort of conflict appeared. Now, if I could enable the WSS support while having the GUS MAX on DMA 3/IRQ 5 and still retaining the DOS-window-in-98 support for GUS games, I'd think my sound card options would be perfectly set. That's a bit out of the scope of the thread and enters a whole world of "creating problems for yourself that add little, if any, benefit."

Glad to hear another success story. I thought I was the only one thinking you didn't need a GUS ACE to run FM in the same PC. BTW, do you still have the hacked WSS driver for the GUS MAX? An upload would be great for future testing.

Ultrinit is working on my 8086 and disable the adlib port.

it is working like this

j^aws wrote:

Glad to hear another success story. I thought I was the only one thinking you didn't need a GUS ACE to run FM in the same PC. BTW, do you still have the hacked WSS driver for the GUS MAX? An upload would be great for future testing.

From Toogam.com:

Toogam.com wrote:

The "GUS MAX CoDec driver "hack" v0.2 for Windows 95/98":
GUS MAX Win98 driver 0.2 (found from MAZ GUS PnP page) is byte-for-byte identical to the file GUSMAX Win95/98 driver v0.2, the latter of which was renamed according to archive of old Utopia Sound Division page found from a link from a downed page referenced in the included README.TXT. Locally the file is zipped as gusm9x02.zip.

The contents of the ReadMe in the event someone stumbles across this post and wants some info on the driver before downloading:

Roel/Utopia Sound Division wrote:

GUS MAX CoDec driver "hack" v0.2 for Windows 95/98 -------------------------------------------------- […]
Show full quote

GUS MAX CoDec driver "hack" v0.2 for Windows 95/98
--------------------------------------------------

This is small hack which uses a Windows Sound System driver which comes
with Windows 98 for getting WAVE out- and input and even more important,
DirectSound support on GUS MAX cards. The hack is a combination of
version 2.31 of ultrinit (used to initialise your GUS MAX) and some minor
changes in a setup file. I've been unable to verify this driver on GUS MAX
rev 1.7/1.8 cards which have a slightly different CoDec than my rev 2.1 GUS
MAX card so I can't guarantee that it'll work on these cards.

So what does this "hack" give me ?
----------------------------------

This hack gives you excellent half-duplex (you cannot record and playback
samples at the same time) wave playback and recording support on your
GUS MAX card. Additionally the driver will emulate the digital (wave) part
of a SoundBlaster v1.0 card when you are in a DOS box which can be usefull
for playing some old games. Of course you can also use your joystick if
you install the "gameport joystick" device (you can only do this if you
pre-initialise your GUS MAX before starting windows with the switch -ej)
You should note though, that there is no MIDI in/out or GF1 support when
you're running Windows 95/98 while using this driver (if you have manually
added the GUS MIDI port driver to your system.ini file you'll have to
remove it !). So if you want to run a program with real GUS support (like
FastTracker II, Death Rally, etc.) you'll have to leave Windows and go to
"real DOS" for using your GUS MAX card. In other words, this is a driver
for "gamers" and not for musicians right now. I'm planning to add
full-duplex (simultaneous recording and playback of samples) and GF1/MIDI
support but this will take considerable more time. Since I've got more
projects right now and I normally don't use the GUS MAX card I can't say
whether a more advanced driver/hack will follow soon.

Below is a small list of programs/games with a description how it performed
with this driver:

WinAMP MP3 playback using:
- WaveMapper : Excellent
- DirectSound : Excellent
ActiveMovie MPEG playback : Excellent
StarCraft : Excellent
Quake 2 : Excellent !! 😉
Small note: change ' set s_primary "1" ' to
' set s_primary "0" ' in
the config.cfg file.
Need For Speed 3 : Excellent
Halflife : Sometimes garbage sound. Didn't investigate
further yet.
Incoming : Slightly breaking up sound and sometimes
loud short garbage sound..
TombRaider 3 : Terrible
Age of Empires : Excellent
Settlers 3 : Excellent
Curse of Monkey Island : Excellent
Total Annihilation : Good. Sometimes a short burst of garbage sound.

As you can see, it's not perfect but quite an improvement.

How to install
--------------

(The below assumes some knowledge about editing text-files and soundcard
basics/DMA/IRQ basics.)

First, you'll have to make sure that there is nothing left in your Windows
installation of the previous GUS MAX driver (the best way is to re-install
Windows 98 is don't know how to do this). Now copy the files in the archive
to C:\GUSMAX (or another directory to your choice).

Second, you have to initialise your GUS MAX card before entering Windows
95/98. The best way to do this is by adding a small part to your autoexec.bat
file in the root directory of your 'C:' drive (e.g. with the help of EDIT or
NOTEPAD). When doing this you need to use 'ultrinit v2.31' which is included
in this package. Below is an example of how you need to add the
initialisation part to your autoexec.bat:

- add the below -
rem Windows 98 GUS MAX driver initialisation part
set ultrasnd=220,1,1,11,7
set ultra16=36c,0,0,1,11
C:\gusmax\ultrinit -ej
rem End of initialisation part
- add the above -

So what does the above mean. Well 'ultrasnd' and 'ultra16' are environment
settings which the ultrinit program uses to configure your ultrasound card.
Let's start with 'ultrasnd'. The values used mean the following:

set ultrasnd=base, dma1, dma2, irq1, irq2
- base = the base adress of your GUS card (e.g. 220, 240, 260)
- dma1 = the playback DMA channel which is also used for uploading samples
to your card. I'd suggest to chose '1' here which will always work
, unless used by another card. If you plan to do some "full duplex"
things in DOS you need to use another value than '1'.
- dma2 = the recording DMA channel. This DMA has to be the same as the
CoDec (the chip which is used to playback samples in Windows 98)
and has to be '1' !!! If you've got another card at DMA channel 1
put it to 3, 5 or 7 (or others if available) !
- irq1 = The irq used by the GUS for native GUS applications. This irq has to
be the same as the CoDec irq !! If not it won't work !
- irq2 = Used for things like SoundBlaster emulation. If you don't need
SoundBlaster emulation use the same irq as you used for irq1

Now for the 'ultra16' (values represent use with the current version of
ultrinit) :

set ultrasnd=codecbase, cdrombase, nothing, playback/recording dma, irq
- codecbase = the base adress of the CoDec on your GUS MAX. This has to be
one of the following values (32c, 33c, 34c, 35c, 36c)
- cdrombase = the base adress of the cdrom controller on your card. normally
you won't use it and thus simply set it to '0'
- nothing = set to '0'.. In full duplex mode (v1.0 of this driver) this will
be the playback DMA channel while the other dma entry will be
for recording.
- playba... = dma channel used for playback and recording of sound. this HAS
to be '1'
- irq = irq used by the CoDec. This has to be the same value as irq1
in the 'ultrasnd' environment setting !

(The below assumes an english version of Windows 98. In other versions of
Windows the procedure might be slightly different)

* If you have done this right, reboot your PC and start windows.
* Go to the 'Control Panel'
* Go to 'Add New Hardware'
* Select: next (twice)
* Select: No, the device isn't in my list + next
* Select: No, I want to select the hardware from a list + next
* Select: Sound, Video and game controllers + next
* Select: Have Disk
* Refer to the directory you've placed the files in this archive, select
the directory matching your version of Windows (Win95 or Win98) and
press 'OK'.

After installing you might have to enter the correct values in the 'Gravis
UltraSound MAX CoDec' driver under the device manager (I assume you know how
to do this). Now restart your computer and Windows 98 will detect
the 'Gravis UltraSound MAX SB v1.0 Emulation" device and install it for you.

Now you can adjust the mixer settings if you like and fine-tune the switches
used with 'ultrinit' in your autoexec.bat (like muting the mic/line/cd input
as default or for that sake for disabling the gameport. for more info on
the use of ultrinit enter 'ultrinit -?').

Now HAVE FUN !

Hey this doesn't work.. Help me !!
----------------------------------
I don't have much free time and thus would prefer that you would ask these
kind of questions in the GUS Digest where there are many GUS users that might
be able to help you. I also read the messages posted there and reply when
I have the time to do so. Below is some info regarding the GUS digest:

The GUS Digest is a "daily" mailing list for which GUS users. In it you
can ask questions to other GUS users.

To (un)subscribe or get help mail to:
gus-general-digest-request@mail.GAIANET.NET

To post to tomorrow's digest mail to:
gus-general@mail.GAIANET.NET

To contact a human (last resort) mail to:
gus-general-digest-owner@mail.GAIANET.NET

If you want to send "thank you messages" or "money" you are free to email me
at rdewit@a1.nl though 😀

All I can say now is that I hope that this hack/driver makes your old GUS MAX
card (with extremely clean sound !) to some use in Windows again.

---
Roel / Utopia Sound Division
http://utopia.a1.nl

This ReadMe also explains my issues above where GUS support in DOS windows within 98 were acting weird. The Windows driver probably traps a certain port that does things like break music in DOOM and break sound effects in Pinball Fantasies. Guess I should have read the ReadMe in its entirety 😀

I also detailed my original experiences with my configuration here, which was before I tried using the hacked WSS driver. All of my issues stemmed from me using the Windows 95 driver for the GUS Max in 98SE. Trying to load and unload SBOS with the GUS Max in Windows likely locked the machine due to resource conflicts and all sorts of other configuration issues. The 95 driver has no sound mixer available and would often lock the machine after horrible crackling playing Starcraft. The WSS driver works just fine with Starcraft and Diablo with no loss of audio quality. I thought the GUS Max sounded "better" than the Sound Blaster Pro, but that was a plain listening test and nothing more. If someone zipped up a pack of tools and instructions on how to objectively measure the results, I'll gladly spare some time investigating.

Sorry about doing a big data dump here, but I'm going to argue that it was all mildly relevant and might save someone some headaches in the future.