Author Topic: Hardware Explorer  (Read 4898 times)

Wim Brul

  • Full Member
  • ***
  • Thank You
  • -Given: 3
  • -Receive: 34
  • Posts: 192
    • View Profile
    • Wim's home page
Re: Hardware Explorer
« Reply #45 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

Remy

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 14
  • Posts: 293
    • View Profile
Re: Hardware Explorer
« Reply #46 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:   
 

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 179
  • Posts: 2479
    • View Profile
Re: Hardware Explorer
« Reply #47 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.

Remy

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 14
  • Posts: 293
    • View Profile
Re: Hardware Explorer
« Reply #48 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. 

Remy

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 14
  • Posts: 293
    • View Profile
Re: Hardware Explorer
« Reply #49 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

Digi

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 12
  • Posts: 46
  • http://os2.snc.ru/
    • View Profile
    • OS/2 ports and applications
Re: Hardware Explorer
« Reply #50 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?

Digi

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 12
  • Posts: 46
  • http://os2.snc.ru/
    • View Profile
    • OS/2 ports and applications
Re: Hardware Explorer
« Reply #51 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?

Remy

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 14
  • Posts: 293
    • View Profile
Re: Hardware Explorer
« Reply #52 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

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 179
  • Posts: 2479
    • View Profile
Re: Hardware Explorer
« Reply #53 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.

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 179
  • Posts: 2479
    • View Profile
Re: Hardware Explorer
« Reply #54 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/

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 14
  • -Receive: 16
  • Posts: 722
    • View Profile
Re: Hardware Explorer
« Reply #55 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.

Digi

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 12
  • Posts: 46
  • http://os2.snc.ru/
    • View Profile
    • OS/2 ports and applications
Re: Hardware Explorer
« Reply #56 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.

Lars

  • Hero Member
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 60
  • Posts: 573
    • View Profile
Re: Hardware Explorer
« Reply #57 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...

Lars

  • Hero Member
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 60
  • Posts: 573
    • View Profile
Re: Hardware Explorer
« Reply #58 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 ...)

Lars

  • Hero Member
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 60
  • Posts: 573
    • View Profile
Re: Hardware Explorer
« Reply #59 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.