Multi-OEM/Retail Project {MRP} - Mk3

Discussion in 'MDL Projects and Applications' started by mxman2k, Oct 15, 2016.

  1. bundyal

    bundyal MDL Junior Member

    Jun 28, 2014
    91
    90
    0
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    :g: no graphics card information...

    I know that section works, maybe something triggered the routine's error checking and ignored that part?

    If it continues to skip that i will take another look in that routine, as no AV is present such as Defender that cannot be the cause of the routine being missed...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. bundyal

    bundyal MDL Junior Member

    Jun 28, 2014
    91
    90
    0
    no graphics card information ...
    isn't that because of the vmware?
    I see this in my VMWare display adapters, VMware SVGA 3D
     
  4. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    it should of displayed the VMware 3D name or the default windows driver name...

    On all my tests win7->10 all shown some gfx data :g:

    Will see how things go, if it keeps skipping on other tests then i will pull the release and put back v107 until it can be sorted.

    Just about to go out to a staff meeting now, (with social distancing, not sure how it going to work but will have to see :D ).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Hmm it shown ok there :g: most puzzling
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Have had a look at code in the QT for the graphics routine, it seems if for some reason the Caption or graphics card's name has any illegal chars within then the routine will skip any checks if those chars cannot be removed. But the odd thing is that that part of code has been the same since v98.0 :g:

    The routine from v98.0 is still there as a backup check if the new way fails so it could be something in VMware v15 that for some weird reason trips up the checking.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Looks like vmware not like the new graphics routine very much...

    Will have a think tomorrow when i get home how to re-work the routine(s) as it also seems the old way also fails on VMWare v15 + :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  9. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  12. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  13. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  14. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  15. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    870
    1,470
    30
  16. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Progress has been made with QT 108.1 Test 6 :D

    It seems when VMware tools is installed on Vmware v15.5 that adaptorRAM is empty - no value which throws out the routines including the WMIC way!

    So have had to make a work around so it shows data...

    Code:
      ==================================================[ Graphics Information ]==================================================
    
    Adapter 1 Info             : VMware SVGA 3D [Active]
    Adapter 1 Other Data       : Resolution: 1024x768 | Bpp: 32 | Driver Date: 2019-10-18 | Driver Vers: 8.16.7.5
    Adapter 1 Other Data       : Unable to process Video Ram amount.
    WinSat Scores              : Unknown State. Graphics driver{s} may not be installed or 'WinSat Formal' not ran. 
    Something like that. Nothing i can do as it is some sort of bug? within vmware's tools... :(

    Will update later as i am off to work, spent all say on this and ran out of time *sigh*

    Check via code below in a admin cmd prompt you will see what i mean when vmware 15 tools installed... :)

    Code:
    WMIC path win32_videocontroller where "DeviceID LIKE 'VideoController1'" GET Caption, Description, DriverDate, DriverVersion, AdapterRam /value
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. bundyal

    bundyal MDL Junior Member

    Jun 28, 2014
    91
    90
    0