- Thread starter Deleted member 710237
- Start date
Enough people that my torrent client's installer comes with an option to install a workaround for the issue, at any rate.
I have that mistake sometime too. Try hide my porn games somewhere so other people not messing with it. It isn't problem if you live alone, but imagine if your parent or child borrow your computer...
You'd be surprised just how quickly a pathname fills up. For example, just putting something on the desktop with a long username and long filename eats up 35 characters alone. And that's just putting it on the desktop.
- May 19, 2020
- 7,280
- 13,925
I could only imagine the horror.
Just imagine having to explain succubus lore to your offspring and why they should stay far away from the soul stealing she-demon.
From some of the screenshots people having problems post 'round here this forum is frequented by the other kind of Windows user...
The avg user is not downloading hentai translations with long folder and file names, nor trying to pointlessly "hide" hentai content in long paths.
What's your point, dude? You asked a question and you got an answer. Yes, the average user doesn't run into the issue often, or they'd have addressed it before Windows was a decade old. That doesn't mean the issue never affects anyone and shouldn't be fixed.
Turn the question around - why should there be a 255 length limit now that we're out of the bad old days and have more than 640 kilobytes of memory?
Turn the question around - why should there be a 255 length limit now that we're out of the bad old days and have more than 640 kilobytes of memory?
Easy answer to that actually: compatibility requirements. There are programs that are years old which are still operating under those restrictions, many of which are enterprise-based (ie corporate) use where efforts to update to less limitations end up with various other issues if not outright breaking. To add, adding new layers of folder infrastructure to programs is not nearly a simple as it seems. Given these factors, updating these restrictions tends to cause a lot more damage than leaving it in place.
Many application creators have created workarounds (applications run through steam for example treat the steam root folder the same as the drive root) but until there's a major change into the OS that isn't going to absolutely break the vast majority of user's experience in the process, that restriction is going to remain.
There is a reason why we use/used Windows, DOS, Intel and AMD...compatibility. Would it be nice to have beyond 255 character length paths? Yes, does windows support it [NTFS]? Yes, however app compatibility is priority over nice to have but not mission critical features. Backwards software compatibility reduces the cost and burden of finding alternative software solutions [which may not even exist, this is a far bigger issue in enterprise then home users] as new OS's are released and it also helps reduce e-waste by not forcing hardware upgrades.
That might be a compelling argument, if they didn't already offer a fix for the issue in Windows 10. They made it opt-in out of an abundance of caution but I have yet to hear a story of it actually breaking compatibility for any but the most legacy of legacy software.
And that still doesn't answer the question of why user athanato decided to be aggro about it on this forum, a place where users are much more likely than average to need the new behavior and not the legacy limitation.
And that still doesn't answer the question of why user athanato decided to be aggro about it on this forum, a place where users are much more likely than average to need the new behavior and not the legacy limitation.
The opt-in option does not work very well and even explorer doesn't support beyond 255, I end up using 7-zip file manager to fix paths back down to below 255. If anyone feels offended by it take it up with MS to fix it but folks need to understand that we are the minority, MS won't make any changes for us. Most folks that want longer paths use Linux or BSD.
Last edited:
- Oct 2, 2021
- 187
- 201
- May 19, 2020
- 7,280
- 13,925
Congratulations on completing the game! I am currently doing a second playthrough where I do the opposite. I heard that there's a god-mode ending where you play as the goddess of vengeance if you beat the game without saving a single maiden.
- Oct 2, 2021
- 187
- 201
You got me curious. I wonder what she does. Might do this on my next playthrough. Not now though, i'm still too fresh of the game
You heard correctly, though it's not entirely God-Mode.
The Goddess of Vengance is a transformation that has flying by default and a rapid-fire attack that homes in on any enemy like the cross and has a damage output equal to the magic whip per hit. World A bosses don't last longer than a few seconds and World B bosses apart from the final one get maybe a full attack cycle before their death. She's not invincible though one of the upgrades you can get with the crowns at the start of a NG+ can fix that. As well she doesn't have access to sub weapons (as you can aim her normal attack in 8 directions) but you don't really need them. That said, I suggest saving often. I've had the game crash after a while using her. Probably a memory issue.
- May 19, 2020
- 7,280
- 13,925
This mode still sounds promising, I was playing through this game normally for a second time but I think I will use the 100 percent save to start new with a few bonuses. After that I am going to play as the goddess of vengeance and bring havoc to all the cute (and not so cute) and cuddly creatures of darkness.
On another note, how do I find the thief? Does she only appear after beating the twin harpies on the ship?
The thief is located in this circled area:
After you cross the bridge you come to a ledge you can't go up and a bunch of blocks to destroy below you. She is in the bottom left of that section.
After you cross the bridge you come to a ledge you can't go up and a bunch of blocks to destroy below you. She is in the bottom left of that section.