This appears to be a fairly close match to the motherboard in your picture: http://arvutimuuseum.ee/th99/m/I-L/33331.htm
Unfortunately, the location of all the jumpers haven't been identified on the diagram, but you should be able to find it on the motherboard.
This should then allow you to at least configure the motherboard properly.

Thank you very much jesolo!
This indeed looks very much like my board and even though the location of jumpers is not specified, there is quite complete description of those. This will help me a lot, appreciate very much!

That manual sais the board has Phoenix bios, and from this http://www.bioscentral.com/postcodes/phoenixbios.htm link I see that 0d is RAM parity failure in first 64K, makes a lot of sense since the 0d code was preceded by 09 (first 64K memory test). This means something is wrong with the chipset or the board, probably. I will inspect if further to check for voltages etc on the RAM slots. The board is old so it might need some treatment. Maybe getting the battery on and resetting the CMOS memory will help, as there might be some garbage in the unpowered CMOS upon starting that might result in some inadequate timings etc.
Now I have hope )

No problem - the only snag is that they don't specify the size of the TAG & Dirty RAM cache modules (although, I must admit, I've never heard of "dirty" ram).
Someone else here on Vogons should be able to provide more insight into this and probably also be able to tell you what the possible sizes should be, depending on what cache memory you install on the motherboard.
Fortunately, there is a jumper on the motherboard (J34) to disable the onboard cache. However, I would later on try to install some cache RAM, as this will improve performance.

jesolo wrote:

No problem - the only snag is that they don't specify the size of the TAG & Dirty RAM cache modules (although, I must admit, I've never heard of "dirty" ram).
Someone else here on Vogons should be able to provide more insight into this and probably also be able to tell you what the possible sizes should be, depending on what cache memory you install on the motherboard.
Fortunately, there is a jumper on the motherboard (J34) to disable the onboard cache. However, I would later on try to install some cache RAM, as this will improve performance.

I will definitely try to start it as naked as possible first, with no cache and on lowest frequency possible, but if it comes back to life I will of course need to plug some cache in and any advice is highly appreciated.

Here's another file I found online - although, it doesn't say much more, compared to what I've already sent.

jesolo wrote:

Here's another file I found online - although, it doesn't say much more, compared to what I've already sent.

appreciate very much, every bit helps!

I have checked the configuration of the board according to the manuals, but it was configured correctly and all the necessary voltages were on, I still get the parity error. Maybe the board needs a parity RAM. I have bought small parity FPM SIMM module on the ebay to test the board with it when it arrives. A pitty if the board is dead, it suits me just fine - the first 486 board I see to support 16 and 20 MHz CPUs, plus all the necessary controllers are embedded: LPT, COM, Floppy, IDE... And if I desolder the DIN-5 keyboard connector there are pads for PS/2 keyboard and mouse connectors under it. So I would love to make it work...

Try "clearing" your CMOS settings - there is a jumper for it.
Are you able to enter the BIOS setup screen? If so, you can try and load the BIOS Setup Defaults.

I've tried clearing CMOS with the jumper, it didn't help, although I have not tried plugging the battery in yet, so it might be the source of the problem too. I will try it as soon as I get hold of a proper connector, did not manage to find anything suitable for that at home.

But so far no POST, black screen is all I get.
Thank you vm for your help jesolo!

Ah and there is one more thing that bothers me. I use ATX->AT adaptor cable to power the board from ATX power source. And being a cheap piece it lacks -5V rail. So might be another candidate for trouble source

Don't think the absence of a -5V rail would prevent the motherboard from posting.
However, it could be a memory problem or, as you mentioned, the fact that there is no battery - normally it would give you a low battery warning in the POST screen.

If you do connect an external battery, just be sure to select the correct jumper settings and also check whether you need to connect a rechargeable or non chargeable battery pack, depending on your jumper settings.

Yeah, I have not found the jumper to choose between rechargeable/non-rechargeable battery on the board, and there is no battery on the board, so i would assume it will not charge anything, but there is a switch to choose between battery voltage (3.4V or 6V). I think I can measure the voltage on the battery pins when the board is powered up and there is no battery connected to see if the board provides a charging current when running... But for a test i will use a battery anyway, even if it gets damaged by the charging current, it should last enough for me to see if the absence of the battery causes the mobo not to POST or not, I think.

If you can measure the voltage on the battery pins and also confirm whether the board provides a charging current, then that would be great.
The last thing you want to do is to connect a non chargeable battery (for an extended period) when the motherboard is providing a charging current.

jesolo wrote:

The last thing you want to do is to connect a non chargeable battery (for an extended period) when the motherboard is providing a charging current.

indeed, it's not the best place for any fireworks ))

OK, so the Parity SIMM arrived, and we have something...

First of all, I wanted to mention that not only this board requires Parity FPM RAM to run, but it needs the only module to be installed in the upmost SIMM slot. But then it runs

Although not quite completely... I didn't have time to solder on the PS/2 keyb/mouse connectors and I do not have an AT keyboard, but it is not the biggest problem in the world anyway. The problem is I believe the mobo does not have BIOS SETUP in ROM. So it is like one of those HP Server boards, it boots and needs you to run a DOS setup utility to alter NVRAM. I believe I am going to have some very tough time finding this utility as I do not even know who was the maker of the PC with this board. Well, good luck me.

So far all I have is this (which is already quite cool to me):

You could try to figure out what the original boot device was (if it was attached to the on-board connectors), and see whether it will boot from that device if some OS is provided there. That would allow you to then run additional diagnostics. This of course assumes that the ISA configuration error and the boot device error are separate...

yawetaG wrote:

You could try to figure out what the original boot device was (if it was attached to the on-board connectors), and see whether it will boot from that device if some OS is provided there. That would allow you to then run additional diagnostics. This of course assumes that the ISA configuration error and the boot device error are separate...

Yes, I will try to hook up the floppy emulator and an IDE HDD with DOS installed later on, after I solder on the PS/2 connectors, as with no keyboard it would not let me pass the POST.
I have also found a Phoenix DOS setup utility here (sorry the website is in Russian but it basically sais that there is a utility (link below the screenshot) that can be run under plain DOS and would let you read/write to CMOS for Phoenix BIOS in case you are unable to enter the BIOS setup during POST): http://vsevinfo.ru/Phoenix/index.htm, I will try that as well.

I think a PS/2 to AT keyboard adapter will also help:

http://cable-trader.co.uk/items/ps2-female-to … eyboard-adapter

tayyare wrote:

I think a PS/2 to AT keyboard adapter will also help:

sure, but in this case I need to order one and wait for it to arrive. On the other hand, the mobo has all the necessary trace routing for both Keyboard and mouse PS/2 connectors (probably there were versions with PS/2 headers instead of AT), so I just need to do some soldering, 20-30 minutes of work. And I like the look of PS/2 connectors better ))
I have even made interposers to redo all my AT boards that do not have PS/2 soldering pads routed on the PCB to fit PS/2 keyboard connectors.

ok, so I soldered on the PS2 keyboard connector. For the PS2 mouse the pcb lacks some smd chokes and capacitors that I yet have to find out nominal for before soldering on. Otherwise, this was a success. The board detected the keyboard and the floppy emulator. And - It has printed "Press F1 to enter BIOS Setup" to me. What a charm!

Working in DOS: