CoffeeOne wrote on 2020-03-21, 15:17:
OSkar000 wrote on 2020-03-21, 11:03:
CoffeeOne wrote on 2020-02-27, 21:24:
1) I recommended to put the 3Com 3C509 into EISA mode, then it will be fully controlled via ECU.
2) Do you use an EISA configuration file for the sound blaster 32?
I changed the 3Com-card to use EISA-mode and that seems to work just fine.
I don't have any configuration file for the SB32 but it seems like the bios/setup-utility sets all resources correct. But the installation program for the drivers can't find the card so I'm a bit stuck here.
The screenshots look good. You may want to disable the IDE port via ECU, too, gives you one more free IRQ when you have nothing connected as in the picture.
But I don't think that has something to do with your sound card driver problem. I am not a specialist, but I am sure others can help.
Please, give more details.
What OS do you run now? MS-DOS?
What installation program?
I know it's bit time consuming, but consider installing Win9x (if possible), because all your hardware should be autodetected, then you would be sure, that all the components work together well. But for that you should have at least a 66MHz cpu (5 volts variant needed) available, with a DX-33 it would be a pain in the ...
OS = Dos 6.22 and WFW 3.11
The installation program I'm reffering to is the setup for the soundcard on the CD I got with it so it should be the original drivers from 1995.
Disabling the IDE-port on the card is on the list of things that I should do but I have to figure out how to do it first. As you say, at the moment its not a problem.
But at the moment it seems like the problem is solved, maybe not the most correct solution but it seems to work fine.
Windows 95A should run quite good on this computer, lots of memory and a "fast" hard drive makes big difference. I ran W95 on a 386DX/33 and 20mb ram for about two years before I got my first Penitum in 1998.
Another thing on the todo-list is to straighten out some pins on a 486 DX/2 66 Overdrive that I found in a box here. I will test it on another motherboard before I put it in the Prosignia since I'm not sure if its ok or not.
JazeFox wrote on 2020-03-22, 13:11:
For DOS: Unisound alone does almost everything the official drivers do, so you don't need them at all, you can remove them from […]
OSkar000 wrote on 2020-03-22, 12:09:
I did a quick test and after running Unisound it seems to work. I could install the drivers and software.
However... i have to run Unisound in autoexec.bat before the soundblaster-drivers and programs are loaded... so there is some more testing left.
For DOS: Unisound alone does almost everything the official drivers do, so you don't need them at all, you can remove them from your CONFIG.SYS and AUTOEXEC.BAT. With one exception: soundfonts management. If you need to load a soundfont bank to AWE RAM with MPU emulation, you'll need to add AWEUTIL /GM (or whatever MIDI option you need) from official drivers.
Only one requirement in AUTOEXEC.BAT: if you don't want the default values Uniound use for address, IRQ/DMA, etc... you'll need to put the BLASTER environment variable before Unisound in AUTOEXEC.BAT (example: SET BLASTER=A220 I5 D1 H5 P330 E620). Anyway, it is recommended to always set the variable, as some games require it.
Fow Windows 3.x: The same as with DOS, but in addition you must install windows drivers. It is possible that the installation would modify the config and autoexec aswell, but you can modify them later removing anything that is not needed.
Thanks! This has helped me a lot!
I just made a really quick test earlier today so I still have lots of things to do before its done. And my config.sys / autoexec.bat is a total mess at the moment so lots of things has to be done there.
Next problem on the list... Drivers for the SCSI CD-ROM!