Interesting, Ill give this a whirl on some of my 386/486 systems. While I think many people will always crave for more, I personally think 386 is a very reasonable starting point.

Thanks for the hard work in updating this great tool!

Excellent news! Thank you!

A tool that I used a lot back in the late '90s (together with Dr.Hardware), thanks for reviving it!

Approximately which range of systems will this run on, e.g. from 386SX up to Athlon XP and the Pentium 4?

WOOHOO! I’ve been hoping and praying for this for a long time! Thank you!

386+ is fine, of course, but a 16-bit version I would LOVE as well, if possible.

Sweet, thank you! Do you have any specific plans for further developing it? The last time I've checked 5.5.5 it was one of the better tools for PS/2 systems - it did identify them and even some adapters correctly, but also managed to hang my PS/2 95A and could not provide much information about SCSI drives (no model/manufacturer).

thanks for the update !!! I have now added it to my testing/checking CF card 😀
it correctly detected the test system I used it with

feipoa wrote on 2020-03-19, 03:41:

Approximately which range of systems will this run on, e.g. from 386SX up to Athlon XP and the Pentium 4?

Currently it's 386SX up to approx. Intel Core family, perhaps a few newer too. But later ones might lack a few things as I scrapped some support to save memory. I don't expect users of those system to be running DOS.
So Athlon XP and Pentium 4 are supported in the DOS version for sure.

keropi wrote on 2020-03-19, 08:32:

thanks for the update !!! I have now added it to my testing/checking CF card :) it correctly detected the test system I used it […]
Show full quote

thanks for the update !!! I have now added it to my testing/checking CF card 😀
it correctly detected the test system I used it with

Thank you that looks nice. Since this is a rare system, could you please attach the report file for my reference ? You can create it automatically by running "HWINFO -r" or pressing the F2 key stores the actual screen content into HWiNFO.LOG file.

GL1zdA wrote on 2020-03-19, 07:30:

Sweet, thank you! Do you have any specific plans for further developing it? The last time I've checked 5.5.5 it was one of the better tools for PS/2 systems - it did identify them and even some adapters correctly, but also managed to hang my PS/2 95A and could not provide much information about SCSI drives (no model/manufacturer).

Yes, I have a plan to continue development here, although it's not easy to add support/fix things on such systems without having direct access.
SCSI controllers use proprietary internal protocols, so SCSI drives are detected in the DOS version only if ASPI is installed.
If you encounter any issue, please let me know more details about the system and exact place what's wrong or where it is hanging/crashing.

Mumak wrote on 2020-03-19, 08:41:

Thank you that looks nice. Since this is a rare system, could you please attach the report file for my reference ? You can create it automatically by running "HWINFO -r" or pressing the F2 key stores the actual screen content into HWiNFO.LOG file.

I tried with the -r parameter and it just hangs forever at the "Memory Information" portion of the report creation - if you tell me what to do I will try it
edit: yeah it also hangs (no freeze) when I select one of the memory items in the System info page

this is the mobo in question

keropi wrote on 2020-03-19, 09:12:

I tried with the -r parameter and it just hangs forever at the "Memory Information" portion of the report creation - if you tell […]
Show full quote

Mumak wrote on 2020-03-19, 08:41:

Thank you that looks nice. Since this is a rare system, could you please attach the report file for my reference ? You can create it automatically by running "HWINFO -r" or pressing the F2 key stores the actual screen content into HWiNFO.LOG file.

I tried with the -r parameter and it just hangs forever at the "Memory Information" portion of the report creation - if you tell me what to do I will try it
edit: yeah it also hangs (no freeze) when I select one of the memory items in the System info page

this is the mobo in question

Is that the same mobo you posted a screenshot above?
Can you please store manually the screens that work using F2 key to a log file and take a picture of the screen where it hangs?

yep I can! gimme some mins

allright I am attaching the log and the screen where the system waits for an eternity 😁

edit:
this screen also hangs on my 2nd different 386DX mobo, maybe it's a bug ?

keropi wrote on 2020-03-19, 09:33:

allright I am attaching the log and the screen where the system waits for an eternity :D […]
Show full quote

allright I am attaching the log and the screen where the system waits for an eternity 😁

edit:
this screen also hangs on my 2nd different 386DX mobo, maybe it's a bug ?

Thank you, please give me some time to analyze this. I also need to check why the CPU isn't reported properly as TI.

keropi wrote on 2020-03-19, 09:33:

allright I am attaching the log and the screen where the system waits for an eternity :D […]
Show full quote

allright I am attaching the log and the screen where the system waits for an eternity 😁

edit:
this screen also hangs on my 2nd different 386DX mobo, maybe it's a bug ?

OK, I think I found a problem in the memory screen. Can you please try this version and let me know the result:

Awesome work - THX!

Mumak wrote on 2020-03-19, 13:10:

OK, I think I found a problem in the memory screen. Can you please try this version and let me know the result: HWINF601.ZIP

allright! it no longer hangs - and I believe as expected there is no info on the memory modules because there is no way to get such info from 30pin simms 😁

so I believe for now all is working well! thanks!