OS/2, eCS & ArcaOS - Technical > Applications

Hardware Explorer

<< < (12/17) > >>

Dariusz Piatkowski:

--- Quote from: Dave Yeo on February 12, 2020, 01:00:12 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.

--- End quote ---

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:

--- Quote from: Dave Yeo on February 12, 2020, 01:07:01 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/

--- End quote ---

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.


--- Quote from: Dave Yeo on February 12, 2020, 01:00:12 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.

--- End quote ---

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:
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:
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:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version