VOGONS


HWiNFO for DOS resurrected !

Topic actions

Reply 740 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
andunn wrote on 2021-10-21, 09:00:

Sure, here it is.

Thanks. I tried to adjust reporting of the FPU to show IIT4C87DLC and proper clock. Can you please try this build and let me know the result:

Filename
HWINF615.ZIP
File size
995.18 KiB
Downloads
27 downloads
File license
Fair use/fair dealing exception

Reply 741 of 808, by ALEKS

User metadata
Rank Newbie
Rank
Newbie

Hi Martin,

Just out of curiosity, I was trying HWiNFO 4.6.4 (I know it's too old, don't ask!) to compare to 6.1.3 on the CX486DLC CPU (well actually I have the TX version but they are basically the same CPU).

For the CPU itself HWiNFO 6.1.3 shows the correct and complete name.
But for the FPU, HWiNFO 4 shows the TM text on the FasMath name but 6.1.3 does not. Is this as expected? The FPU has TM in its name, for sure. It's even written on top of the ceramic package.
Also on version 4 the name of the BIOS is completely spelled as Microid Research while the new one is trimmed down. Again, is it as expected?

hwinfo4.jpg
Filename
hwinfo4.jpg
File size
364.48 KiB
Views
681 views
File license
Fair use/fair dealing exception
hfinfo613.jpg
Filename
hfinfo613.jpg
File size
393.65 KiB
Views
681 views
File license
Fair use/fair dealing exception

I have one additional question: regarding the differences in CPU vs. FPU frequency. I have noticed differences with the 386/387 pair as well. Is the frequency display inferred from some kind of software algorithm? And if so, can't it be made more accurate? It's not an issue by itself. But practically in these kind of systems, the CPU and FPU all run on the same CLK2 signal.

Thanks,
Alex

TX486DLC / 40 MHz | 32 Mb RAM | Tseng Labs ET4000/W32i with 2 Mb RAM | ISA I/O Interface | ISA Audio Interface | 3.5" & 5.25" FDD | 4 x 512 Mb CF | Intel EtherExpress 16

Reply 742 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
ALEKS wrote on 2021-10-31, 11:19:
Hi Martin, […]
Show full quote

Hi Martin,

Just out of curiosity, I was trying HWiNFO 4.6.4 (I know it's too old, don't ask!) to compare to 6.1.3 on the CX486DLC CPU (well actually I have the TX version but they are basically the same CPU).

For the CPU itself HWiNFO 6.1.3 shows the correct and complete name.
But for the FPU, HWiNFO 4 shows the TM text on the FasMath name but 6.1.3 does not. Is this as expected? The FPU has TM in its name, for sure. It's even written on top of the ceramic package.
Also on version 4 the name of the BIOS is completely spelled as Microid Research while the new one is trimmed down. Again, is it as expected?

hwinfo4.jpg

hfinfo613.jpg

I have one additional question: regarding the differences in CPU vs. FPU frequency. I have noticed differences with the 386/387 pair as well. Is the frequency display inferred from some kind of software algorithm? And if so, can't it be made more accurate? It's not an issue by itself. But practically in these kind of systems, the CPU and FPU all run on the same CLK2 signal.

Thanks,
Alex

The trademark symbol has been removed in later versions, it doesn't make much sense to display this.
I will update HWiNFO to show full "Microid Research" BIOS manufacturer.
FPU frequency is determined by measuring time required to execute a batch of FPU instructions. This requires exact knowledge of FPU present and how many clock cycles the instruction takes. There's no other precise method available and if the FPU is not properly recognized or the amount of clock cycles not exactly known (which is often the case due to lack of detailed documentation), the result won't be correct.

Reply 743 of 808, by andunn

User metadata
Rank Newbie
Rank
Newbie
Mumak wrote on 2021-10-21, 09:39:

I tried to adjust reporting of the FPU to show IIT4C87DLC and proper clock.

Those seem to be fixed, see results attached.

Attachments

  • 2021-11-01-21.00.42.jpg
    Filename
    2021-11-01-21.00.42.jpg
    File size
    176.21 KiB
    Views
    640 views
    File license
    Fair use/fair dealing exception
  • Filename
    HWINF_8570.zip
    File size
    3.54 KiB
    Downloads
    13 downloads
    File license
    Fair use/fair dealing exception

Reply 744 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
andunn wrote on 2021-11-01, 19:27:
Mumak wrote on 2021-10-21, 09:39:

I tried to adjust reporting of the FPU to show IIT4C87DLC and proper clock.

Those seem to be fixed, see results attached.

Looks great, thanks!

Reply 745 of 808, by ALEKS

User metadata
Rank Newbie
Rank
Newbie

Where is the "computer name" string read from? I have seen that only some mainboards report such a name. Is it an identifier within the BIOS? Or a specific BIOS function that returns this string?

Thanks,
A.

TX486DLC / 40 MHz | 32 Mb RAM | Tseng Labs ET4000/W32i with 2 Mb RAM | ISA I/O Interface | ISA Audio Interface | 3.5" & 5.25" FDD | 4 x 512 Mb CF | Intel EtherExpress 16

Reply 746 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
ALEKS wrote on 2021-11-02, 15:46:

Where is the "computer name" string read from? I have seen that only some mainboards report such a name. Is it an identifier within the BIOS? Or a specific BIOS function that returns this string?

Thanks,
A.

That depends on system, there are several methods used. In most cases it's a string read from BIOS, in a few others it's based on some IDs or functions.

Reply 747 of 808, by FlashCade

User metadata
Rank Newbie
Rank
Newbie
Mumak wrote on 2021-04-05, 17:57:

If there would be a demand for an 8086-80286 version I can start work on such project.

Hello, it would be very interesting for these old machines.
I'll add: +1
Thanks for your efforts, the 386 version is still awesome.

IBM Ps-2 model 30 (8086 / Nec v30) - Tridend 8900d 1024 ram - floppy 720 kb - HDD 20 Mb (KO) - XT CF-Lite v4.1 with 1GB CF Microdrive IBM

Reply 748 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
FlashCade wrote on 2021-11-21, 14:01:
Hello, it would be very interesting for these old machines. I'll add: +1 Thanks for your efforts, the 386 version is still aweso […]
Show full quote
Mumak wrote on 2021-04-05, 17:57:

If there would be a demand for an 8086-80286 version I can start work on such project.

Hello, it would be very interesting for these old machines.
I'll add: +1
Thanks for your efforts, the 386 version is still awesome.

I have just released HWiNFO16 for 8086-286 systems: Introducing HWiNFO16 (for 8086/88/186/188/286)
Any feedback is welcome.

Reply 749 of 808, by feipoa

User metadata
Rank l33t++
Rank
l33t++
Mumak wrote on 2021-11-23, 13:21:

I have just released HWiNFO16 for 8086-286 systems: Introducing HWiNFO16 (for 8086/88/186/188/286)
Any feedback is welcome.

Nice! I will be setting up at 286 sometime in 2022.

Ultimate 486 Benchmark | Ultimate 686 Benchmark | Cyrix 5x86 Enhancements | 486 Overkill Graphics | Worlds Fastest 486

Reply 752 of 808, by ruthan

User metadata
Rank Oldbie
Rank
Oldbie

Is possible to merge 286 a 386+ version to one and on the fly detect on which machine is HWinfo running and run right code?

Im old goal oriented goatman, i care about facts and freedom, not about egos+prejudices. Hoarding=sickness. If you want respect, gain it by your behavior. I hate stupid SW limits, SW=virtual world, everything should be possible if you have enough raw HW.

Reply 753 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
ruthan wrote on 2021-12-04, 11:19:

Is possible to merge 286 a 386+ version to one and on the fly detect on which machine is HWinfo running and run right code?

HWiNFO (386) is already requiring a lot of system memory to fit, yet it's possible to keep it by using the 386 (32-bit) instruction set which reduces size. Including 286-capable code would result in a significant increase in size.

Reply 754 of 808, by ruthan

User metadata
Rank Oldbie
Rank
Oldbie

Still it seems possible in theory make some starter .exe to detect on which machine is program running and after than run 386+ or 286 exe.. Only disadvantage which i see is bigger program size.. Of course with more clever method (use only 286 code for start detect machine and after by some if and else use or not use some 386 instructions.. )

Im old goal oriented goatman, i care about facts and freedom, not about egos+prejudices. Hoarding=sickness. If you want respect, gain it by your behavior. I hate stupid SW limits, SW=virtual world, everything should be possible if you have enough raw HW.

Reply 755 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie

It would be possible to create a launcher that based on a quick CPU check would run either HWINFO or HWINFO16.
But duplicating the same methods using 286 and 386 set in the same program doesn't make much sense. And there would have to be a 8086 version anyway...

Reply 756 of 808, by ruthan

User metadata
Rank Oldbie
Rank
Oldbie

Its not possible make 386 + 086-286? We would need 3 versions?

Im old goal oriented goatman, i care about facts and freedom, not about egos+prejudices. Hoarding=sickness. If you want respect, gain it by your behavior. I hate stupid SW limits, SW=virtual world, everything should be possible if you have enough raw HW.

Reply 758 of 808, by soggi

User metadata
Rank Member
Rank
Member

Hey Mumak,

some years ago I decided to mirror HWiNFO v5.5.5 (in the tools section of my website -> soggi.org - tools) as development had stopped back then and I was afraid that it will vanish from your website - I always want to preserve great tools (and many other things).

Now where you restarted development I just want to ask, if it's still OK to mirror HWiNFO for DOS / HWiNFO16!? There will also be a link to this thread to reach the ongoing support.

kind regards
soggi

Vintage BIOSes, firmware, drivers, tools, manuals and (3dfx) game patches -> soggi's BIOS & Firmware Page

soggi.org on Twitter - talent borrows, genius steals...

Reply 759 of 808, by Mumak

User metadata
Rank Oldbie
Rank
Oldbie
soggi wrote on 2021-12-06, 15:02:
Hey Mumak, […]
Show full quote

Hey Mumak,

some years ago I decided to mirror HWiNFO v5.5.5 (in the tools section of my website -> soggi.org - tools) as development had stopped back then and I was afraid that it will vanish from your website - I always want to preserve great tools (and many other things).

Now where you restarted development I just want to ask, if it's still OK to mirror HWiNFO for DOS / HWiNFO16!? There will also be a link to this thread to reach the ongoing support.

kind regards
soggi

Of course, feel free to do so 😀