VOGONS


BIOS image collection - requests, discussion etc

Topic actions

First post, by Predator99

User metadata
Rank l33t
Rank
l33t

...for discussion + requests etc of

80286 BIOS image collection
80286 BIOS image collection

80386 BIOS image collection
80386 BIOS image collection

80486 BIOS image collection
80486 BIOS image collection

XT BIOS image collection
XT BIOS image collection

Socket 4, 5, 7 BIOS image collection
Socket 4, 5, 7 BIOS image collection

EGA Video cards - BIOS image collection
EGA Video cards - BIOS image collection

Links to other sites:
http://chukaev.ru54.com/bios_cs_en.htm
http://chukaev.ru54.com/bios_en.htm[/quote]

Thanks for your contributions!

Last edited by Predator99 on 2020-11-10, 10:41. Edited 7 times in total.

Reply 1 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t
Anonymous Coward wrote:

Might I suggest also indicating which BIOS the board is using? Both the manufacturer, and the version number.

Maybe we can addd as option? Main goal should be to have a BIOS to get a Board running, not to have the latest revision. Especially when the BIOS is divided in H+L its difficult to see the Version in the file itself and I think it makes too much work to power on the board for every upload.

ATauenis wrote:
#16 Manufacturer/Identifier: Unknown rev.03 (looks like Magitronic TK-82C491-386-4N-D02C/US Technologies TK-82C491, 493 386-4N-D […]
Show full quote

#16
Manufacturer/Identifier: Unknown rev.03 (looks like Magitronic TK-82C491-386-4N-D02C/US Technologies TK-82C491, 493 386-4N-D04/UM386 GRN/no-name 386-GRN).
Chipset: UMC UM82C491F
BIOS ID: 08/30/93-UMC-491-214X2000-OO
P1140892.1527279638.jpg
BIOS:

386grn-like.zip

#almost all other (but w/o images):
http://chukaev.ru54.com/bios_cs_en.htm
http://chukaev.ru54.com/bios_en.htm

Yes I know these links but I dont think this is very complete. I have added it above.

Can you please also upload your image directly at Vogons? I see many old threads here with linked images from other sites that doesnt work anymore...therefore Vogons is the best option?

Reply 2 of 288, by ATauenis

User metadata
Rank Member
Rank
Member
Predator99 wrote:

Can you please also upload your image directly at Vogons? I see many old threads here with linked images from other sites that doesnt work anymore...therefore Vogons is the best option?

Okay, reuploaded to Vogons.

2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.

Reply 3 of 288, by Deksor

User metadata
Rank l33t
Rank
l33t

80486 BIOS image collection
Hmm I'm not sure if that one should be counted as a 486, this is a IBM 486slc which is pretty much a "386SX2" with internal cache

Trying to identify old hardware ? Visit The retro web - Project's thread The Retro Web project - a stason.org/TH99 alternative

Reply 4 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t

Indeed, its in between. Didnt find too much about this board. This is most informative, but dont know if all is true:

https://www.almostallexports.com/products/ryc … it-isa-opti-ami

"RYC" ALARIS LEOPARD LX REV D
Vintage 286-type Motherboard
made by Alaris for IBM in 1993
with 386-class IBM-486SLC2-50 50MHz CPU soldered on
motherboard IBM P/N: FRU: 61G7659
Baby-AT form Factor small - about 9"x9"
this is basically an "AT" 286 and 386SX 16-bit motherboard with a 32bit 486 CPU
that has a 16-bit external bus (ie. the 486SLC CPU)
so hardware (cards, etc) see this as a 286 motherboard but software
sees this as a 486SX and if a 387sx CoPro is added then software sees this as a 486DX
CPU: IBM 50G6950 clock doubled, 386SX pinout, 486SX intruction set, 16KB cache CPU
Seven full-length 16-bit ISA slots
Made in 1993 by Alaris
Based on the OPTI 82C283 chip and Samsung KS83C206Q
the BIOS setup has specific parameters for tuning the CPU and chipset
such as "Pipeline Mode" and 82C286 Access Wait state
Eight 30-pin RAM slots - comes with 16MB RAM - can handle 32MB RAM

AMI BIOS ID: 30-0100-006328-00101111-060692-OPSXPI-H
HEY NEAT!! This BIOS has built-in HARD DISK UTILITY for MFM/RLL/ESDI hard drive
testing and low-level-formatting. You won't see that on many 486 motherboards !!!
This configuration will run Win95 with ease,
addition of a Math Copro will turn this into a 50MHz 486DX

Reply 5 of 288, by einr

User metadata
Rank Member
Rank
Member

I was going to upload BIOS for the M Technology R418 486 PCI board, but I'd better check first how to best do it:

There are four BIOS images for four board variations: Award or AMI BIOS and SMC or Winbond super I/O chip. The ones with Award BIOS are R418W2 and the ones with AMIBIOS are R418A2. There is no model number difference between the I/O chips so you need to check which one you have.

Not sure what format would be best to use for the post. These are all essentially the same board but four different variants. They all look the same, except the markings on the chips. Do I make one post, two or four?

Reply 7 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

@Predator99 may I ask you how you dump the BIOS ROMs? (Eprom reader vs. NSSI vs. DEBUG). I started adding the 80286 ROMs to the MAME emulator, and at least #2 and #3 in your 80286 thread have the EPROM type visible in the photo (27256 = 32KB) but your dumps are 64KB and duplicate the content.
Heads up for the great project, though! I'll go through my stuff as well and add what I have.

BTW your #2's ROM from the 80286 collection is identical to one MAME has for a "Magitronic B233" board.

Reply 9 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t
rfka01 wrote:

@Predator99 may I ask you how you dump the BIOS ROMs? (Eprom reader vs. NSSI vs. DEBUG). I started adding the 80286 ROMs to the MAME emulator, and at least #2 and #3 in your 80286 thread have the EPROM type visible in the photo (27256 = 32KB) but your dumps are 64KB and duplicate the content.

Indeed. Most of my ROMs are dumped with a TL866. I Selected a 64k ROM for reading as standard. Most times there is a label on the EPROM so you cannot determine its size anyway. And with 64k you are on the safe side. In case its only a 32k ROM its content is duplicate.
I have only read the soldered ones with NSSI/debug.

rfka01 wrote:

Heads up for the great project, though! I'll go through my stuff as well and add what I have.

Thanks, I am happy its useful for somebody and also thanks to the other contributors.

rfka01 wrote:

BTW your #2's ROM from the 80286 collection is identical to one MAME has for a "Magitronic B233" board.

Thats possible. I also think that most 286 ROMs are interchangable, but havent verified this so far.

dorkbert wrote:

Any thought of adding video BIOS to the collection?

Why not? Not sure if there is much demand for it however?

Reply 10 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

Thanks for the explanation! Do you have 80286 board #1 (the AMI before they became American Megatrends) in a working condition?
I ask because the ROMs somehow don't line up for the usual jump vector at at the end of the ROM and it ends up going into the weeds - yet it looks like a bog standard early family pizza size 80286 board.
If it isn't too much of a hassle, could you dump the ROMs again?

Reply 11 of 288, by flakes

User metadata
Rank Newbie
Rank
Newbie

Is there any chance the Test / Diag BIOS(s) can also be added to the listings? I know a few exist but not in an easy to reach area like the other BIOS you have listed.

Reply 12 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t
rfka01 wrote:

Thanks for the explanation! Do you have 80286 board #1 (the AMI before they became American Megatrends) in a working condition?
I ask because the ROMs somehow don't line up for the usual jump vector at at the end of the ROM and it ends up going into the weeds - yet it looks like a bog standard early family pizza size 80286 board.
If it isn't too much of a hassle, could you dump the ROMs again?

I still own this board but I have to Check again if its running or not. on my Photo CPU is missing but this doesnt mean anything. Give me some days..Will take a look at the dumps later.

Reply 13 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t

Already checked, the 286 #1 is running. Added a screenshot in the other thread. Both dumps have strings inside...

Date - 06/12/86. (C)Copyright Access Methods Inc. 1985, 1986. All rights reserved. 590 Valley Road, Upper Montclair, New Jersey - 07043. Phone no. (201)-744-9126

...so I have no doubt they are correct and I dont see any reason to re-read them. Do the other ROMs work in the emulator but this one not?

Maybe I will add a CF-card and dump with debug...tomorrow 😉

Reply 14 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

Thanks for checking! BIOS #s 2-4 are working after trimming them down to 32K, #2 was already in.

If you can, please dump it via DEBUG - usually seeing a botched jump vector means I'm loading the ROMs incorrectly, (e.g. odd instead of even and vice versa). If all else fails I'll pass that one to the developers 😀

0000.png
Filename
0000.png
File size
4.88 KiB
Views
6257 views
File license
Fair use/fair dealing exception
0001.png
Filename
0001.png
File size
4.81 KiB
Views
6257 views
File license
Fair use/fair dealing exception

Reply 15 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t

Hi, cool, thanks for trying that!

Can you do me a favor? Can you check this ROM
Re: Suntac 80286 Mainboards

(AWARD 3.03HLS) in your Emulator? I like to get it running in an emulator but PCem refuses it...some other people also tried.

I am currently dealing with 286#1. I combined the images and get a file of 128kb. Both 64 kb parts are identical. It contains some strings and a JMP instruction at offset FFF0 (EA6A8092F0). So it seems to be valid?
It did a quick try to get DOS booted on the board. XT-IDE detected my CF, but didnt load its content. Dont have more time and energy for trying. Maybe I will extract the ROMs again to verify...

Last edited by Predator99 on 2019-07-27, 07:33. Edited 1 time in total.

Reply 16 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

It's working in MAME, I just booted an image of DR-DOS 3.41
The "refresh timing error" persists after setting the information in the BIOS, so it's aware it's not running on the real thing.

0001.png
Filename
0001.png
File size
7.39 KiB
Views
6236 views
File license
Fair use/fair dealing exception

Reply 17 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

The access methods BIOS dump is strange, the standard value at location F0000 is 0f000h:0e05bh instrucion (far jmp). The first screenshot is from the MAME debugger window showing the SUNTAC BIOS from befor as a comparison.

standard.jpg
Filename
standard.jpg
File size
96.49 KiB
Views
6231 views
File license
Fair use/fair dealing exception

The access methods BIOS looks like this instead at the relevant address:

access methods.jpg
Filename
access methods.jpg
File size
96.36 KiB
Views
6231 views
File license
Fair use/fair dealing exception

I don't know enough about the hardware and the emulation, but my take on this is: If you can dump the top 64K from the running system, and it has the standard JMP vector (and will run), then it's the emulator's fault for not providing the equivalent of the address jumbling that's taking place with the EPROMs on the real hardware.

Robert

Reply 18 of 288, by Predator99

User metadata
Rank l33t
Rank
l33t

MANY THANKS for trying the AWARD 3.03HLS BIOS! I need to give MAME a try...!

Regarding the 286#1 ROM: I verified the ROMs and there was indeed an error in the 2nd file 🙁 I am very sorry for this and your wasted time...dont have an explanation, it must have been a loose contact while reading the 1st time. Already fixed the file. Also tried in in PCem and its working. Also tried these ROM in a Suntac-ST62-Board I have and its also working there. Supporting the assumption that the 286-ROMs have a high degree of compatibility. Even more a surprise the AWARD 3.03HLS from the Suntac board does not work in PCem but the 286#1 image does...

Reply 19 of 288, by rfka01

User metadata
Rank Newbie
Rank
Newbie

No wasted time at all! By adding the ROMs to MAME we find these errors, your archive is meant for people to experinent and repair their boards, this aligns very well with MAME's purpose. I'll post here if any others give me grief.
It's not in mainline MAME yet as I have to push it to GIT and hope it'll be included before the next official MAME release. If not it'll be in the one after that.

new dump.jpg
Filename
new dump.jpg
File size
96.38 KiB
Views
6200 views
File license
Fair use/fair dealing exception

Looks much better now ... and runs!

0002.png
Filename
0002.png
File size
3.98 KiB
Views
6199 views
File license
Fair use/fair dealing exception

I don't know how to add new stuff to PCem, so my only hint is that in this case you dumped the ROMs as two 16K files - the other 286 BIOS are 32K files. Maybe you need to change some loading parameter in PCem or if all else fails pad the ROMs with FFs at the beginning to inflate them to 32K.

In the MAME source, loading files of different lengths looks like this:

// Access Methods Inc. for Flying Triumph (AMI before they became American Megatrends) - BIOS String: Ref. no. 1406-061296
// complains about "Channel-2 timer not funcional but boots
ROM_SYSTEM_BIOS(26, "ami_ft", "AMI Flying Triumph")
ROMX_LOAD( "286_access_methods_rom2_32k.bin", 0x10000, 0x8000, CRC(749c65af) SHA1(7c6e9e217afe020b7b36785549fdbfb89de8f872), ROM_SKIP(1) | ROM_BIOS(26) )
ROMX_LOAD( "286_access_methods_rom4_32k.bin", 0x10001, 0x8000, CRC(0f15581a) SHA1(2a22635f30388ca371f0f1f31652cfa647bb322d), ROM_SKIP(1) | ROM_BIOS(26) )
// BIOS ROMs are marked TCI, Award 286 Modular BIOS Version 3.03HLS
// complains about "refresh timing error, but works
ROM_SYSTEM_BIOS(27, "tci_suntac", "tci_suntac")
ROMX_LOAD( "suntac_80286_lo.bin", 0x18000, 0x4000, CRC(f7bf6c49) SHA1(d8e813c264008f096006f46b90769c0927e44da9), ROM_SKIP(1) | ROM_BIOS(27) )
ROMX_LOAD( "suntac_80286_hi.bin", 0x18001, 0x4000, CRC(5f382e78) SHA1(8ba222df9d7028513e37978598d8139906e8834c), ROM_SKIP(1) | ROM_BIOS(27) )
ROM_END

You can see how the loading address relative to the reserved area for BIOS roms changes for the length of the BIOS files.

Last edited by rfka01 on 2019-07-27, 11:35. Edited 1 time in total.