reth

n.s.

@reth

the display name is my initials

experimenting and all that.
chief executive dysfunction officer. few of my posts are high-effort, but at least they're funny.
current avatar is an old art by fireflufferz because i'm bored with having michiru pfps.
.-.-.-.-.-.

lastfm listening

log inask
last.fm
last.fm/user/clmty
reth
@reth

window the tenth: conputer operation system

so i've been using filezilla to throw some .torrents onto my seedbox, and filezilla showed me A Peculiar Folder i haven't seen before in my user folder - PrintHood.

i attempted to list it through filezilla and got "You do not have permission to list this directory". little does it know, that i am the permission. tried to look it up in explorer, and... nothing. not even with the "view hidden files" toggle.

looked it up and... what. why. the fuck?? why does it do this? why this name? what? windows are you okay.

You must log in to comment.

in reply to @reth's post:

KylieNeko
@KylieNeko

It's a Junction. Junctions are like links, except not, and they redirect to a real place, except when they don't. There's quite a few of these hidden around (Documents and Settings -> Users comes readily to mind).

This specific junction leads to your user folder for printer shortcuts.

In a normal command prompt, you can see where these things go when in the folder it resides:

dir /a

And you'll probably end up with something like <JUNCTION> PrintHood [C:\Users\ReallyCoolUserName\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]

Explorer and most views of the filesystem just suppress junctions. And some operations just fail when applied to a junction, though I forget why and what API shenanigans are going on.

Edit: And forgot to answer the why. To remap things that were previously hardcoded. There's also another quirky remap that causes any program that attempts to write data to Program Files to instead get written to a safe place in your user folder and the program is no wiser because it's overlaid. Backwards compatibility cheats.

login to reply
reth
@reth

oh my god. another backwards compatibility thing that had to be patched in with quirks. i wonder what is the number of backwards-compatibility solutions that are in w11 already. probably in the high tens, maybe hundreds.

login to reply
Pinned Tags