Jump to content

MrX1980

Members
  • Posts

    47
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by MrX1980

  1. Hi Team,

    I noticed, that at AIDA64 -> Motherboard -> SPD -> Memory Module Features -> Thermal Sensor has the value "Not Present", but at Computer -> Sensor -> Temperatures I see all four DIMM temperatures.  So I think this value should be "Present/Available" or similar. Is it a bug?

    AIDA64 v7.00.6723 Beta
    ASRock X99M Extreme4
    Motherboard ID    63-0100-000001-00101111-051215-Chipset$0AAAA000_BIOS DATE: 10/03/17 10:41:11 VER: 05.0000B
    Module Name    4x G Skill Trident Z F4-3200C14-8GTZ
    OS Version    10.0.22000.2538 (Win11 21H2 RTM)

    Regards,
    MrX1980

    AIDA64_Sensor.png

    AIDA64_SPD.png

    smbusdump_full.txt

  2. I have enabled "Battery Charge Rate" (Aida64 -> System stability test -> Preferences -> Power) and tried to display the discharging rate with the graph, but because we cannot set negative values (Min. value >= 0), the results are not visible. We can only show/view values beginning with 0 watt.

    So it would be nice, if we can set negative values for an upcoming Aida64 release.

    Aida64_Power_graph.PNG

  3. Hi Fiery, I have done some tests.

    I updated AIDA64 an run one liniear test run, copied the values to LibreOffice Calc. = working

    Then I started a second run with another block size, copied again to LibreOffice Calc = there is still the first copied value in the clipboard

    I closed Calc and AIDA64 and started both again.

    Now I run two linear test runs and copied the value to Calc = there are still the values of the first run in the clipboard

    So I think, if more than two runs was done, the copy function is not working.

     

    post-23-0-89345500-1463504776_thumb.png

  4. Hi AIDA64 team,

     

    I would like to have:

    a) Read Test Suite - Possibility to save the results as CSV file and not only as PNG

    B) Read Test Suite - Possibility to select more than one block size, so we can run the tests in a "batch mode" (without to change the block size after every test run manually)

     

    Thanks

     

    Currently I use AIDA64 v5.70.3837 beta (Disk Benchmark v1.06.09)

  5. Now supported with Version: 3.20.2651 (Nov 06, 2013)

     

    • Storage / ATA / Automatic Partial to Slumber Transitions detection
    • Storage / ATA / Device Initiated Interface Power Management detection
    • Storage / ATA / DEVSLP detection
    • Storage / ATA / Hardware Feature Control detection
    • Storage / ATA / Host Initiated Interface Power Management detection
    • Storage / ATA / HPA Security Extensions detection
    • Storage / ATA / Hybrid Information Feature detection
    • Storage / ATA / IDLE IMMEDIATE With UNLOAD FEATURE detection
    • Storage / ATA / Link Power State Device Sleep detection
    • Storage / ATA / NCQ Autosense detection
    • Storage / ATA / NCQ Streaming detection
    • Storage / ATA / Service Interrupt detection
    • Storage / ATA / various ATA commands detection
    • Storage / SMART / special support for OCZ Vector 150 SSDs
    • ...

     

    Thanks

  6. Hi, what about this ?

     

    serial-ata-ahci-tech-proposal-rev1_3_1.pdf

    page 9ff

     

    Offset 44h: PxDEVSLP – Port x Device Sleep

    bit = 1

     

    Device Sleep Present (DSP):
    If set to „1", the platform supports Device Sleep on this port.
    If cleared to „0‟, the platform does not support Device Sleep on this port.

     

    Else can you try to contact james.a.boyd@intel.com ?

    My experience is not enough to ask the right questions :-)

  7. Hello Fiery, I see it is really poorly documented by khronus.org :angry:

    But attached is what I found out.

    I have created an Excel file with hyperlinks to the "khronus registry documentation", but sadly I cannot find all extensions (so not all hyperlinks will work).

    I'm not 100% sure with all values. It would be good if some peoples could prove this.

    Hopefully my Excel file will help you.

    Update:

    I asked at the khronos forum for help:

    http://www.khronos.org/message_boards/viewtopic.php?f=4&t=5555

    OpenGL_ES_Extensions.zip

  8. Hi,

    please add OpenGL ES to "OpenGL Compliancy".

    Now:

    OpenGL Compliancy:

    OpenGL 1.1 Yes (100%)

    OpenGL 1.2 Yes (100%)

    OpenGL 1.3 Yes (100%)

    OpenGL 1.4 Yes (100%)

    OpenGL 1.5 Yes (100%)

    OpenGL 2.0 Yes (100%)

    OpenGL 2.1 Yes (100%)

    OpenGL 3.0 Yes (100%)

    OpenGL 3.1 Yes (100%)

    OpenGL 3.2 Yes (100%)

    OpenGL 3.3 Yes (100%)

    OpenGL 4.0 Yes (100%)

    OpenGL 4.1 Yes (100%)

    OpenGL 4.2 Yes (100%)

    OpenGL 4.3 Yes (100%)

    Future:

    OpenGL Compliancy:

    OpenGL 1.1 Yes (100%)

    OpenGL 1.2 Yes (100%)

    OpenGL 1.3 Yes (100%)

    OpenGL 1.4 Yes (100%)

    OpenGL 1.5 Yes (100%)

    OpenGL 2.0 Yes (100%)

    OpenGL 2.1 Yes (100%)

    OpenGL 3.0 Yes (100%)

    OpenGL 3.1 Yes (100%)

    OpenGL 3.2 Yes (100%)

    OpenGL 3.3 Yes (100%)

    OpenGL 4.0 Yes (100%)

    OpenGL 4.1 Yes (100%)

    OpenGL 4.2 Yes (100%)

    OpenGL 4.3 Yes (100%)

    OpenGL ES 1.0 Yes (100%)

    OpenGL ES 1.1 Yes (100%)

    OpenGL ES 2.0 Yes (100%)

    OpenGL ES 3.0 Yes (100%)

    Thanks

  9. Hello Fiery,

    sorry for the late reply.

    1) Because of problems with HDMI->DVI I have switched to VGA->VGA (secondary).

    I don't know if this was the reason that Aida64 now starts always on the primary monitor or something was changed between v1.80.x and v2.20.x

    2) I use always the custom/advanced installation and "Perform a clean installation". After that I don't change a setting.

    At the moment I have v295.73 installed.

    I have tried it with a new aida64.ini too.

    But starting on the primary monitor is now better than on the secondary.

    So it is only a low priority bug for me.

  10. Display -> OpenGL is working now on both PC's.

    Thanks

    Display -> GPGPU -> Stream: RV730 is empty because of installation errors of the AMD AGP Hotfix (APP) drivers.

    The installation log show only "installation failed" but no exact error message.

    As always AMD are not able to give working drivers and the installer/uninstaller is still a shame. ;)

×
×
  • Create New...