Mumak wrote on 2021-05-02, 15:17:

Can you please also post the first two screens as before?

Attached...

Grzyb wrote on 2021-05-02, 15:37:

Mumak wrote on 2021-05-02, 15:17:

Can you please also post the first two screens as before?

Attached...

Thanks. Please try this new build:

If there's still some issue, please attach a new DBG file so I can check the detail.

Mumak wrote on 2021-05-02, 16:04:

Please try this new build:

OK, the Celeron is Celeron again, see the attachment...

But I can see a display glitch in the "CPU Tcase_max:" line: where there should be the degree sign, there's character #176 - "Light shade".
Shouldn't it be #248 instead?
I'm using CP437, the default for vast majority of cards.

Thanks for the feedback and testing! Degree sign shall be fixed in the next build.

Version 6.1.4 has just been released. Head to HWiNFO for DOS resurrected ! for more details.

All I can say is that I'm so happy and thankful you are maintaining this software! I'm always looking forward for the next build! Great tool!

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried it on the 386DX-40 that I recently fixed, other previous versions of your program I have used not much long ago in various PCs that I tested.
At the moment I am restarting the older PCs I have, this 386DX-40 was bought last month, at first it had some problems, but luckily I have solved them, if you want to see the progress I have made you can find it here:
Re: Test and troubleshoot PC@LIVE motherboards
I'll try to fix some 486s soon, some just need an oxide cleaning, because they have the CMOS battery to replace.

PC@LIVE wrote on 2021-07-02, 20:25:

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried […]
Show full quote

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried it on the 386DX-40 that I recently fixed, other previous versions of your program I have used not much long ago in various PCs that I tested.
At the moment I am restarting the older PCs I have, this 386DX-40 was bought last month, at first it had some problems, but luckily I have solved them, if you want to see the progress I have made you can find it here:
Re: Test and troubleshoot PC@LIVE motherboards
I'll try to fix some 486s soon, some just need an oxide cleaning, because they have the CMOS battery to replace.

Thanks for the results! It would be great if you could generate a full log + debug file (HWINFO -r -d) and attach both files produced. This is useful for my reference.

Mumak wrote on 2021-07-02, 21:16:

PC@LIVE wrote on 2021-07-02, 20:25:

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried […]
Show full quote

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried it on the 386DX-40 that I recently fixed, other previous versions of your program I have used not much long ago in various PCs that I tested.
At the moment I am restarting the older PCs I have, this 386DX-40 was bought last month, at first it had some problems, but luckily I have solved them, if you want to see the progress I have made you can find it here:
Re: Test and troubleshoot PC@LIVE motherboards
I'll try to fix some 486s soon, some just need an oxide cleaning, because they have the CMOS battery to replace.

Thanks for the results! It would be great if you could generate a full log + debug file (HWINFO -r -d) and attach both files produced. This is useful for my reference.

Please imagine, if you can suggest me how to generate them, I shouldn't have difficulty putting them online.
Currently the 386 PC has a temporary configuration, and for some time it will not be modified, but later I will make some changes, I will increase the RAM to 8MB or more, I will change the CF to another larger 128MB or 256MB, maybe I also change the VGA or I bring it to 512KB by adding a couple of RAM chips, and I will try other OS.
However if you are interested I can restart other PCs that I have on the bench, a couple of VX with P200MMX and K6-2-360, an athlon 800 (462), I also have many others that I can restart (see signature), so if you have patience as I restart them I can make your sw run on them.

PC@LIVE wrote on 2021-07-02, 21:42:

Please imagine, if you can suggest me how to generate them, I shouldn't have difficulty putting them online. Currently the 386 P […]
Show full quote

Mumak wrote on 2021-07-02, 21:16:

PC@LIVE wrote on 2021-07-02, 20:25:

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried […]
Show full quote

Hi, I just downloaded what should be the latest version (HWi614) for DOS, despite having very little space on the disk, I tried it on the 386DX-40 that I recently fixed, other previous versions of your program I have used not much long ago in various PCs that I tested.
At the moment I am restarting the older PCs I have, this 386DX-40 was bought last month, at first it had some problems, but luckily I have solved them, if you want to see the progress I have made you can find it here:
Re: Test and troubleshoot PC@LIVE motherboards
I'll try to fix some 486s soon, some just need an oxide cleaning, because they have the CMOS battery to replace.

Thanks for the results! It would be great if you could generate a full log + debug file (HWINFO -r -d) and attach both files produced. This is useful for my reference.

Please imagine, if you can suggest me how to generate them, I shouldn't have difficulty putting them online.
Currently the 386 PC has a temporary configuration, and for some time it will not be modified, but later I will make some changes, I will increase the RAM to 8MB or more, I will change the CF to another larger 128MB or 256MB, maybe I also change the VGA or I bring it to 512KB by adding a couple of RAM chips, and I will try other OS.
However if you are interested I can restart other PCs that I have on the bench, a couple of VX with P200MMX and K6-2-360, an athlon 800 (462), I also have many others that I can restart (see signature), so if you have patience as I restart them I can make your sw run on them.

Thanks, any reports are welcome. You can easily generate those files by running HWINFO with the -r and -d command-line arguments, so: HWINFO -r -d

OK thank you.
Today I tried to run it on the athlon-800, but probably because I start it inside W.ME, it doesn't work and says the DOS version is too recent.
I did as you suggested, and the program has created two files that I am attaching, the date and time are not accurate but I do not think it is important anyway.
I thought that I can easily put it on a 486-DX2-66 PC (CPU i'TS if I'm not mistaken or ST I don't remember), is it VLB with 20MB of RAM and MB PCCHIPS M949? (the one with fake L2 cache), for the cache I would have to delete the fake chips and replace them with real chips, but for the moment I don't have the chips and the time to make the switch.

Thanks! Do you know what mainboard is in the 386DX-40 system?

I don't know what model it is, from the BIOS it seems to be produced by SERITECH ENTERPRISE CO., LTD, but it is very similar to the GIGABYTE GA-386UM 33/40, on the MB there is a written TK-82C390A-4N-D11SE, I don't know if from this info you can understand exactly what it is.

A little while ago I ran your program on the 486-DX2-66 VLB, obviously I created the two files as you suggested, it was easy because I have a CF-IDE adapter instead of the HD.
The CPU I remembered was IT'S or ST, in fact it is, even if it is practically a Cyrix with different screen printing.
The MB instead is PCCHIPS but the right model is M912 (I didn't remember well), it has fake cache chips although when the BIOS starts it detects the presence of 256KB (in reality they are 0KB therefore), I installed a total of 20MB of RAM , 16MB is two 72PIN SIMMs plus four 1MB 30PIN SIMMs.
I have two floppy drives one 3.5 "1.44MB and the other 5.25" should be 1.2MB, in fact I don't know if that's the case, the drive is a TEAC FD-55GFR.
I attach the zipped files and some screenshots.

Thank you! HWiNFO did quite well here (although the ST / Cx CPU probably can't be distinguished). It also identified the mobo and absence of L2 cache.

Why on EGA/EGA Monochrome system in HWINFO for DOS font reprogramming is not used (for buttons, UI lines, windows)? For example Norton Utilities used this reprogramming with great success and better look-and-feel.

Working well for me! Just a post to say thank you, and also to submit my log for posterity.

Yes, thanks it worked well, for the CPU I think it depends on the fact that it is a Cyrix with a different brand, so it is not wrong to identify it.
Regarding the cache it rightly detects 0KB, because the present one of 256KB is fake.
Today I ran the program on another PC, an S7 P200MMX i430VX chipset, I am attaching the created files, unfortunately I have to zip them because one cannot be attached with its extension.
I will see in the next days to start other old-PCs, and run the program to create the files to attach.

b_w wrote on 2021-07-04, 16:42:

Why on EGA/EGA Monochrome system in HWINFO for DOS font reprogramming is not used (for buttons, UI lines, windows)? For example Norton Utilities used this reprogramming with great success and better look-and-feel.

Well, I guess because I never owned an EGA adapter and they are/were rather rare.. My first gfx was a VGA (CL-GD610) and there didn't even seem to be a demand for improved graphics on EGAs.

RichB93 wrote on 2021-07-04, 17:20:

Working well for me! Just a post to say thank you, and also to submit my log for posterity.

Thank you! What monitor do you have, I retrieved only its ID as EXN0000.

PC@LIVE wrote on 2021-07-04, 19:09:

Yes, thanks it worked well, for the CPU I think it depends on the fact that it is a Cyrix with a different brand, so it is not w […]
Show full quote

Yes, thanks it worked well, for the CPU I think it depends on the fact that it is a Cyrix with a different brand, so it is not wrong to identify it.
Regarding the cache it rightly detects 0KB, because the present one of 256KB is fake.
Today I ran the program on another PC, an S7 P200MMX i430VX chipset, I am attaching the created files, unfortunately I have to zip them because one cannot be attached with its extension.
I will see in the next days to start other old-PCs, and run the program to create the files to attach.

Thanks again! Looks good, is the audio adapter ALS-100 Plus ?