SxS doesn't require links, it makes use of them to reduce the actual disk usage. The conversation was about how many people "hate" the WinSxS folder because when you look at the properties in explorer it shows a very large number of GB, but fail to realize this number is not accurate due to the large number of DLLs that are shared with System32. If we can't make use of hardlinks, we can just copy the actual files. The HDD space used will grow, but it's not like if our installation is 15gb... ;P

On 10 March 2015 at 13:41, Pierre Schweitzer <pierre@reactos.org> wrote:

I'm not sure you realize what you're praising.

Links & junctions are not supported on FAT, they require NTFS.

On 03/10/2015 12:37 PM, Huw Campbell wrote:
> SxS uses hard links, not symlinks.
> Seems like the way to go too, as we're already hitting the boundary with common controls and it's how windows does version compatibly.
> Huw
>
> -----Original Message-----
> From: "Ged Murphy" <gedmurphy.maillists@gmail.com>
> Sent: ‎10/‎03/‎2015 10:27 PM
> To: "'ReactOS Development List'" <ros-dev@reactos.org>
> Subject: Re: [ros-dev] ReactOS versioning
>
> It might also be useful to employ some form of heuristics as UAC does. Things like file name detection, string table detection, marked processes via user defined requests or a hash database, etc. Perhaps even scanning the imports (although this is harder to manage due to people using GetProcAddress to detect OS version)
>
>
> -----Original Message-----
> From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Timo Kreuzer
> Sent: 07 March 2015 12:44
> To: ReactOS Development List
> Subject: [ros-dev] ReactOS versioning
>
>
> 1. We need a method to specify which application should be run in which environment. We should probably use the same mechanism that is used on Windows. Compatibility information is stored in a registry key HKCU\Software\Microsodt\Windows NT\CurrentVersion\AppCompatFlags\... The trick is to make this easy / transparent for the user. A right-click -> properties -> compatibility approach should for now probably be the easiest thing,
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>

--
Pierre Schweitzer <pierre@reactos.org>

System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.

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