Hi,

It is like polluting PicoGUS posts by picoMEM but Anyway 😀

I added Mindscape and Covox to the PicoMEM.
Couvox sound master, sound master 2 and multiple other rare boards could be added as well.
So, maybe Ian will take those code and add to the PicoGUS. 😉

What other kind of "not CPU intensive/Impossible with a Pico" can be nice to add ?

FreddyV wrote on Yesterday, 09:54:

Hi, […]
Show full quote

Hi,

It is like polluting PicoGUS posts by picoMEM but Anyway 😀

I added Mindscape and Covox to the PicoMEM.
Couvox sound master, sound master 2 and multiple other rare boards could be added as well.
So, maybe Ian will take those code and add to the PicoGUS. 😉

What other kind of "not CPU intensive/Impossible with a Pico" can be nice to add ?

IBM Music Feature? There's emulation for it in DOSBox, but i guess it needs to be ported to ARM. No idea if the RP2040 can do it, if not maybe the RP2350

I'm having an issue getting the CDRom drivers to load on my PicoGUS 2.0 on my 486 Machine.

Specs:
Motherboard: Freetech/Flexus 486F38X
CPU: 486DX2-66
RAM: 64MB
Video: QDI S3VGA PS805 (VLB)
Sound: Soundblaster AWE64 Value
I/O: DTC2278E (VLB)
OS: DOS 6.22
Driver: CDMKE.SYS from PicoGUS wiki

Autoexec.bat:
@ECHO OFF
PROMPT $p$g
SET PATH=C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS
SET CTCM=C:\CTCM
SET SOUND=C:\SB16
SET BLASTER=A220 I7 D1 H7 P300 E620 T6
SET MIDI=SYNTH:1 MAP:E MODE:0
LH C:\CTCM\CTCU /S
LH C:\SB16\DIAGNOSE /S
LH C:\SB16\AWEUTIL /S
LH C:\SB16\MIXERSET /P /Q
LH C:\CTMOUSE\CTMOUSE.EXE /S1
LH C:\DOS\MSCDEX /D:MSCD000

Config.sys:
DOS=HIGH,UMB
FILES=40
BUFFERS=40
STACKS=9,256
LASTDRIVE=H
DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
REM DEVICE=C:\DOS\EMM386.EXE RAM
DEVICEHIGH=DOSEIDE.SYS /2
DEVICEHIGH=C:\DOS\CDMKE.SYS /P:250 /D:MSCD000 /Q
DEVICEHIGH=C:\CTCM\CTCM.EXE

All the other modes work fine on the PicoGus (I use it often with my MT-32Pi), I can see all the images on my USB stick, and I can switch between them. The problem is that when the CDMKE.SYS comes up to load during boot, it gives back an error that states "Interface Board or CD-Rom Drive is not ready". I tried different things with my AUTOEXEC.BAT and CONFIG.SYS files but nothing worked so far. I even tried the CDGOD disk with several different drivers, but none of them can detect the PicoGUS virtual CD. Anyone got any suggestions?

Isstanar wrote on Yesterday, 18:47:

All the other modes work fine on the PicoGus (I use it often with my MT-32Pi), I can see all the images on my USB stick, and I can switch between them. The problem is that when the CDMKE.SYS comes up to load during boot, it gives back an error that states "Interface Board or CD-Rom Drive is not ready". I tried different things with my AUTOEXEC.BAT and CONFIG.SYS files but nothing worked so far. I even tried the CDGOD disk with several different drivers, but none of them can detect the PicoGUS virtual CD. Anyone got any suggestions?

Try and move the port around (E.g. try 260 or 280), remember the port has to be changed in config.sys (/P:280 parameter) and also on the picogus (/cdport 280 /save). 250 may be blocked by another device.

NeoG_ wrote on Yesterday, 21:20:

Isstanar wrote on Yesterday, 18:47:

All the other modes work fine on the PicoGus (I use it often with my MT-32Pi), I can see all the images on my USB stick, and I can switch between them. The problem is that when the CDMKE.SYS comes up to load during boot, it gives back an error that states "Interface Board or CD-Rom Drive is not ready". I tried different things with my AUTOEXEC.BAT and CONFIG.SYS files but nothing worked so far. I even tried the CDGOD disk with several different drivers, but none of them can detect the PicoGUS virtual CD. Anyone got any suggestions?

Try and move the port around (E.g. try 260 or 280), remember the port has to be changed in config.sys (/P:280 parameter) and also on the picogus (/cdport 280 /save). 250 may be blocked by another device.

I cannot believe it was that simple. I switched to port 280 and now it works fine. Thank you sir.

I swear I did try to change the port, but I'm guessing I forgot the /save part.

Isstanar wrote on Yesterday, 21:43:

NeoG_ wrote on Yesterday, 21:20:

Isstanar wrote on Yesterday, 18:47:

All the other modes work fine on the PicoGus (I use it often with my MT-32Pi), I can see all the images on my USB stick, and I can switch between them. The problem is that when the CDMKE.SYS comes up to load during boot, it gives back an error that states "Interface Board or CD-Rom Drive is not ready". I tried different things with my AUTOEXEC.BAT and CONFIG.SYS files but nothing worked so far. I even tried the CDGOD disk with several different drivers, but none of them can detect the PicoGUS virtual CD. Anyone got any suggestions?

Try and move the port around (E.g. try 260 or 280), remember the port has to be changed in config.sys (/P:280 parameter) and also on the picogus (/cdport 280 /save). 250 may be blocked by another device.

I cannot believe it was that simple. I switched to port 280 and now it works fine. Thank you sir.

I swear I did try to change the port, but I'm guessing I forgot the /save part.

Question 1: "and also on the picogus (/cdport 280 /save)"
=> means that you added a line in the AUTOEXEC.BAT like this?
SET PICOGUS /cdport 280 / save

Question 2: currently I have a PicoGUS 2.0 + MT32 Raspberry board and an AWE64 value with 4 colors + SIMMconn 32MB PS/2
=> how do I connect them with a "sound cable" in order to enable this combination in Doom 1: General Midi on GUS and SB16 effects on AWE64
=> do I need to connect the line out of the GUS to the line in of the AWE64 (which one of the 4 colors shall I take?)

eliot_new wrote on Yesterday, 23:11:

Question 1: "and also on the picogus (/cdport 280 /save)"
=> means that you added a line in the AUTOEXEC.BAT like this?
SET PICOGUS /cdport 280 / save

Run: pgusinit /cdport 280 /save
This will set the port and then save the settings to the card so it will remember for future start ups. You need to do this so the settings are ready for the MKE driver in config.sys to be loaded, since any settings you change in autoexec.bat will be too late.

eliot_new wrote on Yesterday, 23:11:

Question 2: currently I have a PicoGUS 2.0 + MT32 Raspberry board and an AWE64 value with 4 colors + SIMMconn 32MB PS/2
=> how do I connect them with a "sound cable" in order to enable this combination in Doom 1: General Midi on GUS and SB16 effects on AWE64
=> do I need to connect the line out of the GUS to the line in of the AWE64 (which one of the 4 colors shall I take?)

Yes, connect to the line in of the AWE64, which should be the blue jack. Make sure to turn up the mixer volume for the line in to make sure you can actually hear it.