Nx586 PCI throws Fatal Error (real mode)

mt777 wrote on 2022-04-25, 01:29:

Nx586 PCI throws Fatal Error (real mode)

Please run with -d switch and attach the HWINFO.DBG file it generated.

I a little helped with Nexgen but must give due to lacking of time for continously checking.
So if someone else can test then can ask for 6.21 version

Posting version 6.21 (which fixes Nx586 detection) into initial post for anyone willing to test.

got "Fatal Error" when starting, DBG log:

1VidMode=3
2DispComb=8
3HWiNFO v6.2.1 
4Flushing disk caches ...
5
6Reading Data ...
7
8DetectCPU - 586
9CPUID=513
10Check Cx
11Cx[C2]=FF
12Cx[C3]=FF
13Cx[C0]=FF
14Cx[C2]=FF
15Cx[C3]=FF
16Cx[C0]=FF
17CxType=0
18Check Potomac

roytam1 wrote on 2022-05-28, 14:09:

got "Fatal Error" when starting, DBG log: […]
Show full quote

got "Fatal Error" when starting, DBG log:

Copy code to clipboard

1VidMode=3
2DispComb=8
3HWiNFO v6.2.1 
4Flushing disk caches ...
5
6Reading Data ...
7
8DetectCPU - 586
9CPUID=513
10Check Cx
11Cx[C2]=FF
12Cx[C3]=FF
13Cx[C0]=FF
14Cx[C2]=FF
15Cx[C3]=FF
16Cx[C0]=FF
17CxType=0
18Check Potomac

What CPU do you have and are you using the latest HWiNFO v6.21?

Mumak wrote on 2022-05-28, 14:15:

roytam1 wrote on 2022-05-28, 14:09:

got "Fatal Error" when starting, DBG log: […]
Show full quote

got "Fatal Error" when starting, DBG log:

Copy code to clipboard

1VidMode=3
2DispComb=8
3HWiNFO v6.2.1 
4Flushing disk caches ...
5
6Reading Data ...
7
8DetectCPU - 586
9CPUID=513
10Check Cx
11Cx[C2]=FF
12Cx[C3]=FF
13Cx[C0]=FF
14Cx[C2]=FF
15Cx[C3]=FF
16Cx[C0]=FF
17CxType=0
18Check Potomac

What CPU do you have and are you using the latest HWiNFO v6.21?

tested on "Script PC" emulator, NSSI shows:

and yes I tested with 6.2.1. BTW hwinfo16 works.

Are you still interested in random reports? If so here's a ThinkPad 365X report and debug.

I've got a weird problem with a Toshiba Satellite 4000CDs where it acts like the last key you press is stuck down when in the application. I need to play with the machine more though to see if it's just a dodgy laptop!

SteveC wrote on 2022-06-24, 17:58:

Are you still interested in random reports? If so here's a ThinkPad 365X report and debug.

I've got a weird problem with a Toshiba Satellite 4000CDs where it acts like the last key you press is stuck down when in the application. I need to play with the machine more though to see if it's just a dodgy laptop!

Yes, still interested in any retro reports 😀 Thanks!

I have some issues with it here: https://gamesystemrequirements.com/user/rando … /devices/289361

CPU and RAM not detected.

RandomStranger wrote on 2022-09-09, 20:21:

I have some issues with it here: https://gamesystemrequirements.com/user/rando … /devices/289361

CPU and RAM not detected.

Try the latest version of HWiNFO for DOS, not HWiNFO16 which is for 8086-286 only.

IBM PC 330 Model 466DX2 (486 DX/2 66MHz) DBG and LOG file

SteveC wrote on 2022-09-18, 17:09:

IBM PC 330 Model 466DX2 (486 DX/2 66MHz) DBG and LOG file

Thanks!

Thanks for resurrecting HWinFO!
As someone who developed DOS programs myself, I was always really impressed by HWiNFO's great text interface (TUI), and always wondered how it was build.
I know that we can't expect HWinFO to become open source any time soon.... but are you willing to tell maybe something how you build the interface?
For example programming language it was developed in, and if it's completely custom build, or some kind of TUI library was used?

I think it can be super interesting for any developer working on TUI interfaces (even modern ones) to learn about how this classing programming was build!

werchter wrote on 2022-10-05, 16:28:

Thanks for resurrecting HWinFO! As someone who developed DOS programs myself, I was always really impressed by HWiNFO's great t […]
Show full quote

Thanks for resurrecting HWinFO!
As someone who developed DOS programs myself, I was always really impressed by HWiNFO's great text interface (TUI), and always wondered how it was build.
I know that we can't expect HWinFO to become open source any time soon.... but are you willing to tell maybe something how you build the interface?
For example programming language it was developed in, and if it's completely custom build, or some kind of TUI library was used?

I think it can be super interesting for any developer working on TUI interfaces (even modern ones) to learn about how this classing programming was build!

The interface is completely custom-built mostly using object-oriented C++, a bit of ASM. It wasn't that hard to create it.

Textual user interfaces are easy to create in C++ and asm. A complete windowing system is almost as easy. You just need to write it initially in pseudo code, and break it down to the smallest elements. I need to rewrite my own for my x86 OS 😀

Mumak wrote on 2022-10-05, 16:45:

The interface is completely custom-built mostly using object-oriented C++, a bit of ASM. It wasn't that hard to create it.

Thanks!

Yes, I writing a DOS interface is relatively uncomplicated, compared to for example cross platform nix* development with ncurses or similar frameworks.
I did some development with Turbo Vision in Borland's Pascal in '90s. Turbo Vision give great results as well, but is relatively complex, especially for straightforward use cases.

Anyway, great work @Mumak on the interface, especially for time period when it was initially released!

werchter wrote on 2022-10-05, 18:11:

Thanks! […]
Show full quote

Mumak wrote on 2022-10-05, 16:45:

The interface is completely custom-built mostly using object-oriented C++, a bit of ASM. It wasn't that hard to create it.

Thanks!

Yes, I writing a DOS interface is relatively uncomplicated, compared to for example cross platform nix* development with ncurses or similar frameworks.
I did some development with Turbo Vision in Borland's Pascal in '90s. Turbo Vision give great results as well, but is relatively complex, especially for straightforward use cases.

Anyway, great work @Mumak on the interface, especially for time period when it was initially released!

Thanks. Some others (creating similar tool(s)) have copied a lot including several details and textual descriptions.. But I won't name them...

downloaded HWiNFO32.exe ..

it wont run, get an error

when i click on it (go to run it) in windows 95 on my p166 machine I get "Error Starting Program" "A required .DLL file, WININET.DLL, was not found"..

this new version doesnt work on win 95 4.00.950a

is there an old original version that does?

according to this page which lists wininet.dll versions the dll comes in the internet explorer package or the OS install (WIN(95OSR2 onwards).. https://www.geoffchappell.com/studies/windows … story/index.htm
wondering which version is necessary?
does this mean i have install Internet Explorer (ughh i dont want that crap on my system) .. or just the dll - which i have no idea where to get from and potentially opening up a can of worms as theres 11ty million different versions..?
ok ok so say i manage to find this missing dll, then what? where does it go? in the same folder as hwinfo32 or somewhere else like the windows folder?

ah retro computing... just as i remember it back in the day .. a complete headache

This is the thread for HWinfo for DOS which doesn't require Windows.....