By the way, stored as C:\blah, or as: \Device\HardDriveVolumeX where X = 0 would be for C:\, and so on …

De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de David Quintana (gigaherz)
Envoyé : mercredi 10 décembre 2014 13:37
À : ReactOS Development List
Objet : Re: [ros-dev] [ros-diffs] [pschweitzer] 65596: [NTOSKRNL] THE oneliner.... Properly read the information from the IRP to get the reparse tag. This fixes the handling of reparse mount points in ReactOS. To make it short and ...

You mean if it changes AFTER installation? Because I recall installing Windows XP on top of another Windows XP, and getting the OS drive to be mapped to D: and everything was working fine (just on the wrong drive). The problem was I had to reformat and install with a different media in order to get it as C: (I had an upgrade disk around only), because changing the drive letter of the system drive after installation is unfeasible.

The problem is not hardcoding C:, the problem is just that ALL of those paths are stored in absolute form in the registry, without even using environment strings such as %SYSTEMROOT% to store them. But really, it's not like you can go around unexpanding environment strings, chances are it would open quite a lot of security holes.

On 10 December 2014 at 09:15, Michael Fritscher <michael@fritscher.net> wrote:

Hi,

congratulations! It's a pity that MS hardcodes the C:\ at more and more
places... Original Windows NT 4.0 can boot completely even if the
drive-letter changes, WinNT + IE throws an error message but works, on
Windows 2000 one is automatically logged out again if it changes, on
Windows XP even the login-Screen doesn't appear...

Best regards,
Michael Fritscher


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev