VOGONS


First post, by DJNW

User metadata
Rank Newbie
Rank
Newbie

I've got a 440BX motherboard with the appropriate header on it. The board manual mentions the header, so I'd presume that it's intended to work, right? Someone in another thread on there got the same board working with a YMF724 board, so I'd have presumed there's no necessary settings unavailable in the rather spartan BIOS.

I've got a soundcard that came with the header (TTSOLO-NL v1.2). Again, the header's obviously factory-soldered, not added by someone after the fact. ID on the chip is K370. There's an ATMEL 93C46 eprom on there. Except for the chip ID + the size of the eprom (sticker on the back hints at May 2021, so ) , it's identical to Joseph Joestar's one here

BTW: I have a theory, looking at the various TTSOLO-XX on the retroweb - the "L" in - TTSOLO-[NL /SL] sbLink. Feel free to speculate what the preceding letters stand for.


It'll happily initialise using DDMA mode, but (stubborn fool that I am) I'm feeling driven to get PC/PCI working.

Any attempt to get PC/PCI going, results in it saying it can't see the Audiodrive:

-I've turned on PCI 2.1 Compliance in the BIOS, which is meant to enable some degree of allow-ISA-stuff while PCI is doing things-ness. The BIOS doesn't have an option for Passive Release, or I'd turned that on too. I'm game to break out PCISET or similar if anyone knows what/where to prod. I've also backed-up my BIOS (including onto a floppy) in-case of any BIOS-patching suggestions after the time I whoopsed the bootblock to the point it could see hard drive, but not boot from them. (I did say I'm a fool!)
-I've tried force-assigning IRQ5 to the slot in the BIOS
-I've hex-edited byte 12 of essolo.ini to 02 (and then set it to read-only) as per here

BTW: did you know that there's settings that affect rebuilding this file in the registry? Have a dig through the oemsetup.inf for the windows drivers:

; To use PCPCI DMA mode change 01,00 to 01,01 ; HKR,Config,"Use PCPCI DMA Mode",01,00 HKR,Config,"DDMA Base",01,00,38 […]
Show full quote

; To use PCPCI DMA mode change 01,00 to 01,01
;
HKR,Config,"Use PCPCI DMA Mode",01,00
HKR,Config,"DDMA Base",01,00,38

Search for these strings in regedit and they're there!

You can also stop it meddling with config.sys/autoexec.bat, as it's (understandably) unable to place the lines it's inserting sensibly on a system that's got a menu in config.sys and any corresponding GOTOs in autoexcec.bat

; Write parameter to ESSOLO.SYS /s:xxxx HKR,Config,"AddParaToESSOLO",01,ff HKR,Config,"Add ESSOLO.COM To Autoexec.bat",01,FF HKR […]
Show full quote

; Write parameter to ESSOLO.SYS /s:xxxx
HKR,Config,"AddParaToESSOLO",01,ff
HKR,Config,"Add ESSOLO.COM To Autoexec.bat",01,FF
HKR,Config,"Add DEVICE=ESSOLO.SYS",01,FF

I'm curious whether that means we should perhaps edit essolo.sys as well given the above?

I've tried a hacked-up copy of essolo.com someone posted that they said forces PC/PCI on

-I've tried a plain 2x3 IDC connector (which I've beep-tested with a multi-meter to check every wire's working and in-order). I've also tried reversing the motherboard-end connector just-in-case
-I've tried running dupont wires one-by-one from card-to-motherboard

-I've checked where the pins of the connector on the card connect to on the 1938S and (as someone else noted elsewhere) it's off-spec:

1 PCIGNT 62 2 NC 3 GROUND 100 4 PCIREQ 61 5 GROUND 100 6 SERIRQ 57 […]
Show full quote

1 PCIGNT 62
2 NC
3 GROUND 100
4 PCIREQ 61
5 GROUND 100
6 SERIRQ 57

Numbers before are PC/PCI header pins, numbers after are pins on the 1938S per the datasheet someone posted. (hooray for PDF rotation!)
-After seeing the above, I tried doing it again with dupont wires, only taking pin3 from the card to pin2 on the motherboard, which should match with the proper spec for PC/PCI.

So:
1)Is the length of the wires used going to affect it? I'd presume that it'd work, but be plagued with issues, not fail outright.
2)I'm sure someone posted something about how boards with working sblink have pull-up resistors - any suggestions on checking this? I've got access to a multi-meter and a (cheap diy) oscilloscope
3)Any other suggestions?

Reply 1 of 5, by akimmet

User metadata
Rank Member
Rank
Member

You are not alone. I have several motherboards where my Solo-1 sound cards will refuse to use PC/PCI, but PC/PCI works without issue with Mastero-2 or YMF cards.
I have been able to confirm K revision Solo-1 chips are not compatible with ESSVOL. Not having mixer controls can be annoying if one is using DOS without Windows.

Reply 2 of 5, by DJNW

User metadata
Rank Newbie
Rank
Newbie

I feel like it has to be something on the card. When Ive got the time and inclination I'm going to see if this thing's got pull-ups on it and what the spec says about that.

Reply 3 of 5, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie

Look around for the modified ESSOLO.COM which forces PC/PCI... Whether you're going to get any sound out of it though is another story.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 4 of 5, by akimmet

User metadata
Rank Member
Rank
Member

I am more inclined to believe it is ESSOLO.COM not liking something about your chipset or BIOS.

Reply 5 of 5, by DJNW

User metadata
Rank Newbie
Rank
Newbie

I've just had an explore of the header on the motherboard:

1: ~3.5v
2: GROUND
3: NC
4: ~3.2v
5: GROUND
6: ~3.2v

Looks like 1/4/6 are pulled high, with some sort of activity on there that's way faster than my DSO 138 mini can follow, but it does periodically show blips of some sort of signal, so motherboard seems to be talking down the link.
Probably time to start exploring PCI bus registers.

Ed: spent an evening prodding registers. It accepts register writes, but doesn’t initialise that way, either.