Haos wrote:And for me it`s compatibility that does maatter. You`d need to ask dev for details, but it`s because of hardcoded dirs, we are using this layout.
Another thing is that i cant see why you dont like it. It`s clear enough for me.
but it's not hardcoded that's the point.
other than very generally; ie, %windir%\inf, %windir%\system32, etc ...
and the reason i don't like buckshot is because it makes it harder to find. you as a end-user may not have to dig around windows very often, but me as a network administrator that frequently deals with file servers, print servers, domain controllers and exchange servers ... i hate having to dig for stuff. after a while you learn where stuff is, but if it were arranged logically it would be less of a pain.
Windows has good structure! A ton of useless crap goes in C:\Windows,
nothing useful goes in C:\Windows\System, your bootloader goes in C:\, your system stuff goes in C:\Windows\system32, your hives go in C:\Windows\System32\config, and your drivers top out at C:\Windows\System32\drivers. That is all the "directory structure" you need to boot.
Reacter wrote:Windows has good structure! A ton of useless crap goes in C:\Windows,
nothing useful goes in C:\Windows\System, your bootloader goes in C:\, your system stuff goes in C:\Windows\system32, your hives go in C:\Windows\System32\config, and your drivers top out at C:\Windows\System32\drivers. That is all the "directory structure" you need to boot.
windows HAD good structure before IE got a hold of it and before MS started dinkin' with it.
Under .\Windows (besides the hotfix $%$ directories), i have
addins
AppPatch
assembly
Config
Connection Wizard
CSC
Cursors
Debug
Downloaded Program Files
Driver Cache
ehome
Fonts
Help
ie7
ie7updates
ime
inf
Installer
java
Media
Microsoft.NET
msagent
msapps
Offline Web Pages
pchealth
PeerNet
Prefetch
Provisioning
RegisteredPackages
Registration
repair
Resources
SchCache
security
SHELLNEW
SoftwareDistribution
srchasst
Sun
system
system32
Tasks
Temp
twain_32
VirtualEar
WBEM
Web
WinSxS
... now it seems to me half of that stuff could be reorganized into a more logical and less redundant structure.
Yes i know we have to use sun's java because of the MS VM lawsuit (well, that and we need java).
I'm just saying it's messy and could stand some logical groupings. about 1/3 of those folders are IE related and that in itself is stupid. compare an NT4 box without IE to an XP box. why not just put those, i don't know, under .\program files\internet explorer?
Phalanx wrote:The x64 versions have a lot more folders than that...
yeah, i've seen xp x64 and it just gets worse.
i'm not very happy with windows and that's part of the reason--which is why i was hoping that React would address this goofy situation.
Z98 wrote:Now the question you need to ask yourself is, how much of it is to ensure backwards compatibility with 32 bit apps?
probably none of it, seeing as most of those folders are labeled with 64 somewhere in there, they're probably for 64 subsystems and apps. but obviously that's just a guess at this point.