Kordanor wrote on 2024-08-03, 18:40:

Saw Phils video but I am wondering whether you can then also use a PS/2 Mouse and a PS/2 to USB adapter and use it on this card. That way you would have a somewhat newer but still somewhat period accurate input device.

No. There are two types of PS/2 to USB adapters
- passive, will not work because signal stays PS2 and pee doesnt expect that
- active ones work in opposite direction

all in all PicoGUS could really use another rp2040 on board for more IO to enable more fun stuff like this.

rasz_pl wrote on 2024-08-03, 21:01:

No. There are two types of PS/2 to USB adapters - passive, will not work because signal stays PS2 and pee doesnt expect that - a […]
Show full quote

Kordanor wrote on 2024-08-03, 18:40:

Saw Phils video but I am wondering whether you can then also use a PS/2 Mouse and a PS/2 to USB adapter and use it on this card. That way you would have a somewhat newer but still somewhat period accurate input device.

No. There are two types of PS/2 to USB adapters
- passive, will not work because signal stays PS2 and pee doesnt expect that
- active ones work in opposite direction

all in all PicoGUS could really use another rp2040 on board for more IO to enable more fun stuff like this.

Alright, thanks a lot for the clarification!

Anyone kind enough to reply to my question please?

weedeewee wrote on 2024-05-30, 21:10:

polpo wrote on 2024-05-30, 20:44:

appiah4 wrote on 2024-05-30, 12:23:

I don't think there is a compiled binary of pgusinit for linux, and I don't know if that is possible, but now I'm also curious.. Presumably if the PicoGUS could be initialized under linux then the GUS kernel modules would work..

The card doesn't need to be initialized with pgusinit if it's using the default port of 240h. Linux would be interesting to try out, especially since the Linux Ultra Sound Project drivers are what evolved into ALSA. I remember those drivers being really good back in the 90s on my GUS.

Someone should also try it under OS/2.

I just tested my PicoGUS 2.0 (with the GUS firmware saved to the card) on a Gateway 2000 4DX2 in OS/2 Warp 3. The Manley Drivers initialize the PicoGUS during boot-up, and the drivers work for digital audio. Unfortunately, the drivers do not map MIDI to the PicoGUS's wavetable (that's a known issue with the drivers). On the other hand, the UltiMOD program that comes with the drivers will use the PicoGUS's wavetable during .MOD playback.

The Manley Drivers will work with OS/2 versions as old as 2.0 (with MMPM installed) which would be nice if you don't have a sound card compatible with older versions of OS/2.

Omarkoman wrote on 2024-08-02, 23:56:

wow ! just wow ! […]
Show full quote

zuldan wrote on 2024-07-30, 06:17:

New release! V2.1.0 MPU-401 now available in all modes.

wow ! just wow !

so to clarify, the picogus.uf2 is the firmware that needs to be flashed onto the card? is there a video showing the process how to do it ?

and then use the latest pgusinit.exe to run it after boot and select what mode I want? eg -mode sb for SB compatibility and nothing else to get the wavetable header working as its automatic right away with ALL modes at same time? so can just go to game, choose SB for digital sounds and select General Midi on 330 for music using something like Dreamblaster S2 connected to the header port?

thanks

What you have written is correct.

The latest video from PhilsComputerLab shows the initial flashing of the new picogus.uf2, at https://youtu.be/GiyuoIrxi5U?&t=191.

Then you will be able to use "pgusinit.exe /mode sb" to set SB mode, which now includes MPU (without IRQ) function.

Let us know if you have any questions about the detail of the procedure.

ahyeadude wrote on 2024-08-03, 19:09:

Linoleum wrote on 2024-08-03, 18:23:

ahyeadude wrote on 2024-08-03, 14:23:

Has anyone had any luck getting the PicoGUS to work in GUS mode for Windows 3.11 drivers? I saw some discussion in this thread, but no specific instructions on how to install the driver. I attempted to follow this guide

Guide: How to install Gravis Ultrasound Drivers in Windows 3.11

But, am still getting "Driver Error: Cannot load the Ultra Wave and MIDI Synth driver..." message when trying to add the driver in Windows 3.11.

Yes it works! Check if the SYSTEM.INI has a section for the GUS drivers (outside of the MIDI=, WAV=, MIXER= settings)... If it has, check if the settings are okay (DMA, IRQ, Port, etc).

What steps did you take to install? Also did you use the standard driver pack supplied with PicoGUS? (ultrasnd.zip)

The guide you mentioned points to the solution:
"copy the files from c:\ultrasnd\windows\system to c:\windows\system (only the files from system folder to system folder)"

However, you'll need to add a Windows shortcut to the mixer and create a MIDI MAPPER profile where you select GUS for every channel...

To your question, I believe I took the driver package from VogonsDrivers.com... Most probably the CD V1.2 drivers since it says "Driver V4.11 for DOS and Windows 3.1/3.11".

Like I said before, check the [ultrasnd.drv] entry in SYSTEM.ini... You should be able to change port, irq and dma.

Omarkoman wrote on 2024-08-02, 23:56:

wow ! just wow ! […]
Show full quote

zuldan wrote on 2024-07-30, 06:17:

New release! V2.1.0 MPU-401 now available in all modes.

wow ! just wow !

so to clarify, the picogus.uf2 is the firmware that needs to be flashed onto the card? is there a video showing the process how to do it ?

and then use the latest pgusinit.exe to run it after boot and select what mode I want? eg -mode sb for SB compatibility and nothing else to get the wavetable header working as its automatic right away with ALL modes at same time? so can just go to game, choose SB for digital sounds and select General Midi on 330 for music using something like Dreamblaster S2 connected to the header port?

thanks

Yes, picogus.uf2 is the all in one firmware that needs to be flashed. I don't think I've seen a how-to video for the new firmware, but it's very easy. Instructions are fairly clear on Github: https://github.com/polpo/picogus/blob/v2.0.0/ … sinit/README.md

Once flashed, you will have to use pgusinit to change modes. I don't know if you absolutely have to mention a mpu port everytime with "/mpuport 330", but I do just to be sure. So, "pgusinit /mode sb /mpuport 330".

thank you so much for the replies ! I will have a crack at it now.

Kordanor wrote on 2024-08-03, 21:15:

rasz_pl wrote on 2024-08-03, 21:01:

- passive, will not work because signal stays PS2 and pee doesnt expect that

Alright, thanks a lot for the clarification!

Except I was confidently wrong 🙁 brain fog got me 😀
If the mouse is PS2 but comes with passive PS2 to USB adapter then obviously mouse itself detects and switches to talking USB meaning it should work.
BUT it needs to be a mouse specifically sold as universal with the converter included. I dont remember ever seeing PS2 mice with ps2-usb converters, only USB mice with USB-PS2.

rasz_pl wrote on 2024-08-03, 23:11:

BUT it needs to be a mouse specifically sold as universal with the converter included. I dont remember ever seeing PS2 mice with ps2-usb converters, only USB mice with USB-PS2.

Got one of those PS2 mice with a ps/2-usb converter and they work for example with the PicoMem so it would indeed work with the PicoGUS as well.

successfully upgraded the firmware and got bot SB + MPU401 working, omg this is amazing !

quick video of Monkey Island 1 Talkie on Pocket386 :

https://youtu.be/eHzCKBA3zHk?si=ZMoG4Ej-peODotEr

Also quick video of Sam and Max

https://youtu.be/MnMz3xehkYE?si=BRhrNzTaArQalpsb

Interesting, stock for the PicoGUS on JCM went from 110 to 71 in the past 72 hours. I guess he’ll be sold out in a week or two.

https://jcm-1.com/product/picogus-v2/

https://datasheets.raspberrypi.com/rp2350/rp2 … 0-datasheet.pdf just dropped

> 1 × auxiliary QSPI chip select, for a second XIP device
> External Flash and PSRAM (XIP)

additional QSPI chip select and native PSRAM support/mapping

> Increased the number of PIO blocks from two to three (8 → 12 state machines).

+ some additional instructions for syncing all PIOs

> Reduced DMA request (DREQ) latency by one cycle vs RP2040.
> 48 user GPIOs in the QFN-80 package

price bump by $0.1-0.2 per chip

And what about 5V tolerant I/O? It could be connect direct to the isa bus. 😀

According to the datasheet https://www.raspberrypi.com/products/rp2350/ chapter 14.8.2 GPIO pins 0 to 39 seems to be 5V fault tolerant, when powered with 3.63V. But I don't know if the high level of the chip is good enough to work stable on the ISA bus. What also sounds interesting is that the RP2350B also has more GPIO pins. Would this allow a 16bit version of the PicoGUS?

Caligula wrote on 2024-08-09, 09:15:

According to the datasheet https://www.raspberrypi.com/products/rp2350/ chapter 14.8.2 GPIO pins 0 to 39 seems to be 5V fault tolerant, when powered with 3.63V. But I don't know if the high level of the chip is good enough to work stable on the ISA bus.

it still cuts the need for half of level translators, 244s instead of 245s

rasz_pl wrote on 2024-08-09, 02:00:

https://datasheets.raspberrypi.com/rp2350/rp2 … 0-datasheet.pdf just dropped

I've had the opportunity to play with a Pico-2 for a while. It's been tough keeping my mouth shut! Unfortunately real life circumstances have meant no time to dig into creating a hardware design based on the RP2350B yet, but I definitely want to get there. Here are my takeaways so far:
- The PicoGUS codebase was pretty easy to port over to the Pico 2. There are a few small differences, for example GPIOs need to explicitly have inputs enabled.
- It's almost as overclockable as the RP2040 and can run at about the same speed the PicoGUS firmware overclocks to.
- The RP2350 is almost fast enough to run nuked-opl3. It's tantalizingly close and with some optimization could probably run. This would open up the ability to emulate SBPro, SB16, WSS, etc.
- Memory mapped QSPI PSRAM with cache will greatly simplify GUS emulation and could possibly solve the longest standing bugs in the project.
- 2x the RAM means I could have more emulations running simultaneously.
- Hardware floating point and DSP bring some interesting possibilities for audio filtering.
- More GPIOs could mean supporting 16-bit ISA which is actually less of a big deal than it may seem. Even SB16 runs fine with 8-bit DMA and basically all titles support it (Creative themselves shipped Vibra SB16 boards only capable of 8-bit DMA). Instead I'm more interested in supporting multiple IRQ channels for simultaneous emulation of multiple cards that need IRQ.

Has anyone tried this on an old Tandy 1000TL? It's a 286 8mhz. I'd quite like the ability to have an Adlib, MPU401, serial mouse/joystick single board in this old box for old gaming...

Multiple interrupts at the same time would be a great feature, also supporting the interrupts 10-15 which are on the 16bit part of the ISA connector.

But since the 2350B has 18 additional pins, would it be possible to support multiple interrupts and 16bit I/O transfer at the same time? If I remember correctly it does not matter from software point of view if the card is connected via 8bit or 16bit (except when transferring data via HighDMA), but the speed benefit of 16bit should be significant if the PicoGus emulates multiple cards at the same time (especially network cards).

Got the opportunity to play around with the v2.1.0 firmware.

USB Serial mouse support I was able to get working, but for the life of me I could not get it to respond on anything other than COM1. I'd set it to COM2 (or 3, or 4) via the /mousecom switch, but no matter what PGUSINIT reported back, CuteMouse could only ever find the device on COM1. Note that for each other COM port that I tried, I made sure to set the IRQ jumper to the typically-associated IRQ for that port (IRQ3 for COM2, IRQ4 for COM1).

Also, the MPU401 port was unavailable alongside the USB mouse. Manually adding /mpuport 330 didn't open the port either, despite PGUSINIT saying that it was open. The only thing I could do to get the port to even open was to specify /mpudelay 1, but despite the port being "opened," no MIDI data that was sent through it was routed over to my MIDI device via the waveblaster header or the external MIDI-out jack.

Switching to MPU-only mode, SB mode, or GUS mode opened the port properly.

Unsure whether these are bugs with the USB mode aspect of the firmware, or an issue with my chipset (Intel Triton 430FX) since I don't have multiple systems at the ready to test on.