Sure ! it's available over here http://www.win3x.org/win3board/viewtopic.php? … =172925#p172925

HanJammer wrote on 2020-04-15, 17:14:

#60 Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0) Chipset : Headland HT21A BIOS : Phoenix 07/28/91, on a 27C5 […]
Show full quote

#60
Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0)
Chipset : Headland HT21A
BIOS : Phoenix 07/28/91, on a 27C512 type ROM chip (64KB)
ID string :

Nice looking board. Does it have two eproms (Hi and Lo) like a 286 ? Also what speed is that 386, cannot read it. Just curious.

Thermalwrong wrote on 2019-08-03, 00:42:

The board in that picture (which I also have) seems to be a clone of the BEK P405 motherboard: https://www.instagram.com/p/BjsYiyqgp4y/

Could you make a BIOS dump of the BEK P405 motherboard? Can't find anything online about the P405 or this M1487/9 rev. B1 board.

Thanks.

Brightraven wrote on 2020-04-21, 17:08:

Thermalwrong wrote on 2019-08-03, 00:42:

The board in that picture (which I also have) seems to be a clone of the BEK P405 motherboard: https://www.instagram.com/p/BjsYiyqgp4y/

Could you make a BIOS dump of the BEK P405 motherboard? Can't find anything online about the P405 or this M1487/9 rev. B1 board.

Thanks.

Sure 😀 Here's the BIOS file for it

Deunan wrote on 2020-04-25, 12:39:

#60 Manufacturer: ??? Chipset: UM8498F + UM8496F BIOS string: 12/08/94-UMC-498GP-2C4X6S21-00 BIOS label: BIOS ISA 486 BIOS versi […]
Show full quote

#60
Manufacturer: ???
Chipset: UM8498F + UM8496F
BIOS string: 12/08/94-UMC-498GP-2C4X6S21-00
BIOS label: BIOS ISA 486
BIOS version: Award Modular BIOS v4.50G

That POST string suggests it's a Soyo motherboard, but I couldn't find any matching soyo board ...
Is there anything labeled on the board (front or back) or on the lowest ISA slot on a sticker that could help ?

Deksor wrote on 2020-04-25, 12:59:

That POST string suggests it's a Soyo motherboard, but I couldn't find any matching soyo board ...
Is there anything labeled on the board (front or back) or on the lowest ISA slot on a sticker that could help ?

NSSI detects it as SY-25 Q/R but that mobo has VLB slots and external cache. Otherwise though the layout is similar, especially the mixed size memory slots. Could be a cheaper variant?

No text strings or stickers of any interest, other that what you can see on the photo. On the side of the ISA slot there's just a warranty void sticker with July '96 date. There does seem to be a smaller round sticker under it, but possibly just a QC stamp.

On the back there is 1042495 number in white paint, and your typical TEAN TN1 94V-0 and 9509 date code. And that's it.

Well ... that's going to be a though one to identify clearly I guess ^^

Another board I find weird :

Predator99 wrote on 2018-05-25, 11:14:

#1 Manufacturer/Identifier: CH-386S-16/20/25G P/N:001-0386S-016 Chipset: CHIPS F82C836 386-CH-386S.zip 386-CH-386S.jpg […]
Show full quote

#1
Manufacturer/Identifier: CH-386S-16/20/25G P/N:001-0386S-016
Chipset: CHIPS F82C836
386-CH-386S.zip
386-CH-386S.jpg

This board is made by Chicony it seems, but the BIOS rom you've provided doesn't seem to correspond at all.
The chipset is a Chips and Technologies SCATsx.
But the POST string says this "30-0100-D01425-00101111-050591-SCAMPSX-0".
"1425" isn't Chicony's manufacturer code and SCAMPSX corresponds to a VLSI SCAMPsx chipset, not the C&T chipset there is on the motherboard.
Are you sure this is the correct BIOS ?

Thermalwrong wrote on 2020-04-24, 21:32:

Sure 😀 Here's the BIOS file for it

Awesome, thanks again! 😀 I'm going to see if it works with this M1487/9 board as it has an AMI winbios which I am not a fan of...

Deksor wrote on 2020-04-25, 13:56:

Well ... that's going to be a though one to identify clearly I guess ^^ […]
Show full quote

Well ... that's going to be a though one to identify clearly I guess ^^

Another board I find weird :

Predator99 wrote on 2018-05-25, 11:14:

#1 Manufacturer/Identifier: CH-386S-16/20/25G P/N:001-0386S-016 Chipset: CHIPS F82C836 386-CH-386S.zip 386-CH-386S.jpg […]
Show full quote

#1
Manufacturer/Identifier: CH-386S-16/20/25G P/N:001-0386S-016
Chipset: CHIPS F82C836
386-CH-386S.zip
386-CH-386S.jpg

This board is made by Chicony it seems, but the BIOS rom you've provided doesn't seem to correspond at all.
The chipset is a Chips and Technologies SCATsx.
But the POST string says this "30-0100-D01425-00101111-050591-SCAMPSX-0".
"1425" isn't Chicony's manufacturer code and SCAMPSX corresponds to a VLSI SCAMPsx chipset, not the C&T chipset there is on the motherboard.
Are you sure this is the correct BIOS ?

Not 100% sure. Also not sure if the board was running or not. But at least AMI and 386SX seems to match.

Quite possible I exchanged the file or I got the board with a wrong ROM...

386 #23 and #37 are identical. Both are Shuttle HOT-317 with the exact same BIOS from 1993

HanJammer wrote on 2019-07-01, 00:22:

#43 Manufacturer/Identifier: TAM/33,40-U2 Chipset: UMC 491F BIOS: AMI ID string: 40-0102-001105-00101111-040493-UMC491F […]
Show full quote

#43
Manufacturer/Identifier: TAM/33,40-U2
Chipset: UMC 491F
BIOS: AMI
ID string: 40-0102-001105-00101111-040493-UMC491F

amibios-40-0102-001105-00101111-040493-UMC491F.zip
IMG_20190701_014335.jpg

and

lgj1107 wrote on 2020-03-07, 05:09:

Unknown 386 motherboard

Are identical (but both posts have a different AMI bios). It's a Pine PT-321

HanJammer wrote on 2020-04-15, 17:14:

#60 Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0) Chipset : Headland HT21A BIOS : Phoenix 07/28/91, on a 27C5 […]
Show full quote

#60
Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0)
Chipset : Headland HT21A
BIOS : Phoenix 07/28/91, on a 27C512 type ROM chip (64KB)
ID string :

You only copied half of the BIOS ! there are two ROMs. (And also you copied the first one as a 512kb rom, but it's a 256kb rom).

Also I think I've found a matching board in TH99
https://stason.org/TULARC/pc/motherboards/U/U … X-20-25-64.html

Predator99 wrote on 2020-04-27, 19:18:

#63 Manufacturer/Identifier: Morse 386 Chipset: UMC UM82C206L MORSE 91A311 91A310 BIOS: […]
Show full quote

#63
Manufacturer/Identifier: Morse 386
Chipset: UMC UM82C206L MORSE 91A311 91A310
BIOS:

Nice looking board ! I loaded bios in an Emulator and also Hex edited and got a weird bios string. Have you peeked under those Morse labels ? Am curious if they are UMC 82C480 series. Similar to #51 but different !

Deksor wrote on 2020-04-26, 20:37:

You only copied half of the BIOS ! there are two ROMs. (And also you copied the first one as a 512kb rom, but it's a 256kb rom). […]
Show full quote

HanJammer wrote on 2020-04-15, 17:14:

#60 Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0) Chipset : Headland HT21A BIOS : Phoenix 07/28/91, on a 27C5 […]
Show full quote

#60
Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0)
Chipset : Headland HT21A
BIOS : Phoenix 07/28/91, on a 27C512 type ROM chip (64KB)
ID string :

You only copied half of the BIOS ! there are two ROMs. (And also you copied the first one as a 512kb rom, but it's a 256kb rom).

Also I think I've found a matching board in TH99
https://stason.org/TULARC/pc/motherboards/U/U … X-20-25-64.html

Missing the second ROM image is why I asked :

Horun wrote on 2020-04-16, 00:30:

HanJammer wrote on 2020-04-15, 17:14:

#60 Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0) Chipset : Headland HT21A BIOS : Phoenix 07/28/91, on a 27C5 […]
Show full quote

#60
Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0)
Chipset : Headland HT21A
BIOS : Phoenix 07/28/91, on a 27C512 type ROM chip (64KB)
ID string :

Nice looking board. Does it have two eproms (Hi and Lo) like a 286 ? Also what speed is that 386, cannot read it. Just curious.

You verified what I was wondering, Thanks !
Edit: And good work on finding what appears to be the correct board at MH TH99

Horun wrote on 2020-04-28, 01:58:

Predator99 wrote on 2020-04-27, 19:18:

#63 Manufacturer/Identifier: Morse 386 Chipset: UMC UM82C206L MORSE 91A311 91A310 BIOS: […]
Show full quote

#63
Manufacturer/Identifier: Morse 386
Chipset: UMC UM82C206L MORSE 91A311 91A310
BIOS:

Nice looking board ! I loaded bios in an Emulator and also Hex edited and got a weird bios string. Have you peeked under those Morse labels ? Am curious if they are UMC 82C480 series. Similar to #51 but different !

Thanks! Dont know, I will not remove the labels 😉 Also didnt test the board so far. It was hidden in this pile:

Bought these (retro) hardware today

Is anyone responsible for editing the entries in the BIOS threads? I see multiple user errors. As already mentioned, there are duplicate entries from users who don't verify the board hasn't already been posted before uploading. A few boards have stickers over their chipsets with the OEM name on it. We know for a fact that BIOTEQ and MORSE for example do not make chipsets. In cases we know for certain what is under the sticker the chipset entry should be edited to reflect that. I also keep seeing people listing the 82C206 system controller as the "chipset".

Horun wrote on 2020-04-28, 02:01:

Edit: And good work on finding what appears to be the correct board at MH TH99

Hehe, well I'm working on something that should interest all of you. I won't tell you more yet but it should be done in the upcoming months.

Anonymous Coward wrote on 2020-04-28, 13:14:

Is anyone responsible for editing the entries in the BIOS threads? I see multiple user errors. As already mentioned, there are duplicate entries from users who don't verify the board hasn't already been posted before uploading. A few boards have stickers over their chipsets with the OEM name on it. We know for a fact that BIOTEQ and MORSE for example do not make chipsets. In cases we know for certain what is under the sticker the chipset entry should be edited to reflect that. I also keep seeing people listing the 82C206 system controller as the "chipset".

No, nobody responsible only the uploaders.
- duplicate entries doesnt matter as there maybe different BIOS-version. I dont expect anybody checks this before uploading.
- nobody will remove a sticker to see what chip is under?
- 82C206 system controller is not part of the "chipset" but also a chip used on a board. Therefore this may help to find it, especially if other chips are hidden under labels.
So all OK for me 😉

Deksor wrote on 2020-04-28, 15:02:

Hehe, well I'm working on something that should interest all of you. I won't tell you more yet but it should be done in the upcoming months.

Hehe, curious and looking forward to see what you are doing 😉 A new database?

Well actually I've found two posts showing the same board AND the same BIOS (both had the same hash) ^^

Something that's really lacking imo is POST codes as they can sometimes be really helpful and that you can't always get them just with the ROM (for most 386s/286s I could use PCem, but for 486s it doesn't work ..).

Deksor wrote on 2020-04-26, 20:37:

You only copied half of the BIOS ! there are two ROMs. (And also you copied the first one as a 512kb rom, but it's a 256kb rom). […]
Show full quote

HanJammer wrote on 2020-04-15, 17:14:

#60 Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0) Chipset : Headland HT21A BIOS : Phoenix 07/28/91, on a 27C5 […]
Show full quote

#60
Board ID : Generic 386SX board (sometimes called HT18 Rev. 2.0)
Chipset : Headland HT21A
BIOS : Phoenix 07/28/91, on a 27C512 type ROM chip (64KB)
ID string :

You only copied half of the BIOS ! there are two ROMs. (And also you copied the first one as a 512kb rom, but it's a 256kb rom).

Also I think I've found a matching board in TH99
https://stason.org/TULARC/pc/motherboards/U/U … X-20-25-64.html

Oh great... I should have known better and use the programmer instead of relying on the NSSI to do the job... damn it 😒
I already sold this board, it's in my friend's hands, he won't be able to rip the ROMs with programmer, so maybe at least you can point me at some software we can use to rip the ROM reliably (unlike NSSI)?

Also posting the BIOSes as post in threads seems highly unreliable/hard to manage/hard to keep track of and not really logical to me - can't we use the VOGONS wiki for example instead?