First you need to enter the BIOS and set it correctly up. I spot the floppy drive are not installed correctly. Unless you only have 5,25 inch drives in the machine. Then you need to power it off and let it sit the night over, to check if there are any juice left in the dallas battery.

After all that, you need to recheck the BIOS, and find a way to write images to floppy drives. That can be done in a lot of ways, like getting an old P4 machine with a floppy drive or get a USB floppy drive for your personal main computer.

Ok so now i know why there is no battery on the board 😀 i will try to fix it and mount cell battery on top of it, like i saw its possible to do. And yes i will fix some p4 pc but why cant i boot from hdd? I have read somewhere (some hot-433 mob informations)that there is no ide controller driver of 8886AF chip in Windows 95 could this be the problem?

I have seen quite a few mobos that use the DALLAS RTC not boot / hang / black screen if the battery inside the chip is dead.
Do the CR2032 mod on the DALLAS RTC, chances are it will fix your issue.

Ok i will try it tomorrow thx for fast reply and help, its the 3rd day already that i am challenging this old pc 😀

A good overhead shot with the board completely removed and the slots and IDE/floppy connectors depopulated, with the board oriented such that the keyboard port is to the lower right, will help finding it in the line drawings here: https://stason.org/TULARC/pc/motherboards/m486_1.html

Model numbers can sometimes be found silkscreened in the space between slots. Also, the BIOS ID may show up on the bottom of the screen when attempting to boot, so that is another thing useful in identifying the board.

manczyslaw wrote:

I have read somewhere (some hot-433 mob informations)that there is no ide controller driver of 8886AF chip in Windows 95 could this be the problem?

Booting from the hard drive doesn't depend on any Windows 95 driver. Getting all the way into Windows might, but just getting the "Starting Windows 95..." on the screen doesn't.

You can get it to boot far enough to retrieve the bios ID string from the bottom of the previous screen, that will usually do nicely in identifying the board.