Jump to content

EPERM: Operation Not Permitted, rename


Nimarus

Recommended Posts

I'd copy and paste the entire error for the developers to look over, but Vortex doesn't allow me to highlight the text at all. When installing the latest XP32 Maximum Skeleton mod, I get a failed to install error that says failed: EPERM: Operation Not Permitted. I've seen a few other posts with the word "EPERM" and everyone recommends rolling back to the previous version of Vortex to fix the problem.

 

https://forums.nexusmods.com/index.php?/topic/5004160-xp32-maximum-skeleton-special-extended-xpmsse/?p=62450212

Link to comment
Share on other sites

Hmm, doing a few tests, ah, I see what the problem is.


Basically, xp32 FOMOD-installer tells you, if you choose the "None"-option on any of the option-screens, to use the contents of the "None"-directory. Since the "None"-directory is empty (except for "Character Creation\None"), Vortex thinks you meant to re-name the "none"-directory instead but this re-naming fails since you've already got the directory you're trying to re-name to.


Where's at least two methods to fix the problem:

Method 1, add a text-file or another file with a name you're not going to use for anything to all the "none"-directories in the xp32-mod-archive (except "Character Creation\None").


Method 2, edit "fomod\ModuleConfig.xml" in the xp32-mod-archive and for all the "none"-options, except for "Character Creation", remove the 3 lines starting with

<files>

and ending with

</files>
Link to comment
Share on other sites

that may be true, but it seems to work on NMM and MO, so it's just Vortex being a little weird about it.

unless Tannin42 can convince me that we need to convince Groovtama to make these changes for us, the Vortex users, I say Vortex needs to be fixed.

Link to comment
Share on other sites

 

Hmm, doing a few tests, ah, I see what the problem is.
Basically, xp32 FOMOD-installer tells you, if you choose the "None"-option on any of the option-screens, to use the contents of the "None"-directory. Since the "None"-directory is empty (except for "Character Creation\None"), Vortex thinks you meant to re-name the "none"-directory instead but this re-naming fails since you've already got the directory you're trying to re-name to.
Where's at least two methods to fix the problem:
Method 1, add a text-file or another file with a name you're not going to use for anything to all the "none"-directories in the xp32-mod-archive (except "Character Creation\None").
Method 2, edit "fomod\ModuleConfig.xml" in the xp32-mod-archive and for all the "none"-options, except for "Character Creation", remove the 3 lines starting with
<files>
and ending with
</files>

 

Thank you for this. Method 1 worked like a charm.

 

Obviously I had this issue, and yeah the Vortex devs should fix since it downloads with the other mod managers [if thats the case]

Link to comment
Share on other sites

 

Hmm, doing a few tests, ah, I see what the problem is.
Basically, xp32 FOMOD-installer tells you, if you choose the "None"-option on any of the option-screens, to use the contents of the "None"-directory. Since the "None"-directory is empty (except for "Character Creation\None"), Vortex thinks you meant to re-name the "none"-directory instead but this re-naming fails since you've already got the directory you're trying to re-name to.
Where's at least two methods to fix the problem:
Method 1, add a text-file or another file with a name you're not going to use for anything to all the "none"-directories in the xp32-mod-archive (except "Character Creation\None").
Method 2, edit "fomod\ModuleConfig.xml" in the xp32-mod-archive and for all the "none"-options, except for "Character Creation", remove the 3 lines starting with
<files>
and ending with
</files>

 

Just fyi, if I would do Method 2 that would break NMM xD, I could leave my .gitignore files in the future in the folders if people don't mind getting trash thrown in their data folder.

 

But XPMSSE is not the only installer that breaks, CBBE's breaks too. Can devs pls be consistent with the schema that fomod has, NMM has already some retarded quirks for fomods. I would like that Vortex would not start with adding some.

Link to comment
Share on other sites

 

But XPMSSE is not the only installer that breaks, CBBE's breaks too.

 

Just came to look for info on this - installed Vortex for the first time, tried installing CBBE - and ran into the same error. EPERM: Operation not permitted

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...