NeoG_ wrote on 2026-10-03, 22:24:

90% is a lot better than random, i'll check it out later today with those ISO images

thanks a lot, any test or help just tell me. Yes, always fail, more soon or not, but always fail, or show latest iso image structure or disc empty, but ALWAYS fail, no chance i can enjoy one day without this problem jeje

And thanks but dont hurry, i just a hobby!

What about PicoGUS 2.0 on a Unisys CWD 486 4002 VIA VT82C496G (Pluto).
The chipset is not mentioned in the compatibility-list. There is only a short info in this thread that there might be problems.

Thx Doc

Hello everybody,

I ask forgiveness to write my question (maybe) again, as I cannot find my old posting in the search.
Currently I have a PicoGUS 2.0 with latest firmware 3.2.1 and a Wavetable Pi with 32GB sdcard on it.
I have put all pictures in a handy PDF:
1. PicoGUS with Wavetable Pi, mine is jumpered at irq 3 and dma 3
2. the directories of the sdcard: firmware, roms, soundfonts
3. I will add below my autoexec.bat where the PicoGUS behaves as General Midi card

My question is: how can I get Monkey Island 1 playing MT32 music on the PicoGUS with the Wavetable Pi?

Although everything is prepared with the proper MT32 files I don't hear any sound, maybe I made sth wrong?

Please watch the PDF and help me with the correct configuration.

Autoexec.bat:

1
2:PICOGUS
3ECHO 1) Gravis Ultrasound (GUS)
4ECHO 2) MPU401 GM/GS/MT-32
5ECHO 3) Sound Blaster 2.0
6ECHO 4) AdLib Gold
7ECHO 5) Tandy 
8ECHO 6) CMS
9CHOICE /C:123456 /N "Waehle den Modus fuer PicoGUS: "
10
11IF ERRORLEVEL 6 GOTO PG_CMS
12IF ERRORLEVEL 5 GOTO PG_TANDY
13IF ERRORLEVEL 4 GOTO PG_ADLIB 
14IF ERRORLEVEL 3 GOTO PG_SB 
15IF ERRORLEVEL 2 GOTO PG_MPU 
16IF ERRORLEVEL 1 GOTO PG_GUS
17
18:PG_GUS
19C:\DOS\UNISOUND.COM /C1 /D
20C:\DOS\UNISOUND.COM /C2 /D
21SET SOUND=C:\ULTRASND
22SET ULTRADIR=C:\ULTRASND
23SET ULTRASND=240,3,3,3,3
24SET MIDI=ULTRASND
25SET BLASTER=A240 I3 D3 P300 T4
26LH C:\ULTRASND\PGUSINIT.EXE /GUSPORT 240 /MODE GUS /SAVE
27GOTO BOOTLABELS
28
29:PG_MPU
30C:\DOS\UNISOUND.COM /C1 /D
31C:\DOS\UNISOUND.COM /C2 /D
32SET SOUND=C:\ULTRASND
33SET ULTRADIR=C:\ULTRASND
34SET ULTRASND=240,3,3,3,3
35SET MIDI=ULTRASND
36SET BLASTER=A240 I3 D3 P330 T4 
37LH C:\ULTRASND\PGUSINIT.EXE /GUSPORT 240 /MODE MPU /MPUPORT 330 /MPUDELAY 1 /MPUFAKE 0 
38GOTO BOOTLABELS
39

eliot_new wrote on 2026-10-11, 09:33:

My question is: how can I get Monkey Island 1 playing MT32 music on the PicoGUS with the Wavetable Pi?

Although everything is prepared with the proper MT32 files I don't hear any sound, maybe I made sth wrong?

Is the PicoGUS red light blinking when Monkey Island is attempting to play MIDI data? The red light blinking means the MIDI data is getting as far as the MPU401 interface on the PicoGUS

One thing that may be gumming up the works is that the pgusinit cannot accept mode change parameters (E.G. /mode GUS) and configuration commands (E.G. /gusport 240) in the same call, those need to be separated onto 2 lines unless you save the parameters to flash (in which case you don't need to set the configuration again at all, only the mode).

pgusinit also only accepts parameters for the current mode, so having GUS configuration commands when in MPU mode doesn't do anything.

NeoG_ wrote on 2026-10-11, 09:49:

Is the PicoGUS red light blinking when Monkey Island is attempting to play MIDI data? The red light blinking means the MIDI data […]
Show full quote

eliot_new wrote on 2026-10-11, 09:33:

My question is: how can I get Monkey Island 1 playing MT32 music on the PicoGUS with the Wavetable Pi?

Although everything is prepared with the proper MT32 files I don't hear any sound, maybe I made sth wrong?

Is the PicoGUS red light blinking when Monkey Island is attempting to play MIDI data? The red light blinking means the MIDI data is getting as far as the MPU401 interface on the PicoGUS

One thing that may be gumming up the works is that the pgusinit cannot accept mode change parameters (E.G. /mode GUS) and configuration commands (E.G. /gusport 240) in the same call, those need to be separated onto 2 lines unless you save the parameters to flash (in which case you don't need to set the configuration again at all, only the mode).

pgusinit also only accepts parameters for the current mode, so having GUS configuration commands when in MPU mode doesn't do anything.

I wil try and tell you.

But another question: do I really need to start the PicoGUS in GM mode?
Because maybe there is some error in the process:

1. PicoGUS can make general midi without Wavetable Pi, right?
=> this means, that it should deliver GM sound in e.g. Doom1 without the Wavetable Pi?

2. PicoGUS can be in SB Mode, emulating a SBPro 2.0 oder SB 2.0 Card with wavetable header?
=> maybe this is the right mode for the subsequent Wavetable Pi?

3. Year ago I bought the PicoGUS 2.0 in bundle with the Wavetable Pi, believing that both were produced by User polpo, but maybe the are completely independent and it was only the seller from Portugal who decided to bundle them?

Here I read, that the Wavetable Pi needs an extra .exe file in the autoexec.bat:
https://github.com/gmcn42/mt32-pi-control/blo … bin/MT32-PI.TXT

1MT32-PI.EXE accepts the following UNIX-style parameters: (MT32-PI.EXE is independent from PGUSINIT.exe?)
2
3USAGE: MT32-PI.EXE [OPTIONS]
4OPTIONS:
5  -h/--help: Print this info.
6  -v/--verbose: Be verbose about what is going on.
7  -r/--reboot: Reboot the Pi. Will block for a few secs to give it time.
8  -p [ADDR]: Set the port address of the MPU401 interface. Default: 330.
9  -m/--mt32: Switch mt32-pi to MT-32 mode.
10  -g/--fluidsynth: Switch mt32-pi to FluidSynth mode.
11  -b/--romset [old, new, cm32l]: Switch MT-32 romset.
12  -s/--soundfont [NUMBER]: Set FluidSynth SoundFont.
13  -S/--mt32-rstereo [0, 1]: Enable/disable MT-32 reversed stereo.
14  --mt32-reset: Send an MT-32 reset SysEx message.
15  --gm-reset: Send a GM reset SysEx message.
16  --gs-reset: Send a GS reset SysEx message.
17  -t/--mt32-txt "Some text": Send an MT-32 text display SysEx.
18  -T/--sc55-txt "Some text": Send an SC-55 text display SysEx.
19  -P/--sc55-bmp FILE.BMP: Display a 16x16 1bpp BMP on the screen. (SC-55 SysEx)
20  -X/--sc55-btxt "SomeText": Display a string on the screen as a Bitmap. (SC-55)
21  -N/--negative: Reverse image color. Use with '-P/--sc55-bmp'.
22  -M/--midi "C0 01 C0 DE": Send a list of custom MIDI bytes.
23  -Y/--syx file.syx : Send the contents of a SYX-file.

edit: although many of you dislike AI, I have gotten this very usefull information, as I had plugged in my earphones into the PicoGUS not knowing, that I should have connected them wo the Wavetable Pi:

"and you can tap into them via the Wavetable Pi's audio output (or via loopback)"

Ok, that makes sense, but it seems not that conformatble as the Serdar Wavetable board, that (according to advertising) you can plug onto a SB Pro 2.0 card like Terratec 929 and then use their line-out to here GM music, right?

eliot_new wrote on 2026-10-11, 16:30:

I wil try and tell you. […]
Show full quote

NeoG_ wrote on 2026-10-11, 09:49:

Is the PicoGUS red light blinking when Monkey Island is attempting to play MIDI data? The red light blinking means the MIDI data […]
Show full quote

eliot_new wrote on 2026-10-11, 09:33:

My question is: how can I get Monkey Island 1 playing MT32 music on the PicoGUS with the Wavetable Pi?

Although everything is prepared with the proper MT32 files I don't hear any sound, maybe I made sth wrong?

Is the PicoGUS red light blinking when Monkey Island is attempting to play MIDI data? The red light blinking means the MIDI data is getting as far as the MPU401 interface on the PicoGUS

One thing that may be gumming up the works is that the pgusinit cannot accept mode change parameters (E.G. /mode GUS) and configuration commands (E.G. /gusport 240) in the same call, those need to be separated onto 2 lines unless you save the parameters to flash (in which case you don't need to set the configuration again at all, only the mode).

pgusinit also only accepts parameters for the current mode, so having GUS configuration commands when in MPU mode doesn't do anything.

I wil try and tell you.

But another question: do I really need to start the PicoGUS in GM mode?
Because maybe there is some error in the process:

1. PicoGUS can make general midi without Wavetable Pi, right?
=> this means, that it should deliver GM sound in e.g. Doom1 without the Wavetable Pi?

2. PicoGUS can be in SB Mode, emulating a SBPro 2.0 oder SB 2.0 Card with wavetable header?
=> maybe this is the right mode for the subsequent Wavetable Pi?

3. Year ago I bought the PicoGUS 2.0 in bundle with the Wavetable Pi, believing that both were produced by User polpo, but maybe the are completely independent and it was only the seller from Portugal who decided to bundle them?

Here I read, that the Wavetable Pi needs an extra .exe file in the autoexec.bat:
https://github.com/gmcn42/mt32-pi-control/blo … bin/MT32-PI.TXT

Copy code to clipboard

1MT32-PI.EXE accepts the following UNIX-style parameters: (MT32-PI.EXE is independent from PGUSINIT.exe?)
2
3USAGE: MT32-PI.EXE [OPTIONS]
4OPTIONS:
5  -h/--help: Print this info.
6  -v/--verbose: Be verbose about what is going on.
7  -r/--reboot: Reboot the Pi. Will block for a few secs to give it time.
8  -p [ADDR]: Set the port address of the MPU401 interface. Default: 330.
9  -m/--mt32: Switch mt32-pi to MT-32 mode.
10  -g/--fluidsynth: Switch mt32-pi to FluidSynth mode.
11  -b/--romset [old, new, cm32l]: Switch MT-32 romset.
12  -s/--soundfont [NUMBER]: Set FluidSynth SoundFont.
13  -S/--mt32-rstereo [0, 1]: Enable/disable MT-32 reversed stereo.
14  --mt32-reset: Send an MT-32 reset SysEx message.
15  --gm-reset: Send a GM reset SysEx message.
16  --gs-reset: Send a GS reset SysEx message.
17  -t/--mt32-txt "Some text": Send an MT-32 text display SysEx.
18  -T/--sc55-txt "Some text": Send an SC-55 text display SysEx.
19  -P/--sc55-bmp FILE.BMP: Display a 16x16 1bpp BMP on the screen. (SC-55 SysEx)
20  -X/--sc55-btxt "SomeText": Display a string on the screen as a Bitmap. (SC-55)
21  -N/--negative: Reverse image color. Use with '-P/--sc55-bmp'.
22  -M/--midi "C0 01 C0 DE": Send a list of custom MIDI bytes.
23  -Y/--syx file.syx : Send the contents of a SYX-file.

edit: although many of you dislike AI, I have gotten this very usefull information, as I had plugged in my earphones into the PicoGUS not knowing, that I should have connected them wo the Wavetable Pi:

"and you can tap into them via the Wavetable Pi's audio output (or via loopback)"

Ok, that makes sense, but it seems not that conformatble as the Serdar Wavetable board, that (according to advertising) you can plug onto a SB Pro 2.0 card like Terratec 929 and then use their line-out to here GM music, right?

Info about WavetablePi can be found here.

There's a 2x3 jumper (J1 and J2) that you need to configure, depending on which output MT32-Pi is configured to use (DAC/I2S or PWM).
Normally if using DAC/I2S, you need to put a jumper cap on 1-2 of both J1 and J2 to be able to get sound.
If the jumper caps are not present or not configured properly you won't hear any output.

eliot_new wrote on 2026-10-11, 16:30:

I wil try and tell you. […]
Show full quote

I wil try and tell you.

But another question: do I really need to start the PicoGUS in GM mode?
Because maybe there is some error in the process:

1. PicoGUS can make general midi without Wavetable Pi, right?
=> this means, that it should deliver GM sound in e.g. Doom1 without the Wavetable Pi?

It cannot, there is no onboard MIDI synthesizer

eliot_new wrote on 2026-10-11, 16:30:

2. PicoGUS can be in SB Mode, emulating a SBPro 2.0 oder SB 2.0 Card with wavetable header?
=> maybe this is the right mode for the subsequent Wavetable Pi?

Yes the wavetable header works in all modes, only the strictest intilligent mode games require full MPU mode. However, it does not affect the compatibility with wavetable cards so if it doesn't work in MPU mode, it also won't work in SB or GUS mode either.

eliot_new wrote on 2026-10-11, 16:30:

3. Year ago I bought the PicoGUS 2.0 in bundle with the Wavetable Pi, believing that both were produced by User polpo, but maybe the are completely independent and it was only the seller from Portugal who decided to bundle them?

Yes the wavetable Pi and PicoGUS are two completely separate projects that were bundled together by the seller

eliot_new wrote on 2026-10-11, 16:30:

Here I read, that the Wavetable Pi needs an extra .exe file in the autoexec.bat:
https://github.com/gmcn42/mt32-pi-control/blo … bin/MT32-PI.TXT

The WavetablePi will produce sound without the mt32-pi control program, however without the front panel controller it is the only way to switch between MT32/GM and different soundfonts

eliot_new wrote on 2026-10-11, 16:30:

Ok, that makes sense, but it seems not that conformatble as the Serdar Wavetable board, that (according to advertising) you can plug onto a SB Pro 2.0 card like Terratec 929 and then use their line-out to here GM music, right?

The sound will be output through the wavetable header and the audio jack at the same time, there is no need for line input cable if the wavetable header is working. But you could do this if you wanted.

Adventures with PicoGUS are continuing! Outside of Windows getting greater and greater results. In Windows...
DirectX sound is working. But only in 8Bit modes. This turned out to be confirmed by Jazz Jackrabbit 2. Which offers direct selection of 16 bit audio or 8 bit audio. Once 8 bit is selected, audio resumes working.
So I've gone into Windows 95 multimedia options, and selected to offer up to 8bit, 44khz audio to applications.
BUT some games were just hardcoded to 16bit audio. Those still don't play.
Not a real problem, as those are better suited to a more recent PC all around.

Geriatric Danmaku wrote on Today, 21:53:

Adventures with PicoGUS are continuing! Outside of Windows getting greater and greater results. In Windows... DirectX sound […]
Show full quote

Adventures with PicoGUS are continuing! Outside of Windows getting greater and greater results. In Windows...
DirectX sound is working. But only in 8Bit modes. This turned out to be confirmed by Jazz Jackrabbit 2. Which offers direct selection of 16 bit audio or 8 bit audio. Once 8 bit is selected, audio resumes working.
So I've gone into Windows 95 multimedia options, and selected to offer up to 8bit, 44khz audio to applications.
BUT some games were just hardcoded to 16bit audio. Those still don't play.
Not a real problem, as those are better suited to a more recent PC all around.

Have you checked in the hardware reousrces for the sound blaster 16 device in windows that the low and high DMA are set to the same value? (If it even lets you do that). Without that, 16-bit sound won't work which is the same as DOS