Thanks for this! It's great to see devs of old programs we all used appearing again and updating them

It doesn't seem to like my 386 even if I have tried to make it a pretty much standard 386. Video test gives fatal error and quits. Peripheral test gets stuck at trying to find gravis ultrasound. Just normal dos 6.22 and no emm386 loaded.

Edit: It also claims I have intel 82595 ethernet adapter in the system at port 0200 even if I don't have any network card in the system.

keropi wrote on 2020-03-19, 13:31:

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 s […]
Show full quote

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!

Thanks for the feedback. Memory module details are not possible to retrieve, this is available only for later DIMM modules with SPD.
It would be even better if I could tell the TI486DLC from Cx486S, but I'm not sure if this is possible at all.

Baoran wrote on 2020-03-19, 15:02:

It doesn't seem to like my 386 even if I have tried to make it a pretty much standard 386. Video test gives fatal error and quits. Peripheral test gets stuck at trying to find gravis ultrasound. Just normal dos 6.22 and no emm386 loaded.

Edit: It also claims I have intel 82595 ethernet adapter in the system at port 0200 even if I don't have any network card in the system.

What video card do you have? Are you able to catch at which point it crashes? A screenshot might be helpful.
Also what other cards are in the system, especially in the 210h-280h IO range?

Mumak wrote on 2020-03-19, 15:27:

Baoran wrote on 2020-03-19, 15:02:

It doesn't seem to like my 386 even if I have tried to make it a pretty much standard 386. Video test gives fatal error and quits. Peripheral test gets stuck at trying to find gravis ultrasound. Just normal dos 6.22 and no emm386 loaded.

Edit: It also claims I have intel 82595 ethernet adapter in the system at port 0200 even if I don't have any network card in the system.

What video card do you have? Are you able to catch at which point it crashes? A screenshot might be helpful.
Also what other cards are in the system?

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbond I/O card that has ide, floppy, com ports and parallel ports.
So basically I have that et4000ax card that is in that picture in that thread that I linked, sound blaster CT1320C and the I/O card in the system.
It also does not detect that the sound blaster is using irq 7 or dma 1 when running irq and dma tests and reports them as free.

Baoran wrote on 2020-03-19, 15:47:

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbon […]
Show full quote

Mumak wrote on 2020-03-19, 15:27:

Baoran wrote on 2020-03-19, 15:02:

It doesn't seem to like my 386 even if I have tried to make it a pretty much standard 386. Video test gives fatal error and quits. Peripheral test gets stuck at trying to find gravis ultrasound. Just normal dos 6.22 and no emm386 loaded.

Edit: It also claims I have intel 82595 ethernet adapter in the system at port 0200 even if I don't have any network card in the system.

What video card do you have? Are you able to catch at which point it crashes? A screenshot might be helpful.
Also what other cards are in the system?

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbond I/O card that has ide, floppy, com ports and parallel ports.
So basically I have that et4000ax card that is in that picture in that thread that I linked, sound blaster CT1320C and the I/O card in the system.
It also does not detect that the sound blaster is using irq 7 or dma 1 when running irq and dma tests and reports them as free.

screen1.jpg

Thanks, that information helps me to narrow down the problem. And I think I already found why video detection crashes: "Tseng ET-4000 BIOS v3.00 and v8.00 - BUG. Note: due to an omitted end-of-list marker, these versions of the BIOS crash the system on this function"

Do you know I/O port range does the SB occupy?

Mumak wrote on 2020-03-19, 15:59:

Baoran wrote on 2020-03-19, 15:47:

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbon […]
Show full quote

Mumak wrote on 2020-03-19, 15:27:

What video card do you have? Are you able to catch at which point it crashes? A screenshot might be helpful.
Also what other cards are in the system?

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbond I/O card that has ide, floppy, com ports and parallel ports.
So basically I have that et4000ax card that is in that picture in that thread that I linked, sound blaster CT1320C and the I/O card in the system.
It also does not detect that the sound blaster is using irq 7 or dma 1 when running irq and dma tests and reports them as free.

screen1.jpg

Thanks, that information helps me to narrow down the problem. Do you know I/O port range does the SB occupy?

It has the standard sound blaster settings set by jumpers on the card I/O 220, irq 7 and dma 1

Baoran wrote on 2020-03-19, 16:03:

Mumak wrote on 2020-03-19, 15:59:

Baoran wrote on 2020-03-19, 15:47:

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbon […]
Show full quote

It is this system Early 90s 386 build as close to period correct as possible. except I switched the I/O card to a generic winbond I/O card that has ide, floppy, com ports and parallel ports.
So basically I have that et4000ax card that is in that picture in that thread that I linked, sound blaster CT1320C and the I/O card in the system.
It also does not detect that the sound blaster is using irq 7 or dma 1 when running irq and dma tests and reports them as free.

screen1.jpg

Thanks, that information helps me to narrow down the problem. Do you know I/O port range does the SB occupy?

It has the standard sound blaster settings set by jumpers on the card I/O 220, irq 7 and dma 1

Can you please also post at which Gravis port does the scan freeze?

Mumak wrote on 2020-03-19, 16:06:

Baoran wrote on 2020-03-19, 16:03:

Mumak wrote on 2020-03-19, 15:59:

Thanks, that information helps me to narrow down the problem. Do you know I/O port range does the SB occupy?

It has the standard sound blaster settings set by jumpers on the card I/O 220, irq 7 and dma 1

Can you please also post at which Gravis port does the scan freeze?

Port 280

Baoran wrote on 2020-03-19, 16:12:

Mumak wrote on 2020-03-19, 16:06:

Baoran wrote on 2020-03-19, 16:03:

It has the standard sound blaster settings set by jumpers on the card I/O 220, irq 7 and dma 1

Can you please also post at which Gravis port does the scan freeze?

Port 280

Is anything at that port, perhaps the IO card ?

Thanks, i will add it to my Dos drivers and tools package:
X58/i865/V880 - Yamaha7x4/AurealV1/2 pure Dos7.1- compatibility list/research/ultim. drivers configs, WIP- gurus needed

Because im greedy i would really love that extended memory version for all old and modern system, for quite HW info just from Freedos boot USB.

With older version i had lots of start crashes and memory problems, so i had to use Navratil System info, which is great... only problem which im aware are wrong VRAM size detection and on some system im getting too many IRQ or PCI devices errors during initial diagnostics on more modern systems.

Mumak wrote on 2020-03-19, 16:19:

Baoran wrote on 2020-03-19, 16:12:

Mumak wrote on 2020-03-19, 16:06:

Can you please also post at which Gravis port does the scan freeze?

Port 280

Is anything at that port, perhaps the IO card ?

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game blaster compatibility of old sound blaster card like this and if it uses any address that I don't know about.
Pctools 9.0 system information detects the sound blaster fine and it passes the tests in that.

Edit: nevermind the parallel port must be disabled by jumpers on the IO card. Pctools 9.0 doesn't detect any parallel ports in the system.

Incredibly I finally have both the time and being in the right location to test my Compaq Presario 2232 media GX system.
Clock speed reporting is off, as in it's inconsistent from try to try, I actually don't know for certain the speed of the chip, info on this old piece of crap is limited, but as I recall 180 MHz is the purported speed although you'd never know it to use it.
It also hard locks on the peripherals information page, but does show the information, note that the inbuilt onchip audio is detected as Soundblaster 16.

BSA Starfire wrote on 2020-03-19, 16:41:

Incredibly I finally have both the time and being in the right location to test my Compaq Presario 2232 media GX system. Clock s […]
Show full quote

Incredibly I finally have both the time and being in the right location to test my Compaq Presario 2232 media GX system.
Clock speed reporting is off, as in it's inconsistent from try to try, I actually don't know for certain the speed of the chip, info on this old piece of crap is limited, but as I recall 180 MHz is the purported speed although you'd never know it to use it.
It also hard locks on the peripherals information page, but does show the information, note that the inbuilt onchip audio is detected as Soundblaster 16.
DSC_0200.JPG
DSC_0196.JPG
DSC_0197.JPG
DSC_0198.JPG
DSC_0199.JPG

Thanks for the feedback, I will look into that.
Could you please create a report of the machine and attach it as described here: Re: HWiNFO for DOS resurrected !
If any hard locks, please post a picture of where exactly it does lock up, that might help me to search for the problem.

Baoran wrote on 2020-03-19, 16:33:

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game b […]
Show full quote

Mumak wrote on 2020-03-19, 16:19:

Baoran wrote on 2020-03-19, 16:12:

Port 280

Is anything at that port, perhaps the IO card ?

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game blaster compatibility of old sound blaster card like this and if it uses any address that I don't know about.
Pctools 9.0 system information detects the sound blaster fine and it passes the tests in that.

Edit: nevermind the parallel port must be disabled by jumpers on the IO card. Pctools 9.0 doesn't detect any parallel ports in the system.

Please try this version: [removed old build, newer posted below]
I expect it not to crash during video detection and Gravis check. Would be great if you could post the report file of the system.

Mumak wrote on 2020-03-19, 18:31:

Baoran wrote on 2020-03-19, 16:33:

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game b […]
Show full quote

Mumak wrote on 2020-03-19, 16:19:

Is anything at that port, perhaps the IO card ?

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game blaster compatibility of old sound blaster card like this and if it uses any address that I don't know about.
Pctools 9.0 system information detects the sound blaster fine and it passes the tests in that.

Edit: nevermind the parallel port must be disabled by jumpers on the IO card. Pctools 9.0 doesn't detect any parallel ports in the system.

Please try this version: HWINF602.zip
I expect it not to crash during video detection and Gravis check. Would be great if you could post the report file of the system.

Here is a partial log file. It freezes in "sound blaster and compatible information". It shows 3 lines there, first one is dsp 1.5, second is dsp copyright that is empty and third is port 220 and after that the system is frozen and I have to reset.

Baoran wrote on 2020-03-19, 19:24:

Mumak wrote on 2020-03-19, 18:31:

Baoran wrote on 2020-03-19, 16:33:

Shouldn't be. Com ports are 02f8 and 03f8 and parallel port is disabled in bios. Only thing I have no knowledge of is the game blaster compatibility of old sound blaster card like this and if it uses any address that I don't know about.
Pctools 9.0 system information detects the sound blaster fine and it passes the tests in that.

Edit: nevermind the parallel port must be disabled by jumpers on the IO card. Pctools 9.0 doesn't detect any parallel ports in the system.

Please try this version: HWINF602.zip
I expect it not to crash during video detection and Gravis check. Would be great if you could post the report file of the system.

Here is a partial log file. It freezes in "sound blaster and compatible information". It shows 3 lines there, first one is dsp 1.5, second is dsp copyright that is empty and third is port 220 and after that the system is frozen and I have to reset.

HWINFO.LOG

Thanks. This should fix the hang in SB info: [removed old build, newer posted below]
But I don't know how to determine the IRQ/DMA for older SB cards (prior to SB16).

I tested this on my Thinkpad 560X.

I tried it cold, just running my defaut configuration with JEMMEX.

It did its usual thing complaining about me having a memory manager loaded. But this time it actually loaded, ran through all the tests, and worked! It never used to do that before, would only work in certain situations on certain machines.

Gave me tons of useful information.

So I'd call that a success.

I'll keep testing on more machines.

keenmaster486 wrote on 2020-03-19, 20:40:

I tested this on my Thinkpad 560X. […]
Show full quote

I tested this on my Thinkpad 560X.

I tried it cold, just running my defaut configuration with JEMMEX.

It did its usual thing complaining about me having a memory manager loaded. But this time it actually loaded, ran through all the tests, and worked! It never used to do that before, would only work in certain situations on certain machines.

Gave me tons of useful information.

So I'd call that a success.

I'll keep testing on more machines.

I'd be happy to get report files from your system(s). That helps me to analyze the outcome and see if I can improve something.

Here's what is says on my gateway bat4ip3 mobo--

1                                 HWiNFO v6.0.1 
2  º Main Processor:           AMD Am5x86, 119.6 MHz                          º
3  º Bus Type:                 PCI (V2.00) + ISA                              º
4  º Mainboard Model:          Unknown                                        º
5  º Mainboard Chipset:        Intel 82420EX                                  º
6  º First Level Cache:        1 KBytes                                       º
7  º Second Level Cache:       256 KBytes of Asynchronous SRAM                º

Three oddities:
[*] The first level cache seems small.
[*] The reported speed varies between 110 and 120Mhz.

When I try and do a full report, it locks up here:

The log that it did generate is attached.