The BPP/Video Mode and some other parts may not show if the adaptor is not 'active' at the time of the query.
I see it is using the WMIC method and not the vbscript one , the wmic one if the ram value is not a whole amount such as 1GB, 2GB and is say 1.5GB etc then it fails, i am working on a way to work around this problem....
Hopefully found a way around the odd values above Zero such as 1.5GiB etc... This is only for the WMIC method, but if the value returned by the API is a negative number which it can sometimes then it throws the calculations out and will set as zero (N/A) to prevent a crash, plus SET /A is limited to 32 bit operations and below zero is set as zero. I now use another method which can go way up to EiB, TiB, YiB , however this routine will only use the inputted value to calculate it does not obtain the value from the OS... Also the routine will set the returned value to zero IF the inputted amount is a negative amount.
Code: Adapter 2 Description : Intel{R} Q45/Q43 Express Chipset {Microsoft Corporation - WDDM 1.1} {Ref:w} Adapter 2 Video Memory : 1.63 GB [Rounded Value] {Results above 4 GB cannot be shown correctly, see VRam notes} At least it shown the amount this time Before the old routine could not show the .63 part because SET /A only works with integers and as it had a fraction amount, it ended up being zeroed, the new routine's convert bytes program can work with fractions.
I agree at least now it will show the right amount (if below 4GB/GiB) when the older wmic routine is used and like VBScript it will show the fraction part too.
When i think a particular section is OK, a rare case kicks the door in on my coding I not like to give in, and in this scenario i managed to fix the glitch. Sadly for 4GiB+ gfx cards i have to take a break as it was taking over my life with trying things and i have to admit defeat on that for now, so the message will stay mentioning that over 4GiB wont be shown.
Why not give general values? e.g. 1 GB or greater, 2 GB or greater.. even Microsoft's WU Detectoid calculate it similary Code: b.WmiQuery Namespace="root\cimv2" WqlQuery="SELECT AdapterRAM FROM Win32_VideoController WHERE AdapterRAM >= 4293918720" b.WmiQuery Namespace="root\cimv2" WqlQuery="SELECT AdapterRAM FROM Win32_VideoController WHERE AdapterRAM >= 2147483648" b.WmiQuery Namespace="root\cimv2" WqlQuery="SELECT AdapterRAM FROM Win32_VideoController WHERE AdapterRAM >= 1073741824"
Win32_videocontroller wont detect over 4gb as it is seems 32bit only. Powershell even failed which i thought would be more 64bit capable. Seems using a program language such as C or maybe .net can access the gfx card direct as i have tried every normal way following all the ms docs. For now i will leave things as they are as i want to concentrate on other project parts as they been left behind a bit.
No, it's oobe based. You can brand many things manually though. System Brand Changer v1.2.1 is available but doesn't work properly on 10 atm.
When i get some time to work on the 'online' branding version of the project, it will work in the same way as the Branding one Alphawaves wrote, i had started a GUI version but it is on hold at moment as other things in life take precedence. Hopefully after when MRP 130 is released in October i will have the time to resume that GUI, it will be written using AutoIT, so most AV's will throw its dummy out due to the way it works but nothing nasty will be within it. It just an easier way for me to program GUI's as i tried C++ and totally got confused in its syntax. Typing on my phone during my break at work, sorry for spelling errors.