- 25 Jun, 2015 1 commit
-
-
Thomas Faller authored
-
- 24 Jun, 2015 18 commits
-
-
Michael Müller authored
-
Michael Müller authored
-
Sebastian Lackner authored
-
Piotr Caban authored
-
Hans Leidekker authored
This matches more recent versions of Windows.
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Jared Smudde authored
-
Hugh McMaster authored
-
Hugh McMaster authored
-
Hugh McMaster authored
-
Jacek Caban authored
-
Jacek Caban authored
-
André Hentschel authored
-
Sebastian Lackner authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
- 23 Jun, 2015 21 commits
-
-
Huw Davies authored
-
Nikolay Sivov authored
-
Jacek Caban authored
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-
Erich E. Hoover authored
NT-style paths that have a device prefix (\??\) also return the drive of the current working directory (even if they're valid devices).
-
Erich E. Hoover authored
Paths that are not NT and not even close to DOS don't actually fail catastrophically. Even though MSDN suggests that it returns the boot drive in this case, tests indicate that it returns the drive of the current working directory.
-
Erich E. Hoover authored
Add support for "semi-DOS" paths, these paths revert to the drive letter specified in the first character.
-
Erich E. Hoover authored
-
Erich E. Hoover authored
-
Erich E. Hoover authored
The purpose of this function is to return the most fundamental path without leaving a filesystem. Steam uses this so that it can use inode searches, without this functionality some installations/validations will fail if the Steam Library is not on the same drive as Steam itself (symlink'd to another location).
-
Iván Matellanes authored
-
Iván Matellanes authored
-
Iván Matellanes authored
-
Alistair Leslie-Hughes authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Alex Henrie authored
-
Nikolay Sivov authored
-