OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Digi on January 22, 2020, 05:53:08 pm

Title: Hardware Explorer
Post by: Digi on January 22, 2020, 05:53:08 pm
We would like to ask you to test a new product. This is an alternative to the standard Hardware Manager. See the readme.txt file in the archive for new features and benefits over the standard manager. Please post your screenshots in this forum thread so that we can see what can be improved.

New versions can be downloaded here: http://os2.snc.ru/product-HwExplorer.html (http://os2.snc.ru/product-HwExplorer.html)

Special thanks to: David Graser for icons, Lars Erdmann for source of HwMan and helpful tips, Os4User for testing and sharing ideas.
Title: Re: Hardware Explorer
Post by: _Hermit_ on January 22, 2020, 09:27:12 pm
Hi, Digi.
This is data from my machine.
Title: Re: Hardware Explorer
Post by: Digi on January 22, 2020, 11:49:16 pm
Hi, Digi.
This is data from my machine.

Many thanks. Now we need to understand why the types of devices with red question icons have not been detected.
Please download utility:
ftp://ftp.os2.snc.ru/pub/HwExplorer/resmgr.exe (ftp://ftp.os2.snc.ru/pub/HwExplorer/resmgr.exe)
run it:
resmgr.exe > resmgr.txt
 and send me resmgr.txt by e-mail (see address in readme.txt).
Title: Re: Hardware Explorer
Post by: Sergey Posokhov on January 23, 2020, 02:01:56 am
It works!
Title: Re: Hardware Explorer
Post by: Andreas Schnellbacher on January 23, 2020, 02:24:16 am
I'm at my system from 2005 and everything works well, no red question marks and all recognizable components named.
Title: Re: Hardware Explorer
Post by: _Hermit_ on January 23, 2020, 08:53:39 am
Many thanks. Now we need to understand why the types of devices with red question icons have not been detected.
Please download utility:
ftp://ftp.os2.snc.ru/pub/HwExplorer/resmgr.exe (ftp://ftp.os2.snc.ru/pub/HwExplorer/resmgr.exe)
run it:
resmgr.exe > resmgr.txt
 and send me resmgr.txt by e-mail (see address in readme.txt).
Made and sent. There is still Merlin's PCI Hardware Sniffer report, but Pcidevs.txt from 16.05.2013. I didn't find anything newer.
Screenshot from the updated program.
Title: Re: Hardware Explorer
Post by: Digi on January 23, 2020, 11:22:23 am
Made and sent. There is still Merlin's PCI Hardware Sniffer report, but Pcidevs.txt from 16.05.2013. I didn't find anything newer.
Screenshot from the updated program.

As I understand it, the screenshots from the previous post were made with the native kernel, and the last with the OS/4 kernel?
Please, send me resmgr.exe output witn IBM kernel to understand why you have red "?" instead icons.

By the way, here you can see how much better the tree of devices with the OS/4 kernel turns out. Much clearer and more logical.

Hardware Explorer does not use Pcidevs.txt file. Instead, the data is read from a more modern PCI.IDS and USB.IDS (see readme.txt).
Title: Re: Hardware Explorer
Post by: _Hermit_ on January 23, 2020, 11:31:46 am
As I understand it, the screenshots from the previous post were made with the native kernel, and the last with the OS/4 kernel?
Please, send me resmgr.exe output witn IBM kernel to understand why you have red "?" instead icons.
Both are made with OS/4 core. For the latter,  was replaced oemhlp.bpd. In the mail indicated. I'll do it with IBM later.
Title: Re: Hardware Explorer
Post by: Tom on January 23, 2020, 05:39:33 pm
Made and sent. There is still Merlin's PCI Hardware Sniffer report, but Pcidevs.txt from 16.05.2013. I didn't find anything newer.

On Hobbes you can find a newer version from 2018:

https://hobbes.nmsu.edu/?search=pcidevs

leads to

https://hobbes.nmsu.edu/download/pub/os2/util/system/pcidevs_20180114.zip

Title: Re: Hardware Explorer
Post by: Dave Yeo on January 23, 2020, 06:06:53 pm
Made and sent. There is still Merlin's PCI Hardware Sniffer report, but Pcidevs.txt from 16.05.2013. I didn't find anything newer.

On Hobbes you can find a newer version from 2018:

https://hobbes.nmsu.edu/?search=pcidevs

leads to

https://hobbes.nmsu.edu/download/pub/os2/util/system/pcidevs_20180114.zip

The latest, updated most days, should be at https://pci-ids.ucw.cz/ (https://pci-ids.ucw.cz/)
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on January 24, 2020, 02:55:33 am
Hi Digi,

Thanks, this is really nice. For one, my AMD Phenom II X6 is finally recgonized as one instead of seing a "Hallo" msg.

Oh, no issues found here, attached is the resmgr output.
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on January 25, 2020, 06:07:30 pm
Digi,

Found something that doesn't appear to be setup related.

Take a look at the attached captures please.

1) HW Manager
- when doing the menu drop-down from 'System Setup => Hardware Manager' the full listing is auto-populated

2) HW Explorer
- when executing the same navigation path as above nothins shows up, it is empty, however once I right-click and allow it to open up in it's separate window from that point onwards it's always pre-populated

My theory: somehow the default HW Manager knows to pre-populate the contents whereas HW Explorer does not. I think you should consider changing this since otherwise it's easy to erroneously conclude that HW Explorer is somehow 'not working'.
Title: Re: Hardware Explorer
Post by: Dave Yeo on January 25, 2020, 06:14:22 pm
I have the opposite results. The hardware manager stopped showing anything some time back (before hardware explorer) whereas the hardware explorer populates right away though opening it in tree view is more informative.
Only thing missing here is more video info beyond VGA.
Title: Re: Hardware Explorer
Post by: David Graser on January 25, 2020, 06:38:15 pm
I have the opposite results. The hardware manager stopped showing anything some time back (before hardware explorer) whereas the hardware explorer populates right away though opening it in tree view is more informative.
Only thing missing here is more video info beyond VGA.

Dave

I have seen this happen when I installed Lars version in ArcaOS.  Reading Lars info, his version is good for OS/2 and eCS, and not ArcaOS.  I don't think he has ArcaOS and as such has not tested it under ArcaOD.
Title: Re: Hardware Explorer
Post by: Dave Yeo on January 25, 2020, 07:40:12 pm
Yes, I did install Lars's version at one point. I guess I need to uninstall it and remember to read the docs better :)
Title: Re: Hardware Explorer
Post by: OS4User on January 25, 2020, 07:59:46 pm
Starting from SVN5686 OS/4 organizes RM info in a bit different way.
One can see a real PCI bus(es) structure of his equipment (see  PCI_Bus_0 node and its tree).
It is something similar  to output of PCI.exe.

If any driver provides PCI info to RM  -  it is also reflected in Hardware Explorer.
So far this PCI info is provided by Lars's USB drivers only.

Only thing missing here is more video info beyond VGA.

VGA info is provided by screen03.sys on OS/4 and resource.sys on OS/2.
These drivers are not very smart so cannot give more info.
At the same time HardWare Explorer showed the name of my graphic card  correctly.

Dave, I will try to add LFB mapping in screen03.sys. What info would you like to see ?
Title: Re: Hardware Explorer
Post by: Digi on January 26, 2020, 12:06:54 pm
2) HW Explorer
- when executing the same navigation path as above nothins shows up, it is empty, however once I right-click and allow it to open up in it's separate window from that point onwards it's always pre-populated

The contents of the Hardware Explorer are filled during the initialization of the WPS object and when you go to it through the menu, the folder should already be filled.
I did not meet the described problem on my systems. It would be interesting to learn about this point from other testers.
Title: Re: Hardware Explorer
Post by: Pete on January 26, 2020, 05:18:09 pm
Hi Digi

I see the same as Dariusz: Hardware Explorer shows "(No objects)".

I tried several times to double check.

I then typed this message but before clicking the "Post" button I tested again.

Result: It worked this time - No idea why it did not on the previous 4 or 5 attempts...


Regards

Pete
Title: Re: Hardware Explorer
Post by: Dave Yeo on January 26, 2020, 07:23:36 pm
Hi Digi, ideally would be the info shown in the screen object. I'm currently using SNAP and it shows monitor, chipset, and memory. I guess that info can be queried with the SNAP SDK (pm.lib) with the functions,
Code: [Select]
GA_configInfo

Declaration

typedef struct {
    N_uint32        dwSize;
    char            ManufacturerName[80];
    char            ChipsetName[80];
    char            DACName[80];
    char            ClockName[80];
    char            VersionInfo[80];
    char            BuildDate[80];
    char            Certified;
    char            CertifiedDate[20];
    N_uint16        CertifyVersion;
    } GA_configInfo
prototyped in snap/graphics.h
There's also GetMonitorInfo().

Hopefully there's a similar way to query Panorama.
BTW, here the Hardware Monitor is always populated, using the stock kernel.
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on January 26, 2020, 07:43:28 pm
Hi Digi,

The contents of the Hardware Explorer are filled during the initialization of the WPS object and when you go to it through the menu, the folder should already be filled.
I did not meet the described problem on my systems. It would be interesting to learn about this point from other testers.

...tell me what you need to debug further and I'd be happy to track this down!
Title: Re: Hardware Explorer
Post by: Digi on January 30, 2020, 04:18:52 pm
...tell me what you need to debug further and I'd be happy to track this down!

Please try the new version: http://os2.snc.ru/product-HwExplorer.html (http://os2.snc.ru/product-HwExplorer.html)
Is this problem still in your system with it?
Title: Re: Hardware Explorer
Post by: Pete on January 31, 2020, 03:59:29 am
Hi Digi

The new version resolves the problem here.


Regards

Pete
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on January 31, 2020, 04:07:03 am
Digi, everyone..

...The new version resolves the problem here...

Yup, same here, all good. Thank you!
Title: Hardware Explorer ver. 0.0.5
Post by: Digi on February 06, 2020, 03:08:37 pm
New version:

http://os2.snc.ru/product-HwExplorer.html (http://os2.snc.ru/product-HwExplorer.html)

Pay attention to the second page of the USB Info tab of the notepad of any connected USB device.
The utility for removing/installing the native and extended Hardware Manager has been added to the archive.
See whatsnew.txt and readme.txt .
Title: Re: Hardware Explorer
Post by: David Graser on February 06, 2020, 04:05:43 pm
Hi Digi

I have seen one problem and it has to do with this one piece of hardware.  I have attached a pic with the hardware highlighted.  When I double click on this, or right click and select properties, it locks up my computer big time causing me to hard boot.  Cannot even bring up TOP to kill it.  This is an internal camera and not a USB camera.

Attached is the resmgr txt.

I have tested other components and the properties page comes up fine.
Title: Re: Hardware Explorer
Post by: Digi on February 06, 2020, 04:23:55 pm
This is an internal camera and not a USB camera.

The screenshot shows that the resource manager considers this a USB device. Did you have this problem on the previous version?
Please send me the output of this utility:
http://ftp.os2.snc.ru/in/usbresm.exe
Title: Re: Hardware Explorer
Post by: David Graser on February 06, 2020, 04:33:49 pm
Yes it did it in earlier versions.  I did not test further at he time. 

I just tested and everything in the branches for this controller locks the computer also.  Selecting the ECHI_0 Enhanced USB controller itself does bring up its properties.  Everything in its branches locks the computer.

Title: Re: Hardware Explorer
Post by: Digi on February 06, 2020, 04:42:16 pm
Yes it did it in earlier versions.  I did not test further at he time. 

I just tested and everything in the branches for this controller locks the computer also.  Selecting the ECHI_0 Enhanced USB controller itself does bring up its properties.  Everything in its branches locks the computer.

What about usbresm.exe output?
Title: Re: Hardware Explorer
Post by: David Graser on February 06, 2020, 04:42:55 pm
Executing the usbresm.exe locks my computer up big time  which also requiries a hard boot.
Title: Re: Hardware Explorer
Post by: David Graser on February 06, 2020, 04:53:18 pm
This is as much as I can get before it locks the computer.

Devices 3

Device 1   Resource Manager handle: 0x3757
Calc. length 102
Vendor device: release: 044D:C52B:1203

I remember when doing the original testing, I could not produce output from the u.exe because of the same lockup.
Title: Re: Hardware Explorer
Post by: Digi on February 06, 2020, 04:59:40 pm
Executing the usbresm.exe locks my computer up big time  which also requiries a hard boot.

Perhaps this is due to usbresmg.sys driver problems on your system. Make sure that this driver and other USB drivers (USBEHCD.SYS ?) are from the same source (Lars Erdmann / eCS / ArcaNoae) and same version. You can use the bldlevel utility. Look in config.sys where USBRESMG.SYS is loaded from.
Title: Re: Hardware Explorer
Post by: Digi on February 06, 2020, 05:04:26 pm
This is as much as I can get before it locks the computer.

Devices 3

Device 1   Resource Manager handle: 0x3757
Calc. length 102
Vendor device: release: 044D:C52B:1203

This tells me that the usbresmg driver hangs on an IOCTLF_ACQUIREDEVICE request.
Title: Re: Hardware Explorer
Post by: David Graser on February 06, 2020, 05:13:45 pm
Executing the usbresm.exe locks my computer up big time  which also requiries a hard boot.

Perhaps this is due to usbresmg.sys driver problems on your system. Make sure that this driver and other USB drivers (USBEHCD.SYS ?) are from the same source (Lars Erdmann / eCS / ArcaNoae) and same version. You can use the bldlevel utility. Look in config.sys where USBRESMG.SYS is loaded from.
There is only one USBRESMG.SYS on my system.  This is the bldlevel output.

Title: Re: Hardware Explorer
Post by: Digi on February 06, 2020, 05:21:51 pm
Executing the usbresm.exe locks my computer up big time  which also requiries a hard boot.

Perhaps this is due to usbresmg.sys driver problems on your system. Make sure that this driver and other USB drivers (USBEHCD.SYS ?) are from the same source (Lars Erdmann / eCS / ArcaNoae) and same version. You can use the bldlevel utility. Look in config.sys where USBRESMG.SYS is loaded from.
There is only one USBRESMG.SYS on my system.  This is the bldlevel output.

Compare it with bldlevel data for ?:\OS2\BOOT\USBEHCD.SYS
Title: hwmanager testing results
Post by: David Graser on February 06, 2020, 06:29:59 pm
I am having to start another post because I have been locked out of responding to the hwmanager explorer topic.

I have 3 ArcaOS partitions.  Two of the partitions use Lars latest USB drivers.  USBresm.exe works fine on these two partitions.  So does hwmanager explorer.

It is only on the partition that uses ArcaOS latest USB 32 bit drivers does the problem occur of the usb testing tools locking up the system. 

This partition also has os4 kernel. I could be wrong, but I don't think this is the problem.

The build levels match for the USB 32 bit drivers.

Has anyone else tested USBresm.exe with ArcaOS's latest 32 bit drivers?

David
Title: Re: hwmanager testing results
Post by: Dave Yeo on February 06, 2020, 06:49:44 pm
I was wondering why there was no way to reply to that thread :)
I'm getting similar results with the OS4 kernel, testing the regular OS/2 kernel gives me a trap 3 (debug point) in usbresmg.sys with USBresm.exe displaying one line similar to you then locking hard with the OS4 kernel and an instant trap 3 with the OS/2 kernel.
All drivers match,
Code: [Select]
D:\OS2\BOOT>bldlevel usbresmg.sys
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Arca Noae LLC:12.03#@##1## 15 Sep 2019 09:55:01     DAZAR1
 ::::::@@USBCALLS Driver (32 bit) for OS/2 (c) 2019 Arca Noae LLC
Vendor:          Arca Noae LLC
Revision:        12.03
Date/Time:       15 Sep 2019 09:55:01
Build Machine:   DAZAR1
File Version:    12.3
Description:     USBCALLS Driver (32 bit) for OS/2 (c) 2019 Arca Noae LLC

Can't remember testing with the previous version but assume I did.
Title: Re: hwmanager testing results
Post by: Digi on February 06, 2020, 06:55:19 pm
The problem is already known. There is a ticket 0002740 on the AN bugtracker.
A fixed driver USBRESMG.SYS is attached to this ticket.
Title: Re: hwmanager testing results
Post by: David Graser on February 06, 2020, 07:12:48 pm
The problem is already known. There is a ticket 0002740 on the AN bugtracker.
A fixed driver USBRESMG.SYS is attached to this ticket.

Thanks Digi!

The fix worked.  Hwmanager is now working great with ArcaOS's 32 bit USB drivers.

David
Title: Re: hwmanager testing results
Post by: Digi on February 06, 2020, 07:27:04 pm
The fix worked.  Hwmanager is now working great with ArcaOS's 32 bit USB drivers.

Hardware Explorer 0.0.5 ?
Title: Re: hwmanager testing results
Post by: David Graser on February 06, 2020, 07:33:08 pm
The fix worked.  Hwmanager is now working great with ArcaOS's 32 bit USB drivers.

Hardware Explorer 0.0.5 ?

Yes, it works fine.
Title: Re: Hardware Explorer
Post by: Martin Iturbide on February 07, 2020, 01:59:02 am
Moderator's Note: I don't know what happened or why the first thread got locked. I had merged the two threads. Maybe it was a mistake but I will keep checking.
Title: Re: Hardware Explorer
Post by: Wim Brul on February 09, 2020, 04:24:41 pm
Hi Digi,

When I invoke Hardware Explorer 0.0.5 from System Setup then its tree view display is not stable. It sort of flashes every 2 seconds. I think it has to do with the new function "If the USB device is not found in the USB.IDS file, then the name consists of data taken from the device itself". The title of the Properties pages of such devices flash every 2 seconds too. I have several of such devices. I have attached 2 snapshots of my behringer umc204hd device. The 1st one is shown for about 2 seconds and the 2nd one (not easy to capture) is shown as a brief flash. It happens both on ArcaOS 5.0 and eComStation 2.0 with Lars Erdmann 10.232 drivers.

Wim   
Title: Re: Hardware Explorer
Post by: Lars on February 09, 2020, 07:39:12 pm
I can say from my own experience that it is a bad idea in general to directly reread descriptors over and over again.
USBD.SYS caches the device and the configuration descriptor which can always be queried by USBRESMG.SYS.
If it is attempted to read a string descriptor (for example to get a manufacturer name or a device name), you need to be aware of that it often is unstable (don't ask me why) and also that there is a chance that either no string descriptor exists (string id = 0), or worse, the device descriptor reports string ids <> 0 but still has no string descriptors to offer. It's a mess, as everything else with USB.

I guess THAT is the reason why someone came up with the idea to create usb.ids and I would not be surprised if Linux ONLY uses this static info to return device and manufacturer name instead of querying string descriptors.

There is also a logical FLAW in USBRESMG.SYS in that it gets totally confused if two attached devices have the very same vendor and product id (yes, this happens, even with devices that look completely different !).
That typically leads to hangs/crashes when reading string descriptors. Would need to rewrite/change USBRESMG.SYS to also take the serial number into account (I think there even is a shitty Microsoft specific descriptor for that) to distinguish devices but oh well …

Lars
Title: Re: Hardware Explorer
Post by: Digi on February 10, 2020, 10:24:39 am
I can say from my own experience that it is a bad idea in general to directly reread descriptors over and over again.

You already talked about this earlier and I took into account your advice by minimizing the use of USBRESMG. Description strings for each device in HwE are read only once and stored to avoid repeated calls. The USBRESM$ file handle also opens only once.
Thanks for the advice!
Title: Re: Hardware Explorer
Post by: Lars on February 10, 2020, 02:41:19 pm
ok, caching is the correct thing to do.

That leaves us with the remaining problem: if you have 2 devices attached that happen to have the same vendor and product ids, then USBRESMG.SYS will fail on reading the string descriptor as it will then confuse one device with the other. This is true even if you only open USBRESMG.SYS once and even if you only access one USB device at a time.

These days it might also be valuable to have a look at reading string descriptor with special string id = 0xEE. That will return Microsoft specific info (an OS identifier string) and if that works, it will open the door to other Microsoft specific descriptors, amongst those also a serial number. I seem to remember. All manufacturers will be forced to go the Microsoft way anyway (it already started with WinXP and the latest service pack).

Please note that reading the string descriptor for "device serial number" (iSerialNumber value in device descriptor) will not be possible most of the times because there are a lot of devices that do not provide a serial number in a string format (iSerialNumber = 0 for these devices).
Title: Re: Hardware Explorer
Post by: Wim Brul on February 10, 2020, 03:15:29 pm
Hi Digi,

The flashing display problem has been solved with the TEST and TEST2 versions you sent me by private mail. Thank you.

However, on my dell latitude e6500 system, I get a trap when I want to display the "MOUSE_0 IBM Compatible Mouse" properties.
Sometimes I can see it shortly, so a took a snapshot of it, but I think the problem has to do with "Unknown Mouse Adapter".   


02-10-2020  14:31:37  SYS3175  PID 005e  TID 0020  Slot 006a
H:\OS2\PMSHELL.EXE
c0000005
1d23b05f
P1=00000002  P2=980f7208  P3=XXXXXXXX  P4=XXXXXXXX
EAX=00e33770  EBX=980f7200  ECX=00e33bf0  EDX=720f56e4
ESI=00e30020  EDI=00e30000
DS=0053  DSACC=d0f3  DSLIM=bfffffff
ES=0053  ESACC=d0f3  ESLIM=bfffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1d23b05f  CSACC=d0df  CSLIM=bfffffff
SS:ESP=0053:00ea9d70  SSACC=d0f3  SSLIM=bfffffff
EBP=00000000  FLG=00010202

HWEXP.DLL 0002:0000b05f

------------------------------------------------------------

02-10-2020  14:31:37  SYS3170  PID 005e  TID 0001  Slot 0048
H:\OS2\PMSHELL.EXE
00000000
00000001
EAX=00e33770  EBX=00e30000  ECX=00e30030  EDX=980f7200
ESI=00e30000  EDI=00000000
DS=0053  DSACC=d0f3  DSLIM=bfffffff
ES=0053  ESACC=d0f3  ESLIM=bfffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1d23b0e3  CSACC=d0df  CSLIM=bfffffff
SS:ESP=0053:0004f900  SSACC=d0f3  SSLIM=bfffffff
EBP=0004f92c  FLG=00010287


Wim
Title: Re: Hardware Explorer
Post by: Remy on February 11, 2020, 12:57:09 am
I just tried to install 005 build and near end of installation, I've got a trap forcing to do power off/on resulting into lost of my BIOS settings.
ArcaOS system + latest drivers
Trap information follows:   
 
Title: Re: Hardware Explorer
Post by: Dave Yeo on February 11, 2020, 01:25:43 am
Hi Remy, you need the updated USBRESMG.SYS attached to ticket 0002740 at the Arca Noae bug tracker.
Strange that it affected your BIOS.
Title: Re: Hardware Explorer
Post by: Remy on February 11, 2020, 01:44:34 am
Hi Remy, you need the updated USBRESMG.SYS attached to ticket 0002740 at the Arca Noae bug tracker.
Strange that it affected your BIOS.

The trap seems having set an invalid state making during power off process (holding power on/off button more than 3s to power off) the bios reset all values to default values. 
Title: Re: Hardware Explorer
Post by: Remy on February 11, 2020, 01:45:13 am
Hi Remy, you need the updated USBRESMG.SYS attached to ticket 0002740 at the Arca Noae bug tracker.
Strange that it affected your BIOS.

Will have a look on this ticket...
Thanks
Title: Re: Hardware Explorer
Post by: Digi on February 11, 2020, 07:40:46 pm
Hi Digi, ideally would be the info shown in the screen object. I'm currently using SNAP and it shows monitor, chipset, and memory.
....
Hopefully there's a similar way to query Panorama.

Thanks for the advice. I implemented this for a future version 0.0.6. But Panorama is installed on all my systems. Can you tell me where I can try to search for information to get such data from Panorama?
Title: Re: Hardware Explorer
Post by: Digi on February 11, 2020, 07:50:58 pm
There is also a logical FLAW in USBRESMG.SYS in that it gets totally confused if two attached devices have the very same vendor and product id (yes, this happens, even with devices that look completely different !).
That typically leads to hangs/crashes when reading string descriptors. Would need to rewrite/change USBRESMG.SYS to also take the serial number into account (I think there even is a shitty Microsoft specific descriptor for that) to distinguish devices but oh well …

This is a very deplorable situation. Is there any chance that the problem will be fixed in your USBRESMG.SYS?
Title: Re: Hardware Explorer
Post by: Remy on February 11, 2020, 09:54:53 pm
There is also a logical FLAW in USBRESMG.SYS in that it gets totally confused if two attached devices have the very same vendor and product id (yes, this happens, even with devices that look completely different !).
That typically leads to hangs/crashes when reading string descriptors. Would need to rewrite/change USBRESMG.SYS to also take the serial number into account (I think there even is a shitty Microsoft specific descriptor for that) to distinguish devices but oh well …

This is a very deplorable situation. Is there any chance that the problem will be fixed in your USBRESMG.SYS?

Installed suggested fix before GA of USBRESMG and no more any trap. Resolved
Title: Re: Hardware Explorer
Post by: Dave Yeo on February 12, 2020, 01:00:12 am
Hi Digi, ideally would be the info shown in the screen object. I'm currently using SNAP and it shows monitor, chipset, and memory.
....
Hopefully there's a similar way to query Panorama.

Thanks for the advice. I implemented this for a future version 0.0.6. But Panorama is installed on all my systems. Can you tell me where I can try to search for information to get such data from Panorama?

Interestingly I tried the OS4 kernel yesterday and Hardware Explorer displayed the correct video card etc in the VGA properties under the PCI Info tab. With the AOS kernel, this tab doesn't exist.
As for Panorama, not too sure, \var\log\vbe2gradd.log seems to have most of the info though not the monitors name here., just size and preferred resolution.
Title: Re: Hardware Explorer
Post by: Dave Yeo on February 12, 2020, 01:07:01 am
There is also a logical FLAW in USBRESMG.SYS in that it gets totally confused if two attached devices have the very same vendor and product id (yes, this happens, even with devices that look completely different !).
That typically leads to hangs/crashes when reading string descriptors. Would need to rewrite/change USBRESMG.SYS to also take the serial number into account (I think there even is a shitty Microsoft specific descriptor for that) to distinguish devices but oh well …

This is a very deplorable situation. Is there any chance that the problem will be fixed in your USBRESMG.SYS?

Using the AOS 12.4 prerelease driver, the serial number of my USB sticks does show, it's blank on my Logitech unified receiver.
I have one stick that when inserted make the tree view of the Hardware Explorer redraw every  or 3 seconds (2.5 seconds?) with the text seeming to jump slightly which doesn't look good. Other sticks are fine, this one is formatted EXT4 but partitioned by our LVM if it matters. Currently using the OS4 kernel, I'll test with the AOS one later.
Here's the properties of it, it's labeled a Duracell 128GB stick/
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on February 12, 2020, 04:56:26 am
Interestingly I tried the OS4 kernel yesterday and Hardware Explorer displayed the correct video card etc in the VGA properties under the PCI Info tab. With the AOS kernel, this tab doesn't exist.

Same situation here on AOS kernel, did not test with OS4...this is for my ATI X850 XT card (1002:5D4D) running SNAP drivers.
Title: Re: Hardware Explorer
Post by: Digi on February 12, 2020, 06:45:29 am
Using the AOS 12.4 prerelease driver, the serial number of my USB sticks does show, it's blank on my Logitech unified receiver.
I have one stick that when inserted make the tree view of the Hardware Explorer redraw every  or 3 seconds (2.5 seconds?) with the text seeming to jump slightly which doesn't look good. Other sticks are fine, this one is formatted EXT4 but partitioned by our LVM if it matters. Currently using the OS4 kernel, I'll test with the AOS one later.
Here's the properties of it, it's labeled a Duracell 128GB stick/

Manufacturers often do not indicate the serial number in the strings of a USB device.
The twitching tree problem has already been solved; this will be included in the next version 0.0.6.

Interestingly I tried the OS4 kernel yesterday and Hardware Explorer displayed the correct video card etc in the VGA properties under the PCI Info tab. With the AOS kernel, this tab doesn't exist.

Under OS/4, the system Resource Manager provides more meaningful information in a logical way. Hardware Explorer uses all these features.
We would have had more information about PCI cards if all the driver developers were not too lazy to indicate things like PCI_DevFunc in their products.
Title: Re: Hardware Explorer
Post by: Lars on February 12, 2020, 08:54:45 am
Hi Digi,
you can read graphics card info directly by using the VBE programming interface. See VBE spec.,there is an info structure that contains manufacturer name etc.
Since you'll need to make Real Mode calls:
there is a programming interface for OS/2 (for Ring 3 application level) to do just that.
Unfortunately,I don't know for how long OS/2 will support real mode calls. Unless AN develops a minimum real mode SW interrupt emulation layer for all those UEFI only machines.
I'll try to find the real mode stuff in the DDK header files...
Title: Re: Hardware Explorer
Post by: Lars on February 12, 2020, 09:16:15 am
Reading info:
you need to use "VIDEOPMI32Request" entry point in VIDEOPMI.dll.
That supports a function code PMIREQUEST_SOFTWAREINT that allows you to make int 10h SW interrupts in real mode.
See "Graphics Adapter Device Driver Reference" in the DDK.
I can slap together some sample code (if I can find the VBE spec in my mess ...)
Title: Re: Hardware Explorer
Post by: Lars on February 12, 2020, 10:26:29 pm
I now have sample code ready to read Video vendor/product/rev info. Just let me know where to send it to.
You need the DDK to build the code. I tested it under VirtualBox and it returns the Info for the "virtual" VirtualBox screen driver.
Title: Re: Hardware Explorer
Post by: Lars on February 14, 2020, 09:15:30 am
Sent to you via email.
Title: Re: Hardware Explorer
Post by: Digi on February 15, 2020, 06:39:54 pm
Hardware Explorer 0.0.6 is available for download.
  http://os2.snc.ru/product-HwExplorer.html (http://os2.snc.ru/product-HwExplorer.html)

See "History of changes" on the web page (or whatsnew.txt).
Many thanks to everyone who helped.
Special thanks to Lars Erdmann for helping with the code receiving the VBE data.
Title: Re: Hardware Explorer
Post by: Dave Yeo on February 15, 2020, 07:19:40 pm
Looks good on a SNAP system, thanks.
Title: Re: Hardware Explorer
Post by: Dariusz Piatkowski on February 16, 2020, 06:47:37 am
Digi,

Here are a couple of screenshots showing the results in both OS2 and OS4 kernels.

Seems like the OS4 version is more 'complete', however that also means there are double occurencies of hardware being listed.

For example, if you look at the Realtek NIC you will find the following:
1) r8169_0 Network Adapter
2) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

They are certainly referencing the same hardware, that being the NIC.

I think similar can be said for other devices such as SB chipset and matching IDE_x/1/2 xATA controller icons, or the PCI_Bus_0 and duplicate PCI_Bus_0 icons. PCI_Bus_1/2/3 are not duplicated, however in the OS2 version of the output only PCI_Bus_0 is shown.
Title: Re: Hardware Explorer
Post by: OS4User on February 16, 2020, 08:45:42 am
Seems like the OS4 version is more 'complete', however that also means there are double occurencies of hardware being listed.

For example, if you look at the Realtek NIC you will find the following:
1) r8169_0 Network Adapter
2) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller


You are very observant :).  OS/4 version is not just more 'complete'   -  OS/4 adds to it's RM all equipment that is available on PCI bus, considering  bus topology.

What you can see under PCI_Bus_0  is your real PCI tree and thus PCI_Bus_0 is your root bridge.

OS/4 RM combines real PCI tree and adapters added by drivers if a certain driver provides PCI address for its  adapter.   For ex.  Lars's USB controllers' drivers.

If a driver does not provide PCI address - then you can see its adapter under PCI_Bus_Misc node which is artificial and does not reflect real PCI tree.

Title: Re: Hardware Explorer
Post by: Lars on February 17, 2020, 05:53:14 pm
One obswrvation:
The port and memory ranges are too big by one,that is,the highest port/memory address should be one less as it is now.
Title: Re: Hardware Explorer
Post by: guzzi on February 17, 2020, 06:15:56 pm
Version 0.0.3 installed ok and worked. Version 0.0.6 traps the system with a trap 0003 in usbresmg. First time it did install over 0.0.3 but opening it resulted in the trap and after rebooting the system trapped again. Booted to command prompt and deleted hwexp.dll. Rebooted to wps and uninstalled using warpin. Installed again. This time the trap already occurred during installation.
Title: Re: Hardware Explorer
Post by: Dave Yeo on February 17, 2020, 06:32:51 pm
See ticket 0002740 at the Arca Noae bug tracker.
Title: Re: Hardware Explorer
Post by: guzzi on February 17, 2020, 06:51:42 pm
See ticket 0002740 at the Arca Noae bug tracker.

Solved. Thanks.
Title: Re: Hardware Explorer
Post by: Digi on February 17, 2020, 07:12:42 pm
One obswrvation:
The port and memory ranges are too big by one,that is,the highest port/memory address should be one less as it is now.

Indeed. Thank you! What a stupid mistake.  :)
Title: Re: Hardware Explorer
Post by: Digi on February 17, 2020, 07:28:52 pm
See ticket 0002740 at the Arca Noae bug tracker.

Solved. Thanks.

There are also no problems with drivers from Lars, can be found on Hobbes. I even have one device (USB microscope) that works well with these drivers, but doesn’t work with Arca drivers.
Title: Re: Hardware Explorer
Post by: ivan on February 18, 2020, 03:45:37 pm
Hi Digi,

You might be interested in the results I get from my AMD Ryzen box.  Sorry it is split but I only have a 1920x1200 monitor.
Title: Re: Hardware Explorer
Post by: Digi on February 18, 2020, 04:52:30 pm
You might be interested in the results I get from my AMD Ryzen box.  Sorry it is split but I only have a 1920x1200 monitor.

Thanks! It’s a little strange for me that at least the manufacturer has not determined on a USB mouse and keyboard. Check if the usb.ids file is in the %etc% directory?

It would be interesting to see the results under OS/4. There, the picture with your PCI bridges will be much clearer and more logical.
Title: Re: Hardware Explorer
Post by: Lars on February 18, 2020, 06:57:33 pm
You might be interested in the results I get from my AMD Ryzen box.  Sorry it is split but I only have a 1920x1200 monitor.

Thanks! It’s a little strange for me that at least the manufacturer has not determined on a USB mouse and keyboard. Check if the usb.ids file is in the %etc% directory?

It would be interesting to see the results under OS/4. There, the picture with your PCI bridges will be much clearer and more logical.
That might be a misunderstanding. My USB keyboard and mouse drivers will try and query the string descriptor for the product and they will also add a device to the RM tree. If they fail,they will instead display that message. Therefore I assume that Ivan is using my driver set.
By the way: my USBMSD.ADD also adds a RM device for each USB stick/disk/floppy/cdrom attached.
Title: Re: Hardware Explorer
Post by: ivan on February 18, 2020, 07:06:21 pm
Hi Digi,

That could be due to the fact this board has a massive amount of USB 3 and 3.1 ports attached to both the processor and a dedicated  USB 3 chip.

To be able to use any USB device requires a real (Via) USB 2 addin card.  The keyboard is highlighted in the lower screen grab which also shows the trackball as Kensington Orbit Optical.
Title: Re: Hardware Explorer
Post by: ivan on February 18, 2020, 07:11:24 pm
Hi Lars,

You are correct in assuming I am using your drivers.  They are from the time when I was trying to get some of the spare buttons working.