* Memory leakage in message
"sizeof(SCANNER_MESSAGE) * threadCount * requestCount" bytes long memory is allocated but only "sizeof(SCANNER_MESSAGE) * threadCount" bytes long of it is freed.
* Handles malloc function fail case
* Refactors comment line
* Solves the miscalculation of the message index
* simbatt: Fix broken registry read-back
The GetSimBattStateFromRegistry function is currently using default settings if GetSimBattStateFromRegistry succeeds, whereas settings from registry are only applied if GetSimBattStateFromRegistry fails. This does not make sense to me.
Therefore proposing to remove the `!` negation from `if (!NT_SUCCESS(Status)) {` on the line after `Status = GetSimBattStateFromRegistry(Device, RegState);` so that default settings are loaded when registry read-back fails.
* Issue of freeing memory without waiting completion of threads accessing it is fixed
* Fixes information leakage warning
Fixes the issue of possible information leakage from uninitialized padding bytes
* Avoids possible multiplication overflow warning
* Avoids possible multiplication overflow warning
* CI Pipelines build with WDK Nuget Packages (#1179)
Integrate nuget into the workflow pipelines
* FI from main to develop (#1188)
Fix text and minor issues in Winget configuration files
Co-authored-by: Adonais Romero Gonzalez <adonais.neoadonis@gmail.com>
* Improve version info, vsix installation, and update building locally readme
* Fix printing vsix version
* Refactored vsix install and cleaned up build sampleset
---------
Co-authored-by: İsa Yurdagül <38290414+isayrdgl@users.noreply.github.com>
Co-authored-by: Fredrik Orderud <fredrik.orderud@ge.com>
Co-authored-by: Christian Allred <13487734+cgallred@users.noreply.github.com>
Co-authored-by: tristanb-ntdev <60945150+tristanb-ntdev@users.noreply.github.com>
Co-authored-by: Matt <138825652+middlemose@users.noreply.github.com>
Co-authored-by: Adonais Romero Gonzalez <adonais.neoadonis@gmail.com>
FAT Volume Label is stored in the root directory entry and therefore when
setting new Volume Label with leading 0xE5 byte it first needs to be
converted to 0x05 byte. This step is also required by Microsoft FAT
specification (fatgen103.doc) and also applied for all other files and
directories. But not for volume label yet. First byte 0xE5 in directory
entry means that entry is removed.
Similarly, when reading Volume Label from the root directory, leading byte
0x05 first needs to be converted to 0xE5 and then later processed. This is
reverse operation as described in previous paragraph.
FAT Volume Label is converted from Unicode to bytes according to OEM code
page. OEM code page is configured in Language for non-Unicode applications
settings in Country/Region settings.
When it is set to English (United Kingdom), then OEM code page is 850. And
in 850 is Unicode LATIN CAPITAL LETTER O WITH TILDE represented as 0xE5.
Therefore this pull request fixes setting FAT label "Õ" when regional
settings are set to English (United Kingdom).
Adonais Romero Gonzalez
JakobL-MSFT
Christian Allred
zlockard
Zac Lockard
Jason
Heesung Kim
Rod Widdowson
astro
olegkMS
witer33
Oleg Kagan (111592)
darwin-msft
pali
Barry Golden
Den Delimarsky
Den (Microsoft)
Quinten Johnson
garanews
Ged Murphy
Julio Garcia
Pierre Schweitzer
Christian Allred
Wei Mao