windows-driver-samples.git/filesys/fastfat, branch developUnnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/windows-driver-samples.git/atom/filesys/fastfat?h=develop2024-02-26T17:47:25ZRemove x86 and ARM configurations for sample projects. (#1126)2024-02-26T17:47:25ZAdonais Romero Gonzálezadonais.neoadonis@gmail.com2024-02-26T17:47:25Zurn:sha1:3fcc0f2bee2fbd40fe953ecbcb15b2bd8b0d3eb9
* Removed Win32 and Arm from the project configurations.
* Set default platform to x64.Add ARM64 as target platform on multiple samples (#1104)2024-02-19T22:26:14ZAdonais Romero Gonzálezadonais.neoadonis@gmail.com2024-02-19T22:26:14Zurn:sha1:cff1465ff184c6e89d43083f8430040e72d69283
* Add ARM64 as target platform on multiple samples
* Remove ARM64 from WFPSampler temporarily
---------
Co-authored-by: Jakob Lichtenberg (170957) <jakobl@microsoft.com>Update some filesys projects' DriverTargetPlatform to be 'Windows Driver' (#962)2023-04-07T01:49:00ZJasonjasonknichel@users.noreply.github.com2023-04-07T01:49:00Zurn:sha1:03dbb616869946fd74cd73efb6ff684da9f60213
Co-authored-by: Jason Knichel <jknichel@ntdev.microsoft.com>Fix typo in comment (#557)2023-02-08T22:02:54ZRod Widdowsonrdw@steadingsoftware.com2023-02-08T22:02:54Zurn:sha1:c48bf7dd5c31141b4ea5a355801b9f5a5ee36113
The code grabs the FCB SHARED, not ExReplaced ExAllocatePoolWithTag to more secure ExAllocatePoolZero in samples of filesystems and filesystem filters; made necessary changes to make solutions buildable under recent Visual Studio (#725)2022-05-18T22:26:38ZolegkMS86095074+olegkMS@users.noreply.github.com2022-05-18T22:26:38Zurn:sha1:b8d3abcd822aafc27af851f7ec6b8938b21e57b5update hash algorithm to sha2562021-06-02T03:32:14Zdarwin-msft42794227+darwin-msft@users.noreply.github.com2021-06-02T03:32:14Zurn:sha1:7f70194fa2b3bbeaee27b62bc9c3d2d5e3c34519
update hash algorithm to sha256
Fix changing and reading FAT labels with leading 0xE5 byte in fastfat.sys (#303)2019-09-24T21:12:26Zpali7141871+pali@users.noreply.github.com2019-09-24T21:12:26Zurn:sha1:16022c593787aef040b8a37ef697316e07f1322e
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).Update README.md (#417)2019-09-16T21:04:28ZBarry Goldenbagold@microsoft.com2019-09-16T21:04:28Zurn:sha1:f064dfb2d92ac3f1f4344d435e4690e4339b5025Update README.md (#404)2019-08-20T13:48:59ZBarry Goldenbagold@microsoft.com2019-08-20T13:48:59Zurn:sha1:00c331aa9912fcbbe650d42fa794130643579e46Update README.md2019-08-17T23:50:38ZBarry Goldenbagold@microsoft.com2019-08-17T23:50:38Zurn:sha1:3156a4118e1f2d51c7df451525e514e1504c7d81