^^handy list. It's also been discussed that expanded support is planned for the future.
Not PicoGUS related, but Bret Johnson's old USB utilities are another way t0 use USB gamepads in DOS. They seem to work quite well, provided your system has a certain type of USB host controller (details in the link).
This is very interesting, and I had never run into these drivers before. Decided to give them a test and found that keyboard, mouse, and joystick seems to work pretty well on my system. Probably the main downside is that the drivers seem to force into low memory even when using LH which uses a good amount of conventional memory.
Otherwise I also need to dive more into the documentation of the configuration options to fine tune some things like mouse sensitivity and gamepad button mapping. Pretty cool drivers to have around.
stamasdwrote on 2024-08-31, 12:48:I have some trouble with PicoGUS (v2.0, firmware: latest 2.1.0) and serial mice emulation.
My setup: socket7 motherboard, P200MM […] Show full quote
I have some trouble with PicoGUS (v2.0, firmware: latest 2.1.0) and serial mice emulation.
My setup: socket7 motherboard, P200MMX, Win98SE, S3 Virge video, SB32PNP (CT3600) and PicoGUS with Dreamblaster X2 attached.
With the SB32+PicoGUS I aim to get the "ultimate" sound setup. The SB for SB and AWE sound, PicoGUS for everything else.
I have moved the SB32's MPU401 to address 0x300 to leave 0x330 for the PicoGUS' MPU401 which is what I will be using by default.
The sound setup works great, SB sounds and AWE synth through the SB32, and Adlib/wavetable synth through the PicoGUS set in Adlib mode.
The motherboard however does not have a usable PS/2 mouse port and I've been using a serial mouse attached to the on-board COM1. I'd rather use a USB mouse instead.
So I've made a little batch file to set the PicoGUS to initialize an emulated COM3 port and use cutemouse to enable that.
The last line is to get cutemouse to specifically use the mouse attached to COM3 with IRQ4 (and yes, I set the jumpers on the PicoGUS accordingly: IRQ4 and no DMA).
Pgusinit works fine and reports that it has set a serial mouse on COM3.
However, ctmouse does not find a mouse on COM3. "error: device not found"
If I continue booting to Win98 and have it scan for new hardware, it does find the new MPU401 (and it's usable), the new COM3 and a serial mouse attached to it. However, the mouse on COM3 does not work in Windows. And if I reboot to DOS mode, it is not usable under DOS either. If I detach the serial mouse from COM 1 and remove it from device manager, then I have no more mouse in Windows (or DOS) even after rebooting.
FWIW, the mouse I'm using attached to the PicoGUS' USB port is a Logitech M720. It works fine everywhere else. I don't have another USB mouse to test with unfortunately.
Am I making a glaring mistake, or is this sort of wireless USB mouse just not supported?
Replying to my own post with more information
So I went out and got a proper USB corded mouse, verified that it actually works on another system (it does).
Connected it to the PicoGUS, still configured as COM3. Same error, not detected by cutemouse.
I then disabled the on-board COM2 in BIOS and configured the PicoGUS to emulate COM2, changed the IRQ jumper to 3 etc.
pgusinit reports that it emulates COM2 now and a serial mouse on it. But ctmouse /S23 still gives the same error "device not found". So it's not the mouse hardware that's at fault, it's something about the emulation or the way PicoGUS interacts with cutemouse that causes the issue.
I/O, I/O,
It's off to disk I go,
With a bit and a byte
And a read and a write,
I/O, I/O
stamasdwrote on 2024-08-31, 18:18:Replying to my own post with more information
So I went out and got a proper USB corded mouse, verified that it actually works o […] Show full quote
stamasdwrote on 2024-08-31, 12:48:I have some trouble with PicoGUS (v2.0, firmware: latest 2.1.0) and serial mice emulation.
My setup: socket7 motherboard, P200MM […] Show full quote
I have some trouble with PicoGUS (v2.0, firmware: latest 2.1.0) and serial mice emulation.
My setup: socket7 motherboard, P200MMX, Win98SE, S3 Virge video, SB32PNP (CT3600) and PicoGUS with Dreamblaster X2 attached.
With the SB32+PicoGUS I aim to get the "ultimate" sound setup. The SB for SB and AWE sound, PicoGUS for everything else.
I have moved the SB32's MPU401 to address 0x300 to leave 0x330 for the PicoGUS' MPU401 which is what I will be using by default.
The sound setup works great, SB sounds and AWE synth through the SB32, and Adlib/wavetable synth through the PicoGUS set in Adlib mode.
The motherboard however does not have a usable PS/2 mouse port and I've been using a serial mouse attached to the on-board COM1. I'd rather use a USB mouse instead.
So I've made a little batch file to set the PicoGUS to initialize an emulated COM3 port and use cutemouse to enable that.
The last line is to get cutemouse to specifically use the mouse attached to COM3 with IRQ4 (and yes, I set the jumpers on the PicoGUS accordingly: IRQ4 and no DMA).
Pgusinit works fine and reports that it has set a serial mouse on COM3.
However, ctmouse does not find a mouse on COM3. "error: device not found"
If I continue booting to Win98 and have it scan for new hardware, it does find the new MPU401 (and it's usable), the new COM3 and a serial mouse attached to it. However, the mouse on COM3 does not work in Windows. And if I reboot to DOS mode, it is not usable under DOS either. If I detach the serial mouse from COM 1 and remove it from device manager, then I have no more mouse in Windows (or DOS) even after rebooting.
FWIW, the mouse I'm using attached to the PicoGUS' USB port is a Logitech M720. It works fine everywhere else. I don't have another USB mouse to test with unfortunately.
Am I making a glaring mistake, or is this sort of wireless USB mouse just not supported?
Replying to my own post with more information
So I went out and got a proper USB corded mouse, verified that it actually works on another system (it does).
Connected it to the PicoGUS, still configured as COM3. Same error, not detected by cutemouse.
I then disabled the on-board COM2 in BIOS and configured the PicoGUS to emulate COM2, changed the IRQ jumper to 3 etc.
pgusinit reports that it emulates COM2 now and a serial mouse on it. But ctmouse /S23 still gives the same error "device not found". So it's not the mouse hardware that's at fault, it's something about the emulation or the way PicoGUS interacts with cutemouse that causes the issue.
Putting aside the PicoGUS for a moment, for this quick question - Does CTMOUSE work on that system, if you use it to drive your old serial mouse connected to COM1?
Supporter of PicoGUS, PicoMEM, mt32-pi, WavetablePi, Throttle Blaster, Voltage Blaster, GBS-Control, GP2040-CE, RetroNAS.
This time I even went as far as to pull my Orpheus out even though it's game port was disabled via jumper.
It is worth pointing out that no revision of any Orpheus card that was ever sold has a jumper to disable the game port. Control of all devices and their resources must be done through one of CWDINIT, UNISOUND, ORPHINIT or the Windows drivers; this includes the game port. The only exception is for cards with the on-board PCMIDI feature (at one time it was optional). For PCMIDI only, the jumper block must be used for resource assignment.
The other jumper block selects which MIDI signals are routed to the on-board wavetable daughterboard header, dedicated MIDI jack and game port MIDI pins. This has absolutely no effect on whether the game port itself is enabled, nor which resources are assigned to it.
Of course, all of the foregoing may have absolutely no impact on the problem that you are experiencing; it was just to clear up any potential confusion.
640K!enoughwrote on 2024-09-01, 03:21:It is worth pointing out that no revision of any Orpheus card that was ever sold has a jumper to disable the game port. Control […] Show full quote
This time I even went as far as to pull my Orpheus out even though it's game port was disabled via jumper.
It is worth pointing out that no revision of any Orpheus card that was ever sold has a jumper to disable the game port. Control of all devices and their resources must be done through one of CWDINIT, UNISOUND, ORPHINIT or the Windows drivers; this includes the game port. The only exception is for cards with the on-board PCMIDI feature (at one time it was optional). For PCMIDI only, the jumper block must be used for resource assignment.
The other jumper block selects which MIDI signals are routed to the on-board wavetable daughterboard header, dedicated MIDI jack and game port MIDI pins. This has absolutely no effect on whether the game port itself is enabled, nor which resources are assigned to it.
Of course, all of the foregoing may have absolutely no impact on the problem that you are experiencing; it was just to clear up any potential confusion.
Good to know! I also had my doubts whether pulling the jumper off this block was actually disabling the game port or not. My interpretation of the silk screen print on the PCB actually indicated that it likely does not disable but only switches between the two protocols like you mentioned. Thank you for the clarification on this.
I'm happy to report that my attempt to build 2x femto edition was succesfull. First one was bit nightmare, but thanks to this thread I made it work. 2nd one was immediately functional. This is first time I tried to assemble a PCB with such small components by hand, I'm quite surprised it's working. Huge thanks to @polpo for making this possible.
Adlib emulation is working on a tandy 1000TL, but I cannot get the joystick to function. The 1000TL has built-in joystick ports but they can be disabled. Should an xbox one controller work with this card, or is it xbox 360 controllers only?
*edit*
Bad USB cable. Seems to be working great. Is there any method to remap buttons? This "up button to jump" game is annoying as **t to play on a game pad...
Is it possible to use the PicoGUS with Tandy/CMS + Wavetable + USB mouse?
I'm lucky enough to have an Orpheus 2 and was going to pair it with a WP32 McCake but then use the PicoGUS for Tandy/CMS with an X2GS for General Midi (and USB mouse). Is this possible? That should provide basically everything (OPL3, GUS, MT32 [McCake], GM [X2GS]) ?
(I'm also very fortunate to have a real MT32 and SC55MK2 but I like the idea of everything combined into the PC so I don't need lots of cables, etc)
Is it possible to use the PicoGUS with Tandy/CMS + Wavetable + USB mouse?
I'm lucky enough to have an Orpheus 2 and was going to pair it with a WP32 McCake but then use the PicoGUS for Tandy/CMS with an X2GS for General Midi (and USB mouse). Is this possible? That should provide basically everything (OPL3, GUS, MT32 [McCake], GM [X2GS]) ?
(I'm also very fortunate to have a real MT32 and SC55MK2 but I like the idea of everything combined into the PC so I don't need lots of cables, etc)
Basically the answer to your question is Yes. The main caveat is that there are some limits on which Picogus features can be used simultaneously (as there is only one Interrupt to go around).
This image shows which features are active in each of the PicoGUS's modes :
The attachment image.jpg is no longer available
Changing modes is a simple DOS command that takes 1-2 seconds to action.
Supporter of PicoGUS, PicoMEM, mt32-pi, WavetablePi, Throttle Blaster, Voltage Blaster, GBS-Control, GP2040-CE, RetroNAS.
I'm pretty sure the serial mouse emulation is not working correctly in this version of the firmware. At least it is not working on my system.
In addition to the tests above, I have done the following:
-disabled the on-board COM1
-set the PicoGUS in AdLib mode
-set the emulated mouse to COM1; jumper is set correctly to IRQ4
At boot, the pgusinit.exe reports that a mouse is emulated on COM1. Ctmouse 1.9.1 reports that it found a mouse on COM1 with the correct I/O address and IRQ.
However, the mouse is not detected or usable in Windows98. Moreover, it is not usable in plain DOS either by several games I tested.
Also, unrelated: something is weird with the MPU-401 emulation in AdLib mode. Sometimes if works flawlessly, for instance under pure DOS I have had no problem with it whatsoever. However in Windows 98 - sometimes it works as it should, and sometimes it doesn't. Occasionally it takes a very long time to start sending messages to an external device (tested with a real MT-32, and with a MT32-Pi). Sound is supposedly playing, but the activity link on the card itself isn't blinking and the external device doesn't receive anything. Sometimes it ends like this, with no activity on the external MIDI at all. And sometimes, suddenly after 10-20 seconds it starts sending messages: onboard LED starts blinking, external device receives MIDI and music starts playing.
I/O, I/O,
It's off to disk I go,
With a bit and a byte
And a read and a write,
I/O, I/O
Unless I'm doing something wrong it doesn't seem to be very compatible with a Viper 808 single-board computer. Chipset is PicoPower (Cirrus Logic) PT867C768/PT86C718.
The only GUS sound I've been able to hear is from Second Reality which sounds phenomenal, zero issues.
Doom hangs at "calling DMX_Init", dosmid plays no audio, ultramid -c reports "error loading patch".
It would be nice if someone who has skills and time to maintain the thread. Would make thread here in vogons, that contains picogus compatibility with games and hardware.
I don't have any hardware issues but most of the games I would like to play doesn't work with picogus, so I mainly use it in mpu401 role.
Has anyone used a 15-pin to USB adapter? Just in case I feel like using ye olde Gravis Gamepad instead of an xbox one controller...
Unless the USB adapter converts the gameport signals to XInput format, then it probably won't work with the current version of the PicoGUS firmware. :\
Has anyone used a 15-pin to USB adapter? Just in case I feel like using ye olde Gravis Gamepad instead of an xbox one controller...
Unless the USB adapter converts the gameport signals to XInput format, then it probably won't work with the current version of the PicoGUS firmware. :\
Yeah I figured as much. If I can track down a cheap one on ebay I'll see what happens though.
On the plus side, on my computer everything seems to work flawlessly OTHER than GUS, so even if that's not working 100% I've still gotten a lot of upgrades in a single slot!
It would be nice if someone who has skills and time to maintain the thread. Would make thread here in vogons, that contains picogus compatibility with games and hardware.
I don't have any hardware issues but most of the games I would like to play doesn't work with picogus, so I mainly use it in mpu401 role.
