sampson wrote on 2025-09-14, 20:09:

Niemi_81 wrote on 2025-09-14, 17:50:

After getting everything set in autoexec.bat & config.sys i am having trouble accessing emulated CD drive.
Sometimes it shows image file loaded, sometimes not. PGUSINIT / CDLIST never works. Same thing in USB mode. Any tips for me or could my Picogus be faulty. Thanks!

Which flash drive brand/model, capacity, and partition configuration?

I have a bunch of different brand-name USB flash drives, ranging in age from 6-12m old, to 8-10yr old, and in various capacities. Some flash drives work flawlessly, and some not-so-much. I see the same thing with the CH375 interface as well. For my PicoGUS I am using a Sandisk Extreme Pro 256G at the moment. It is configured with an 8GB FAT32 partition, with the rest of the capacity unallocated. I have several Team Group flash drives in 32GB and 128GB capacities and they also work well with both solutions (again, using 4-16GB partitions). I've got a couple flash drives that just act flaky and unreliable. Good luck!

I guess i will try a different USB sticks then, i have tried just a white 8Gb Sandisk stick. It has a LED light and it is blinking quite fast all the time its connected to Picogus, as if data ia being read at all time. FAT 32, probably just 1084kb partitioning or some other default. Thanks for the tips!

Took out some crappy Aliexpress 16Gb stick, and it worked just fine. 🙏

Niemi_81 wrote on 2025-09-16, 13:28:

Took out some crappy Aliexpress 16Gb stick, and it worked just fine. 🙏

FWIW I am using a Sandisk Ultra Fit 128GB USB 3.1 drive which works perfectly with the PicoGUS. I would recommend this device to anyone looking for a USB drive to use for optical emulation as it's extremely fast copying disc images, small so it doesn't stick out much and cheap to buy on Amazon.

NeoG_ wrote on 2025-09-17, 02:57:

Niemi_81 wrote on 2025-09-16, 13:28:

Took out some crappy Aliexpress 16Gb stick, and it worked just fine. 🙏

FWIW I am using a Sandisk Ultra Fit 128GB USB 3.1 drive which works perfectly with the PicoGUS. I would recommend this device to anyone looking for a USB drive to use for optical emulation as it's extremely fast copying disc images, small so it doesn't stick out much and cheap to buy on Amazon.

I used the 32GB version of the same USB stick and I had problems with it. 😀 Changed it to an older/slower USB stick and that worked perfectly.

Yoghoo wrote on 2025-09-17, 05:06:

NeoG_ wrote on 2025-09-17, 02:57:

Niemi_81 wrote on 2025-09-16, 13:28:

Took out some crappy Aliexpress 16Gb stick, and it worked just fine. 🙏

FWIW I am using a Sandisk Ultra Fit 128GB USB 3.1 drive which works perfectly with the PicoGUS. I would recommend this device to anyone looking for a USB drive to use for optical emulation as it's extremely fast copying disc images, small so it doesn't stick out much and cheap to buy on Amazon.

I used the 32GB version of the same USB stick and I had problems with it. 😀 Changed it to an older/slower USB stick and that worked perfectly.

How odd, maybe the 32GB and 128GB drives have a different controller

NeoG_ wrote on 2025-09-17, 07:04:

Yoghoo wrote on 2025-09-17, 05:06:

NeoG_ wrote on 2025-09-17, 02:57:

FWIW I am using a Sandisk Ultra Fit 128GB USB 3.1 drive which works perfectly with the PicoGUS. I would recommend this device to anyone looking for a USB drive to use for optical emulation as it's extremely fast copying disc images, small so it doesn't stick out much and cheap to buy on Amazon.

I used the 32GB version of the same USB stick and I had problems with it. 😀 Changed it to an older/slower USB stick and that worked perfectly.

How odd, maybe the 32GB and 128GB drives have a different controller

Could be. Polpo also said he saw something with a Sandisk USB 3.2 stick. My problem was that playing music from a CD would be too slow. So sound was playing at 90% speed. Sounded very funny. 😜

Treah wrote on 2025-09-13, 01:18:

Has anyone ever had issues with the USB mouse support on this device? I cant get it to work at all... It will detect that a mouse is there via ctmouse but when I move the mouse I get nothing on the mousetst command. It also wont work in windows 3.11. Dunno if this is just my system or something else is going on.

Also when I do have the picogus where it can emulate a USB device as serial my onboard serial ports behave the same way even with an old MS Home mouse.. They get detected but no data is actually sent from the mouse.

To update on this post it looks like the picogus actually interferes with the computers onboard serial ports. If I have it enabled on a card that does USB mouse support the serial ports onboard the machine also fail to function. They see devices but no communication occurs. Not sure if its how the device is interfacing with the rest of the system or what but even with no usb stuff plugged in its a no go on my 486 packard bell CD12 🙁. Thats a bummer since the usb mouse stuff is the whole reason I bought the board since I already had a AZ tech sound galexy card which does pretty much everything this one does with the exception of GUS support I think. Neat board anyway tho and I might use it in my 386 someday.

Treah wrote on 2025-09-18, 16:21:

To update on this post it looks like the picogus actually interferes with the computers onboard serial ports. If I have it enabled on a card that does USB mouse support the serial ports onboard the machine also fail to function. They see devices but no communication occurs. Not sure if its how the device is interfacing with the rest of the system or what but even with no usb stuff plugged in its a no go on my 486 packard bell CD12 🙁. Thats a bummer since the usb mouse stuff is the whole reason I bought the board since I already had a AZ tech sound galexy card which does pretty much everything this one does with the exception of GUS support I think. Neat board anyway tho and I might use it in my 386 someday.

The PicoGUS emulates a serial mouse. You'll want to disable one of the onboard serial ports. And use

1pgusinit /mousecom x

to set which com port to emulate on.

You might be able to use COM 3 or COM 4 to allow both onboard ports to still work. Make sure you're using the ctmouse driver since it can use non-standard IRQs. Since by default COM 3 uses IRQ 4, and COM 4 uses IRQ 3 with overlap and share with COM 1 and COM 2.

https://github.com/polpo/picogus/wiki/Configu … US#serial-mouse

SScorpio wrote on 2025-09-18, 17:49:

The PicoGUS emulates a serial mouse. You'll want to disable one of the onboard serial ports. And use […]
Show full quote

Treah wrote on 2025-09-18, 16:21:

To update on this post it looks like the picogus actually interferes with the computers onboard serial ports. If I have it enabled on a card that does USB mouse support the serial ports onboard the machine also fail to function. They see devices but no communication occurs. Not sure if its how the device is interfacing with the rest of the system or what but even with no usb stuff plugged in its a no go on my 486 packard bell CD12 🙁. Thats a bummer since the usb mouse stuff is the whole reason I bought the board since I already had a AZ tech sound galexy card which does pretty much everything this one does with the exception of GUS support I think. Neat board anyway tho and I might use it in my 386 someday.

The PicoGUS emulates a serial mouse. You'll want to disable one of the onboard serial ports. And use

Copy code to clipboard

1pgusinit /mousecom x

to set which com port to emulate on.

You might be able to use COM 3 or COM 4 to allow both onboard ports to still work. Make sure you're using the ctmouse driver since it can use non-standard IRQs. Since by default COM 3 uses IRQ 4, and COM 4 uses IRQ 3 with overlap and share with COM 1 and COM 2.

https://github.com/polpo/picogus/wiki/Configu … US#serial-mouse

Thank you I will try this out. I think I only tried out com 1 and 2 on the machine since I can specify that in the bios for the single serial interface that machine has. It probably is due to the IRQ being shared between them is what I am running into. I will check out that link tho and see if I can get my USB mouse working. If so that would be awesome. If not I always have my old semi reliable microsoft home mouse... shudder.

NeoG_ wrote on 2025-09-17, 07:04:

How odd, maybe the 32GB and 128GB drives have a different controller

I work in the industry and very closely with the storage vendors (mostly for NVMe, but also USB attached storage). You're probably right - different controllers is a very distinct possibility, and likely the reason. They probably use the exact same branding and device styling but employ various cost saving strategies for the PCB and controller on a lower capacity version. Same thing happens on NVMe with higher performance devices using an 8-channel NAND interface vs. 4-channel, as well as DRAM vs. DRAMless, and other considerations/choices. In my experience, it's not even possible to recommend an exact model number because different (often silent) revisions will use different internals, which is a very common issue in the DRAM memory market as well.

Treah wrote on 2025-09-18, 23:00:

Thank you I will try this out. I think I only tried out com 1 and 2 on the machine since I can specify that in the bios for the single serial interface that machine has. It probably is due to the IRQ being shared between them is what I am running into. I will check out that link tho and see if I can get my USB mouse working. If so that would be awesome. If not I always have my old semi reliable microsoft home mouse... shudder.

There are two serial IRQs (COM1&3=IRQ4, COM2&4=IRQ3) and fixed memory addresses, the PicoGUS card has to be set to use one of of them that isn't already in use by the motherboard. If the motherboard is set to use COM1/IRQ4, then the PicoGUS must be on IRQ3 and COM2 for example. The downside is that if mouse is using the lone IRQ on the PicoGUS none of the other IRQ dependent systems like SB or GUS will work (Also most software won't allow IRQ 3 or 4 for sound)

NeoG_ wrote on 2025-09-19, 04:27:

There are two serial IRQs (COM1&3=IRQ3, COM2&4=IRQ4) and fixed memory addresses, the PicoGUS card has to be set to use one of of them that isn't already in use by the motherboard. If the motherboard is set to use COM1/IRQ3, then the PicoGUS must be on IRQ4 and COM2 for example. The downside is that if mouse is using the lone IRQ on the PicoGUS none of the other IRQ dependent systems like SB or GUS will work (Also most software won't allow IRQ 3 or 4 for sound)

The PicoGUS's serial mouse emulation only works in Adlib, Tandy/CMS, and USB mode. None of those use the IRQ for anything else.

The ctmouse driver supports non-standard IRQs, so you could have it use COM 3 or 4 and IRQ 5 to have working sound if you switch to one of the soundcard modes. But then you'd lose USB mouse support.

NeoG_ wrote on 2025-09-19, 04:27:

Treah wrote on 2025-09-18, 23:00:

Thank you I will try this out. I think I only tried out com 1 and 2 on the machine since I can specify that in the bios for the single serial interface that machine has. It probably is due to the IRQ being shared between them is what I am running into. I will check out that link tho and see if I can get my USB mouse working. If so that would be awesome. If not I always have my old semi reliable microsoft home mouse... shudder.

There are two serial IRQs (COM1&3=IRQ3, COM2&4=IRQ4) and fixed memory addresses, the PicoGUS card has to be set to use one of of them that isn't already in use by the motherboard. If the motherboard is set to use COM1/IRQ3, then the PicoGUS must be on IRQ4 and COM2 for example. The downside is that if mouse is using the lone IRQ on the PicoGUS none of the other IRQ dependent systems like SB or GUS will work (Also most software won't allow IRQ 3 or 4 for sound)

Yeah I have tried setting my computer to use COM2 for the COMA port on the board and even tried to just disable everything and nothing. As long as the PicoGUS is in USB mode or any mode that allows a USB mouse none of the com ports on the machine function to carry data.

I think its just down to this board doing wierd things with hardware ( it is a shit Packard Bell Machine after all ) I mean these machines were terrible when they were new so its no suprize this is an issue 🤣.

NeoG_ wrote on 2025-09-11, 11:00:

DustyShinigami wrote on 2025-09-10, 09:27:

When I come to order one from Serdashop, should I add any additional GM/GS or LAPC bundles?

I ordered mine with the 3.5" front display and a WP32 McCake. I have been very happy with the WP32 hanging off the wavetable header, especially for MT32 games. Now with GeneralUser GS 2.0+ the GM side is also much more SC-55 like and works well with games. The front display seemed cool at first and was useful for troubleshooting but now it's been on there for a bit I don't think it suits the aesthetic of most systems it would go in to.

So what exactly are those features? The additional GM/GS/LAPC bundles? How do they work and what are their benefits? Thanks.

DustyShinigami wrote on 2025-09-20, 13:20:

NeoG_ wrote on 2025-09-11, 11:00:

DustyShinigami wrote on 2025-09-10, 09:27:

When I come to order one from Serdashop, should I add any additional GM/GS or LAPC bundles?

I ordered mine with the 3.5" front display and a WP32 McCake. I have been very happy with the WP32 hanging off the wavetable header, especially for MT32 games. Now with GeneralUser GS 2.0+ the GM side is also much more SC-55 like and works well with games. The front display seemed cool at first and was useful for troubleshooting but now it's been on there for a bit I don't think it suits the aesthetic of most systems it would go in to.

So what exactly are those features? The additional GM/GS/LAPC bundles? How do they work and what are their benefits? Thanks.

Wavetable boards are a bit of a rabbit hole but this is the summary;

They are boards that render MIDI music/sound and connect to the wavetable header on the PicoGUS. GM/GS is for games with General MIDI music (circa 1993-1997), LAPC is for games with MT-32 music (circa 1988-1992). The PicoGUS by itself can do somewhat OK with General MIDI music in GUS mode, but if you want better sounding and more compatible MIDI music for DOS games a wavetable board is recommended. I got the WP32 McCake (LAPC bundle) because it does both General MIDI and MT-32.

More info at DOS Days: https://www.dosdays.co.uk/topics/wavetable_audio.php

NeoG_ wrote on 2025-09-20, 14:27:

Wavetable boards are a bit of a rabbit hole but this is the summary; […]
Show full quote

DustyShinigami wrote on 2025-09-20, 13:20:

NeoG_ wrote on 2025-09-11, 11:00:

I ordered mine with the 3.5" front display and a WP32 McCake. I have been very happy with the WP32 hanging off the wavetable header, especially for MT32 games. Now with GeneralUser GS 2.0+ the GM side is also much more SC-55 like and works well with games. The front display seemed cool at first and was useful for troubleshooting but now it's been on there for a bit I don't think it suits the aesthetic of most systems it would go in to.

So what exactly are those features? The additional GM/GS/LAPC bundles? How do they work and what are their benefits? Thanks.

Wavetable boards are a bit of a rabbit hole but this is the summary;

They are boards that render MIDI music/sound and connect to the wavetable header on the PicoGUS. GM/GS is for games with General MIDI music (circa 1993-1997), LAPC is for games with MT-32 music (circa 1988-1992). The PicoGUS by itself can do somewhat OK with General MIDI music in GUS mode, but if you want better sounding and more compatible MIDI music for DOS games a wavetable board is recommended. I got the WP32 McCake (LAPC bundle) because it does both General MIDI and MT-32.

More info at DOS Days: https://www.dosdays.co.uk/topics/wavetable_audio.php

Awesome. Thanks for the explanation. I think I did briefly look up wavetable boards some time ago. I suspect going for one would certainly bump the overall price up, but they both sound like good options to have. Even better there’s one that does both! 😄 I know Simon the Sorcerer 1 and 2 in DOS has issues with the SC-55, so those should work nicely.

I have a Wavetable Pi for MT-32 emulation attached to my PicoGUS (I like the smaller form factor) . I also have a Dreamblaster X2GS attached to a SB16 in the same system. I really like having plenty of options for DOS music in my overkill build. I route the PicoGUS output through the SB16's mixer.

badmojo wrote on 2024-07-08, 01:09:

polpo wrote on 2024-07-07, 23:59:

Ok, so I almost mentioned this because I noticed this strange line in your board's manual and I thought it was odd: "FOR 5V CMOS ISA CARD, PLS insert in Slot5" with an illustration of the board the ISA slot on the edge of the board circled. I'm curious if your fixing it meant putting the PicoGUS in that slot, or taking it out of it, or if that slot wasn't involved at all!

Ha yes I moved it into the slot on the outer edge (Slot5 in the manual) so that might be in the mix. What does that mean do you think? PicoGUS needs more juice than the other slots could give it?

I m really glad to read your solution, as I have a Pico GUS 2.0 along with an AWE64 in my 440BX system and will try tomorrow to set it up under DOS 7.0 (bootet from Windows 98SE).
Hope, I will have success and there will be no problems having 2 soundcards.
My goal: to play all games supporting Gravis Ultrasound e.g. OMF 2097, Jazz Jack Rabbit, Epic Pinball, Doom1 as well as all games supporting Creative AWE32 e.g. Crusader No Remorse as well as some games with MT32 e.g. Monkey Island 1.

PS: as I cannot edit my previous posting, I add a new one, please excuse me:

I have also bought 2x daughter boards:

1. Wavetable Pi with a 32 GB SD-card for my Pico GUS and it is physically installed upon it => tomorrow will test whether it plays General Midi sound

2. IMMConn 28MB adapter with a 32 MB EDO RAM simm module => still awaiting the DHL delivery next week

I hope that with this 2x ISA soundcards I will be able to play the majority of all famous DOS or Win9x games using SBpro 2.0, SB 16, GUS, AWE32, MT32, GS/GM

When I was young I hardly could afford to buy soundcards. I remember that I had an old Terratec ISA card with SBpro 2.0 ability. Once I sold it and bouth the Gravic PnP (cannot remember whether it was ACE PnP...)

Just wanted to share that I received my PicoGUS v2.0 today and the GUS emulation is working great but I've not been able to get a USB mouse working. I have the onboard serial ports disabled on the mobo, I have the PicoGUS in USB mode, the PicoGUS jumper is configured for IRQ3. pgusinit is configured with /mousecom 2. I'm using CTmouse /S23 and it throws the error: device not found. The one strange thing I'm noticing is that the LED's on the mouse go dark after a few seconds of plugging it in, like it's no longer receiving power, moving it doesn't wake it up, and I've tried a couple USB mice now.