Mumak wrote on 2021-08-19, 08:38:

I can try that if I get the HWiNFO report + debug file. If there are some markers that could be used, it would be possible.

I had to enable "Skip PnP BIOS Calls" or it froze on the PnP discovery, as well as disable the 'Check Keyboard COntroller and Super IO"

Even with a completely clean boot I get this memory error, followed by the COMMAND.COM Error when running the report. As far as it gets though I've attached the dbg and log.

Thanks! I will try to add a workaround for the hang during SuperIO detection there. Not sure about the PnP issue yet, might be some problem in BIOS.

I have some issues running HWINFO with my old 486 system. The menu flashes and to read VGA info I have to disable the option to check RAMDAC. VGA card is STB WIND/X with S3 86C911.

sprcorreia wrote on 2021-08-30, 02:25:

I have some issues running HWINFO with my old 486 system. The menu flashes and to read VGA info I have to disable the option to check RAMDAC. VGA card is STB WIND/X with S3 86C911.

What happens with the RAMDAC option enabled, does the screen become corrupted, crashes or hangs?
Do you know what RAMDAC is on the 911 card?

Mumak wrote on 2021-08-30, 07:37:

sprcorreia wrote on 2021-08-30, 02:25:

I have some issues running HWINFO with my old 486 system. The menu flashes and to read VGA info I have to disable the option to check RAMDAC. VGA card is STB WIND/X with S3 86C911.

What happens with the RAMDAC option enabled, does the screen become corrupted, crashes or hangs?
Do you know what RAMDAC is on the 911 card?

Lots of garbage but I can still exit the program.
ADV476KN80E

sprcorreia wrote on 2021-08-30, 09:41:

Mumak wrote on 2021-08-30, 07:37:

sprcorreia wrote on 2021-08-30, 02:25:

I have some issues running HWINFO with my old 486 system. The menu flashes and to read VGA info I have to disable the option to check RAMDAC. VGA card is STB WIND/X with S3 86C911.

What happens with the RAMDAC option enabled, does the screen become corrupted, crashes or hangs?
Do you know what RAMDAC is on the 911 card?

Lots of garbage but I can still exit the program.
ADV476KN80E

Could you please export the VBIOS into a file and post here? You can also use the GETBIOS tool located in this thread. Re: HWiNFO for DOS resurrected !

Mumak wrote on 2021-08-30, 10:43:

sprcorreia wrote on 2021-08-30, 09:41:

Mumak wrote on 2021-08-30, 07:37:

What happens with the RAMDAC option enabled, does the screen become corrupted, crashes or hangs?
Do you know what RAMDAC is on the 911 card?

Lots of garbage but I can still exit the program.
ADV476KN80E

Could you please export the VBIOS into a file and post here? You can also use the GETBIOS tool located in this thread. Re: HWiNFO for DOS resurrected !

From the other post I assume that this is the one needed.

sprcorreia wrote on 2021-09-05, 13:42:

Mumak wrote on 2021-08-30, 10:43:

sprcorreia wrote on 2021-08-30, 09:41:

Lots of garbage but I can still exit the program.
ADV476KN80E

Could you please export the VBIOS into a file and post here? You can also use the GETBIOS tool located in this thread. Re: HWiNFO for DOS resurrected !

From the other post I assume that this is the one needed.

Yes, that's it, thanks. I will add a workaround for this board to automatically skip DAC test.

Is it China fake or bad detection?

Are you clocking it at 40 MHz? HWiNFO treats all 40 MHz 386DX as AMD, there were no 40 MHz Intel models.

Martin8bity wrote on 2021-09-09, 07:23:

Is it China fake or bad detection?

What kind of oscillator you have? Show us a picture of the whole board.

It is my own build of Groza 386 single board computer http://www.alexandrugroza.ro/microelectronics … sbmc/index.html. The clock is created from 14.31818 MHz crystal by SC425APB and is set to 40 MHz. Thansk for the advice, I will try to lower the clock to 33 MHz.

Unfortunately I'm not aware of any other way to distinguish an Am386DX from i386DX in software other than the 40 MHz clock. So HWiNFO will always report a 40 MHz 386DX as AMD.

How does it recognize on 33 MHz?

As i386DX-33.

Oh, I see, so there is no way to distinguish Am386 from i386 on 33 Mhzm, isn't it?

Martin8bity wrote on 2021-09-09, 13:35:

Oh, I see, so there is no way to distinguish Am386 from i386 on 33 Mhzm, isn't it?

No, such old CPUs don't have any features that would allow such distinguish.

Mumak wrote on 2021-09-09, 11:02:

Unfortunately I'm not aware of any other way to distinguish an Am386DX from i386DX in software other than the 40 MHz clock. So HWiNFO will always report a 40 MHz 386DX as AMD.

Only way I know to accurately distinguish between an AMD and Intel 386 is with the Universal Chip Analyser, but I'm not sure whether the PGA modules are available yet. Of course, if the chip is not on a motherboard and doesn't have a heatsink glues on, you'd know anyway (if it's not a fake). UCA reads JTAG info.

Martin8bity wrote on 2021-09-09, 10:47:

It is my own build of Groza 386 single board computer http://www.alexandrugroza.ro/microelectronics … sbmc/index.html. The clock is created from 14.31818 MHz crystal by SC425APB and is set to 40 MHz. Thansk for the advice, I will try to lower the clock to 33 MHz.

On that page you link:

support for 80386DX CPUs running at 16 MHz, 25 MHz, 33 MHz, and 40 MHz

Then in the "System Configuration" section:

1JP5, JP6, JP7	CPU CLK	80386DX Clock	CL, CL, OP: 16 MHz (**)
2CL, OP, OP: 25 MHz
3OP, CL, OP: 33 MHz (*)
4OP, CL, CL: 40 MHz

@Mumak

The gpu/mem clocks reported are read from the cards or is it some sort of fixed values fom a database?